Boot problems with qemu-kvm

Hi,

I've tried booting two VMs (Ubuntu and Fedora 11) that previously worked with the latest kvm-userspace. At start, I get the following warning:

Could not open '/dev/kqemu' - QEMU acceleration layer not activated: No such file or directory

But, booting proceeds quickly which seems to indicate that KVM is being used. However, the network device is not started and the graphics don't start properly. CPU usage also spikes to 100% and stays there and I can't interact at all with the VM. I'm running the 2.6.29 KVM kernel in the guests.

Cam

Quoted 10 lines · Cam Macdonell

Hi,

I've tried booting two VMs (Ubuntu and Fedora 11) that previously worked with the latest kvm-userspace. At start, I get the following warning:

Could not open '/dev/kqemu' - QEMU acceleration layer not activated:
No such file or directory

Quoted 7 lines

But, booting proceeds quickly which seems to indicate that KVM is being used. However, the network device is not started and the graphics don't start properly. CPU usage also spikes to 100% and stays there and I can't interact at all with the VM. I'm running the 2.6.29 KVM kernel in the guests.

Cam

As a simpler test, I tried booting the fedora 10 installer. Similar to
my existing VMs, it boots, but when it tries to launch the display, it hangs and 100% cpu usage occurs. I tried with the std, vmware and cirrus vga adapters and the same thing happened each time. Although with cirrus the CPU usage isn't as high, but it still hangs.

Cam

Quoted 24 lines · On Tuesday, April 28, 2009 7:11 AM [email protected] wrote:

Quoted 9 lines · Cam Macdonell

Hi,

I've tried booting two VMs (Ubuntu and Fedora 11) that previously worked with the latest kvm-userspace. At start, I get the following warning:

Could not open '/dev/kqemu' - QEMU acceleration layer not activated:
No such file or directory

Quoted 7 lines

But, booting proceeds quickly which seems to indicate that KVM is being used. However, the network device is not started and the graphics don't start properly. CPU usage also spikes to 100% and stays there and I can't interact at all with the VM. I'm running the 2.6.29 KVM kernel in the guests.

Cam

As a simpler test, I tried booting the fedora 10 installer. Similar to
my existing VMs, it boots, but when it tries to launch the display, it hangs and 100% cpu usage occurs. I tried with the std, vmware and cirrus vga adapters and the same thing happened each time. Although with cirrus the CPU usage isn't as high, but it still hangs.

Quoted 1 line

Cam

I also met the same problem with 2.6.30-rc3. Guest can not get IP and qemu process cpu utilization is always ~100%.

Quoted 24 lines · On Tuesday, April 28, 2009 7:11 AM [email protected] wrote:

Quoted 9 lines · Cam Macdonell

Hi,

I've tried booting two VMs (Ubuntu and Fedora 11) that previously worked with the latest kvm-userspace. At start, I get the following warning:

Could not open '/dev/kqemu' - QEMU acceleration layer not activated:
No such file or directory

Quoted 7 lines

But, booting proceeds quickly which seems to indicate that KVM is being used. However, the network device is not started and the graphics don't start properly. CPU usage also spikes to 100% and stays there and I can't interact at all with the VM. I'm running the 2.6.29 KVM kernel in the guests.

Cam

As a simpler test, I tried booting the fedora 10 installer. Similar to
my existing VMs, it boots, but when it tries to launch the display, it hangs and 100% cpu usage occurs. I tried with the std, vmware and cirrus vga adapters and the same thing happened each time. Although with cirrus the CPU usage isn't as high, but it still hangs.

Quoted 1 line

Cam

I also met the same problem with 2.6.30-rc3. Guest can not get IP and qemu process cpu utilization is always ~100%.

Quoted 1 line

I also met the same problem with 2.6.30-rc3. Guest can not

get IP and qemu process cpu utilization is always ~100%.

Quoted 1 line

Well, I don't get the X display problem with -no-kvm. It's only X that's the problem, terminal output and curses work.

As far as networking goes, I've had success getting the network up with
VDE on one machine, but not with bridged networking. Even running with
-no-kvm doesn't help. But, I have no problems with the lastest Qemu. So there's something in qemu-kvm that is causing the network problems that even -no-kvm doesn't fix.

Yes. If booting guest with -no-kvm, X display can work well. And I am using bridge network, so still can not get network up. :( And qemu cpu utilization is still ~100%.