From: hkran <hkran@vnet.linux.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] balloon driver on winxp guest start failed
Date: Thu, 13 Oct 2011 12:00:25 +0800 [thread overview]
Message-ID: <4E966259.4020500@vnet.linux.ibm.com> (raw)
In-Reply-To: <4E957566.3010705@vnet.linux.ibm.com>
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?
next prev parent reply other threads:[~2011-10-13 4:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 11:09 [Qemu-devel] balloon driver on winxp guest start failed hkran
2011-10-13 4:00 ` hkran [this message]
2011-10-13 14:47 ` Stefan Hajnoczi
2011-10-13 20:55 ` Vadim Rozenfeld
2011-10-14 9:49 ` hkran
2011-10-17 12:55 ` Vadim Rozenfeld
2011-10-20 7:55 ` hkran
2011-10-27 9:49 ` hkran
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E966259.4020500@vnet.linux.ibm.com \
--to=hkran@vnet.linux.ibm.com \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).