Red Hat Bugzilla – Bug 1013025
Windows XP: Slow Network Start because of BallonService
Last modified: 2015-01-09 23:25:40 EST
Description of problem:
I'm running Fedora 19 (with Virtualization Preview Repo, fully updated) and, on a newly installed Windows XP SP3 VM, after isntalling the SPICE guest tools (0.59) the network takes 1.5 minutes to start. I enabled the "show icon in notification area when connected" on the guest NIC and when you restart Windows, right after the Desktop appears, it takes 1 minute, 32 seconds for the network icon to appear.
After some trial & error I found out the BallonService to be the culprit. If I set the service to "disabled" and restart the VM the network starts right away.
I reinstalled the Windows VM in order to recreate the issue and was able to do so.
Version-Release number of selected component (if applicable):
VirtIO SCSI Controller (Driver Version): 184.108.40.20600
VirtIO Ethernet Adapter (Driver Version): 220.127.116.1100
SPICE Guest Tools: 0.59
# rpm -qa | egrep '(virt|qemu|kernel|spice)'
Steps to Reproduce:
(I used WinXP x86 media that already had Service Pack 3 applied)
1) install VM with:
--name WinXP-demo \
--os-variant winxp \
--ram 1024 \
--disk path=/var/lib/libvirt/images/winxpdemo-base.qcow2,bus=virtio,format=qcow2,cache=unsafe,size=8 \
--disk path=/var/lib/libvirt/isos/viostor-0.1-65-floppy.img,device=floppy \
--cdrom /var/lib/libvirt/isos/SW_CD_Windows_XP_Professional_32BIT_SP3.ISO \
2) First thing right after installation: Install virtio driver for NIC (Device Manager --> NIC --> Update driver and then insert virtio CD...)
3) Download WindowsUpdateAgent30-x86 here:
...and install it by:
a) net stop wuauserv
b) WindowsUpdateAgent30-x86.exe /wuforce /norestart
c) net start bits
p.d. we do all this is because if you run WindowsUpdate right after install it won't work.
4) Install IE8 for XP here:
p.d. this is also due to a bug where, when you run the update, it stays "Checking for Update" for minutes & minutes...
5) Finally go to WindowsUpdate:
a) apply all 120+ updates
c) apply remaining 2 updates on WindowsUpdate
6) Activate "Show icon in notification area when connected" on GUEST NIC properties. (so that we know when it comes up)
7) install SPICE Guest Tools 0.59 & restart
Network takes more than 1 minute to start
Network should come up right after the Desktop appears (a couple of seconds after).
If you disable the BallonService on the guest & restart, the network comes up normally.
Can you try latest virito-win-prewhql build (build 71) ,I think Vadim has fixed a balloon service bug recently .
Can you please point me to the executable (build 71)? I'm new to SPICE...
I think this bug is duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1000158 .
Regarding to build71 .It will be released after RHEL6.5 GA ,I am not sure how you can get it in fedora website .Ronen ?
On my system , when enabled, the BallonService is not a 100% (during the first 1.5 minute where network doesn't come up).
Can you please send Jorge the files. It is OK with us.
Indeed we are not updating the Fedora drivers yet.
Created attachment 804456 [details]
winxp build71 balloon&vioserial driver
Pls find the driver in attachment
Thanks for the files. I tried them now but still the same behaviour after a restart.
I first tried to install the files by executing the .exe files on the extracted zip but recieved this message:
StartServiceCtrlDispatcher failed, error code = 1063
I then proceeded to take all the files from the extracted zip and moved them to :
C:\Program Files\SPICE Guest Tools\drivers\winxp\x86\
...overriding existing ones (BallongService was down). I restarted the machine but still the same behaviour (network takes about 1.5 minute to start).
(In reply to Jorge Fábregas from comment #7)
> Thanks for the files. I tried them now but still the same behaviour after a
> I first tried to install the files by executing the .exe files on the
> extracted zip but recieved this message:
> StartServiceCtrlDispatcher failed, error code = 1063
> I then proceeded to take all the files from the extracted zip and moved them
> to :
> C:\Program Files\SPICE Guest Tools\drivers\winxp\x86\
> ...overriding existing ones (BallongService was down). I restarted the
> machine but still the same behaviour (network takes about 1.5 minute to
I'm going recheck it again.
Mike, can we try to reproduce this problem on our setup?
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 19 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.