Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cause:
When creating a new libvirt guest, virt-v2v would not disable caching for disks as is recommended.
Consequence:
Guests created by a virt-v2v used caching for their disks, unless explicitly disabled by the user after conversion.
Fix:
virt-v2v now explicitly disables caching for all disks when creating a new libvirt guest.
Result:
Guests create by virt-v2v now have caching disabled for all disks. The user can enable it again if required after conversion.
Description of problem:
When converting a XML guest configuration from XEN to KVM, the driver tag in the disc section lacks the "cache='none'" attribute. This leads to an error when trying to live migrate the guest on KVM.
Version-Release number of selected component (if applicable):
current virt-v2v on 6.3
How reproducible:
Convert a XEN domain to a KVM guest
Actual results:
# virsh migrate --live guest01 qemu+ssh://host02/system
error: Unsafe migration: Migration may lead to data corruption if disks use cache != none
Expected results:
live migration should work without error
Additional info:
Adding the attribute prevents the error from occurring, change the disk section in the xml like shown:
remove:
<driver name='qemu' type='raw'/>
add:
<driver name='qemu' type='raw' cache='none'/>
I can reproduce this issue with virt-v2v-0.8.7-6.el6.x86_64.
virt-v2v convert all guests,whatever from xen or kvm,to kvm,the disk drive doesn't have cache='none'.
<disk type='file' device='disk'>
<driver name='qemu' type='raw'/>
<source file='/var/lib/libvirt/images/rhel6u1-64b-hv.img'/>
<target dev='vda' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
</disk>
When do migration,it will fail.
# virsh migrate --live xen-hvm-rhel6.2-x86_64 qemu+ssh://10.66.7.56/system xen-hvm-rhel6.2-x86_64
error: Unsafe migration: Migration may lead to data corruption if disks use cache != none
isk>
>
> For xen guest,before conversion,the guest disk driver didn't have
> cache='none',I think it's reasonable that v2v doesn't add cache='none' to
> it.Added --safe when migrate the guest use virsh.
Typo,it should be add --unsafe parameter,not --safe.
#virsh help migrate
--unsafe force migration even if it may be unsafe
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-0477.html
Description of problem: When converting a XML guest configuration from XEN to KVM, the driver tag in the disc section lacks the "cache='none'" attribute. This leads to an error when trying to live migrate the guest on KVM. Version-Release number of selected component (if applicable): current virt-v2v on 6.3 How reproducible: Convert a XEN domain to a KVM guest Actual results: # virsh migrate --live guest01 qemu+ssh://host02/system error: Unsafe migration: Migration may lead to data corruption if disks use cache != none Expected results: live migration should work without error Additional info: Adding the attribute prevents the error from occurring, change the disk section in the xml like shown: remove: <driver name='qemu' type='raw'/> add: <driver name='qemu' type='raw' cache='none'/>