Comment 18 for bug 1342000

------- 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='0'/>
</disk>

<interface type='bridge'>
<model type='virtio-net'/>
<source bridge='brenP1p5s0f0'/>
<address type='pci' bus='0x00' slot='0x01' function='0x0'/>
</interface>

<controller type='scsi' model='ibmvscsi' index='0' />
<controller type='scsi' model='virtio-scsi' index='1' />
<controller type='usb' model='none' />

<memballoon model='none'/>

<console type='pty'>
<target type='serial' port='0'/>
<address type='spapr-vio' reg='0x30000000'/>
</console>

</devices>

<seclabel type='none'/>

</domain>

Here is the output from ps -ef |grep qemu for my system.

The guest that is seeing the problem during this ps-ef is "ubu1"

[root@workkvm ~]# ps -ef |grep qemu
qemu 129208 1 0 12:32 ? 00:00:28 /usr/bin/qemu-system-ppc64 -name ubu2 -S -machine pseries,accel=kvm,usb=off -m 4096 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 99e5a6ca-a787-4556-bff7-4e5f5fb00992 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/ubu2.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device spapr-vscsi,id=scsi0,reg=0x2000 -drive file=/dev/mapper/mpathc,if=none,id=drive-scsi0-0-0-0,format=raw -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -drive file=/var/lib/libvirt/utopic-server-ppc64el.iso,if=none,id=drive-scsi0-0-1-0,readonly=on,format=raw -device scsi-cd,bus=scsi0.0,channel=0,scsi-id=1,lun=0,drive=drive-scsi0-0-1-0,id=scsi0-0-1-0 -netdev tap,fd=26,id=hostnet0 -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:f2:0e:46,bus=pci.0,addr=0x1 -chardev pty,id=charserial0 -device spapr-vty,chardev=charserial0,reg=0x30000000 -msg timestamp=on
qemu 135710 1 3 13:48 ? 00:00:29 /usr/bin/qemu-system-ppc64 -name ubu1 -S -machine pseries,accel=kvm,usb=off -m 4096 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid d3933339-c08c-435d-b5e5-957ba699c6db -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/ubu1.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot strict=on -device spapr-vscsi,id=scsi0,reg=0x2000 -device virtio-scsi-pci,id=scsi1,bus=pci.0,addr=0x2 -drive file=/dev/mapper/mpathe,if=none,id=drive-scsi1-0-0-0,format=raw -device scsi-hd,bus=scsi1.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi1-0-0-0,id=scsi1-0-0-0,bootindex=3 -drive file=/var/lib/libvirt/utopic-server-ppc64el.iso,if=none,id=drive-scsi0-0-0-0,readonly=on,format=raw -device scsi-cd,bus=scsi0.0,channel=0,scsi-id=0,lun=0,drive=drive-scsi0-0-0-0,id=scsi0-0-0-0,bootindex=1 -netdev tap,fd=24,id=hostnet0 -device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:55:8b:92,bus=pci.0,addr=0x1,bootindex=2 -chardev pty,id=charserial0 -device spapr-vty,chardev=charserial0,reg=0x30000000 -msg timestamp=on
root 136784 126693 0 14:01 pts/5 00:00:00 grep --color=auto qemu

This issue is very simple to recreate and can be done 100% of the time.

This is blocking tests.

Whats the target date / build that we will see the fix for this issue in?