From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K644B-0003ZC-1h for qemu-devel@nongnu.org; Tue, 10 Jun 2008 09:39:15 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K6449-0003YT-Jn for qemu-devel@nongnu.org; Tue, 10 Jun 2008 09:39:14 -0400 Received: from [199.232.76.173] (port=53677 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K6449-0003XN-AE for qemu-devel@nongnu.org; Tue, 10 Jun 2008 09:39:13 -0400 Received: from mx03.syneticon.net ([87.79.32.166]:3642) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K6445-0000Lg-IR for qemu-devel@nongnu.org; Tue, 10 Jun 2008 09:39:09 -0400 Received: from localhost (filter1.syneticon.net [192.168.113.3]) by mx03.syneticon.net (Postfix) with ESMTP id 6F79794A6 for ; Tue, 10 Jun 2008 15:39:06 +0200 (CEST) Received: from mx03.syneticon.net ([192.168.113.4]) by localhost (mx03.syneticon.net [192.168.113.3]) (amavisd-new, port 10025) with ESMTP id 5awu1fGQb7jM for ; Tue, 10 Jun 2008 15:39:00 +0200 (CEST) Received: from [192.168.10.145] (koln-4d0b7c3d.pool.mediaWays.net [77.11.124.61]) by mx03.syneticon.net (Postfix) with ESMTP for ; Tue, 10 Jun 2008 15:39:00 +0200 (CEST) Message-ID: <484E83F3.1020005@wpkg.org> Date: Tue, 10 Jun 2008 15:38:59 +0200 From: Tomasz Chmielewski MIME-Version: 1.0 Subject: Re: [Qemu-devel] what is needed to shutdown a guest (including Qemu process)? References: <484E6B53.8030503@wpkg.org> <20080610131815.GD28565@shareable.org> In-Reply-To: <20080610131815.GD28565@shareable.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Jamie Lokier schrieb: (...) >> When I want to halt the guest system, it shutdowns just fine up to: >> >> Will now halt. >> Synchronizing SCSI cache for disk sda: >> System halted. >> >> But the qemu-system-arm process continues to run. >> >> Is there a workaround to that? I would expect qemu process to exit as well. > > Try poweroff instead of halt. No, it doesn't make a difference. Note that it shutdowns fine (including qemu process) when the guest is x86. With an ARM guest, qemu keeps running. Perhaps the guest needs something in the kernel? I added APM, but it didn't make a difference. When the guest is halted, this is what I get when I strace the qemu-system-arm process (endlessly in a loop): --- SIGALRM (Alarm clock) @ 0 (0) --- sigreturn() = ? (mask now []) clock_gettime(CLOCK_MONOTONIC, {7954727, 280679359}) = 0 clock_gettime(CLOCK_MONOTONIC, {7954727, 280821359}) = 0 clock_gettime(CLOCK_MONOTONIC, {7954727, 280954359}) = 0 clock_gettime(CLOCK_MONOTONIC, {7954727, 281085359}) = 0 clock_gettime(CLOCK_MONOTONIC, {7954727, 281215359}) = 0 timer_gettime(0, {it_interval={0, 0}, it_value={0, 0}}) = 0 timer_settime(0, 0, {it_interval={0, 0}, it_value={0, 2381000}}, NULL) = 0 select(8, [5 7], [], [], {0, 0}) = 0 (Timeout) clock_gettime(CLOCK_MONOTONIC, {7954727, 281824359}) = 0 clock_gettime(CLOCK_MONOTONIC, {7954727, 281955359}) = 0 select(8, [5 7], [], [], {0, 10000}) = ? ERESTARTNOHAND (To be restarted) -- Tomasz Chmielewski http://wpkg.org