[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] balloon driver on winxp guest start failed
From: |
Stefan Hajnoczi |
Subject: |
Re: [Qemu-devel] balloon driver on winxp guest start failed |
Date: |
Thu, 13 Oct 2011 15:47:52 +0100 |
On Thu, Oct 13, 2011 at 5:00 AM, hkran <address@hidden> wrote:
> On 10/12/2011 07:09 PM, hkran wrote:
>> 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?
I suggest CCing Vadim on virtio Windows driver questions. Not sure if
he sees every qemu-devel email.
Stefan
- [Qemu-devel] balloon driver on winxp guest start failed, hkran, 2011/10/12
- Re: [Qemu-devel] balloon driver on winxp guest start failed, hkran, 2011/10/13
- Re: [Qemu-devel] balloon driver on winxp guest start failed,
Stefan Hajnoczi <=
- Re: [Qemu-devel] balloon driver on winxp guest start failed, Vadim Rozenfeld, 2011/10/13
- Re: [Qemu-devel] balloon driver on winxp guest start failed, hkran, 2011/10/14
- Re: [Qemu-devel] balloon driver on winxp guest start failed, Vadim Rozenfeld, 2011/10/17
- Re: [Qemu-devel] balloon driver on winxp guest start failed, hkran, 2011/10/20
- Re: [Qemu-devel] balloon driver on winxp guest start failed, hkran, 2011/10/27