KVM behaves weird on AMD64

Hello all,

I have recently compiled kvm-36 in my Ubuntu Desktop 7.04 64 bits running 2.6.22. I can load the AMD module without problems. The issue started when I tried to install OpenBSD 4.1 on a Virtual Machine and It could not manage to write the MBR on disk. That should not happen. I also tried to install an Ubuntu desktop and server machines 32 bits and both of them got stuck on installation when configuring fdutils, I have no idea why this happens.

Eventually I get to install a Debian netinstall with the most basic configuration and it worked. These are the tests I have made. By the way I checked that the Ubuntu machines did write in my 4G feisty.img file.

Is anyone having problems with AMD64 and 2.6.22 kernels? Has anyone a hint about what could I do to get these machines running?

Quoted 15 lines · Miguel Araujo

Hello all,

I have recently compiled kvm-36 in my Ubuntu Desktop 7.04 64 bits running 2.6.22. I can load the AMD module without problems. The issue started when I tried to install OpenBSD 4.1 on a Virtual Machine and It could not manage to write the MBR on disk. That should not happen. I also tried to install an Ubuntu desktop and server machines 32 bits and both of them got stuck on installation when configuring fdutils, I have no idea why this happens.

Eventually I get to install a Debian netinstall with the most basic configuration and it worked. These are the tests I have made. By the way I checked that the Ubuntu machines did write in my 4G feisty.img file.

Quoted 4 lines

Is anyone having problems with AMD64 and 2.6.22 kernels? Has anyone a hint about what could I do to get these machines running?

What was the last kvm version where this worked correctly?

Quoted 21 lines · Avi Kivity

Quoted 19 lines · Miguel Araujo

Hello all,

I have recently compiled kvm-36 in my Ubuntu Desktop 7.04 64 bits running 2.6.22. I can load the AMD module without problems. The issue started when I tried to install OpenBSD 4.1 on a Virtual Machine and It could not manage to write the MBR on disk. That should not happen. I also tried to install an Ubuntu desktop and server machines 32 bits and both of them got stuck on installation when configuring fdutils, I have no idea why this happens.

Eventually I get to install a Debian netinstall with the most basic configuration and it worked. These are the tests I have made. By the way I checked that the Ubuntu machines did write in my 4G feisty.img file.

Is anyone having problems with AMD64 and 2.6.22 kernels? Has anyone a hint about what could I do to get these machines running?

Quoted 2 lines

What was the last kvm version where this worked correctly?

I'm using two machines for testing KVM. In machine "A" KVM worked good. This is a Feisty 7.04 32 bits with 2.6.20-16 Ubuntu standard kernel with kvm installed apt way.

The machine "B" is the one I have mentioned before and It's using a 2.6.22 manually compiled kernel. It has been able to install only Debian netinstall. I would like to know if there is some kind of issue with kvm and this kernel or with AMD64.

Quoted 14 lines · Miguel Araujo

Quoted 12 lines · Avi Kivity

Quoted 10 lines · Miguel Araujo

Hello all,

I have recently compiled kvm-36 in my Ubuntu Desktop 7.04 64 bits running 2.6.22. I can load the AMD module without problems. The issue started when I tried to install OpenBSD 4.1 on a Virtual Machine and It could not manage to write the MBR on disk. That should not happen. I also tried to install an Ubuntu desktop and server machines 32 bits and both of them got stuck on installation when configuring fdutils, I have no idea why this happens.

Eventually I get to install a Debian netinstall with the most basic configuration and it worked. These are the tests I have made. By the way I checked that the Ubuntu machines did write in my 4G feisty.img file.

Is anyone having problems with AMD64 and 2.6.22 kernels? Has anyone a hint about what could I do to get these machines running?

Quoted 5 lines

Quoted 3 lines

What was the last kvm version where this worked correctly?

I'm using two machines for testing KVM. In machine "A" KVM worked good. This is a Feisty 7.04 32 bits with 2.6.20-16 Ubuntu standard kernel with kvm installed apt way.

Is this an Intel or an AMD machine?

Quoted 4 lines

The machine "B" is the one I have mentioned before and It's using a 2.6.22 manually compiled kernel. It has been able to install only Debian netinstall. I would like to know if there is some kind of issue with kvm and this kernel or with AMD64.

It doesn't seem to be related to the machine being AMD. If you can provide an example where just one thing being different causes something to stop working, that would help us isolate the problem. Examples can be the host kernel, host cpu type, or kvm version.

The issue started when I tried to install OpenBSD 4.1 on a Virtual Machine and It could not manage to write the MBR on disk. That should not happen.

Miguel Araujo <[email protected]> writes:

[snip]

Quoted 4 lines

The issue started when I tried to install OpenBSD 4.1 on a Virtual Machine and It could not manage to write the MBR on disk. That should not happen.

I have a probably similar problem with OpenBSD 4.1 and kvm-37 and kvm-39 (didn't have time to test any further versions). Kernel is 2.6.22-gentoo-r5 and processor is Intel Core2 Quad. I use the modules from the unpatched (Gentoo) kernel.

I installed OpenBSD with vanilla qemu and it works perfectly but as soon as I use kvm the OpenBSD kernel panics on boot with

root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
panic: root filesystem has size 0

and then enters the debugger. With -no-kvm it works as flawlessly as in vanilla qemu.

I don't have much time at the moment but I'll try to find a working kvm version. If you need further information I'll see if I can provide it as I'd really like to see OpenBSD working with kvm.

Quoted 15 lines · Tobias Brink

I have a probably similar problem with OpenBSD 4.1 and kvm-37 and kvm-39 (didn't have time to test any further versions). Kernel is 2.6.22-gentoo-r5 and processor is Intel Core2 Quad. I use the modules from the unpatched (Gentoo) kernel.

I installed OpenBSD with vanilla qemu and it works perfectly but as soon as I use kvm the OpenBSD kernel panics on boot with

root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
panic: root filesystem has size 0

and then enters the debugger. With -no-kvm it works as flawlessly as in vanilla qemu.

Quoted 4 lines

I don't have much time at the moment but I'll try to find a working kvm version. If you need further information I'll see if I can provide it as I'd really like to see OpenBSD working with kvm.

I think this is fixed in the latest release.

Quoted 17 lines · Avi Kivity

Quoted 15 lines · Tobias Brink

I have a probably similar problem with OpenBSD 4.1 and kvm-37 and kvm-39 (didn't have time to test any further versions). Kernel is 2.6.22-gentoo-r5 and processor is Intel Core2 Quad. I use the modules from the unpatched (Gentoo) kernel.

I installed OpenBSD with vanilla qemu and it works perfectly but as soon as I use kvm the OpenBSD kernel panics on boot with

root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302
panic: root filesystem has size 0

and then enters the debugger. With -no-kvm it works as flawlessly as in vanilla qemu.

Quoted 7 lines

Quoted 5 lines

I don't have much time at the moment but I'll try to find a working kvm version. If you need further information I'll see if I can provide it as I'd really like to see OpenBSD working with kvm.

I think this is fixed in the latest release.

It is. Thank you very much. I'm now running OpenBSD 4.1 on kvm-43 without issues.

Greetings,
Tobias

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
kvm-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/kvm-devel