[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] Network issue in dom0
Has anyone information about the bu Todd mentioned. Unfortuantely I couldn't find any information about it. And I'm still struggeling with the error...
Regards, Markus
On 30.01.2008, at 14:59, Todd Deshane wrote:
On Jan 30, 2008 4:52 AM, Markus Gerber < markus@xxxxxxxxxxxxx> wrote: Hi Todd, I just created a dummy interface and added it to a new bridge. Like this I can now access dom0 again from domU1 (which is the firewall/router) and vice versa. Respectifly I can access every machine in my different subnets and the internet fromdom0. But: I still have the problem that the network goes down when transfering a lot of data. It's not as bad as before, since dom0 now has it's own newtorksegment - the rest of the network is no longer affected and the users can work normally. But it's still not possible to copy a lot of data. It's no difference whether I copy (wget) data from the internet or from another local machine (scp). And I still can't find any log entry...
What else can I try? I think I remember a bug recently about someone with a similar network problem, but I think they had a crash when doing a large transfer. Does anyone else recall that? Maybe you can search the archives and also the bugs. I do think that it is probably some sort of bug though, as network io is known to work of course.
Thanks & regards, Markus
----- Ursprüngliche Nachricht ----- Von: "Todd Deshane" <deshantm@xxxxxxxxx> An: "Markus Gerber" <markus@xxxxxxxxxxxxx> Gesendet: Dienstag, 29. Januar 2008 17.02 Uhr (GMT+0100) Europe/Berlin Betreff: Re: [Xen-users] Network issue in dom0
Hi Markus,
You could setup a dummy device in dom0 and have it bridge with a private network of your domU1. If you look back within the last week or so. I gave some basic instructions on how to do this. Let me/the list know if you run into problems or have further questions on that.
Regards, Todd
On Jan 29, 2008 1:51 AM, Markus Gerber < markus@xxxxxxxxxxxxx> wrote: Hi Todd,
The idea of this setup is that I do not want to provide any service in dom0.
In domU1 I have all the NICs in it, since it is the router/firewall. The other domUs are in different subnets and have therefore access to different NICs (there are other servers - in the respective subnet - that are connected to the server).
My main question is how to best access dom0...
Thanks and regards, Markus
On 29.01.2008, at 05:32, Todd Deshane wrote:
On Jan 27, 2008 12:08 PM, Markus Gerber < markus@xxxxxxxxxxxxx> wrote: Hello,
I have a network issue in dom0; I'm not sure if it's a configuration problem or a design problem in my setup.
My setup: The server (dom0) runs Ubuntu 7.10, Xen was installed using apt-get (means version: Xen 3.10, Kernel 2.6.22-14). This server has 4 NICs. I use bridged networking with my own script which creates 4 bridges ("$dir/network-bridge" "$g" vifnum=0 netdev=eth0 bridge=xenbr0 - this line I use four times for each interface). This works great so far. /etc/network/interfaces in dom0 brings only up eth2 with a static address (10.10.1.2). domU1 acts as router/firewall and has all bridges connected to it. And every ethX in domU1 has it's own subnet (10.10.1.0/24 to 10.10.4.0/24). This works as well. My problem: Each time I download a lot of data (i.e. an apt-get upgrade which upgrades the kernel) in dom0, the network in dom0 freezes. Furthermore, the whole subnet 10.10.1.0/24 freezes. The network comes back after a couple of minutes or after a couple of hours. This varies. So far, I couldn't find any log, where I entry is made when the network stalles. I can't access any other net from within dom0 and dom0 can't be accessed from any other place.
My question: What could be the problem for this behaviour? Is there a better way to access dom0 from within domU1 (or any other domU)?
Thank you in advance for any tipps. I don't have any ideas yet. What is the purpose of this setup though?
Regards, Todd
Regards, Markus _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
_______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|