[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] trouble installing
On Tue, Feb 22, 2011 at 06:27:43AM -0600, Ted Brenner wrote: > Yeah, I commented out the entire line after sending that and it boots and > shuts down fine. So are you suggesting using routing instead of bridging > where routing uses the distros networking tools instead of xen? > No. I'm suggesting you set up the bridges using distro network settings. -- Pasi > On Tue, Feb 22, 2011 at 12:22 AM, Pasi Kärkkäinen <[1]pasik@xxxxxx> wrote: > > On Mon, Feb 21, 2011 at 08:14:33PM -0600, Ted Brenner wrote: > > Thanks for the help Pasi. So why use Debian network scripts in > lieu of > > Xen scripts when the Debian wiki doesn't suggest it? > > > > It has been a 'best practive' to use distro provided network scripts > for years already.. > > Upcoming Xen 4.1 with the new default xl/libxl toolstack actually > as a default requires you to set up the networking using the distro > scripts! > > > I removed 'bridge=eth0' from the network-script line but I'm still > having > > trouble with the xen daemon. When I boot up it isn't running and > when I > > shutdown it still hangs apparently because it's getting no response > from > > eth0. Do I have to do something to make my change to > xend-config.sxp > > permanent? > > > > When I try and start up xend I see this error: > > > > # xend start > > ifdown: interface eth0 not configured > > RTNETLINK answers: Device or resource busy > > /etc/xen/scripts/network-bridge: line 240: sigerr: command not > found > > > > You have to remove the whole "network-script" line ! > > -- Pasi > > > On Mon, Feb 21, 2011 at 4:18 AM, Pasi Kärkkäinen > <[1][2]pasik@xxxxxx> wrote: > > > > On Sun, Feb 20, 2011 at 10:14:06PM -0600, Ted Brenner wrote: > > > Hi, > > > > > > I'm trying to setup Xen 4.0 on Debian Squeeze. I've been > following > > this > > > wiki for the most part. > [1][2][3]http://wiki.debian.org/Xen. When I > > first went > > > through the process, after rebooting I just got a blank > black > > screen with > > > no grub. So after reinstalling my OS I've been rebooting > after > > every step > > > and everything works fine (not sure why I got the grub error > the > > first > > > time). But after uncommenting the network-script part of > > xen-config.sxp > > > file and adding 'network-bridge antispoof=yes', things start > to act > > up. > > > The first thing I noticed was that shutdowing down the dom0 > now > > hangs, > > > usually at the point of stopping the xend daemon. So I > tried > > adding > > > 'bridge=eth0'. Nothing really change but I still installed > a domU, > > Ubuntu > > > Maverick. However, I couldn't connect as I was getting > errors like > > this: > > > > > > Error: Device 0 (vif) could not be connected. Hotplug > scripts not > > working. > > > > > > Checking the hotplug log it said this > > > can't add vif1.0 to bridge eth0: Operation not supported > > > > > > > Sounds like 'eth0' is not a bridge. So probably wrong bridge= > parameter > > used for that vm. > > > > eth0 is my dom0 network interface so the problem is that it is > already in > > use correct? > > > > > > > So I'm wondering how I should be setting up the > network-scripts. > > Every > > > instruction I read mentions it but they all seem to have > slightly > > > different variants. Any help would be much appreciated. > I'm > > running on > > > amd64 platform. > > > > > > > I'd recommend to disable xen network-script in > /etc/xen/xend-config.sxp > > and set up the required bridges using debian network scripts. > > > > > > > > -- Pasi > > > > -- > > Ted Brenner > > > > References > > > > Visible links > > 1. mailto:[4]pasik@xxxxxx > > 2. [5]http://wiki.debian.org/Xen > > -- > Ted Brenner > > References > > Visible links > 1. mailto:pasik@xxxxxx > 2. mailto:pasik@xxxxxx > 3. http://wiki.debian.org/Xen > 4. mailto:pasik@xxxxxx > 5. http://wiki.debian.org/Xen _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |