maverick kvm guests not seeing virtio disks

Bug #624915 reported by Dustin Kirkland 
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
debian-installer (Ubuntu)
Fix Released
High
Colin Watson
Maverick
Fix Released
High
Colin Watson
linux (Ubuntu)
Invalid
High
Unassigned
Maverick
Invalid
High
Unassigned

Bug Description

Just launched the Maverick Server amd64 Daily ISO today in a KVM (on an amd64 maverick host), with virtio disks.

The server installer complained about not seeing any disks.

Dropping to the shell, I confirmed that /dev/vda was not there, as I expected that it should have been.

Checking lsmod, I see the virtio modules loaded.

I don't have much more information for now, but it's easy to reproduce, and this is a beta blocker, I think.

Revision history for this message
Dustin Kirkland  (kirkland) wrote :

Filed against both kernel and debian-installer. I'm not quite sure where the bug is, but hopefully the people watching those two packages will be able to triage it appropriately.

Changed in debian-installer (Ubuntu Maverick):
milestone: none → ubuntu-10.10-beta
importance: Undecided → High
Changed in linux (Ubuntu Maverick):
importance: Undecided → High
milestone: none → ubuntu-10.10-beta
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

My vm was launched through testdrive with the following command line:

kvm -m 1024 -smp 2 -cdrom /home/kirkland/.cache/testdrive/iso/ubuntu_maverick-server-amd64.iso -drive file=/home/kirkland/.cache/testdrive/img/testdrive-disk-qKihPq.img,if=virtio,cache=writeback,index=0,boot=on -usb -usbdevice tablet -net nic,model=virtio -net user -soundhw es1370 -vga cirrus

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

Confirmed, I get the same behavior with

kvm -cdrom ubuntu_maverick-server-amd64.iso -boot d -drive /srv/serge/vms/lucid-delme.img,if=virtio,index=0 -m 512M

Changed in debian-installer (Ubuntu Maverick):
status: New → Confirmed
Changed in linux (Ubuntu Maverick):
status: New → Confirmed
Revision history for this message
Colin Watson (cjwatson) wrote :

This happened because somebody inappropriately removed (at least some of) the -17 kernel udebs while d-i was still built against them. The latter was because I had the temerity to be on holiday for a day. Shame on me.

I've uploaded d-i built against -19, and this should sort it out.

Changed in linux (Ubuntu Maverick):
status: Confirmed → Invalid
Changed in debian-installer (Ubuntu Maverick):
assignee: nobody → Colin Watson (cjwatson)
status: Confirmed → Fix Released
Changed in linux (Ubuntu Maverick):
milestone: ubuntu-10.10-beta → none
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.