From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: OpenBSD 5.3 guest on KVM Date: Fri, 6 Nov 2015 16:57:17 +0100 Message-ID: <563CCDDD.8050709@redhat.com> References: <20130904233114.GA4460@defiant.freesoftware> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit To: dbareiro@gmx.net, KVM list Return-path: Received: from mail-wm0-f43.google.com ([74.125.82.43]:34811 "EHLO mail-wm0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751615AbbKFP5V (ORCPT ); Fri, 6 Nov 2015 10:57:21 -0500 Received: by wmnn186 with SMTP id n186so45680794wmn.1 for ; Fri, 06 Nov 2015 07:57:20 -0800 (PST) In-Reply-To: <20130904233114.GA4460@defiant.freesoftware> Sender: kvm-owner@vger.kernel.org List-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 05/09/2013 01:31, Daniel Bareiro wrote: > Hi all! > > These days I tested OpenBSD 5.3 and pleasantly surprised me notice > that they implemented VirtIO for block devices, network and memory > ballooning. It is an important step for those who contribute to > the project. > > Now what I'm seeing is that there seems to be some sort of problem > with the ACPI to shutdown the VM. I remember that at one time it > was not working, then they corrected it and now seems to be new > problems with these messages. > > I tried turning off the VM from libvirt (virsh) and also from Qemu > monitor booting the VM manually and in either case the result is > the same: the VM freezes. > > # sysctl hw hw.machine=amd64 hw.model=QEMU Virtual CPU version > 1.1.2 hw.ncpu=1 hw.byteorder=1234 hw.pagesize=4096 > hw.disknames=cd0:,sd0:be0e0f1c0cdc4dae,fd0:,fd1: hw.diskcount=4 > hw.cpuspeed=2009 hw.vendor=Bochs hw.product=Bochs > hw.uuid=501ef229-2337-165f-8da3-905b12832049 hw.physmem=535814144 > hw.usermem=535801856 hw.ncpufound=1 hw.allowpowerdown=1 > > > hw.allowpowerdown set to 1 (the default) allows a power button > shutdown. > > Someone had this problem and could solve it somehow? There any > debug information I can provide to help solve this? Sure, you can gather a trace on the host using trace-cmd. trace-cmd record -e kvm qemu-system-x86_64 --enable-kvm ... This will produce a huge trace.dat file. You can compress it with xz and send it my way. Thanks, Paolo