Red Hat Bugzilla – Bug 618569
RHEL6 PV guest hangs there after migration failed
Last modified: 2012-04-18 03:55:40 EDT
Created attachment 434642 [details]
Description of problem:
In the RHEL5.5 i386 platform,we cannot use vnc tool to view the RHEL6 beta2 snapshot8 i386 pv guest after migration failed.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Change xend configration to enable migration and setup NFS storage for migration.
2.Copy PV domain images to shared NFS storage server.
3.Mount the NFS image directory on host-A.
4.Create the VM guest on source host-A:
[host]#xm create $vm.cfg
5.In host-A, you can connect to guest via vncviewer successfully
6.Don't mount the NFS image directory on host-B
7.Execute command migrate from host-A to host-B.
[host]#xm migrate $domid $ip_host-B
8.In host-A, connect to guest via vncviewer.
1.After step 8, after migration failed, guest doesn't keep its previous state and we cannot connect to guest via vnc.
1.After step 8, when migration failed, guest should keep its previous state and we can also connect to guest via vnc.
Please see attachment:
configure file of pv
Created attachment 434643 [details]
configure file of pv
In addition, we have tried to reproduce this bug with RHEL-5.4 PV guest. As a result, this bug didn't occur with RHEL-5.4 PV guest. So until now, this bug only applies to RHEL6-beta2-snapshot8 PV guest.
What's more, we have deleted "vfb" in the configure file in RHEL6-beta2-snapshot8 PV guest (# vfb = ['type=vnc,vncunused=1,keymap=en-us,vnclisten=0.0.0.0' ]) to reproduce this bug.Under this situation, the PV guest would be in s(shutdown) state.
While with "vfb" in the configure file, the PV guest would hang there in r(running) state.
This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release.
** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **
In x86-64 host, after x86-64 guest migration failed, a zombie guest occurs and the guest will restart.
[host]# xm li
Name ID Mem(MiB) VCPUs State Time(s)
Domain-0 0 6854 4 r----- 587.6
Zombie-xen-pv-guest 5 1024 1 --p-cd 24.2
xen-pv-guest 6 1024 2 -b---- 32.8
Created attachment 449684 [details]
Version-Release number of selected component:
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
This request was erroneously denied for the current release of Red Hat
Enterprise Linux. The error has been fixed and this request has been
re-proposed for the current release.
This request was erroneously denied for the current release of
Red Hat Enterprise Linux. The error has been fixed and this
request has been re-proposed for the current release.
*** Bug 615187 has been marked as a duplicate of this bug. ***
Even with suspend cancellation, the following patches may be needed:
c7853ae (xen: xenbus PM events support)
b3e96c0 (xen: use freeze/restore/thaw PM events for suspend/resume/chkpt)
I'll go ahead and dev-ack this, but I think it'll come down to just doing some tests and seeing if there's any surprises, i.e. if something breaks that wouldn't have been solved with suspend-cancellation. Assuming we don't find anything, then this bug will get closed as CANTFIX.
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update release.
Since this is TestOnly I'm switching it to MODIFIED in order to get it onto QA.
In the end, I think we'll just WONTFIX this bug. We don't have suspend-cancellation anyway, and disk space is now checked in the tools, so I think we're pretty safe to just ignore any other possible cases at this stage.