From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:57014) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qr1XG-0006xv-3q for qemu-devel@nongnu.org; Wed, 10 Aug 2011 01:40:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qr1XE-0003OC-AR for qemu-devel@nongnu.org; Wed, 10 Aug 2011 01:40:58 -0400 Received: from adelie.canonical.com ([91.189.90.139]:58302) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qr1XE-0003O6-0u for qemu-devel@nongnu.org; Wed, 10 Aug 2011 01:40:56 -0400 Received: from loganberry.canonical.com ([91.189.90.37]) by adelie.canonical.com with esmtp (Exim 4.71 #1 (Debian)) id 1Qr1XD-0004Gy-2q for ; Wed, 10 Aug 2011 05:40:55 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id 1358F2E8047 for ; Wed, 10 Aug 2011 05:40:55 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Wed, 10 Aug 2011 05:32:53 -0000 From: showrun <823733@bugs.launchpad.net> Sender: bounces@canonical.com References: <20110810053253.11269.76752.malonedeb@gac.canonical.com> Message-Id: <20110810053253.11269.76752.malonedeb@gac.canonical.com> Errors-To: bounces@canonical.com Subject: [Qemu-devel] [Bug 823733] [NEW] Soloaris can't be poweroff Reply-To: Bug 823733 <823733@bugs.launchpad.net> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Public bug reported: Thank you forgive my poor English. It seems KVM can=E2=80=99t poweroff solairs 10 or sloalrs 11 VM. I have created solaris 10 and 11 as usual. Everything in VM is running OK, = but finally I use shell command =E2=80=98poweroff=E2=80=99 or =E2=80=98init= 5=E2=80=99, the solaris VM (both 10 & 11) system could=E2=80=99t be powero= ff but with promoting me the message: perss any key to reboot =E2=80=A6.. = ,I pressed any key in vnc client, solaris VM reboot immediately. Endless re= boot loop above. the solaris 10 & 11 from oracle iso file name : sol-10-u9-ga-x86-dvd.iso sol-11-exp-201011-text-x86.iso the solaris 10 & 11 from oracle iso file name : sol-10-u9-ga-x86-dvd.iso sol-11-exp-201011-text-x86.iso 1. On my real physical machine,the solaris can be poweroff 2. On vmware ,the solaris can be poweroff 3. On my real physical machine,I have try to disbale the ACPI opiton in BOI= S, then the solaris can't be poweroff,Like the problem I have described abo= ve so ,I doubt the KVM has a little problem in ACPI = I have try the suggestion as follows, but I can=E2=80=99t solve the problem. 7.2 Solaris reboot all the time on grub menu =E2=80=A2 Run through the installer as usual = =E2=80=A2 On completion and reboot, the VM will perpetually reboot. "Stop" = the VM. = =E2=80=A2 Start it up again, and immediately open a vnc console and select = the Safe Boot from the options screen = =E2=80=A2 When prompted if you want to try and recover the boot block, say = yes = =E2=80=A2 You should now have a Bourne terminal with your existing filesyst= em mounted on /a = =E2=80=A2 Run /a/usr/bin/bash (my preferred shell) = =E2=80=A2 export TERM=3Dxterm = =E2=80=A2 vi /a/boot/grub/menu.1st (editing the bootloader on your mounted = filesystem), to add "kernel/unix" to the kernel options for the non-safe-mo= de boot. Ex : = Config File : /a/boot/grub/menu.lst = kernel$ /platform/i86pc/multiboot -B $ZFS-BOOTFS kernel/unix According to KVM requirements, I collected the following information: CPU model name model name : Intel(R) Xeon(R) CPU X3450 @ 2.67GHz kvm -version QEMU PC emulator version 0.12.3 (qemu-kvm-0.12.3), Copyright (c) 2003-2008 = Fabrice Bellard Host kernel version Ubuntu 10.04.1 LTS 2.6.32-25-server = What host kernel arch you are using (i386 or x86_64) X86_64 Guest OS Solaris 10 and Solaris 11=EF=BC=8Cboth can not shutdown The qemu command line you are using to start the guest First, I used the command line as follows: kvm -m 1024 -drive file=3Dsolaris10.img,cache=3Dwriteback -net nic -net use= r -nographic -vnc :1 then I try to use -no-kvm-irqchip or -no-kvm ,but the problem also appears! Secondly, have created and run solaris 10&11 by using Virsh, still solaris = can't be poweroff, the XML file content is : solairs 85badf15-244d-4719-a2da-8c3de064137d 1677721 1677721 1 hvm destroy restart destroy /usr/bin/kvm libvirt-f36f5289-692e-6f1c-fe71-c6ed19453e2f ** Affects: qemu Importance: Undecided Status: New -- = You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/823733 Title: Soloaris can't be poweroff Status in QEMU: New Bug description: Thank you forgive my poor English. It seems KVM can=E2=80=99t poweroff solairs 10 or sloalrs 11 VM. I have created solaris 10 and 11 as usual. Everything in VM is running OK= , but finally I use shell command =E2=80=98poweroff=E2=80=99 or =E2=80=98in= it 5=E2=80=99, the solaris VM (both 10 & 11) system could=E2=80=99t be powe= roff but with promoting me the message: perss any key to reboot =E2=80=A6..= ,I pressed any key in vnc client, solaris VM reboot immediately. Endless = reboot loop above. the solaris 10 & 11 from oracle iso file name : sol-10-u9-ga-x86-dvd.iso sol-11-exp-201011-text-x86.iso the solaris 10 & 11 from oracle iso file name : sol-10-u9-ga-x86-dvd.iso sol-11-exp-201011-text-x86.iso 1. On my real physical machine,the solaris can be poweroff 2. On vmware ,the solaris can be poweroff 3. On my real physical machine,I have try to disbale the ACPI opiton in B= OIS, then the solaris can't be poweroff,Like the problem I have described a= bove so ,I doubt the KVM has a little problem in ACPI = I have try the suggestion as follows, but I can=E2=80=99t solve the probl= em. 7.2 Solaris reboot all the time on grub menu =E2=80=A2 Run through the installer as usual = =E2=80=A2 On completion and reboot, the VM will perpetually reboot. "Stop= " the VM. = =E2=80=A2 Start it up again, and immediately open a vnc console and selec= t the Safe Boot from the options screen = =E2=80=A2 When prompted if you want to try and recover the boot block, sa= y yes = =E2=80=A2 You should now have a Bourne terminal with your existing filesy= stem mounted on /a = =E2=80=A2 Run /a/usr/bin/bash (my preferred shell) = =E2=80=A2 export TERM=3Dxterm = =E2=80=A2 vi /a/boot/grub/menu.1st (editing the bootloader on your mounte= d filesystem), to add "kernel/unix" to the kernel options for the non-safe-= mode boot. Ex : = Config File : /a/boot/grub/menu.lst = kernel$ /platform/i86pc/multiboot -B $ZFS-BOOTFS kernel/unix According to KVM requirements, I collected the following information: CPU model name model name : Intel(R) Xeon(R) CPU X3450 @ 2.67GHz kvm -version QEMU PC emulator version 0.12.3 (qemu-kvm-0.12.3), Copyright (c) 2003-200= 8 Fabrice Bellard Host kernel version Ubuntu 10.04.1 LTS 2.6.32-25-server = What host kernel arch you are using (i386 or x86_64) X86_64 Guest OS Solaris 10 and Solaris 11=EF=BC=8Cboth can not shutdown The qemu command line you are using to start the guest First, I used the command line as follows: kvm -m 1024 -drive file=3Dsolaris10.img,cache=3Dwriteback -net nic -net u= ser -nographic -vnc :1 then I try to use -no-kvm-irqchip or -no-kvm ,but the problem also appear= s! Secondly, have created and run solaris 10&11 by using Virsh, still solari= s can't be poweroff, the XML file content is : solairs 85badf15-244d-4719-a2da-8c3de064137d 1677721 1677721 1 hvm destroy restart destroy /usr/bin/kvm libvirt-f36f5289-692e-6f1c-fe71-c6ed19453e2f To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/823733/+subscriptions