Bug 491473
| Summary: | guest migration between Intel and AMD fail to start listening VM when they both use Snap5.2 | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Vivian Bian <vbian> | ||||||||||||||||||
| Component: | qemu-kvm | Assignee: | Amit Shah <amit.shah> | ||||||||||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | |||||||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||||||
| Priority: | low | ||||||||||||||||||||
| Version: | 6.0 | CC: | berrange, cpelland, llim, ovirt-maint, Rhev-m-bugs, shuang, tburke, virt-maint, xen-maint, ykaul | ||||||||||||||||||
| Target Milestone: | rc | Keywords: | Reopened | ||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||
| Hardware: | All | ||||||||||||||||||||
| OS: | Linux | ||||||||||||||||||||
| Whiteboard: | |||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||
| Last Closed: | 2010-05-05 12:44:52 UTC | Type: | --- | ||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||
| Embargoed: | |||||||||||||||||||||
| Bug Depends On: | 488489 | ||||||||||||||||||||
| Bug Blocks: | |||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||
|
Description
Vivian Bian
2009-03-21 14:01:57 UTC
(In reply to comment #0) > Description of problem: > Install snap5.2 both in Intel and AMD boxes,and then did a migration between > the two boxes.Got a libvir:QEMU error: fail to start listening VM,but between a > snap4 AMD and snap5.2 Intel migration will be ok. snap4 Intel and snap5 AMD > will still be ok. > the ok guest is an empty one without any system installed.And now I installed win2k3_x86_64(R2).But this guest could not be migrated between the two boxes (both Intel and AMD installed Snap5.2) and for the win2k8 system I could migrate it between two AMD boxes,but failed in Intel and AMD fail to start listening VM at the first time libvir: Remote error :socket closed unexpectedly at the second time Cross vendor migration is not supported. Actually it should be forbidden by libvirt. Could you please confirm if its supported on the kvm level? While cross-vendor migration is not supported, I don't believe vbian should be seeing the error messages mentioned in comments 1 or 2. vbian, can you attach the two files /var/log/libvirt/qemu/$DOMNAME.log from both the source and destination hosts. Dor, libvirt explicitly restricts its scope to providing 'mechanism', and not 'policy'. As such any restrictions on migration between different CPU types should be enforced by the management application using libvirt, not libvirt itself. (In reply to comment #5) > While cross-vendor migration is not supported, I don't believe vbian should be > seeing the error messages mentioned in comments 1 or 2. > > vbian, can you attach the two files /var/log/libvirt/qemu/$DOMNAME.log from > both the source and destination hosts. migrated win2k8 from AMD to Intel,a running guest hang in the Intel boxes.And I could see no error output. But please try the attached rhel5u3.xml to define a guest,and then try to migrate it from AMD to Intel.The error referred in comment 2 will be seen. Steps: # iscsiadm --mode discovery --type sendtargets --portal 10.66.70.7 # iscsiadm --mode node --targetname dhcp-65-108.nay.redhat.com:storage-pool --portal 10.66.70.7 --login # virsh pool-define storage-pool.xml # virsh define rhel5u3.xml # virsh start rhel5u3 # virsh migrate --live rhel5u3 qemu+tcp://10.66.70.52/system libvir: QEMU error: operation failed: failed to start listening VM # virsh migrate --live rhel5u3 qemu+tcp://10.66.70.52/system libvir: Remote error: socket closed unexpectedly libvir: Remote error: socket closed unexpectedly Created attachment 336263 [details]
rhel5u3 log
Created attachment 336264 [details]
rhel5u3 guest definition file
Created attachment 336265 [details]
after migration ,the log in the Intel box
Created attachment 336266 [details]
the win2k8 guest definition file
Created attachment 336267 [details]
AMD win2k8 guest log
Created attachment 336268 [details]
win2k8 guest log in Intel box
> migrated win2k8 from AMD to Intel,a running guest hang in the Intel boxes. > And I could see no error output. Ok, the log shows the libvirt migration option completed successfully. So the resulting hang must just be due to the incompatibility in instruction set between the AMD & Intel CPUs. > But please try the attached rhel5u3.xml to define a guest,and then try to > migrate it from AMD to Intel.The error referred in comment 2 will be seen. The log file for this VM contains /usr/bin/qemu-kvm -S -M pc -m 3906 -smp 1 [snip more args] -incoming tcp:0.0.0.0:49154 madvise: Cannot allocate memory Could not allocate physical memory So KVM on the destination was unable to allocate memory to start the VM for incoming migration. This is why libvirt gave back the error message for rhel5u3 VM. This is also not a libvirt bug - either the host is OOM, or there is some problem in KVM allocating memory. Re-assigning to KVM to verify whether the 'cannot allocate memory' problem is a real bug or not. If not, can just close this WONTFIX, since cross-vendor migration is expected to not work reliably Created attachment 336270 [details]
cpuinfo in 10.66.65.167 ,the source box
Created attachment 336271 [details]
cpuinfo in 10.66.70.52.the destination box
worth mentioned I have migrated the win2k8 guest successfully between AMD and Intel ,and it is living now . In addition, the win2k8 mentioned in this bug is just a core ,not a full installation,and after I reinstalled a full one,it could not be migrated,and the error is the same with the comment 2 *** This bug has been marked as a duplicate of bug 488489 *** Moving back to NEW, that was the status before the bug was closed as duplicate. Since amd-intel is not supported at all I'm closing the bug. Even if it works it is not supported so please don't try it. There is a cross-vendor migration bug (bug #488489), proposed for rhev-1.1. Proposing this one for rhev-1.1 too. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. On RHEL-6, the KVM userspace package is named "qemu-kvm". Moving bug to the right component. |