[SOLVED] Re: libvirt/kvm virtual hosts unbootable after upgrading hypervisor to wheezy from squeeze

Thanks Zenaan. Had a lucky break: I changed the virtual disks from SCSI to SATA using virt-manager and suddenly they were bootable again. On Wed, May 15, 2013 at 9:00 PM, Zenaan Harkness wrote: > I can only give wild suggests: read errata; use (low-level) tools to > check disk availability; tr

Re: libvirt/kvm virtual hosts unbootable after upgrading hypervisor to wheezy from squeeze

I can only give wild suggests: read errata; use (low-level) tools to check disk availability; try running your vm on a test box - you did test a migration before deploying the upgrade, hint hint :) Good luck Zenaan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject

Re: libvirt/kvm virtual hosts unbootable after upgrading hypervisor to wheezy from squeeze

Belatedly realizing the VM configuration would probably be helpful in diagnosing: vm01 0026ba80-bdd4-ffb0-e120-3cc331bfaebb 1310720 1310720 2 hvm destroy restart restart /usr/bin/kvm

libvirt/kvm virtual hosts unbootable after upgrading hypervisor to wheezy from squeeze

Hi all, I have hardly had to touch libvirt/kvm since I set it up for a server several years ago, but need to learn fast after a wheezy upgrade has made them unbootable. I can connect to the virtual hosts through virt-manager and see that the virtual firmware is unable to find any bootable media.