| |
|
 |
|
 |
|
|
|
| |
|
|
xen-users
Re: [Xen-users] dom0 network down after domU destroy
OK. i've made modifications in the config file to be sure.
Here is what i have now:
#(network-script network-bridge)
(network-script 'network-bridge netdev=eth1')
# (network-script 'network-bridge bridge=<name>')
#
#(network-script network-dummy)
#(network-script network-wrapper)
#
#
#(vif-script vif-bridge)
#(network-script network-route)
#(vif-script vif-route)
#(network-script network-nat)
#(vif-script vif-nat)
Normally, it must be ok like that?
Here is the result of brtcl show before I start domU:
superxen:~# brctl show
bridge name bridge id STP enabled interfaces
eth1 8000.0026b9854d47 no peth1
Then, xm create domU...
superxen:~# xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 48285 1 r----- 122.1
casa 1 16384 1 -b---- 1.8
superxen:~# brctl show
bridge name bridge id STP enabled interfaces
eth1 8000.0026b9854d47 no peth1
vif1.0
And after xm destroy, same problem!
Selon Tapas Mishra <mightydreams@xxxxxxxxx>:
> I see a problem in this file.See if you are using a bridge then
> type command brctl show
> and see what is the output.
> (network-script 'network-bridge bridge=<name>')
> it should be uncommented
> where <name> should be replaced by your default ethernet name.
> Then I see (network-script network-wrapper) uncommented have you
> written the script yourself known as network-wrapper if not then do
> comment it.
> (vif-script vif-bridge) is uncommented this is ok if you are having a
> bridge connection.In this case
> #(network-script network-bridge) should be also uncommented.
> These are what I understand from your config.sxp.
>
> On Mon, Apr 19, 2010 at 12:58 AM, <ninoochka@xxxxxxx> wrote:
> > Here it is.
> >
> > Selon Tapas Mishra <mightydreams@xxxxxxxxx>:
> >
> >> Can you post the entries from your /etc/xen/xend-config.sxp
> >>
> >> On Fri, Apr 16, 2010 at 9:11 PM, Virginie <ninoochka@xxxxxxx> wrote:
> >> > Hi all,
> >> >
> >> > I've just installed xen on a server with debian lenny. What I would like
> >> > seems to be simple.
> >> > domU is bridged to eth1. Everything is ok for dom0 and domU when I
> >> > start domU (xm create domU). When I destroy domU (xm destroy domU), dom0
> >> > network goes down and the only thing i can do is to reboot the machine
> >> > (/etc/init.d/networking restart does not solve the problem). This
> >> > problem occurs since the beginning and every time I shut down the domU.
> >> > When I shutdown domU, domU is stalled on s state and never really
> >> > shutdowns.
> >> >
> >> > Is anybody have an idea ? The same conf is working very well on another
> >> > server) ?
> >> >
> >> > Virginie
> >> >
> >> > Kernel:
> >> > Dell R905
> >> > Linux superxen 2.6.26-2-xen-amd64 #1 SMP Wed Mar 10 00:29:48 UTC 2010
> >> > x86_64 GNU/Linux
> >> > Ethernet controller (4): Broadcom Corporation NetXtreme II BCM5708
> >> > Gigabit Ethernet (rev 12)
> >> >
> >> >
> >> > _______________________________________________
> >> > Xen-users mailing list
> >> > Xen-users@xxxxxxxxxxxxxxxxxxx
> >> > http://lists.xensource.com/xen-users
> >> >
> >>
> >>
> >>
> >> --
> >> Tapas
> >>
> >
>
http://wiki.xensource.com/xenwiki/How_to_run_4_Application_servers_on_same_piece_of_hardware_with_a_separate_OS_for_each_of_them.
> >> +91 8971248477
> >>
> >
> >
> >
>
>
>
> --
> Tapas
>
http://wiki.xensource.com/xenwiki/How_to_run_4_Application_servers_on_same_piece_of_hardware_with_a_separate_OS_for_each_of_them.
> +91 8971248477
>
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
| |
|
Home