kvm-85 won't boot guests with virtio block device
Hello!
After an upgrade from kvm-84 to kvm-85 all my guests won't start because no boot device could be found. The kvm host is an 2xDual-Opteron 2212 with 8 GB RAM installed on debian lenny 2.6.26-2-amd64. All the guests are debian etch 2.6.26-1-amd64 or debian lenny 2.6.26-2-amd64 with 1 CPU and 1 GB mem.
A rollback to kvm-84 OR changing the hdd from vda to ide for the guests and everything is OK again (grub entrys have to be changed also from vda1 to hda1).
It seems that kvm-85 has a Problem detecting guest configured to use virtio block device.
I would like to habe virtio block device support because the performance of the guest is much better with it.
Can You help?
Greetings
Darius
Hi Darius,
Quoted 2 lines
After an upgrade from kvm-84 to kvm-85 all my guests won't start because no boot device could be found.
[...]
Quoted 2 lines
A rollback to kvm-84 OR changing the hdd from vda to ide for the guests and everything is OK again
I'm having the same problem and repored it to the list just some hours ago.
Do you use the kvm kernel modules that came with your host kernel or the ones that came with kvm-85? I used the ones that came with my 2.6.29.1 host kernel.
Kind regards,
Gerd
Quoted 7 lines
Quoted 2 lines
After an upgrade from kvm-84 to kvm-85 all my guests won't start because no boot device could be found.
[...]
Quoted 2 lines
A rollback to kvm-84 OR changing the hdd from vda to ide for the guests and everything is OK again
I'm having the same problem and repored it to the list just some hours ago.
No problem here, my guests run fine with kvm-85 and 2.6.29.1:
-drive file="$IMG",format=raw,cache=none
Quoted 1 line
Do you use the kvm kernel modules that came with your host kernel or the ones that came with kvm-85? I used the ones that came with my 2.6.29.1 host kernel.
I use the modules from kvm-85.
Bernhard
Quoted 5 lines · Bernhard Held
Quoted 5 lines
Quoted 2 lines
After an upgrade from kvm-84 to kvm-85 all my guests won't start because no boot device could be found.
[...]
Quoted 1 line
Quoted 8 lines
Quoted 5 lines
Quoted 2 lines
A rollback to kvm-84 OR changing the hdd from vda to ide for the guests and everything is OK again
I'm having the same problem and repored it to the list just some hours ago.
No problem here, my guests run fine with kvm-85 and 2.6.29.1:
-drive file="$IMG",format=raw,cache=none
That's a bit strange - because other guests - such as RHEL-5.3 guests work fine on RHEL-5.3 hosts with virtio block device.
So KVM-85 works here.
Signature · 1 line
-Alexey Eromenko "Technologov"
Hi Bernhard,
Quoted 5 lines
Quoted 2 lines
Quoted 2 lines
After an upgrade from kvm-84 to kvm-85 all my guests won't start because no boot device could be found.
No problem here, my guests run fine with kvm-85 and 2.6.29.1:
-drive file="$IMG",format=raw,cache=none
Are you sure you are using a virtio blockdevice and not a regular ide one? IIRC, you need to add if=virtio to the -drive parameter to get virtio. Or became virtio the default these days?
Kind regards,
Gerd
Quoted 6 lines
Quoted 4 lines
Quoted 2 lines
Quoted 2 lines
After an upgrade from kvm-84 to kvm-85 all my guests won't start because no boot device could be found.
No problem here, my guests run fine with kvm-85 and 2.6.29.1:
-drive file="$IMG",format=raw,cache=noneAre you sure you are using a virtio blockdevice and not a regular ide one? IIRC, you need to add if=virtio to the -drive parameter to get virtio. Or became virtio the default these days?
Oh, sorry, I picked the wrong one :-(
This is the right example:
-drive file="$IMAGE1",if=virtio,format=raw,cache=none,boot=on
I'm running 32 bit guest on 32 bit host and 32 bit guest on 64 bit host. Both "big floppies" and images with partition tables work.
Sorry for the noise,
Bernhard
Hi Bernhard,
Quoted 8 lines
Quoted 5 lines
Quoted 5 lines
Quoted 2 lines
Quoted 2 lines
After an upgrade from kvm-84 to kvm-85 all my guests won't start because no boot device could be found.
No problem here, my guests run fine with kvm-85 and 2.6.29.1:
-drive file="$IMG",format=raw,cache=noneThis is the right example:
-drive file="$IMAGE1",if=virtio,format=raw,cache=none,boot=on
Hmm, ok. Now we've got to find out whats different between yours and Alexeys systems where it works and mine and Darius' where it doesnt.
Quoted 2 lines
I'm running 32 bit guest on 32 bit host and 32 bit guest on 64 bit host. Both "big floppies" and images with partition tables work.
I tried 32 bit and 64 bit guest on a 64 bit host.
So bitness doesn't seem to be the issue. The kvm-modules seem not to be the issue too because Darius wrote he's using the modules from kvm-85 (seems he forgot to cc the list).
Any other ideas?
Kind regards,
Gerd