Xen users - Sep 2009 - 2 network devices inside a domU with one bridge

Hi,

is there a way to get eth0 and eth1 inside my VM with just one bridge in
dom0?
I am transfering an VPN server to a VM and would like to keep the
configuration like
it is on the real machine.

We use CENTOS with this line in the VM configfile.

vif = [ "mac=00:16:3e:45:9c:df,bridge=xenbr0" ]

I already tried to add another "" section, but this gave me a kernel
panic
when i started the VM.

big thnx


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hello,


i tried "./network-bridge start vifnum=1 netdev=eth0 bridge=xenbr1"
but that
only crashed my ssh connection
and I couldnt connect again.
Is this even possible? I just need 2 devices inside the domU.
We have a 2nd readl device on the dom0, but this is needed fpr failover
stuff.


cheers..

On Mon, Sep 28, 2009 at 10:34 AM, Rupert <linuxmls@googlemail.com> wrote:
> Hi,
>
> is there a way to get eth0 and eth1 inside my VM with just one bridge in
> dom0?
> I am transfering an VPN server to a VM and would like to keep the
> configuration like
> it is on the real machine.
>
> We use CENTOS with this line in the VM configfile.
>
> vif = [ "mac=00:16:3e:45:9c:df,bridge=xenbr0" ]
>
> I already tried to add another "" section, but this gave me a
kernel panic
> when i started the VM.
>
> big thnx
>
>
>
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Mon, Sep 28, 2009 at 3:34 PM, Rupert <linuxmls@googlemail.com>
wrote:
> Hi,
>
> is there a way to get eth0 and eth1 inside my VM with just one bridge in
> dom0?
> I am transfering an VPN server to a VM and would like to keep the
> configuration like
> it is on the real machine.
>
> We use CENTOS with this line in the VM configfile.
>
> vif = [ "mac=00:16:3e:45:9c:df,bridge=xenbr0" ]
using

vif = [ "mac=00:16:3e:45:9c:df,bridge=xenbr0",
"mac=00:16:3e:45:9c:e0,bridge=xenbr0" ]

should work
>
> I already tried to add another "" section, but this gave me a
kernel panic
> when i started the VM.
domU panic? What does it say?
Did you use the latest kernel-xen? If not, try updating first.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Tue, Sep 29, 2009 at 2:02 PM, Rupert <linuxmls@googlemail.com>
wrote:
> On Tue, Sep 29, 2009 at 8:52 AM, Fajar A. Nugraha <fajar@fajar.net>
wrote:
>> domU panic? What does it say?
>> Did you use the latest kernel-xen? If not, try updating first.
>>
> i have the 2.6.18-92.1.22.el5xen kernel inside the domU and
> 2.6.18-92.1.13.el5xen in the dom0.
Redhat is at 2.6.18-164.el5. Centos should be around 2.6.18-128.*
using latest xen and kernel helps rule-out known problems.

In any case, if the panic is in domU, then upgrading domU kernel
should help. Paste the text so others can help you pinpoint the
problem.

If dom0 panics because you start domU, well ,,, lets just say that
shouldn''t happen. At least not with up-to-date RHEL/Centos dom0. If it
happens then your system have a serious problem.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Tue, Sep 29, 2009 at 12:37 AM, Fajar A. Nugraha <fajar@fajar.net>
wrote:
> On Tue, Sep 29, 2009 at 2:02 PM, Rupert <linuxmls@googlemail.com>
wrote:
> > On Tue, Sep 29, 2009 at 8:52 AM, Fajar A. Nugraha
<fajar@fajar.net>
> wrote:
>
> >> domU panic? What does it say?
> >> Did you use the latest kernel-xen? If not, try updating first.
> >>
>
> > i have the 2.6.18-92.1.22.el5xen kernel inside the domU and
> > 2.6.18-92.1.13.el5xen in the dom0.
>
> Redhat is at 2.6.18-164.el5. Centos should be around 2.6.18-128.*
> using latest xen and kernel helps rule-out known problems.
>
> In any case, if the panic is in domU, then upgrading domU kernel
> should help. Paste the text so others can help you pinpoint the
> problem.
>
> If dom0 panics because you start domU, well ,,, lets just say that
> shouldn''t happen. At least not with up-to-date RHEL/Centos dom0.
If it
> happens then your system have a serious problem.
>
> --
> Fajar
>
> __
>
CentOS is at 2.6.18-164.el5 as well.

Grant McWilliams


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Hello,

i just tried it again and I got a panic again,
than I did a kernel update inside the domu and now the system is running.

thnx a lot for your help

greetings

On Tue, Sep 29, 2009 at 10:41 AM, Grant McWilliams <
grantmasterflash@gmail.com> wrote:
>
> On Tue, Sep 29, 2009 at 12:37 AM, Fajar A. Nugraha
<fajar@fajar.net>wrote:
>
>> On Tue, Sep 29, 2009 at 2:02 PM, Rupert <linuxmls@googlemail.com>
wrote:
>> > On Tue, Sep 29, 2009 at 8:52 AM, Fajar A. Nugraha
<fajar@fajar.net>
>> wrote:
>>
>> >> domU panic? What does it say?
>> >> Did you use the latest kernel-xen? If not, try updating first.
>> >>
>>
>> > i have the 2.6.18-92.1.22.el5xen kernel inside the domU and
>> > 2.6.18-92.1.13.el5xen in the dom0.
>>
>> Redhat is at 2.6.18-164.el5. Centos should be around 2.6.18-128.*
>> using latest xen and kernel helps rule-out known problems.
>>
>> In any case, if the panic is in domU, then upgrading domU kernel
>> should help. Paste the text so others can help you pinpoint the
>> problem.
>>
>> If dom0 panics because you start domU, well ,,, lets just say that
>> shouldn''t happen. At least not with up-to-date RHEL/Centos
dom0. If it
>> happens then your system have a serious problem.
>>
>> --
>> Fajar
>>
>> __
>>
>
> CentOS is at 2.6.18-164.el5 as well.
>
> Grant McWilliams
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users