https://bugzilla.novell.com/show_bug.cgi?id=371579
User g.w.kant@hunenet.nl added comment
https://bugzilla.novell.com/show_bug.cgi?id=371579#c24
--- Comment #24 from Dion Kant 2008-04-10 16:49:56 MST ---
Thanks for the update. However, I ran into a remarkable phenomena when
downloading the .rpm. Not related to this bug id of course, but I would like to
share this possible race anyway.
I downloaded the patch with
dom0:~ # wget https://bugzilla.novell.com/attachment.cgi?id=207276 and at 56%,
the network subsystem (vifs) on all domUs completely stopped.
The configuration is as follows:
dom0 talks to the Internet via a cascade of two domUs. The standard bridged
network config is used:
dom0-eth0---xenbr0---eth0-domU1-eth1---xenbr2---eth0-domU2-eth1---Internet
The domU2-eth1 interface is a physical pci-passed-through interface and this
one is still working. I was logged in via ssh over the Internet on domU2 and
from there onto dom0 running the wget. Then I had to drive for one hour to go
to the site where the box is located. Logging in on the console(s) worked fine,
no signs of trouble (nothing logged) but no network. After a reboot I went home
(without testing the .rpm.)
Now you may think what is all this fuzz about? Well, when arrived home, I was
able to repeat the thing. This time on another box at a distance of a two hours
drive from my place (similar configuration), again at 56% download.
Conclusion: The network hangup is repeatable when using wget
https://bugzilla.novell.com/attachment.cgi?id=207276 in the configuration as
described. Does anybody else have seen similar problems? I will try to simplify
the configuration till the point where this still occurs. Then I will search
for a bug ID somewhere...
The good news is that virt-manager is fixed (tested by two persons). Thanks for
this.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.