Hello everyone,
we switched from using qemu-img from CentOS 7.x to qemu-img-ev from the Virt SIG several months ago, to allow us to generate Hyper-V images.
My attempts to build Vagrant images are failing the automated tests since the beginning of July, apparently due to corrupt filesystems. I see XFS metadata corruption in the CentOS 7 images when using qemu-img-ev, as well as ext4 superblock corruption in the CentOS 6 images.[1]
The distro installer runs just once and the resulting disk image is converted by Image Factory to different formats, depending on the virtualization target. Since the VirtualBox images are working as expected, while the libvirt images don't even boot due to filesystem corruption, I would assume that the installation produces a valid image, but the conversion of the disk images for libvirt-kvm fall prey to bugs in qemu-img-ev and the stock qemu-img. If anyone has the possibility to test with VmWare or Hyper-V, please write me off-list.
I noticed that qemu-img-ev is at version 2.1.2, while Debian Stable has version 2.8 and Fedora 28 has version 2.11. Maybe such bugs, if real, were already fixed upstream - would it be possible to use a newer version than what qemu-img-ev provides? We reverted to using the EL7 qemu-img, but this still produces broken libvirt images and wețd have to drop the Hyper-V images as well.
Any help or suggestions are appreciated.
Best regards, Laurențiu
[1] https://people.centos.org/bstinson/vagrant/c6-vagrant.png
After generating new images including open-vm-tools, Michael Vermaes gracefully helped us by testing them with VMware Fusion. The VMware images don't boot, complaining about XFS corruption:
XFS (dm-0): Mounting V5 Filesystem XFS (dm-0): totally zeroed log XFS (dm-0): Corruption warning: Metadata has LSN (3:6277) ahead of current LSN (1:0). Please unmount and run xfs_repair (>= v4.3) to resolve.
The VirtualBox image boots without issues, but with XFS corruption affecting both the VMware and the libvirt images, I'm not so sure anymore that qemu-img is the reason.
On 27/07/18 21:03, Laurentiu Pancescu wrote:
My attempts to build Vagrant images are failing the automated tests since the beginning of July, apparently due to corrupt filesystems. I see XFS metadata corruption in the CentOS 7 images when using qemu-img-ev, as well as ext4 superblock corruption in the CentOS 6 images.[1]
The distro installer runs just once and the resulting disk image is converted by Image Factory to different formats, depending on the virtualization target. Since the VirtualBox images are working as expected, while the libvirt images don't even boot due to filesystem corruption, I would assume that the installation produces a valid image, but the conversion of the disk images for libvirt-kvm fall prey to bugs in qemu-img-ev and the stock qemu-img. If anyone has the possibility to test with VmWare or Hyper-V, please write me off-list.
I noticed that qemu-img-ev is at version 2.1.2, while Debian Stable has version 2.8 and Fedora 28 has version 2.11. Maybe such bugs, if real, were already fixed upstream - would it be possible to use a newer version than what qemu-img-ev provides? We reverted to using the EL7 qemu-img, but this still produces broken libvirt images and wețd have to drop the Hyper-V images as well.
Any help or suggestions are appreciated.
Best regards, Laurențiu
[1] https://people.centos.org/bstinson/vagrant/c6-vagrant.png _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 08/31/2018 03:34 PM, Laurentiu Pancescu wrote:
After generating new images including open-vm-tools, Michael Vermaes gracefully helped us by testing them with VMware Fusion. The VMware images don't boot, complaining about XFS corruption:
XFS (dm-0): Mounting V5 Filesystem XFS (dm-0): totally zeroed log XFS (dm-0): Corruption warning: Metadata has LSN (3:6277) ahead of current LSN (1:0). Please unmount and run xfs_repair (>= v4.3) to resolve.
The VirtualBox image boots without issues, but with XFS corruption affecting both the VMware and the libvirt images, I'm not so sure anymore that qemu-img is the reason.
On 27/07/18 21:03, Laurentiu Pancescu wrote:
My attempts to build Vagrant images are failing the automated tests since the beginning of July, apparently due to corrupt filesystems. I see XFS metadata corruption in the CentOS 7 images when using qemu-img-ev, as well as ext4 superblock corruption in the CentOS 6 images.[1]
The distro installer runs just once and the resulting disk image is converted by Image Factory to different formats, depending on the virtualization target. Since the VirtualBox images are working as expected, while the libvirt images don't even boot due to filesystem corruption, I would assume that the installation produces a valid image, but the conversion of the disk images for libvirt-kvm fall prey to bugs in qemu-img-ev and the stock qemu-img. If anyone has the possibility to test with VmWare or Hyper-V, please write me off-list.
I noticed that qemu-img-ev is at version 2.1.2, while Debian Stable has version 2.8 and Fedora 28 has version 2.11. Maybe such bugs, if real, were already fixed upstream - would it be possible to use a newer version than what qemu-img-ev provides? We reverted to using the EL7 qemu-img, but this still produces broken libvirt images and wețd have to drop the Hyper-V images as well.
Any help or suggestions are appreciated.
Best regards, Laurențiu
I see new vagrant images here:
http://cbs.centos.org/koji/taskinfo?taskID=565931
http://cbs.centos.org/koji/taskinfo?taskID=565933
Are those ready for release?
Thanks, Johnny Hughes
On 02/10/18 17:05, Johnny Hughes wrote:
I see new vagrant images here:
http://cbs.centos.org/koji/taskinfo?taskID=565931
http://cbs.centos.org/koji/taskinfo?taskID=565933
Are those ready for release?
Yes, we switched from XFS to ext4 to get working images - still no idea why we get XFS corruption (I can also reproduce it with Packer, without Image Factory). Could you please copy and sign them?
Thanks, Laurențiu
On 10/02/2018 10:31 AM, Laurentiu Pancescu wrote:
On 02/10/18 17:05, Johnny Hughes wrote:
I see new vagrant images here:
http://cbs.centos.org/koji/taskinfo?taskID=565931
http://cbs.centos.org/koji/taskinfo?taskID=565933
Are those ready for release?
Yes, we switched from XFS to ext4 to get working images - still no idea why we get XFS corruption (I can also reproduce it with Packer, without Image Factory). Could you please copy and sign them?
Doing now.
Thanks, Johnny Hughes
-
Johnny Hughes -
Laurentiu Pancescu