virt-manager / kvm: after installing any operating system it won't boot

[Aleksi Nurmi]

Binary package hint: virt-manager

I've tried to install Debian Etch, FreeBSD, Arch Linux, ReactOS and Windows Server 2003 using virt-manager and kvm in Hardy. All of them seemed to install fine, but none of them was able to boot from the hard disk after the mandatory reboot. Debian kept waiting for the root to mount, ReactOS said "freeldr.sys not found" etc. etc. I used the default configuration for everything.

It would seem that virt-manager or the middleware it uses mess up the order of hard drives: I was able to boot Debian after replacing root=/dev/hdb with root=dev/hda in GRUB. Maybe this has something to do with the automatic changing of boot options after reboot (virt-manager doesn't boot from the cd-rom after reboot)?

I'm not 100 % sure if this is a virt-manager problem, but at least I'm able to install the operating systems fine using the command line:
kvm -hda foo.img -cdrom disk.iso -boot X (where X is c or d)
So it's not directly kvm-related either.

I have an AMD64 processor capable of full virtualization and the AMD64 version of Hardy.

[Dustin Kirkland  (kirkland)]

Hi, thanks for the bug report.

I notice that all of your attempts were to install non-Ubuntu OS's (Debian Etch, FreeBSD, Arch Linux, ReactOS and Windows Server 2003).

Obviously those should work too, but could you try to install an Ubuntu OS, such as Hardy or Intrepid?

I'm thinking this might be a duplicate of bug #220463.

:-Dustin

[mugginz (mugginz1)]

I have found that you can get it to boot if you have two virtual hard drives.

With only one I couldn't get anything to boot after installation succeeded as well.

[Victor Vargas (kamus)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!