[Bug 1342000] Comment bridged from LTC Bugzilla
--- Comment From cha...@us.ibm.com 2014-09-30 20:16 EDT--- Able to install Ubuntu14.10 on virtio-scsi disk properly with latest daily ISO. Bug has been closed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1342000 Title: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1342000] Comment bridged from LTC Bugzilla
--- Comment From vaish...@in.ibm.com 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- ? ? ? DAC960 ? ? ? a100u2w ? ? ? aacraid ? ? ? aic79xx ? ? ? aic7xxx ? ? ? ? Go Back ? ? ? ??? Here is my xml: [root@workkvm ~]# cat ubu1-scsi.xml domain type='kvm' nameubu1/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_poweroffdestroy/on_poweroff on_rebootrestart/on_reboot on_crashcoredump-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='0x3000'/ /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=char serial0 -device spapr-vty,chardev=charserial0,reg=0x3000 -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
[Bug 1342000] Comment bridged from LTC Bugzilla
--- Comment From rsche...@us.ibm.com 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. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1342000 Title: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1342000] Comment bridged from LTC Bugzilla
--- Comment From rsche...@us.ibm.com 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. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1342000 Title: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1342000] Comment bridged from LTC Bugzilla
--- Comment From vaish...@in.ibm.com 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-b lk-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_5EC57420,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,bootindex=1 -drive file=/dev/disk/by-id/dm-uuid-part1-mpath-36005076802810c1fa0b1,if=none,id=drive-scsi1-0-4-0,format=raw -device scsi-hd,bus=scsi1.0 ,channel=0,scsi-id=4,lun=0,drive=drive-scsi1-0-4-0,id=scsi1-0-4-0 -netdev tap,fd=23,id=hostnet0 -device spapr-vlan,netdev=hostnet0,id=net0,mac=52:54:00:45:66:ac,reg=0x1000,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 154457 1 28 18:14 ?00:02:05 /usr/bin/qemu-system-ppc64 -machine accel=kvm -name netg3 -S -machine pseries,accel=kvm,usb=off -cpu host,compat=power8 -m 8000 -realtime mlock=off -smp 4,sockets=1,cores=2,threads=2 -uuid 0cdf201f-a85c-4b62-a05e-4e42213b5ae5 -nographic -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/netg3.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 -device virtio-scsi-pci,id=scsi0,bus=pci.0,addr=0x4 -drive file=/gto_hwr5_ext4/netg3_root.raw,if=none,id=drive-scsi0-0-1-0,format=raw -device scsi-hd,bus=scsi0.0,channel=0,scsi-id=1,lun=0,drive=drive-scsi0-0-1-0,id=scsi0-0-1-0,bootindex=1 -drive file=/usb_rdx_ext4/netg3_usb_io.raw,if=none,id=drive-virtio-disk0,format=raw -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk0,id=virtio-disk0 -netdev tap,fd=27,id=hostnet0,vhost=on,vhostfd= 28 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:3e:a5:40,bus=pci.0,addr=0x1,bootindex=2 -chardev pty,id=charserial0 -device spapr-vty,chardev=charserial0,reg=0x30001000 -device
[Bug 1342000] Comment bridged from LTC Bugzilla
--- Comment From fno...@us.ibm.com 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? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1342000 Title: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1342000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1342000] Comment bridged from LTC Bugzilla
--- Comment From vaish...@in.ibm.com 2014-07-24 06:37 EDT--- *** Bug 113737 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1342000 Title: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1342000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1342000] Comment bridged from LTC Bugzilla
--- Comment From vaish...@in.ibm.com 2014-07-21 10:52 EDT--- *** Bug 113085 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1342000 Title: UBUNTU14.10-LE:liz:Ubuntu installation failing on virtio-scsi disk with disk image type raw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1342000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
