Re: [Qemu-devel] ATA timeouts on Solaris/OpenIndiana/Opensolaris
Andreas script worked for me. Thank you. But i seem to be running into an issue with when i set multiple cores. (-smp cores=4). Multiple CPUs works fine (-smp 4) During boot i get these messages: NOTICE: System detected 4 cpus, but only 1 cpu(s) were enabled during boot NOTICE: Use boot-ncpus parameter to enable more CPU(s).See eeprom(1M) I tried eeprom but to no avail.. It seems there is an issue in the BIOS. Have any of you encountered such an issue before? On Wed, Apr 2, 2014 at 10:23 PM, Ben Taylor bentaylor.sol...@gmail.comwrote: On Wed, Apr 2, 2014 at 11:51 AM, Andreas Färber afaer...@suse.de wrote: Hi, Am 02.04.2014 09:32, schrieb Sai Prajeeth: I am booting an OpenIndiana image on qemu by using the -smp 4 option. I seem to be running into this known bug http://docs.oracle.com/cd/E19253-01/820-5245/ggmsj/index.html Can someone tell me how can i go about doing workaround 2 on qemu?? Here's my script for running OpenIndiana using AHCI (SATA): qemu-system-x86_64 -enable-kvm -smp cores=1,threads=1,sockets=1 -m 2G \ -netdev user -device e1000,macaddr=... \ -device ahci,id=ahci \ -device ide-drive,bus=ahci.0,drive=ahcihd \ -drive file=/.../openindiana-151a.img,format=raw,if=none,id=ahcihd \ Note that live migration doesn't work with AHCI ATM. If you could start qemu with both ata and ahci, add a new lun to the ahci controller, and use beadm to migrate to the achi disk, then disconnect the ata disk/controller and bump the cores back to 4. I think that workaround 1 is not technically correct. however, you'd need a really good understanding of Solaris/opensolaris/OI to force the system to reenumerate the device path from a failsafe boot. But this is not for the faint of heart. If it's a new install (ie, not much customization/data), why not just start a new QEMU instance that uses the ahci controller? Ben Ben
[Qemu-devel] ATA timeouts on Solaris/OpenIndiana/Opensolaris
Hi I am booting an OpenIndiana image on qemu by using the -smp 4 option. I seem to be running into this known bug http://docs.oracle.com/cd/E19253-01/820-5245/ggmsj/index.html Can someone tell me how can i go about doing workaround 2 on qemu?? Workaround 3,4 are not an option for me. I already tried workaround 5 and it does not work. Can someone help me ? Thanks.
Re: [Qemu-devel] ATA timeouts on Solaris/OpenIndiana/Opensolaris
Hi, Am 02.04.2014 09:32, schrieb Sai Prajeeth: I am booting an OpenIndiana image on qemu by using the -smp 4 option. I seem to be running into this known bug http://docs.oracle.com/cd/E19253-01/820-5245/ggmsj/index.html Can someone tell me how can i go about doing workaround 2 on qemu?? Here's my script for running OpenIndiana using AHCI (SATA): qemu-system-x86_64 -enable-kvm -smp cores=1,threads=1,sockets=1 -m 2G \ -netdev user -device e1000,macaddr=... \ -device ahci,id=ahci \ -device ide-drive,bus=ahci.0,drive=ahcihd \ -drive file=/.../openindiana-151a.img,format=raw,if=none,id=ahcihd \ Note that live migration doesn't work with AHCI ATM. HTH, Andreas -- SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
Re: [Qemu-devel] ATA timeouts on Solaris/OpenIndiana/Opensolaris
On Wed, Apr 2, 2014 at 11:51 AM, Andreas Färber afaer...@suse.de wrote: Hi, Am 02.04.2014 09:32, schrieb Sai Prajeeth: I am booting an OpenIndiana image on qemu by using the -smp 4 option. I seem to be running into this known bug http://docs.oracle.com/cd/E19253-01/820-5245/ggmsj/index.html Can someone tell me how can i go about doing workaround 2 on qemu?? Here's my script for running OpenIndiana using AHCI (SATA): qemu-system-x86_64 -enable-kvm -smp cores=1,threads=1,sockets=1 -m 2G \ -netdev user -device e1000,macaddr=... \ -device ahci,id=ahci \ -device ide-drive,bus=ahci.0,drive=ahcihd \ -drive file=/.../openindiana-151a.img,format=raw,if=none,id=ahcihd \ Note that live migration doesn't work with AHCI ATM. If you could start qemu with both ata and ahci, add a new lun to the ahci controller, and use beadm to migrate to the achi disk, then disconnect the ata disk/controller and bump the cores back to 4. I think that workaround 1 is not technically correct. however, you'd need a really good understanding of Solaris/opensolaris/OI to force the system to reenumerate the device path from a failsafe boot. But this is not for the faint of heart. If it's a new install (ie, not much customization/data), why not just start a new QEMU instance that uses the ahci controller? Ben Ben
