From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:60616) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RECVM-000601-2a for qemu-devel@nongnu.org; Thu, 13 Oct 2011 00:02:49 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RECVK-0002A5-4K for qemu-devel@nongnu.org; Thu, 13 Oct 2011 00:02:48 -0400 Received: from e23smtp01.au.ibm.com ([202.81.31.143]:51570) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RECVJ-00025v-H4 for qemu-devel@nongnu.org; Thu, 13 Oct 2011 00:02:46 -0400 Received: from d23relay04.au.ibm.com (d23relay04.au.ibm.com [202.81.31.246]) by e23smtp01.au.ibm.com (8.14.4/8.13.1) with ESMTP id p9D40m7J011306 for ; Thu, 13 Oct 2011 15:00:48 +1100 Received: from d23av04.au.ibm.com (d23av04.au.ibm.com [9.190.235.139]) by d23relay04.au.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p9D3wni61994756 for ; Thu, 13 Oct 2011 14:58:49 +1100 Received: from d23av04.au.ibm.com (loopback [127.0.0.1]) by d23av04.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p9D41BUu003959 for ; Thu, 13 Oct 2011 15:01:11 +1100 Received: from oc0100708617.ibm.com ([9.115.118.14]) by d23av04.au.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p9D41ABG001678 for ; Thu, 13 Oct 2011 15:01:10 +1100 Message-ID: <4E966259.4020500@vnet.linux.ibm.com> Date: Thu, 13 Oct 2011 12:00:25 +0800 From: hkran MIME-Version: 1.0 References: <4E957566.3010705@vnet.linux.ibm.com> In-Reply-To: <4E957566.3010705@vnet.linux.ibm.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] balloon driver on winxp guest start failed List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On 10/12/2011 07:09 PM, hkran wrote: > Hi, > > I used balloon driver for windows virtio-win-0.1-15.iso (from > http://alt.fedoraproject.org/pub/alt/virtio-win/latest/images/bin/) > > following the install guard , I installed the balloon driver like this: > > devcon.exe install d:\wxp\x86\balloon.inf > "PCI\VEN_1AF4&DEV_1002&SUBSYS_00051AF4&REV_00" > then reboot guest Os, but the status of driver installed is always > incorrect, that show me the driver start failed (code 10) in the > device manager. > > I typed the following cmds in the monitor command line: > > (qemu) device_add virtio-balloon > (qemu) info balloon > balloon: actual=2048 > (qemu) balloon 1024 > (qemu) info balloon > balloon: actual=2048 > (qemu) info balloon > balloon: actual=2048 > > And I also tried it by using "qemu -balloon virtio" param when > getting qemu up, the status is worse, the winxp guest froze at boot > screen. > > Am I using balloon driver in a correct way? > > > For the boot failure case, I take more looks into it. I open the trace output and see the following when boot failed Balloon driver, built on Oct 13 2011 10:46:59 ^M<-- DriverEntry ^Mfile z:\source\kvm-guest-drivers-windows\balloon\sys\driver.c line 151 ^M--> BalloonDeviceAdd ^M<-- BalloonDeviceAdd ^M--> BalloonEvtDevicePrepareHardware ^M<-> Port Resource [0000C0A0-0000C0C0] ^M<-- BalloonEvtDevicePrepareHardware ^M--> BalloonEvtDeviceD0Entry ^M--> BalloonInit ^M--> VIRTIO_BALLOON_F_STATS_VQ ^M<-- BalloonInit ^M--> BalloonInterruptEnable ^M<-- BalloonInterruptEnable here, the system is blocked. I compare it with the logfile in the normal case that I hot-plugin the balloon device, and then find the system blocked before calling at BalloonInterruptDpc. Is it meaning that we open the interrupt of balloon device too soon when booting the system?