Comment 1 for bug 362013
Revision history for this message
| Brent Nelson (brent-phys-deactivatedaccount) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I just tried with the Hardy PPA KVM:84. It doesn't have this migration issue, and migration claims to go to completion, however:
1) The first time I tried migrating, after migration completed, the guest VM, also running Hardy, had done a fresh boot.
2) I tried migrating again, this time with a vncviewer attached to the destination. The vncviewer went away on migration completion, but when I started the vncviewer again, the guest VM, now on the destination, had panicked. See screenshot, attached, for what I was able to see of the kernel panic.
PS A minor nuisance with KVM:84, as packaged: if you don't specify script= in your -net options, kvm looks for /etc/kvm-ifup, which does not exist, rather than /etc/kvm/kvm-ifup.