Intrepid fails to install onto virtio block device
Bug #279754 reported by
Niklas Hagman
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kvm (Ubuntu) |
Fix Released
|
High
|
Dustin Kirkland |
Bug Description
Binary package hint: kvm
Installing intrepid beta1 onto a virtio enabled block device, and it fails under the stage "Installing Base System".
/dev/vda (virtio) + intrepid = not working
/dev/hda (normal) + intrepid = working
Have tried raw disk (lv, lvm) and image disk (qcow2).
Using ubuntu 8.10 beta1
kvm-75 compiled from source
Changed in kvm: | |
status: | New → Confirmed |
Changed in kvm: | |
assignee: | nobody → kirkland |
importance: | Undecided → Medium |
milestone: | none → ubuntu-8.10 |
status: | Confirmed → Triaged |
importance: | Medium → High |
To post a comment you must log in.
Temporary solution for this is to install intrepid without having the virtual hard drive accessed the virtio way. Just plain simple /dev/hda type. After installation is finish, I shutdown the machine and switch to virtio block device. The change to /dev/vda is not a problem because UUID is used.
Hardy can be installed with virtio enabled.
Intrepid network works under the installation with virtio-net enabled.
Intrepid partitioning under the installation works with virtio enabled.