WinXP & Slow Network Startup (BallonService)

[Jorge Fábregas]

Hi everyone,

I'm running Fedora 19 (with Preview Repo) and just installed Windows XP
(media already had SP3) and applied all 100+ updates (no additional 3rd
party software installed) with VirtIO (on Net & SCSI controller).  I'm
running the latest virtio drivers.

I proceeded to install the SPICE Agent Tools and rebooted the VM and now
I can copy/paste from guest to host (very cool).  However, I noticed
that the network takes about 1.5 minutes to start.  I have the "show
icon when connected option" and  literally takes 1.5 minutes.   I
searched the mailing list's archive and there was a similar post but
apparently the situation there was related to the .NET framework (which
I don't have installed).

After some trial & error I finally pinpointed the problem to the
"BallonService" installed by the SPICE tools.  If I set the service to
"disabled" and reboot the VM the network starts right away.

Has anyone bumped into this?

Regards,
Jorge

[Tom Horsley]

On Thu, 26 Sep 2013 10:10:33 -0400
Jorge Fábregas wrote:

>  However, I noticed
>  that the network takes about 1.5 minutes to start. 
Yea, that happens on real XP hardware with all the updates
as well. Has something to do with .NET nonsense:

http://answers.microsoft.com/en-us/windows/forum/windows_xp-performance/k...

[Jorge Fábregas]

On 09/26/2013 10:36 AM, Tom Horsley wrote:
>  Yea, that happens on real XP hardware with all the updates
>  as well. Has something to do with .NET nonsense: 
I don't have the .NET framework installed so that's no my case as I
mentioned.  It's something related to the BallonService (installed by
the SPICE tools).

-- 
Jorge

[Cole Robinson]

On 09/26/2013 10:10 AM, Jorge Fábregas wrote:
>  Hi everyone,
>  
>  I'm running Fedora 19 (with Preview Repo) and just installed Windows XP
>  (media already had SP3) and applied all 100+ updates (no additional 3rd
>  party software installed) with VirtIO (on Net & SCSI controller).  I'm
>  running the latest virtio drivers.
>  
>  I proceeded to install the SPICE Agent Tools and rebooted the VM and now
>  I can copy/paste from guest to host (very cool).  However, I noticed
>  that the network takes about 1.5 minutes to start.  I have the "show
>  icon when connected option" and  literally takes 1.5 minutes.   I
>  searched the mailing list's archive and there was a similar post but
>  apparently the situation there was related to the .NET framework (which
>  I don't have installed).
>  
>  After some trial & error I finally pinpointed the problem to the
>  "BallonService" installed by the SPICE tools.  If I set the service to
>  "disabled" and reboot the VM the network starts right away.
>  
>  Has anyone bumped into this? 
Haven't heard of that myself. Please file a bug in bugzilla.redhat.com
Fedora->virtio-win, and basically report what you posted here, along with
virtio driver versions, spice tools link, etc.

Thanks,
Cole

[Vadim Rozenfeld]

----- Original Message -----
From: "Cole Robinson" <crobinso(a)redhat.com&gt;
To: "Jorge Fábregas" <jorge.fabregas(a)gmail.com&gt;
Cc: virt(a)lists.fedoraproject.org
Sent: Friday, September 27, 2013 9:00:23 AM
Subject: Re: [fedora-virt] WinXP & Slow Network Startup (BallonService)

On 09/26/2013 10:10 AM, Jorge Fábregas wrote:
>  Hi everyone,
>  
>  I'm running Fedora 19 (with Preview Repo) and just installed Windows XP
>  (media already had SP3) and applied all 100+ updates (no additional 3rd
>  party software installed) with VirtIO (on Net & SCSI controller).  I'm
>  running the latest virtio drivers.
>  
>  I proceeded to install the SPICE Agent Tools and rebooted the VM and now
>  I can copy/paste from guest to host (very cool).  However, I noticed
>  that the network takes about 1.5 minutes to start.  I have the "show
>  icon when connected option" and  literally takes 1.5 minutes.   I
>  searched the mailing list's archive and there was a similar post but
>  apparently the situation there was related to the .NET framework (which
>  I don't have installed).
>  
>  After some trial & error I finally pinpointed the problem to the
>  "BallonService" installed by the SPICE tools.  If I set the service to
>  "disabled" and reboot the VM the network starts right away.
>  
>  Has anyone bumped into this? 
[VR]
https://bugzilla.redhat.com/show_bug.cgi?id=1000158 


Haven't heard of that myself. Please file a bug in bugzilla.redhat.com
Fedora->virtio-win, and basically report what you posted here, along with
virtio driver versions, spice tools link, etc.

Thanks,
Cole

_______________________________________________
virt mailing list
virt(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/virt

[Jorge Fábregas]

On 09/26/2013 08:02 PM, Vadim Rozenfeld wrote:
>  [VR]
>  https://bugzilla.redhat.com/show_bug.cgi?id=1000158  
Hello Vadim,

Should I open the bug as Cole suggested ? or is it Windows XP - or the
ballon & XP combination-  not really supported with Fedora 19 as a host?

Thanks,
Jorge

[Vadim Rozenfeld]

On Thu, 2013-09-26 at 20:44 -0400, Jorge Fábregas wrote:
>  On 09/26/2013 08:02 PM, Vadim Rozenfeld wrote:
>  > [VR]
>  > https://bugzilla.redhat.com/show_bug.cgi?id=1000158 
>  
>  Hello Vadim,
>  
>  Should I open the bug as Cole suggested ? or is it Windows XP - or the
>  ballon & XP combination-  not really supported with Fedora 19 as a host?
>  
>  Thanks,
>  Jorge 
Hello Jorge,

Balloon kernel mode driver should work on any supported Windows guest.
Balloon user mode service has a bug which was recently fixed.

Feel free to open a new bug in Bugzilla for Product - "Fedora"
and Component - "virtio-win" tracing the problem.

Best regards,
Vadim.

[Jorge Fábregas]

On 09/27/2013 06:56 AM, Vadim Rozenfeld wrote:
>  Feel free to open a new bug in Bugzilla for Product -
> "Fedora"
>  and Component - "virtio-win" tracing the problem. 
Thanks. I'm doing a fresh installation and recording every step in order
to recreate the problem.  If I can recreate it I'll open bug right away.

-- 
Jorge

[Jorge Fábregas]

On 09/27/2013 06:56 AM, Vadim Rozenfeld wrote:
>  Feel free to open a new bug in Bugzilla for Product -
> "Fedora"
>  and Component - "virtio-win" tracing the problem. 
Bug created with very detailed instructions on how to recreate the issue:

https://bugzilla.redhat.com/show_bug.cgi?id=1013025

--
Jorge