JohnS wrote on Mon, 27 Apr 2009 11:09:56 -0400:
If you don't mind when you come to an answer would you please let me know. I am interested to know.
I could not find a real solution. I had to go to another way of creating the network setup for this machine (and maybe others, I will see) and disable the network-bridge script from xen. That new solution is documented on the xen-users mailing-list.
Kai
On Tue, 2009-04-28 at 23:31 +0200, Kai Schaetzl wrote:
JohnS wrote on Mon, 27 Apr 2009 11:09:56 -0400:
If you don't mind when you come to an answer would you please let me know. I am interested to know.
I could not find a real solution. I had to go to another way of creating the network setup for this machine (and maybe others, I will see) and disable the network-bridge script from xen. That new solution is documented on the xen-users mailing-list.
Kai
--- Kai, I read the Xen list and the way your doing it (the last option) looks like something I may try for testing in VMs. Although I do want to say Virtual Box does that very same behavior that you first described in your post. When you start up Virtual Box it takes out my eth1 and I am left with eth0. Makes eth1 Brigded if that makes sense to you like Xen was doing. I have to say it really seems like a better solution the way your doing it now. In fact I am going to give it a try also. It may be a little more effort into doing it but the approach is much better.
Indeed also I when I installed Xen I had to manually take out peth0 when I uninstalled it.
JohnStanley
JohnS wrote on Thu, 30 Apr 2009 02:17:13 -0400:
Kai, I read the Xen list and the way your doing it (the last option) looks like something I may try for testing in VMs.
It works fine, I'm converting all my setups to that now.
Indeed also I when I installed Xen I had to manually take out peth0 when I uninstalled it.
How did you manually take it down? The problem seems to be that peth0 is the physical interface now. But I'm not able to take it down as a bridge nor as a physical interface. And not without breaking the network connection, anyway.
Kai
On Apr 30, 2009, at 7:31 AM, Kai Schaetzl maillists@conactive.com wrote:
JohnS wrote on Thu, 30 Apr 2009 02:17:13 -0400:
Kai, I read the Xen list and the way your doing it (the last option) looks like something I may try for testing in VMs.
It works fine, I'm converting all my setups to that now.
Indeed also I when I installed Xen I had to manually take out peth0 when I uninstalled it.
How did you manually take it down? The problem seems to be that peth0 is the physical interface now. But I'm not able to take it down as a bridge nor as a physical interface. And not without breaking the network connection, anyway.
The problem with Xen's network scripts are they assume a bare bones default network setup. If you have anything more then that then I recommend disabling the automated network setup in xend.sxp and manually setting up your bridges which sounds like the conclusion you came to after much discussion.
-Ross
On Thu, 2009-04-30 at 13:31 +0200, Kai Schaetzl wrote:
JohnS wrote on Thu, 30 Apr 2009 02:17:13 -0400:
Kai, I read the Xen list and the way your doing it (the last option) looks like something I may try for testing in VMs.
It works fine, I'm converting all my setups to that now.
Indeed also I when I installed Xen I had to manually take out peth0 when I uninstalled it.
How did you manually take it down? The problem seems to be that peth0 is the physical interface now. But I'm not able to take it down as a bridge nor as a physical interface. And not without breaking the network connection, anyway.
Kai
---- Correction, the install above should be "uninstalled". Typo error sorry. But that is right peth0 becomes the interface.
JohnStanley
-
JohnS -
Kai Schaetzl -
Ross Walker