Ubuntu
qemu package

UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw

Bug #1342000 reported by bugproxy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
High
Andy Whitcroft
qemu (Ubuntu)
Invalid
High
Unassigned

Bug Description

Problem Description
-----------------------------------
ISST-KVM-UBUNTU1410-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image raw.
Ubuntu installation to virtio-scsi disk type of raw, not able to find the driver by default and not listing virtio-scsi drivers to choose

---uname output---
[root@lizkvm home]# uname -a Linux lizkvm.isst.aus.stglabs.ibm.com 3.10.42-2001.pkvm2_1_1.3.ppc64 #1 SMP Tue Jun 17 13:13:10 CDT 2014 ppc64 ppc64 ppc64 GNU/Linux [root@lizkvm home]#

Steps to reproduce
-----------------------------------
1)
[root@magkvm images]# virsh define lizg3.xml
Domain lizg3 defined from lizg3.xml

2)
[root@lizkvm home]# virsh dumpxml lizg3
<domain type='kvm' id='25'>
  <name>lizg3</name>
  <uuid>da4ce0fd-2268-45b8-b5ca-611ac7926e50</uuid>
  <memory unit='KiB'>6606848</memory>
  <currentMemory unit='KiB'>6606029</currentMemory>
  <vcpu placement='static'>4</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='8'/>
    <vcpupin vcpu='2' cpuset='24'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='ppc64' machine='pseries'>hvm</type>
    <boot dev='hd'/>
    <boot dev='cdrom'/>
    <bootmenu enable='yes'/>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu>
    <topology sockets='2' cores='1' threads='2'/>
  </cpu>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-system-ppc64</emulator>
    <disk type='block' device='lun'>
      <driver name='qemu' type='raw'/>
      <source dev='/dev/sdz'/>
      <backingStore/>
      <target dev='sda' bus='scsi'/>
      <alias name='scsi1-0-0-3'/>
      <address type='drive' controller='1' bus='0' target='0' unit='3'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/home/ubuntu14.10/utopic-server-ppc64el.iso'/>
      <backingStore/>
      <target dev='sdb' bus='scsi'/>
      <readonly/>
      <alias name='scsi0-0-1-1'/>
      <address type='drive' controller='0' bus='0' target='1' unit='1'/>
    </disk>
    <disk type='block' device='lun'>
      <driver name='qemu' type='raw'/>
      <source dev='/dev/sdq'/>
      <backingStore/>
      <target dev='sdc' bus='scsi'/>
      <alias name='scsi1-0-0-2'/>
      <address type='drive' controller='1' bus='0' target='0' unit='2'/>
    </disk>
    <disk type='block' device='lun'>
      <driver name='qemu' type='raw'/>
      <source dev='/dev/sdj'/>
      <backingStore/>
      <target dev='sdd' bus='scsi'/>
      <alias name='scsi1-0-0-0'/>
      <address type='drive' controller='1' bus='0' target='0' unit='0'/>
    </disk>
    <controller type='scsi' index='0' model='ibmvscsi'>
      <alias name='scsi0'/>
      <address type='spapr-vio' reg='0x2000'/>
    </controller>
    <controller type='scsi' index='1' model='virtio-scsi'>
      <alias name='scsi1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </controller>
    <controller type='usb' index='0'>
      <alias name='usb0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'>
      <alias name='pci.0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:91:7f:87'/>
      <source bridge='brenP3p5s0f3'/>
      <target dev='vnet1'/>
      <model type='virtio'/>
      <driver name='qemu'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/3'/>
      <target port='0'/>
      <alias name='serial0'/>
      <address type='spapr-vio' reg='0x30000000'/>
    </serial>
    <console type='pty' tty='/dev/pts/3'>
      <source path='/dev/pts/3'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
      <address type='spapr-vio' reg='0x30000000'/>
    </console>
    <memballoon model='none'>
      <alias name='balloon0'/>
    </memballoon>
  </devices>
  <seclabel type='dynamic' model='selinux' relabel='yes'>
    <label>system_u:system_r:svirt_t:s0:c79,c721</label>
    <imagelabel>system_u:object_r:svirt_image_t:s0:c79,c721</imagelabel>
  </seclabel>
</domain>

3)

[root@magkvm images]# virsh start --console lizg3
Domain lizg3 started
Connected to domain lizg3

Escape character is ^]

SLOF **************************

-->Configured network properly and then moved to Detect disks screen

4)
Proceeded with the installation and when the disk partition screen comes up. Installer is not able to indentify the disk and asks to choose from the list of drivers as below

  ???????????????????????????? [!] Detect disks ?????????????????????????????
  ? ?
  ? No disk drive was detected. If you know the name of the driver needed ?
  ? by your disk drive, you can select it from the list. ?
  ? ?
  ? Driver needed for your disk drive: ?
  ? ?
  ? continue with no disk drive ?
  ? login to iSCSI targets ?
  ? 3w-9xxx ? ?
  ? 3w-sas ? ?
  ? 3w-xxxx ? ?
  ? DAC960 ? ?
  ? a100u2w ? ?
  ? aacraid ? ?
  ? aic79xx ? ?
  ? aic7xxx ?
  ? ?
  ? <Go Back> ?
  ? ?
  ???????????????????????????????????????????????????????????????????????????

<Tab> moves; <Space> selects; <Enter> activates buttons

4) verified for the drivers from the list and none of them belongs to virtio-scsi

optional driver listed are:

  continue with no disk drive ?
  ? login to iSCSI targets ?
  ? 3w-9xxx ? ?
  ? 3w-sas ? ?
  ? 3w-xxxx ? ?
  ? DAC960 ? ?
  ? a100u2w ? ?
  ? aacraid ? ?
  ? aic79xx ? ?
  ? aic7xxx
aic94xx ?
  ? aoe ? ?
  ? arcmsr ?
  ? aten ? ?
  ? atp870u ? ?
  ? bpck ? ?
  ? cciss ? ?
  ? comm ? ?
  ? cryptoloop ? ?
  ? dc395x
dmx3191d ?
  ? dstr ? ?
  ? eata ? ?
  ? epat ?
  ? epia ? ?
  ? fdomain ? ?
  ? fit2 ? ?
  ? fit3 ? ?
  ? floppy ? ?
  ? friq
frpw ?
  ? gdth ? ?
  ? hpsa ? ?
  ? hptiop ? ?
  ? imm ?
  ? initio ? ?
  ? ips ? ?
  ? kbic ? ?
  ? ktti ? ?
  ? libsas

lpfc ?
  ? megaraid ? ?
  ? megaraid_mbox ? ?
  ? megaraid_mm ? ?
  ? megaraid_sas ? ?
  ? mpt2sas ?
  ? mptbase ? ?
  ? mptctl ? ?
  ? mptfc ? ?
  ? mptlan

 mptsas ? ?
  ? mptscsih ? ?
  ? mptspi ? ?
  ? mtip32xx ? ?
  ? mvsas ?
  ? nbd ? ?
  ? on20 ? ?
  ? on26 ? ?
  ? paride

pcd ? ?
  ? pd ? ?
  ? pf ? ?
  ? pg ? ?
  ? ppa ? ?
  ? pt ? ?
  ? qla1280 ?
  ? qla2xxx ? ?
  ? qla4xxx
raid_class ? ?
  ? scsi_debug ? ?
  ? scsi_dh ? ?
  ? scsi_dh_alua ? ?
  ? scsi_dh_rdac ?
  ? scsi_transport_sas ? ?
  ? stex ? ?
  ? sx8
                          tmscsim ? ?
  ? umem ?
  ? none of the above

Install method: Tried both CDROM (ISO image) and Netboot ( Filename : ubuntu-installer/ppc64el/powerpc-ieee1275/core.elf)

Install disk info: sdb is the disk where ubuntu to be installed and disk type virtio-scsi of type raw.

Install ISO Information: ubuntu14.10 : utopic-server-ppc64el.iso

The userspace tool has the following bit modes: uname -a Linux lizg2 3.15.0-6-generic #11-Ubuntu SMP Thu Jun 12 00:40:49 UTC 2014 ppc64le ppc64le ppc64le GNU/Linux

== Comment: #3 - INDIRA P. JOGA <email address hidden> - ==
HI,

Yes this is reproducible every time. And here in xml , used entire disk which is divided into LUNS ( raw whole disk) and hence did not used qemu image.

Regards,
Indira

== Comment: #5 - PRIYA M. A <email address hidden> - ==

I am trying to install ubuntu14.10 on guest : pamg1 at host: pamkvm
Ubuntu installation on virtio-scsi disk type of raw, is unable to find their drivers by default and not listing virtio-scsi drivers to proceed with ubuntu14.10 installation

XML:

[root@pamkvm qemu]# cat pamg1.xml
<!--
WARNING: THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
OVERWRITTEN AND LOST. Changes to this xml configuration should be made using:
  virsh edit pamg1
or other application using the libvirt API.
-->

<domain type='kvm'>
  <name>pamg1</name>
  <uuid>e961fc15-db67-42ba-8729-e14231dbfeeb</uuid>
  <memory unit='KiB'>12582912</memory>
  <currentMemory unit='KiB'>12582912</currentMemory>
  <memtune>
    <soft_limit unit='KiB'>14825792</soft_limit>
  </memtune>
  <vcpu placement='static'>4</vcpu>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='ppc64' machine='pseries'>hvm</type>
    <boot dev='hd'/>
    <boot dev='cdrom'/>
  </os>
  <cpu mode='custom' match='exact'>
    <model fallback='allow'>power7</model>
    <topology sockets='1' cores='1' threads='4'/>
  </cpu>
  <clock offset='utc'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-kvm</emulator>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source dev='/dev/disk/by-id/wwn-0x50000395282849f0'/>
      <target dev='sda' bus='scsi'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source dev='/dev/disk/by-id/wwn-0x5000039528284ab4'/>
      <target dev='sdb' bus='scsi'/>
      <address type='drive' controller='0' bus='0' target='0' unit='1'/>
    </disk>
    <disk type='block' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source dev='/dev/disk/by-id/wwn-0x5000039528285c90'/>
      <target dev='sdc' bus='scsi'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/home/utopic-server-ppc64el.iso'/>
      <target dev='sdd' bus='scsi'/>
      <readonly/>
      <address type='drive' controller='1' bus='0' target='0' unit='0'/>
    </disk>
    <controller type='pci' index='0' model='pci-root'/>
    <controller type='scsi' index='0' model='virtio-scsi'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </controller>
    <controller type='scsi' index='1'>
      <address type='spapr-vio' reg='0x2000'/>
    </controller>
    <controller type='usb' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:0b:35:50'/>
      <source bridge='brenP3p9s0f0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'/>
      <address type='spapr-vio' reg='0x30000000'/>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
      <address type='spapr-vio' reg='0x30000000'/>
    </console>
    <memballoon model='none'/>
  </devices>
  <seclabel type='dynamic' model='selinux' relabel='yes'/>
</domain>

I too encounter the same output as mentioned in this defect

When I tried the same with same xml and ubuntu build 14.04 it worked fine. The disks were listed and I was able to proceed with installation.

== Comment: #7 - INDIRA P. JOGA <email address hidden> - ==
Pls find the logs attached.

Revision history for this message
bugproxy (bugproxy) wrote : /var/log content details

Default Comment by Bridge

tags: added: architecture-ppc64le bugnameltc-112983 severity-critical
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1342000/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Thierry FAUCK (thierry-j) wrote :

This sounds like an issue with qemu and virtio option

affects: ubuntu → qemu-kvm (Ubuntu)
Changed in qemu-kvm (Ubuntu):
status: New → Confirmed
bugproxy (bugproxy)
tags: added: targetmilestone-inin1410
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2014-07-21 10:52 EDT-------
*** Bug 113085 has been marked as a duplicate of this bug. ***

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2014-07-24 06:37 EDT-------
*** Bug 113737 has been marked as a duplicate of this bug. ***

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

Hi,

could you please show the results of 'ps -ef | grep qemu' while the vm is running?

To be clear, are you saying that, on the same host, you are able to install a 14.04 Ubuntu guest, but installing a 14.10 Ubuntu guests fails?

Changed in qemu-kvm (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete
Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2014-07-29 17:16 EDT-------
One of the dup'd bugs mentions:
--------------
This is an regression issue which we had even for Ubuntu 14.04, later got fixed when the working virtio-scsi driver was provided..

Looks like 14.10 is broken again.
-------------

Maybe the updated driver didn't go into both the .04 as well as .10 branches?

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

Is the 'working virtio-scsi driver' which was provided a kernel driver, or is it a qemu patch? If qemu patch, can you point to which one? If it is a kernel issue, then this bug should be re-targeted to 'linux'.

For now I am re-targetting this bug to qemu. (qemu-kvm is the source package based on the qemu-kvm upstream, which is not used in 14.04 or 14.10)

affects: qemu-kvm (Ubuntu) → qemu (Ubuntu)
Revision history for this message
bugproxy (bugproxy) wrote :
Download full text (4.9 KiB)

------- Comment From <email address hidden> 2014-08-05 06:24 EDT-------
-- Externalizing comment from Richard --

(In reply to comment #19)
> Indira, are you or were you able to install 14.04 in the same host?

I have the same issue on on of my guests, netg3, so I can answer this.

When I start the 14.04 LTS install, I see two virtual disks listed in the partitioner questions. One disk is a 55GB virito-scsi disk (the intended root target disk) and the other is a 12GB virtio-block disk (intended for I/O tests).

When I start the 14.10 install, I only see the the 12GB virtio-block disk. The virtio-scsi root disk is not listed.

So, it is definitely possible to install 14.04 on the same guest disk where a 14.10 installation would fail.

> And could you answer the question:
> could you please show the results of 'ps -ef | grep qemu' while the vm is
> running?

I will do this for my KVM host. The relevant guest, in my case, is netg3.

[root@netkvm ~]# ps -ef|grep qemu
qemu 44855 1 73 Jul31 ? 19:49:32 /usr/bin/qemu-system-ppc64 -machine accel=kvm -name netg8 -S -machine pseries,accel=kvm,usb=off -cpu host,compat=power7 -m 12288 -realtime mlock=off -smp 8,sockets=1,cores=2,threads=4 -uuid a39e2a73-5b15-4d7e-a882-a76a7d1b8395 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/netg8.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device pci-ohci,id=usb,bus=pci.0,addr=0x2 -drive file=/gto_hwr5_ext4/netg8_root.raw,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/gto_hwr5_ext4/netg8_nfs1.raw,if=none,id=drive-virtio-disk1,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1 -drive file=/gto_hwr5_ext4/netg8_nfs2.raw,if=none,id=drive-virtio-disk2,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x6,drive=drive-virtio-disk2,id=virtio-disk2 -netdev tap,fd=23,id=hostnet0,vhost=on,vhostfd=24 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:3d:0c:c5,bus=pci.0,addr=0x1,bootindex=2 -chardev pty,id=charserial0 -device spapr-vty,chardev=charserial0,reg=0x30001000 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x3 -msg timestamp=on
qemu 46660 1 47 Jul31 ? 12:56:39 /usr/bin/qemu-system-ppc64 -machine accel=kvm -name netg1 -S -machine pseries,accel=kvm,usb=off -cpu host,compat=power7 -m 8000 -realtime mlock=off -smp 4,sockets=1,cores=1,threads=4 -uuid d439f9ef-0b8b-4cc6-b1d5-1fac8fd783ad -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/netg1.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device pci-ohci,id=usb,bus=pci.0,addr=0x1 -device spapr-vscsi,id=scsi0,reg=0x2000 -device virtio-scsi-pci,id=scsi1,bus=pci.0,addr=0x4 -drive file=/dev/disk/by-id/dm-uuid-part1-mpath-1IBM_IPR-6_5EC5700000000420,if=none,id=drive-scsi0-0-2-0,format=raw -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=2,lun=0,drive=drive-scsi0-0-2-0,id=scsi0-0-2-0,boot...

Read more...

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

I notice that in the netg3 command, one drive is specified as scsi-hd,
while the other is virtio-blk-pci. Was that intended?

Changed in qemu (Ubuntu):
status: Incomplete → New
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1342000

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Andy Whitcroft (apw)
Changed in linux (Ubuntu):
status: Incomplete → Triaged
Revision history for this message
Andy Whitcroft (apw) wrote :

Hmmm seems this change has slipped through the net. I've ported it over to the utopic kernel. Will review further before uploading.

Changed in linux (Ubuntu):
status: Triaged → In Progress
importance: Undecided → High
assignee: nobody → Andy Whitcroft (apw)
Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2014-08-07 17:01 EDT-------
(In reply to comment #24)
> I notice that in the netg3 command, one drive is specified as scsi-hd,
> while the other is virtio-blk-pci. Was that intended?

Yes, that was intentional. This is a test system, and we are attempting to run I/O tests on both types of virtual disk.

Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2014-08-07 17:26 EDT-------
(In reply to comment #25)
> This bug is missing log files that will aid in diagnosing the problem. From
> a terminal window please run:
>
> apport-collect 1342000
>
> and then change the status of the bug to 'Confirmed'.
>
> If, due to the nature of the issue you have encountered, you are unable to
> run this command, please add a comment stating that fact and change the bug
> status to 'Confirmed'.

This error occurs during O/S installation. I chose the menu option to start a shell, but the apport-collect command does not exist in the installation miniroot environment.

I found a menu option to save the installation log files and will attach those files to this bug instead.

Revision history for this message
bugproxy (bugproxy) wrote : hardware-summary file from netg3 installation

------- Comment (attachment only) From <email address hidden> 2014-08-07 17:28 EDT-------

Revision history for this message
bugproxy (bugproxy) wrote : partman file from netg3 installation

------- Comment (attachment only) From <email address hidden> 2014-08-07 17:28 EDT-------

Revision history for this message
bugproxy (bugproxy) wrote : syslog file from netg3 installation

------- Comment (attachment only) From <email address hidden> 2014-08-07 17:28 EDT-------

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla
Download full text (6.2 KiB)

------- Comment From <email address hidden> 2014-08-08 06:35 EDT-------
--- Comment from Shawn T Wright ---
I hit this issue on my Unbuntu 14.10 installs as well but noticed it because I was attempting to install an iso from a VIRTIO-SCSI CD-ROM device.

[[!!]] Detect and Mount CD-ROM
Your installation CD-ROM couldn't be mounted.....

I also tried the same thing for VIRTIO-Block CD-ROM and it failed the same way.

I then tried PAPR-SCSI CD-ROM and it works, but then it comes up and I hit the issue described in this defect that no drives were detected. My Drives are configured for virtio-scsi.

???????????????????????????? [!] Detect disks ?????????????????????????????
? ?
? No disk drive was detected. If you know the name of the driver needed ?
? by your disk drive, you can select it from the list. ?
? ?
? Driver needed for your disk drive: ?
? ?
? continue with no disk drive ?
? login to iSCSI targets ?
? 3w-9xxx ? ?
? 3w-sas ? ?
? 3w-xxxx ? ?
? DAC960 ? ?
? a100u2w ? ?
? aacraid ? ?
? aic79xx ? ?
? aic7xxx ?
? ?
? <Go Back> ?
? ?
???????????????????????????????????????????????????????????????????????????

Here is my xml:
[root@workkvm ~]# cat ubu1-scsi.xml
<domain type='kvm'>
<name>ubu1</name>
<memory unit='GiB'>4</memory>

<cpu>
<topology sockets='1' cores='1' threads='1'/>
</cpu>

<vcpu placement='static'>1</vcpu>

<os>
<type arch='ppc64' machine='pseries'>hvm</type>
<boot dev='cdrom'/>
<boot dev='network'/>
<boot dev='hd'/>
</os>

<features>
<acpi/>
<apic/>
</features>

<clock offset='utc'/>

<on_poweroff>destroy</on_poweroff>
<on_reboot>restart</on_reboot>
<on_crash>coredump-restart</on_crash>

<devices>

<emulator>/usr/bin/qemu-system-ppc64</emulator>

<disk type='block' device='disk'>
<driver name='qemu' type='raw'/>
<source dev='/dev/mapper/mpathe'/>
<target dev='vda' bus='scsi'/>
<address type='drive' controller='1' bus='0' target='0' unit='0'/>
</disk>

<disk type='file' device='cdrom'>
<driver name='qemu' type='raw'/>
<source file='/var/lib/libvirt/utopic-server-ppc64el.iso'/>
<target dev='vdb' bus='scsi'/>
<readonly/>
<address type='drive' controller='0' bus='0' target='0' unit='...

Read more...

Revision history for this message
Tim Gardner (timg-tpi) wrote :

Will appear in Ubuntu-3.16.0-7.12

Changed in linux (Ubuntu):
status: In Progress → Fix Committed
Serge Hallyn (serge-hallyn)
Changed in qemu (Ubuntu):
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 3.16.0-7.12

---------------
linux (3.16.0-7.12) utopic; urgency=low

  [ Andy Whitcroft ]

  * rebase to v3.16 final
  * [Config] d-i -- add virtio_scsi to virtio-modules
    - LP: #1342000

  [ dann frazier ]

  * [Packaging] Fix 'printchanges' to work with versions containing '+'

  [ Tim Gardner ]

  * [Config] CONFIG_MICROCODE=y
    - LP: #1084373
  * [Config] CONFIG_CONTEXT_TRACKING_FORCE=n
    - LP: #1349028
  * [Config] Add hv_balloon to d-i virtio-modules
    - LP: #1292216
  * Release Tracking Bug
    - LP: #1354530

  [ Upstream Kernel Changes ]

  * rebase to v3.16
 -- Tim Gardner <email address hidden> Tue, 29 Jul 2014 09:55:15 -0400

Changed in linux (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
bugproxy (bugproxy) wrote :

------- Comment From <email address hidden> 2014-09-30 20:16 EDT-------
Able to install Ubuntu14.10 on virtio-scsi disk properly with latest daily ISO. Bug has been closed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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