Bug 670986 - virtio-win: balloon driver unable to install on Windows 2008 x86_64
Summary: virtio-win: balloon driver unable to install on Windows 2008 x86_64
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virtio-win
Version: 6.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Vadim Rozenfeld
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 666139
TreeView+ depends on / blocked
 
Reported: 2011-01-19 20:41 UTC by Douglas Schilling Landgraf
Modified: 2011-07-07 01:53 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-23 02:53:36 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Douglas Schilling Landgraf 2011-01-19 20:41:01 UTC
Description of problem:

The PCI standard RAM Controller driver has the Location information the same as 
PCI device that kvm/qemu set for the memory ballooning driver (my test, PCI bus 0, device 5, function 0). 

How reproducible:

Try to install balloon driver following these steps:

1) # yum install virtio-win
2) Mount /usr/share/virtio-win/virtio-win.iso as CDROM to W2008 vm.
3) Copy from CDROM the Ballon Directory to C:
4) Download devcon utility and copy it to C:\Balloon\2k8\x86\
http://support.microsoft.com/kb/311272
5) Start -> Run -> cmd
   Go to C:\Balloon\2k8\x86\ directory

Execute:
#devcon install BALLOON.inf "PCI\VEN_1AF4&DEV_1002&SUBSYS_00051AF4&REV_00"
#blnsvr -i 

Actual results:
Cannot install balloon driver.

Expected results:
The balloon driver should install without any conflict.

Additional info:

Workaround:

Start -> Control Panel -> System -> Device Manager -> System devices -> PCI standard RAM Controller
On the driver Tab, select Update Driver -> Browse my computer
for driver -> Select C:\Balloon\2k8\amd64
 
Then, from DOS install the service:
C:\Balloon\2k8\amd64\blnsvr.exe -i

Reboot

Comment 2 Vadim Rozenfeld 2011-01-20 10:42:15 UTC
(In reply to comment #0)
> Description of problem:
> 
> The PCI standard RAM Controller driver has the Location information the same as 
> PCI device that kvm/qemu set for the memory ballooning driver (my test, PCI bus
> 0, device 5, function 0). 
> 
> How reproducible:
> 
> Try to install balloon driver following these steps:
> 
> 1) # yum install virtio-win
> 2) Mount /usr/share/virtio-win/virtio-win.iso as CDROM to W2008 vm.
> 3) Copy from CDROM the Ballon Directory to C:
> 4) Download devcon utility and copy it to C:\Balloon\2k8\x86\
> http://support.microsoft.com/kb/311272
> 5) Start -> Run -> cmd
>    Go to C:\Balloon\2k8\x86\ directory
> 
Hi Douglas.
Please correct me if I'm wrong, but
do you try to install 32-bit driver on 64-bit platform?
 
> Execute:
> #devcon install BALLOON.inf "PCI\VEN_1AF4&DEV_1002&SUBSYS_00051AF4&REV_00"
> #blnsvr -i 
> 
> Actual results:
> Cannot install balloon driver.
> 
> Expected results:
> The balloon driver should install without any conflict.
> 
> Additional info:
> 
> Workaround:
> 
> Start -> Control Panel -> System -> Device Manager -> System devices -> PCI
> standard RAM Controller
> On the driver Tab, select Update Driver -> Browse my computer
> for driver -> Select C:\Balloon\2k8\amd64
> 
> Then, from DOS install the service:
> C:\Balloon\2k8\amd64\blnsvr.exe -i
> 
> Reboot

Comment 3 Douglas Schilling Landgraf 2011-01-20 11:52:29 UTC
Hi Vadim,

> Hi Douglas.
> Please correct me if I'm wrong, but
> do you try to install 32-bit driver on 64-bit platform?

Sorry, it was just an example that I took from the previous BZ that I have opened.
https://bugzilla.redhat.com/show_bug.cgi?id=666139 which depends on this one.

Unfortunately, I don't have permission to edit the entry but the main point here is that it's not possible to install the balloon driver on Windows 2008 x86_64 because of the PCI standard RAM Controller driver. For while, I cannot see this issue on x86 versions.

Thanks
Douglas

Comment 4 Vadim Rozenfeld 2011-01-20 12:24:25 UTC
(In reply to comment #3)

> Unfortunately, I don't have permission to edit the entry but the main point
> here is that it's not possible to install the balloon driver on Windows 2008
> x86_64 because of the PCI standard RAM Controller driver. For while, I cannot

OK. I will re-check it shortly.
Best regards,
Vadim.
 
> see this issue on x86 versions.
> 
> Thanks
> Douglas

Comment 5 Vadim Rozenfeld 2011-01-20 20:47:04 UTC
(In reply to comment #4)
> (In reply to comment #3)
> 
> > Unfortunately, I don't have permission to edit the entry but the main point
> > here is that it's not possible to install the balloon driver on Windows 2008
> > x86_64 because of the PCI standard RAM Controller driver. For while, I cannot
> 
> OK. I will re-check it shortly.

I have checked amd64 version of devcon from WDK 7600.16385.0. Works like a charm.

btw, http://support.microsoft.com/kb/311272 has binaries from 2002.

Best regards,
Vadim.

Comment 6 Douglas Schilling Landgraf 2011-01-21 03:07:46 UTC
Hi Vadim,

> I have checked amd64 version of devcon from WDK 7600.16385.0. Works like a
> charm.
>
> btw, http://support.microsoft.com/kb/311272 has binaries from 2002.

Oh nice, you found the x86_64 version. So, if I understood correctly this work without need to update manually the driver? Just executed the devcon binary and worked like a charm?

Thanks
Douglas

Comment 7 Vadim Rozenfeld 2011-01-22 20:03:18 UTC
(In reply to comment #6)
> Hi Vadim,
> 
> > I have checked amd64 version of devcon from WDK 7600.16385.0. Works like a
> > charm.
> >
> > btw, http://support.microsoft.com/kb/311272 has binaries from 2002.
> 
> Oh nice, you found the x86_64 version. So, if I understood correctly this work
> without need to update manually the driver? Just executed the devcon binary and
> worked like a charm?
> 
> Thanks
> Douglas

Hi Douglas.
Yes, if you prefer devcon over device manager - you are welcome to use it. Just take one from the recent WDK. On the other hand - you can use device manager. 
It's just a matter of your choice. 
After all, both of them use the same functions from SetupApi.dll.
Best regards,
Vadim.

Comment 8 Douglas Schilling Landgraf 2011-01-23 02:43:41 UTC
Hello Vadim,

>    Hi Douglas.
> Yes, if you prefer devcon over device manager - you are welcome to use it. Just
> take one from the recent WDK. On the other hand - you can use device manager. 
> It's just a matter of your choice. 
> After all, both of them use the same functions from SetupApi.dll.
> Best regards,
> Vadim   

Cool, thanks for this update! Great job!

Cheers
Douglas

Comment 9 Douglas Schilling Landgraf 2011-01-23 02:53:36 UTC
With the previous update from Vadim, we can close this ticket. The only one that we can keep is the documentation procedure about the balloon driver.

Thanks
Douglas


Note You need to log in before you can comment on or make changes to this bug.