Description of problem: When migrating a guest across hosts, the paravirt vnc console does not get activated on the destination. The VNC feature does not appear set on the destination xend data, the VNC daemon is not started, and the vnc port is not present in xenstored Version-Release number of selected component (if applicable): xen-3.0.3-2.el5 How reproducible: Always Steps to Reproduce: 1. Find a paravirt guest running the VNC console 2. Verify the VNC console is active & working 3. Migrate the guest to an alternate host 4. Try and connect to the VNC console Actual results: No VNC server is available for the migrated guest Expected results: VNC server is available on the destination host Additional info: Very likely a similar root cause to bug 211911 (VNC missing after suspend/restore cycle).
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.
The migration codepath does indeed go through the same path as restore, so fixing the restore problem, should fix VNC for migration too.
This should now be operating correctly, as a result of the PVFB upgrade tracked by bug 218050.
A package has been built which should help the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you.
*** Bug 229016 has been marked as a duplicate of this bug. ***