Created attachment 495252 [details]
sosreport of the host

Did you have win admin privileges while installing?
We'll release a newer driver in 6.1 anyway, so most chances this is not an issue.

(In reply to comment #0)
> ---Problem Description---
> Installation of balloon drivers fails while installing on a 64-bit Windows2008
> R2 Server Standard
> edition on RHEL6.1 Snap4 host.
> For verifying the memory ballooning feature, boot the guest using the
> virtio-win iso.
> While installing the Balloon driver, below error is noticed in a command
> prompt:
> Failed: Error 1063 : The service process couldnot connect to the service
> controller.
> 
> 
> ---uname output---
> Linux mx3650b.in.ibm.com 2.6.32-131.0.1.el6.x86_64 #1 SMP Tue Apr 12 16:40:23
> EDT 2011 x86_64 x86_64
> x86_64 GNU/Linux
> 
> Machine Type = x3650 
> 
> 
> ---Steps to Reproduce---
> 1. Install  Windows2008 R2 Server Standard edition as KVM guest on RHEL6.1
> host.
> 2. For verifying the memory ballooning feature, boot the guest using the
> virtio-win iso.
> Below command is used for booting the guest:
> /usr/libexec/qemu-kvm -drive file=/var/lib/libvirt/images/windows2008-64.img
> --balloon virtio -cdrom
> /usr/share/virtio-win/virtio-win-1.1.16.iso -m 1500 -smp 3 -net nic -net
> tap,script=/home/qemu-ifup-latest -vnc :3
> 
> 3. After the CDROM is available in the guest, Open it, go to Balloon, 2k8, x86, 
> 
> 4. Double-click on blnsvr for installing the driver.

blnsvr is not for installing balloon driver. 
Balloon driver can be installed by updating Standard PCI RAM controller
driver in Device Manager. 
blnsvr is a user mode service for collecting memory usage statistics.
It can be installed by running the following command "blnsvr -i" (use "-u"
for uninstall)     
> 
> 5. A command prompt appears for < 1sec, where the below error is noticed, and
> then it exits.
> Failed: Error 1063 : The service process couldnot connect to the service
> controller.
> 
> Machine details :
> --------------------
> Kernel version: 2.6.32-131.0.1.el6.x86_64
> 
> Qemu version: qemu-kvm-0.12.1.2-2.158.el6.x86_64
> 
> Guest OS:  Windows2008 R2 64-bit.
> 
> Guest OS Image storage type:  local file
> 
> Host Machine Type: x3650
> 
> Test Type:  Manual
> 
> Qemu Command Line:  /usr/libexec/qemu-kvm -drive
> file=/var/lib/libvirt/images/windows2008-64.img
> --balloon virtio -cdrom /usr/share/virtio-win/virtio-win-1.1.16.iso -m 1500
> -smp 3 -net nic -net
> tap,script=/home/qemu-ifup-latest -vnc :3
> 
> Using libvirt or not? Yes
> 
> Virtio ISO : virtio-win-1.1.16.iso
> 
> logs 
> -----
> sosreport of the host

------- Comment From santwana.samantray.com 2011-04-28 02:57 EDT-------
Hello Redhat,

I was able to install the virtio balloon drivers by updating Standard PCI RAM controller driver in Device Manager. However, after the driver was installed, I tried ballooning using virsh as below:
[root@mx3650b ~]# virsh qemu-monitor-command --hmp windows2008-64 "info balloon"
balloon: actual=1512

[root@mx3650b ~]# virsh qemu-monitor-command --hmp windows2008-64 "balloon 1300"

[root@mx3650b ~]# virsh qemu-monitor-command --hmp windows2008-64 "info balloon"
balloon: actual=1300

But the changed value of memory isn't getting reflected in the guest. It still shows 1500 MB instead of 1300MB.
Also, after rebooting the guest the ballooning value is changed from 1300 back to 1500MB in the monitor.

Thanks,
Santwana

(In reply to comment #5)
> ------- Comment From santwana.samantray.com 2011-04-28 02:57 EDT-------
> Hello Redhat,
> 
> I was able to install the virtio balloon drivers by updating Standard PCI RAM
> controller driver in Device Manager. However, after the driver was installed, I
> tried ballooning using virsh as below:
> [root@mx3650b ~]# virsh qemu-monitor-command --hmp windows2008-64 "info
> balloon"
> balloon: actual=1512
> 
> [root@mx3650b ~]# virsh qemu-monitor-command --hmp windows2008-64 "balloon
> 1300"
> 
> [root@mx3650b ~]# virsh qemu-monitor-command --hmp windows2008-64 "info
> balloon"
> balloon: actual=1300
> 
> But the changed value of memory isn't getting reflected in the guest. It still
> shows 1500 MB instead of 1300MB.
Do you mean Total Physical Memory or what?

> Also, after rebooting the guest the ballooning value is changed from 1300 back
> to 1500MB in the monitor.

Balloon is not persistent between reboots, but 
it knows how to survive between hibernate/resume events. 
> 
> Thanks,
> Santwana

------- Comment From santwana.samantray.com 2011-04-28 08:34 EDT-------
(In reply to comment #9)
> (In reply to comment #5)
> > Hello Redhat,
> >
> > I was able to install the virtio balloon drivers by updating Standard PCI RAM
> > controller driver in Device Manager. However, after the driver was installed, I
> > tried ballooning using virsh as below:
> > [root@mx3650b ~]# virsh qemu-monitor-command --hmp windows2008-64 "info
> > balloon"
> > balloon: actual=1512
> >
> > [root@mx3650b ~]# virsh qemu-monitor-command --hmp windows2008-64 "balloon
> > 1300"
> >
> > [root@mx3650b ~]# virsh qemu-monitor-command --hmp windows2008-64 "info
> > balloon"
> > balloon: actual=1300
> >
> > But the changed value of memory isn't getting reflected in the guest. It still
> > shows 1500 MB instead of 1300MB.
> Do you mean Total Physical Memory or what?

Yes, I meant the Total Physical Memory. I checked in the Memory usage monitor tab, it was listing the Total Physical Memory as 1500MB, instead of the changed value.

> > Also, after rebooting the guest the ballooning value is changed from 1300 back
> > to 1500MB in the monitor.
> Balloon is not persistent between reboots, but
> it knows how to survive between hibernate/resume events.
> >
> > Thanks,
> > Santwana

Thanks,
Santwana

(In reply to comment #7)
> Yes, I meant the Total Physical Memory. I checked in the Memory usage monitor
> tab, it was listing the Total Physical Memory as 1500MB, instead of the changed
> value.
> 
Total amount of physical memory reported by Windows will be always the same.
Balloon is not equal to hot-add memory. It just tries to abuse memory by allocating pages from non-paged pool, and giving control over them to the hypervisor. But guest still thinks that it has the same amount
of memory as it was reported on boot.

Best regards,
Vadim.

------- Comment From ryanh.com 2011-04-28 13:42 EDT-------
Is there any way to observe the size/value of the balloon from a guest visible perspective?    In linux, we can observe /proc/meminfo changes as the balloon size changes.  What's the equivalent for Windows?

(In reply to comment #9)
> ------- Comment From ryanh.com 2011-04-28 13:42 EDT-------
> Is there any way to observe the size/value of the balloon from a guest visible
> perspective?    In linux, we can observe /proc/meminfo changes as the balloon
> size changes.  What's the equivalent for Windows?

There is nothing like this in Windows. You can roughly estimate the balloon size by monitoring non-paged pool size, but I wouldn't go this way. The best solution will be making balloon size visible to user mode through WMI or IOCTL interface. But it means that balloon driver needs to be WHQL retested and resigned once again.

------- Comment From ryanh.com 2011-04-28 16:35 EDT-------
A balloon driver is a cooperative device so Windows has to know at somone level the amount of memory is has allocated.  Are you saying that this information is not exported in any way for the rest of the operation system to view?  Hence the discussion about an IOCTL?  Is there a debug mode of the driver which could be used to validate that the balloon driver is actually working?

(In reply to comment #11)
> ------- Comment From ryanh.com 2011-04-28 16:35 EDT-------
> A balloon driver is a cooperative device so Windows has to know at somone level
> the amount of memory is has allocated.
>Are you saying that this information is not exported in any way for the rest of >the operation system to view?
Correct. 
Once it was a special handler for reporting the balloon size via WMI, 
but it is not here anymore. 
>Hence the discussion about an IOCTL?
Yes.
>  Is there a debug mode of the driver which could be used to validate that the 
> balloon driver is actually working?
You can use Task Manager for monitoring Available Physical Memory value.
From the host side, you can try inflating the balloon continuously, at some point you will see that you cannot increase the balloon size any more.

------- Comment From santwana.samantray.com 2011-04-29 06:54 EDT-------
(In reply to comment #15)
> (In reply to comment #11)
> > A balloon driver is a cooperative device so Windows has to know at somone level
> > the amount of memory is has allocated.
> >Are you saying that this information is not exported in any way for the rest of >the operation system to view?
> Correct.
> Once it was a special handler for reporting the balloon size via WMI,
> but it is not here anymore.
> >Hence the discussion about an IOCTL?
> Yes.
> >  Is there a debug mode of the driver which could be used to validate that the
> > balloon driver is actually working?
> You can use Task Manager for monitoring Available Physical Memory value.
> From the host side, you can try inflating the balloon continuously, at some
> point you will see that you cannot increase the balloon size any more.

After ballooning, the Total available physical memory in the Task Manager still shows 1499MB. It doesn't reflect the ballooning value.

(In reply to comment #13)
> After ballooning, the Total available physical memory in the Task Manager still
> shows 1499MB. It doesn't reflect the ballooning value.

They call it "Free" in W2K8. In general, you must be able to increase the balloon size to this value.

Can we close it?

------- Comment From santwana.samantray.com 2011-05-10 08:11 EDT-------
Hello Redhat,

While installing the balloon drivers for Windows2008 32-bit guest by updating Standard PCI RAM
controller driver in Device Manager , its failing with the below error:
"Windows encountered a problem installing the driver software for your device. Windows found driver software for your device but encountered an error while attempting to install it.
VirtIO Balloon Driver

Driver is not intended for this platform."

The version of Windows2008 32-bit is" en_windows_server_2008_datacenter_enterprise_standard_sp2_x86_dvd_342333.iso"

The version of virtio is : "virtio-win-1.2.0-1.el6.noarch"

Should we open a separate bug for this issue? Please share your thoughts.

Thanks,
Santwana

(In reply to comment #16)
> ------- Comment From santwana.samantray.com 2011-05-10 08:11 EDT-------
> Hello Redhat,
> 
> While installing the balloon drivers for Windows2008 32-bit guest by updating
> Standard PCI RAM
> controller driver in Device Manager , its failing with the below error:
> "Windows encountered a problem installing the driver software for your device.
> Windows found driver software for your device but encountered an error while
> attempting to install it.
> VirtIO Balloon Driver
> 
> Driver is not intended for this platform."
Sounds like you are trying to install 64-bit driver on 32-bit OS.
But I need to see C:\WINDOWS\setupapi.log file from your system,
to say it for sure.
> 
> The version of Windows2008 32-bit is"
> en_windows_server_2008_datacenter_enterprise_standard_sp2_x86_dvd_342333.iso"
> 
> The version of virtio is : "virtio-win-1.2.0-1.el6.noarch"
> 
> Should we open a separate bug for this issue? Please share your thoughts.
>
Let's keep this bug open and use it for communicating about balloon related issues.

Best regards,
Vadim. 
> Thanks,
> Santwana

------- Comment From santwana.samantray.com 2011-05-16 02:47 EDT-------
Hello Redhat,

While verifying the USB Device feature for windows guest, the driver installation for USB failed. The USB Device was plugged into the host system. This issue is noticed for both 32 and 64-bit Windows2008 guest.

Below is the error noticed, "Could not load driver software. Windows was able to successfully load device driver software, but the driver software encountred a problem when it tried to run.The problem code is 10."

Should we open a separate bug for USB Driver installation failure?

Will there be any newer version of virtio drivers available which solves the virtio balloon driver issue for Windows2008-32 bit guest and USB Driver installation failures.

Please let us know.

Thanks,
Santwana

(In reply to comment #19)
> ------- Comment From santwana.samantray.com 2011-05-16 02:47 EDT-------
> Hello Redhat,
> 
> While verifying the USB Device feature for windows guest, the driver
> installation for USB failed. The USB Device was plugged into the host system.
> This issue is noticed for both 32 and 64-bit Windows2008 guest.
> 
> Below is the error noticed, "Could not load driver software. Windows was able
> to successfully load device driver software, but the driver software encountred
> a problem when it tried to run.The problem code is 10."

Code 10 usually means a "resource allocation" problem.

> 
> Should we open a separate bug for USB Driver installation failure?
Let's try to find the root of the problem first:
- Was the balloon driver installed and running during this test?
- If yes, was it inflated?
- If it was, what was the amount of "Free" memory on the system (VM).
- Is it reproducible? 
- Is it reproducible with deflated balloon?
- What kind of USB device it was? 
> 
> Will there be any newer version of virtio drivers available which solves the
> virtio balloon driver issue for Windows2008-32 bit guest and USB Driver
> installation failures.
> 

I don't think that something is broken inside of balloon. But I can imagine 
the situation when balloon is fully inflated, the system is running almost out of free memory, PnP manager triggered a new USB device arrival event and trying
to load an appropriate driver, driver is trying to allocate some memory from 
paged/non-paged pools, but there is no free memory in the system ...  

Best regards,
Vadim.

> Please let us know.
> 
> Thanks,
> Santwana

------- Comment From santwana.samantray.com 2011-05-16 05:25 EDT-------
(In reply to comment #25)
> (In reply to comment #19)
> > Hello Redhat,
> >
> > While verifying the USB Device feature for windows guest, the driver
> > installation for USB failed. The USB Device was plugged into the host system.
> > This issue is noticed for both 32 and 64-bit Windows2008 guest.
> >
> > Below is the error noticed, "Could not load driver software. Windows was able
> > to successfully load device driver software, but the driver software encountred
> > a problem when it tried to run.The problem code is 10."
> Code 10 usually means a "resource allocation" problem.
> >
> > Should we open a separate bug for USB Driver installation failure?
> Let's try to find the root of the problem first:
> - Was the balloon driver installed and running during this test?
> - If yes, was it inflated?
> - If it was, what was the amount of "Free" memory on the system (VM).
> - Is it reproducible?
> - Is it reproducible with deflated balloon?

The balloon driver wasn't installed since we are facing problems while
installing the drivers on a Windows2008-32 bit guest.
Also for a 64-bit Windows2008 guest, this scenario was tried when ballooning
wasn't active on the guest.
The guest has free memory of 3484MB.

> - What kind of USB device it was?
A USB-pendrive was plugged into the host. I attached the same usb device to the
guest,using the host's <vendorid>:<productid> which was successful. But, the
driver installation fails.
If the scenario is supported, I feel we can raise a separate bug to track this
issue, since the USB Driver installation failure is happening without the
balloon driver.

> >
> > Will there be any newer version of virtio drivers available which solves the
> > virtio balloon driver issue for Windows2008-32 bit guest and USB Driver
> > installation failures.
> >
> I don't think that something is broken inside of balloon. But I can imagine
> the situation when balloon is fully inflated, the system is running almost out
> of free memory, PnP manager triggered a new USB device arrival event and trying
> to load an appropriate driver, driver is trying to allocate some memory from
> paged/non-paged pools, but there is no free memory in the system ...
> Best regards,
> Vadim.
> > Please let us know.
> >
> > Thanks,
> > Santwana

(In reply to comment #21)
> > - What kind of USB device it was?
> A USB-pendrive was plugged into the host. I attached the same usb device to the
> guest,using the host's <vendorid>:<productid> which was successful. But, the
> driver installation fails.
> If the scenario is supported, I feel we can raise a separate bug to track this
> issue, since the USB Driver installation failure is happening without the
> balloon driver.
> 

Sure, please do it.
Btw, do you have any other problems related to balloon driver?

Regards,
Vadim.

------- Comment From santwana.samantray.com 2011-05-16 07:03 EDT-------
(In reply to comment #28)
> (In reply to comment #21)
> > > - What kind of USB device it was?
> > A USB-pendrive was plugged into the host. I attached the same usb device to the
> > guest,using the host's <vendorid>:<productid> which was successful. But, the
> > driver installation fails.
> > If the scenario is supported, I feel we can raise a separate bug to track this
> > issue, since the USB Driver installation failure is happening without the
> > balloon driver.
> Sure, please do it.
> Btw, do you have any other problems related to balloon driver?

Yes, the balloon driver fails to install on Windows2008-32 bit guest. After booting the guest with the virtio-win-1.2.0.iso, when I try to update the Standard PCI RAM controller in device manager, it asks for the location of the driver software.
On specifying the location, it begins to install the driver but fails with the error "Windows encountered a problem installing the driver software for your device. Windows found driver software for your device but encountered an error while attempting to install it. VirtIO Balloon Driver. Driver is not intended for this platform."

I didn't choose the 64-bit driver for this 32-bit O/S.
Also, when I checked C:\WINDOWS\setupapi.log , it lists "The location of the SetupAPI log file has been changed. The new location is D:\Windows\INF"
I couldn't locate the setupapi.log since D: is the CDROM drive.

> Regards,
> Vadim.

(In reply to comment #23)
> I didn't choose the 64-bit driver for this 32-bit O/S.
> Also, when I checked C:\WINDOWS\setupapi.log , it lists "The location of the
> SetupAPI log file has been changed. The new location is D:\Windows\INF"
> I couldn't locate the setupapi.log since D: is the CDROM drive.

It must be just a copy from the installation disk. Please try C:\Windows\INF.
I need to see setupapi.app and setupapi.dev (this one can be pretty big).
 
> 
> > Regards,
> > Vadim.

Created attachment 499307 [details]
Logs for setupapi.app and setupapi.dev


------- Comment on attachment From santwana.samantray.com 2011-05-17 06:51 EDT-------


Hello Redhat,

I have created attachment for setupapi.app and setupapi.dev.

Thanks,
Santwana

(In reply to comment #25)
> Created attachment 499307 [details]
> Logs for setupapi.app and setupapi.dev
> 
> 
> ------- Comment on attachment From santwana.samantray.com 2011-05-17
> 06:51 EDT-------
> 
> 
> Hello Redhat,
> 
> I have created attachment for setupapi.app and setupapi.dev.
> 
> Thanks,
> Santwana

Seems like you are trying to install balloon driver from Wnet subdirectory.
Balloon driver in this directory is signed for Windows XP and Windows Server 2003 only. Windows 2008 balloon can be found in Win7 subdirectory.

Best regards,
Vadim.

------- Comment From santwana.samantray.com 2011-05-18 01:59 EDT-------
(In reply to comment #32)
> (In reply to comment #25)
> > Created attachment 499307 [details]
> > Logs for setupapi.app and setupapi.dev
> > ------- Comment on attachment From santwana.samantray.com 2011-05-17
> > 06:51 EDT-------
> > Hello Redhat,
> >
> > I have created attachment for setupapi.app and setupapi.dev.
> >
> > Thanks,
> > Santwana
> Seems like you are trying to install balloon driver from Wnet subdirectory.
> Balloon driver in this directory is signed for Windows XP and Windows Server
> 2003 only. Windows 2008 balloon can be found in Win7 subdirectory.
> Best regards,
> Vadim.

For installing the balloon driver, I right-clicked on the Unknown device in Device Manager and choose "Update Driver Software". Then it asks for location, to which I choose "Browse my computer for driver software".
After that I select the "D:\" which is the virtio-win-1.2.0, there is a checkbox which says "Include subfolders", which was also marked. Clicking on Next, installation begins which ends in failure.
Also, specifying the location as "D:\Balloon\w7" fails to install the driver.
The same steps worked fine for Windows2008-64 bit guest , whereas its not working for Windows2008- 32 bit guest.
The auto-detection and installation of the Balloon driver from the ISO is failing for the 32-bit guest.

Thanks,
Santwana

(In reply to comment #27)

> For installing the balloon driver, I right-clicked on the Unknown device in

Why "Unknown"? Balloon driver can be installed on top "PCI Standard RAM Controller" only. Anyway, can you right-click on this "Unknown" device, go to Properties->Resources and post the resource settings?
Best regards,
Vadim.

> Device Manager and choose "Update Driver Software". Then it asks for location,
> to which I choose "Browse my computer for driver software".
> After that I select the "D:\" which is the virtio-win-1.2.0, there is a
> checkbox which says "Include subfolders", which was also marked. Clicking on
> Next, installation begins which ends in failure.
> Also, specifying the location as "D:\Balloon\w7" fails to install the driver.
> The same steps worked fine for Windows2008-64 bit guest , whereas its not
> working for Windows2008- 32 bit guest.
> The auto-detection and installation of the Balloon driver from the ISO is
> failing for the 32-bit guest.
> 
> Thanks,
> Santwana

------- Comment From santwana.samantray.com 2011-05-19 01:57 EDT-------
(In reply to comment #34)
> (In reply to comment #27)
> > For installing the balloon driver, I right-clicked on the Unknown device in
> Why "Unknown"? Balloon driver can be installed on top "PCI Standard RAM
> Controller" only. Anyway, can you right-click on this "Unknown" device, go to
> Properties->Resources and post the resource settings?
> Best regards,
> Vadim.

The Resource settings lists out, "This device isn't using any resources because
it has a problem"

Thanks,
Santwana

(In reply to comment #29)
> ------- Comment From santwana.samantray.com 2011-05-19 01:57 EDT-------
> (In reply to comment #34)
> > (In reply to comment #27)
> > > For installing the balloon driver, I right-clicked on the Unknown device in
> > Why "Unknown"? Balloon driver can be installed on top "PCI Standard RAM
> > Controller" only. Anyway, can you right-click on this "Unknown" device, go to
> > Properties->Resources and post the resource settings?
> > Best regards,
> > Vadim.
> 
Installed balloon on my W2K8-32 system with the following steps:
- run Device Manager,
- go to System Devices and right-click on PCI Standard Ram Controller,
- Update Driver Software,
- Browse my computer for driver software,
- Browse -> Computer -> CD Drive (D:) -> Balloon -> 2k8 ->x86 -> OK
- Have Disk ->  CD Drive (D:) -> Balloon -> 2k8 ->x86 -> Open
- you will see balloon.inf here. Click on "Open" again.  
- In "Install From Disk" dialog click on OK,
- Now you must see "VirtIO Balloon Driver" as a compatible hardware,
- Press on Next,
- After a few moments you will see a message saying that "Windows has 
successfully updated your driver software",
- press on "Close" and check "System devices" again. Now 
you should see "VirtIO Balloon Driver" installed on your system.
> The Resource settings lists out, "This device isn't using any resources because
> it has a problem"
Can you try "info pci" command from the qemu console? I'd like to know
who this mysterious "Unknown" device is.

Best regards,
Vadim. 
 
> 
> Thanks,
> Santwana

------- Comment From santwana.samantray.com 2011-05-20 02:00 EDT-------
(In reply to comment #37)
> (In reply to comment #29)
> > (In reply to comment #34)
> > > (In reply to comment #27)
> > > > For installing the balloon driver, I right-clicked on the Unknown device in
> > > Why "Unknown"? Balloon driver can be installed on top "PCI Standard RAM
> > > Controller" only. Anyway, can you right-click on this "Unknown" device, go to
> > > Properties->Resources and post the resource settings?
> > > Best regards,
> > > Vadim.
> Installed balloon on my W2K8-32 system with the following steps:
> - run Device Manager,
> - go to System Devices and right-click on PCI Standard Ram Controller,
> - Update Driver Software,
> - Browse my computer for driver software,
> - Browse -> Computer -> CD Drive (D:) -> Balloon -> 2k8 ->x86 -> OK
> - Have Disk ->  CD Drive (D:) -> Balloon -> 2k8 ->x86 -> Open
> - you will see balloon.inf here. Click on "Open" again.
> - In "Install From Disk" dialog click on OK,
> - Now you must see "VirtIO Balloon Driver" as a compatible hardware,
> - Press on Next,
> - After a few moments you will see a message saying that "Windows has
> successfully updated your driver software",
> - press on "Close" and check "System devices" again. Now
> you should see "VirtIO Balloon Driver" installed on your system.
> > The Resource settings lists out, "This device isn't using any resources because
> > it has a problem"
> Can you try "info pci" command from the qemu console? I'd like to know
> who this mysterious "Unknown" device is.
> Best regards,
> Vadim.

Hello Redhat,

When we boot the guest with the below options:

/usr/libexec/qemu-kvm -drive file=/var/lib/libvirt/images/new-windows2008-32.img -cdrom /usr/share/virtio-win/virtio-win-1.2.0.iso --balloon virtio -net nic -net tap,script=/home/qemu-ifup-latest -m 1500 -name windows -vnc :2

As soon as we login, a dialog box pops-up which says,
"Windows need to install driver software for your PCI Memory"
It has below 3 options:

* Locate and install driver software (recommended)
* Ask me again later
* Don't show this message again for this device

When we select, Locate and install driver software, the error is encountered,
"Windows encountered a problem installing the driver software for your
device. Windows found driver software for your device but encountered an error
while attempting to install it. VirtIO Balloon Driver. Driver is not intended
for this platform."

The auto installation of the VirtIO balloon driver is failing.

In the qemu monitor console, the "info pci" for the "Unknown" Device is as below:
RAM Controller: PCI device 1af4:1002
IRQ 11
BAR0: I/O at 0xc200 [0xc21f]
id ""

When , we select the following steps:
- go to System Devices and right-click on Unknown Device.
- Browse -> Computer -> CD Drive (D:) -> Balloon -> 2k8 ->FAILS
Installation fails,
When we select
- Browse -> Computer -> CD Drive (D:) -> Balloon -> 2k8 -> x86 - PASSES

Basically, when we specify the complete path, now installation happens fine.

Is the auto-installation of the VirtIO drivers, working fine in your setup?
For the windows2008-64 bit guest, it works fine. Issue is only there for the 32-bit guest.

Version of virtio iso: virtio-win-1.2.0.iso

Santwana

(In reply to comment #31)
> Hello Redhat,
> 
> When we boot the guest with the below options:
> 
> /usr/libexec/qemu-kvm -drive
> file=/var/lib/libvirt/images/new-windows2008-32.img -cdrom
> /usr/share/virtio-win/virtio-win-1.2.0.iso --balloon virtio -net nic -net
> tap,script=/home/qemu-ifup-latest -m 1500 -name windows -vnc :2
> 
> As soon as we login, a dialog box pops-up which says,
> "Windows need to install driver software for your PCI Memory"
> It has below 3 options:
> 
> * Locate and install driver software (recommended)
> * Ask me again later
> * Don't show this message again for this device
> 
> When we select, Locate and install driver software, the error is encountered,
> "Windows encountered a problem installing the driver software for your
> device. Windows found driver software for your device but encountered an error
> while attempting to install it. VirtIO Balloon Driver. Driver is not intended
> for this platform."
> 
> The auto installation of the VirtIO balloon driver is failing.
> 
> In the qemu monitor console, the "info pci" for the "Unknown" Device is as
> below:
> RAM Controller: PCI device 1af4:1002
> IRQ 11
> BAR0: I/O at 0xc200 [0xc21f]
> id ""
> 
Everything seems to be fine. I really don't know why Windows named it "Unknown".
It should be "PCI Standard RAM Controller", just as it defined in machine.inf file.   
> When , we select the following steps:
> - go to System Devices and right-click on Unknown Device.
> - Browse -> Computer -> CD Drive (D:) -> Balloon -> 2k8 ->FAILS
> Installation fails,
> When we select
> - Browse -> Computer -> CD Drive (D:) -> Balloon -> 2k8 -> x86 - PASSES
> 
> Basically, when we specify the complete path, now installation happens fine.
> 
> Is the auto-installation of the VirtIO drivers, working fine in your setup?
> For the windows2008-64 bit guest, it works fine. Issue is only there for the
> 32-bit guest.
> 

Unfortunately, the auto-installation will not work for the current iso image layout. 

Best regards,
Vadim.

> Version of virtio iso: virtio-win-1.2.0.iso
> 
> Santwana

------- Comment From santwana.samantray.com 2011-05-23 06:11 EDT-------
(In reply to comment #39)
> (In reply to comment #31)
> > Hello Redhat,
> > When we boot the guest with the below options:
> > /usr/libexec/qemu-kvm -drive
> > file=/var/lib/libvirt/images/new-windows2008-32.img -cdrom
> > /usr/share/virtio-win/virtio-win-1.2.0.iso --balloon virtio -net nic -net
> > tap,script=/home/qemu-ifup-latest -m 1500 -name windows -vnc :2
> > As soon as we login, a dialog box pops-up which says,
> > "Windows need to install driver software for your PCI Memory"
> > It has below 3 options:
> >
> > * Locate and install driver software (recommended)
> > * Ask me again later
> > * Don't show this message again for this device
> >
> > When we select, Locate and install driver software, the error is encountered,
> > "Windows encountered a problem installing the driver software for your
> > device. Windows found driver software for your device but encountered an error
> > while attempting to install it. VirtIO Balloon Driver. Driver is not intended
> > for this platform."
> >
> > The auto installation of the VirtIO balloon driver is failing.
> >
> > In the qemu monitor console, the "info pci" for the "Unknown" Device is as
> > below:
> > RAM Controller: PCI device 1af4:1002
> > IRQ 11
> > BAR0: I/O at 0xc200 [0xc21f]
> > id ""
> >
> Everything seems to be fine. I really don't know why Windows named it
> "Unknown".
> It should be "PCI Standard RAM Controller", just as it defined in machine.inf
> file.
> > When , we select the following steps:
> > - go to System Devices and right-click on Unknown Device.
> > - Browse -> Computer -> CD Drive (D:) -> Balloon -> 2k8 ->FAILS
> > Installation fails,
> > When we select
> > - Browse -> Computer -> CD Drive (D:) -> Balloon -> 2k8 -> x86 - PASSES
> >
> > Basically, when we specify the complete path, now installation happens fine.
> >
> > Is the auto-installation of the VirtIO drivers, working fine in your setup?
> > For the windows2008-64 bit guest, it works fine. Issue is only there for the
> > 32-bit guest.
> >
> Unfortunately, the auto-installation will not work for the current iso image
> layout.
> Best regards,
> Vadim.

Hello Vadim,

If auto-installation of the VirtIO Balloon driver is a known issue, will be there any latest iso where its fixed?
Or, we can close this bug .
Please share your thoughts.

Thanks,
Santwana

(In reply to comment #33)
> Hello Vadim,
> 
> If auto-installation of the VirtIO Balloon driver is a known issue, will be
> there any latest iso where its fixed?
> Or, we can close this bug .
> Please share your thoughts.
> 
> Thanks,
> Santwana

Hello Santwana,

I would like to make it working. Even more,
it can be easily done by strictly following
the MS platform and architecture naming patterns.
But some people prefer seeing "2k8" indstead
of "Wlh" and "x86" instead of "i386",
even though it goes against the rules.

I will forward your question to the relevant people,
and then, based on their answers, we'll see where we
can go from here.

Best regards,
Vadim.

(In reply to comment #34)
> (In reply to comment #33)
> > Hello Vadim,
> > 
> > If auto-installation of the VirtIO Balloon driver is a known issue, will be
> > there any latest iso where its fixed?
> > Or, we can close this bug .
> > Please share your thoughts.
> > 
> > Thanks,
> > Santwana
> 
> Hello Santwana,
> 
> I would like to make it working. Even more,
> it can be easily done by strictly following
> the MS platform and architecture naming patterns.
> But some people prefer seeing "2k8" indstead
> of "Wlh" and "x86" instead of "i386",
> even though it goes against the rules.
> 
> I will forward your question to the relevant people,
> and then, based on their answers, we'll see where we
> can go from here.
> 
> Best regards,
> Vadim.

Hello Santwana,

I have created a new bug, related to the automatic driver installation
problem - https://bugzilla.redhat.com/show_bug.cgi?id=708930

If you don't mind, let's close this bug as duplicated.

Best regards,
Vadim.

------- Comment From santwana.samantray.com 2011-05-31 08:29 EDT-------
(In reply to comment #42)
> > (In reply to comment #33)
> > > Hello Vadim,
> > >
> > > If auto-installation of the VirtIO Balloon driver is a known issue, will be
> > > there any latest iso where its fixed?
> > > Or, we can close this bug .
> > > Please share your thoughts.
> > >
> > > Thanks,
> > > Santwana
> > Hello Santwana,
> > I would like to make it working. Even more,
> > it can be easily done by strictly following
> > the MS platform and architecture naming patterns.
> > But some people prefer seeing "2k8" indstead
> > of "Wlh" and "x86" instead of "i386",
> > even though it goes against the rules.
> > I will forward your question to the relevant people,
> > and then, based on their answers, we'll see where we
> > can go from here.
> >
> I have created a new bug, related to the automatic driver installation
> problem - https://bugzilla.redhat.com/show_bug.cgi?id=708930
> If you don't mind, let's close this bug as duplicated.

Hello Vadim,

Thanks for opening the new bug for the automatic driver installation
problem . We can mark this bug as duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=708930. but still keep it open for tracking purpose. If we close this bug, then tracking the new bug might be difficult.
Let this bug be linked with the new bug.
Please share your thoughts.

Thanks,
Santwana

(In reply to comment #36)
> problem . We can mark this bug as duplicate of
> https://bugzilla.redhat.com/show_bug.cgi?id=708930. but still keep it open for
> tracking purpose. If we close this bug, then tracking the new bug might be
> difficult.
> Let this bug be linked with the new bug.

OK. 
I will target it on 6.2.
Kind regards,
Vadim.
> Please share your thoughts.
> 
> Thanks,
> Santwana

*** This bug has been marked as a duplicate of bug 708930 ***