Hi, I''m trying to setup Xen 4.0 on Debian Squeeze. I''ve been following this wiki for the most part. 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 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. Let me know if I can provide more information. Thanks! Ted Brenner _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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]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.> 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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for the help Pasi. So why use Debian network scripts in lieu of Xen scripts when the Debian wiki doesn''t suggest it? 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 On Mon, Feb 21, 2011 at 4:18 AM, Pasi Kärkkäinen <pasik@iki.fi> 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]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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Looking into this some more:
# ifconfig
eth0 Link encap:Ethernet HWaddr 00:25:22:8d:84:b2
inet addr:10.0.0.3 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::225:22ff:fe8d:84b2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:42 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1710 (1.6 KiB) TX bytes:7252 (7.0 KiB)
Interrupt:207
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:560 (560.0 B) TX bytes:560 (560.0 B)
# more /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
#NetworkManager#iface eth0 inet dhcp
#iface eth0 inet dhcp
#up /etc/xen/scripts/network-bridge start
When I commented out the allow-hotplug eth0 and added the line for iface
eth0 inet dhcp, I couldn''t get my network up at all. So I removed that
line
plus the line below it and uncommented out the allow-hotplug line and things
started okay but I still couldn''t connect to a domU. But I''m
wondering if
something is wrong due to creating three different domUs with different
network interfaces. What is the preferred method of removing a domU?
Thanks for the help.
On Mon, Feb 21, 2011 at 8:14 PM, Ted Brenner <griztown@gmail.com> 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?
>
> 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
>
>
>
> On Mon, Feb 21, 2011 at 4:18 AM, Pasi Kärkkäinen <pasik@iki.fi>
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]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
>
--
Ted Brenner
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
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]pasik@iki.fi> 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]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:pasik@iki.fi > 2. http://wiki.debian.org/Xen_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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? On Tue, Feb 22, 2011 at 12:22 AM, Pasi Kärkkäinen <pasik@iki.fi> 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]pasik@iki.fi> > 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]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:pasik@iki.fi > > 2. http://wiki.debian.org/Xen >-- Ted Brenner _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
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@iki.fi> 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@iki.fi> 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@iki.fi > > 2. [5]http://wiki.debian.org/Xen > > -- > Ted Brenner > > References > > Visible links > 1. mailto:pasik@iki.fi > 2. mailto:pasik@iki.fi > 3. http://wiki.debian.org/Xen > 4. mailto:pasik@iki.fi > 5. http://wiki.debian.org/Xen_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I commented out the network-script network-bridge line in xend-config.sxp.
I then restarted xend and it started fine. I connected to the guest fine.
Things seemed great except the network on guest didn''t work.
Couldn''t ping
any IP addresses, particularly ones I could from dom0. So I then followed
the instructions here, http://wiki.debian.org/BridgeNetworkConnections, to
create a network bridge using debian. When I did, I tried to attach it to
the vif interface. But that told me it was already attached to a bridge.
Sure enough, it''s attached to pan0. Not sure how that''s
getting started but
oh well. So I tried specifying that bridge in my guest config file but
still no internet.
Here are the results of ./network-bridge status
# ./network-bridge status
===========================================================2: eth0:
<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UNKNOWN qlen 1000
link/ether 00:25:22:8d:84:b2 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.3/24 brd 10.0.0.255 scope global eth0
inet6 fe80::225:22ff:fe8d:84b2/64 scope link
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UNKNOWN qlen 1000
link/ether 00:25:22:8d:84:b2 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.3/24 brd 10.0.0.255 scope global eth0
inet6 fe80::225:22ff:fe8d:84b2/64 scope link
valid_lft forever preferred_lft forever
bridge name bridge id STP enabled interfaces
pan0 8000.feffffffffff no vif3.0
10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.3 metric 1
default via 10.0.0.1 dev eth0 proto static
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
10.0.0.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0 0 eth0
===========================================================
Anything obvious jumping out? Why is this so difficult or did I just screw
up some basic setting at some point?
Anyway, thanks for all the help.
Ted
On Tue, Feb 22, 2011 at 6:52 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> 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@iki.fi>
> 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@iki.fi> 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@iki.fi
> > > 2. [5]http://wiki.debian.org/Xen
> >
> > --
> > Ted Brenner
> >
> > References
> >
> > Visible links
> > 1. mailto:pasik@iki.fi
> > 2. mailto:pasik@iki.fi
> > 3. http://wiki.debian.org/Xen
> > 4. mailto:pasik@iki.fi
> > 5. http://wiki.debian.org/Xen
>
--
Ted Brenner
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Tue, Feb 22, 2011 at 09:14:53PM -0600, Ted Brenner wrote:> I commented out the network-script network-bridge line in > xend-config.sxp. I then restarted xend and it started fine. I connected > to the guest fine. Things seemed great except the network on guest didn''t > work. Couldn''t ping any IP addresses, particularly ones I could from > dom0. So I then followed the instructions here, > [1]http://wiki.debian.org/BridgeNetworkConnections, to create a network > bridge using debian. When I did, I tried to attach it to the vif > interface. But that told me it was already attached to a bridge. Sure > enough, it''s attached to pan0. Not sure how that''s getting started but oh > well. So I tried specifying that bridge in my guest config file but still > no internet. > > Here are the results of ./network-bridge status > > # ./network-bridge status > ===========================================================> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state > UNKNOWN qlen 1000 > link/ether 00:25:22:8d:84:b2 brd ff:ff:ff:ff:ff:ff > inet [2]10.0.0.3/24 brd 10.0.0.255 scope global eth0 > inet6 fe80::225:22ff:fe8d:84b2/64 scope link > valid_lft forever preferred_lft forever > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state > UNKNOWN qlen 1000 > link/ether 00:25:22:8d:84:b2 brd ff:ff:ff:ff:ff:ff > inet [3]10.0.0.3/24 brd 10.0.0.255 scope global eth0 > inet6 fe80::225:22ff:fe8d:84b2/64 scope link > valid_lft forever preferred_lft forever > > bridge name bridge id STP enabled interfaces > pan0 8000.feffffffffff no vif3.0 > > [4]10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.3 metric 1 > default via 10.0.0.1 dev eth0 proto static > > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 10.0.0.0 0.0.0.0 255.255.255.0 U 1 0 0 > eth0 > 0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0 0 > eth0 > ===========================================================> > Anything obvious jumping out? Why is this so difficult or did I just > screw up some basic setting at some point? >that bridge called "pan0" doesn''t have any external (physical) interfaces attached to it. I recommend you to set up a bridge called, say, ''br0'', and attach your physical eth0 to it, and also specify ''bridge=br0'' for the VMs. -- Pasi> Anyway, thanks for all the help. > Ted > > On Tue, Feb 22, 2011 at 6:52 AM, Pasi Kärkkäinen <[5]pasik@iki.fi> wrote: > > 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][6]pasik@iki.fi> 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][7]pasik@iki.fi> 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][8]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][9]pasik@iki.fi > > > 2. [5][10]http://wiki.debian.org/Xen > > > > -- > > Ted Brenner > > > > References > > > > Visible links > > 1. mailto:[11]pasik@iki.fi > > 2. mailto:[12]pasik@iki.fi > > 3. [13]http://wiki.debian.org/Xen > > 4. mailto:[14]pasik@iki.fi > > 5. [15]http://wiki.debian.org/Xen > > -- > Ted Brenner > > References > > Visible links > 1. http://wiki.debian.org/BridgeNetworkConnections > 2. http://10.0.0.3/24 > 3. http://10.0.0.3/24 > 4. http://10.0.0.0/24 > 5. mailto:pasik@iki.fi > 6. mailto:pasik@iki.fi > 7. mailto:pasik@iki.fi > 8. http://wiki.debian.org/Xen > 9. mailto:pasik@iki.fi > 10. http://wiki.debian.org/Xen > 11. mailto:pasik@iki.fi > 12. mailto:pasik@iki.fi > 13. http://wiki.debian.org/Xen > 14. mailto:pasik@iki.fi > 15. http://wiki.debian.org/Xen_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks Pasi,
I did that but now the internet doesn''t work on either domU or dom0.
Here''s
my bridge status.
# /etc/xen/scripts/network-bridge status
===========================================================2: eth0:
<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UNKNOWN qlen 1000
link/ether 00:25:22:8d:84:b2 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.3/24 brd 10.0.0.255 scope global eth0
inet6 fe80::225:22ff:fe8d:84b2/64 scope link
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UNKNOWN qlen 1000
link/ether 00:25:22:8d:84:b2 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.3/24 brd 10.0.0.255 scope global eth0
inet6 fe80::225:22ff:fe8d:84b2/64 scope link
valid_lft forever preferred_lft forever
bridge name bridge id STP enabled interfaces
br0 8000.0025228d84b2 no eth0
vif1.0
10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.3 metric 1
default via 10.0.0.1 dev eth0 proto static
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
10.0.0.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0
0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0 0 eth0
===========================================================
On Wed, Feb 23, 2011 at 1:54 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:
> On Tue, Feb 22, 2011 at 09:14:53PM -0600, Ted Brenner wrote:
> > I commented out the network-script network-bridge line in
> > xend-config.sxp. I then restarted xend and it started fine. I
> connected
> > to the guest fine. Things seemed great except the network on guest
> didn''t
> > work. Couldn''t ping any IP addresses, particularly ones I
could from
> > dom0. So I then followed the instructions here,
> > [1]http://wiki.debian.org/BridgeNetworkConnections, to create a
> network
> > bridge using debian. When I did, I tried to attach it to the vif
> > interface. But that told me it was already attached to a bridge.
> Sure
> > enough, it''s attached to pan0. Not sure how
that''s getting started
> but oh
> > well. So I tried specifying that bridge in my guest config file
but
> still
> > no internet.
> >
> > Here are the results of ./network-bridge status
> >
> > # ./network-bridge status
> > ===========================================================>
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast
> state
> > UNKNOWN qlen 1000
> > link/ether 00:25:22:8d:84:b2 brd ff:ff:ff:ff:ff:ff
> > inet [2]10.0.0.3/24 brd 10.0.0.255 scope global eth0
> > inet6 fe80::225:22ff:fe8d:84b2/64 scope link
> > valid_lft forever preferred_lft forever
> > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc
pfifo_fast
> state
> > UNKNOWN qlen 1000
> > link/ether 00:25:22:8d:84:b2 brd ff:ff:ff:ff:ff:ff
> > inet [3]10.0.0.3/24 brd 10.0.0.255 scope global eth0
> > inet6 fe80::225:22ff:fe8d:84b2/64 scope link
> > valid_lft forever preferred_lft forever
> >
> > bridge name bridge id STP enabled interfaces
> > pan0 8000.feffffffffff no vif3.0
> >
> > [4]10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.3
> metric 1
> > default via 10.0.0.1 dev eth0 proto static
> >
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref
> Use
> > Iface
> > 10.0.0.0 0.0.0.0 255.255.255.0 U 1 0
> 0
> > eth0
> > 0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0
> 0
> > eth0
> > ===========================================================>
>
> > Anything obvious jumping out? Why is this so difficult or did I
just
> > screw up some basic setting at some point?
> >
>
> that bridge called "pan0" doesn''t have any external
(physical) interfaces
> attached to it.
>
> I recommend you to set up a bridge called, say, ''br0'',
and attach your
> physical
> eth0 to it, and also specify ''bridge=br0'' for the VMs.
>
> -- Pasi
>
> > Anyway, thanks for all the help.
> > Ted
> >
> > On Tue, Feb 22, 2011 at 6:52 AM, Pasi Kärkkäinen
<[5]pasik@iki.fi>
> wrote:
> >
> > 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][6]pasik@iki.fi> 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][7]pasik@iki.fi> 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][8]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][9]pasik@iki.fi
> > > > 2. [5][10]http://wiki.debian.org/Xen
> > >
> > > --
> > > Ted Brenner
> > >
> > > References
> > >
> > > Visible links
> > > 1. mailto:[11]pasik@iki.fi
> > > 2. mailto:[12]pasik@iki.fi
> > > 3. [13]http://wiki.debian.org/Xen
> > > 4. mailto:[14]pasik@iki.fi
> > > 5. [15]http://wiki.debian.org/Xen
> >
> > --
> > Ted Brenner
> >
> > References
> >
> > Visible links
> > 1. http://wiki.debian.org/BridgeNetworkConnections
> > 2. http://10.0.0.3/24
> > 3. http://10.0.0.3/24
> > 4. http://10.0.0.0/24
> > 5. mailto:pasik@iki.fi
> > 6. mailto:pasik@iki.fi
> > 7. mailto:pasik@iki.fi
> > 8. http://wiki.debian.org/Xen
> > 9. mailto:pasik@iki.fi
> > 10. http://wiki.debian.org/Xen
> > 11. mailto:pasik@iki.fi
> > 12. mailto:pasik@iki.fi
> > 13. http://wiki.debian.org/Xen
> > 14. mailto:pasik@iki.fi
> > 15. http://wiki.debian.org/Xen
>
--
Ted Brenner
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Wed, Feb 23, 2011 at 6:57 PM, Ted Brenner <griztown@gmail.com> wrote:> Thanks Pasi, > > I did that but now the internet doesn''t work on either domU or dom0. Here''s > my bridge status. > > # /etc/xen/scripts/network-bridge statusWhy would you run that command? You commented-out the script from xend.sxp earlier, right?> bridge name bridge id STP enabled interfaces > br0 8000.0025228d84b2 no eth0 > vif1.0 > > 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.3 metric 1 > default via 10.0.0.1 dev eth0 proto static > > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 10.0.0.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0 > 0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0 0 eth0That''s wrong. Let''s start with some simple things: - if you use OS network script do NOT touch /etc/xen/scripts/network-bridge again. Ever. - The sample http://wiki.debian.org/BridgeNetworkConnections is good, although it uses both eth0 and eth1. You most likely only need one (eth0). - Put your dom0 IPs on the bridge (in your case, br0), and NOT the interface member (eth0). The wiki provides good example for both dhcp and static ip address on br0. Why aren''t you following that? From the output you sent it looks like you''re still putting IP addresses on eth0, not br0. Go back and create a correct config for dom0 bridge using /etc/network/interfaces. Don''t start any domU yet. Verify network connection is running fine on dom0. THEN create a domU. If you''re still having problems, paste: - your /etc/network/interfaces - output of "brctl show", "ip ad sh br0", "ip ad sh eth0" (to make sure interfaces are up and properly configured) - netstat -nr (to make sure routing is properly configured) -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, Feb 23, 2011 at 05:57:03AM -0600, Ted Brenner wrote:> Thanks Pasi, > > I did that but now the internet doesn''t work on either domU or dom0. > Here''s my bridge status. >Hey, In dom0 your IP needs to be configured on the br0 interface, not on eth0. I recommend using a dedicated NIC (and bridge) only for VM traffic, and having the dom0 management interface/IP on dedicated nic aswell. -- Pasi> # /etc/xen/scripts/network-bridge status > ===========================================================> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state > UNKNOWN qlen 1000 > link/ether 00:25:22:8d:84:b2 brd ff:ff:ff:ff:ff:ff > inet [1]10.0.0.3/24 brd 10.0.0.255 scope global eth0 > inet6 fe80::225:22ff:fe8d:84b2/64 scope link > valid_lft forever preferred_lft forever > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state > UNKNOWN qlen 1000 > link/ether 00:25:22:8d:84:b2 brd ff:ff:ff:ff:ff:ff > inet [2]10.0.0.3/24 brd 10.0.0.255 scope global eth0 > inet6 fe80::225:22ff:fe8d:84b2/64 scope link > valid_lft forever preferred_lft forever > > bridge name bridge id STP enabled interfaces > br0 8000.0025228d84b2 no eth0 > vif1.0 > > [3]10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.3 metric 1 > default via 10.0.0.1 dev eth0 proto static > > Kernel IP routing table > Destination Gateway Genmask Flags Metric Ref Use > Iface > 10.0.0.0 0.0.0.0 255.255.255.0 U 1 0 0 > eth0 > 0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0 0 > eth0 > ===========================================================> > On Wed, Feb 23, 2011 at 1:54 AM, Pasi Kärkkäinen <[4]pasik@iki.fi> wrote: > > On Tue, Feb 22, 2011 at 09:14:53PM -0600, Ted Brenner wrote: > > I commented out the network-script network-bridge line in > > xend-config.sxp. I then restarted xend and it started fine. I > connected > > to the guest fine. Things seemed great except the network on guest > didn''t > > work. Couldn''t ping any IP addresses, particularly ones I could > from > > dom0. So I then followed the instructions here, > > [1][5]http://wiki.debian.org/BridgeNetworkConnections, to create a > network > > bridge using debian. When I did, I tried to attach it to the vif > > interface. But that told me it was already attached to a bridge. > Sure > > enough, it''s attached to pan0. Not sure how that''s getting started > but oh > > well. So I tried specifying that bridge in my guest config file > but still > > no internet. > > > > Here are the results of ./network-bridge status > > > > # ./network-bridge status > > ===========================================================> > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc > pfifo_fast state > > UNKNOWN qlen 1000 > > link/ether 00:25:22:8d:84:b2 brd ff:ff:ff:ff:ff:ff > > inet [2][6]10.0.0.3/24 brd 10.0.0.255 scope global eth0 > > inet6 fe80::225:22ff:fe8d:84b2/64 scope link > > valid_lft forever preferred_lft forever > > 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc > pfifo_fast state > > UNKNOWN qlen 1000 > > link/ether 00:25:22:8d:84:b2 brd ff:ff:ff:ff:ff:ff > > inet [3][7]10.0.0.3/24 brd 10.0.0.255 scope global eth0 > > inet6 fe80::225:22ff:fe8d:84b2/64 scope link > > valid_lft forever preferred_lft forever > > > > bridge name bridge id STP enabled interfaces > > pan0 8000.feffffffffff no vif3.0 > > > > [4][8]10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.3 > metric 1 > > default via 10.0.0.1 dev eth0 proto static > > > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric Ref > Use > > Iface > > 10.0.0.0 0.0.0.0 255.255.255.0 U 1 0 > 0 > > eth0 > > 0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0 > 0 > > eth0 > > ===========================================================> > > > Anything obvious jumping out? Why is this so difficult or did I > just > > screw up some basic setting at some point? > > > > that bridge called "pan0" doesn''t have any external (physical) > interfaces > attached to it. > > I recommend you to set up a bridge called, say, ''br0'', and attach your > physical > eth0 to it, and also specify ''bridge=br0'' for the VMs. > > -- Pasi > > Anyway, thanks for all the help. > > Ted > > > > On Tue, Feb 22, 2011 at 6:52 AM, Pasi Kärkkäinen > <[5][9]pasik@iki.fi> wrote: > > > > 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][6][10]pasik@iki.fi> 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][7][11]pasik@iki.fi> 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][8][12]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][9][13]pasik@iki.fi > > > > 2. [5][10][14]http://wiki.debian.org/Xen > > > > > > -- > > > Ted Brenner > > > > > > References > > > > > > Visible links > > > 1. mailto:[11][15]pasik@iki.fi > > > 2. mailto:[12][16]pasik@iki.fi > > > 3. [13][17]http://wiki.debian.org/Xen > > > 4. mailto:[14][18]pasik@iki.fi > > > 5. [15][19]http://wiki.debian.org/Xen > > > > -- > > Ted Brenner > > > > References > > > > Visible links > > 1. [20]http://wiki.debian.org/BridgeNetworkConnections > > 2. [21]http://10.0.0.3/24 > > 3. [22]http://10.0.0.3/24 > > 4. [23]http://10.0.0.0/24 > > 5. mailto:[24]pasik@iki.fi > > 6. mailto:[25]pasik@iki.fi > > 7. mailto:[26]pasik@iki.fi > > 8. [27]http://wiki.debian.org/Xen > > 9. mailto:[28]pasik@iki.fi > > 10. [29]http://wiki.debian.org/Xen > > 11. mailto:[30]pasik@iki.fi > > 12. mailto:[31]pasik@iki.fi > > 13. [32]http://wiki.debian.org/Xen > > 14. mailto:[33]pasik@iki.fi > > 15. [34]http://wiki.debian.org/Xen > > -- > Ted Brenner > > References > > Visible links > 1. http://10.0.0.3/24 > 2. http://10.0.0.3/24 > 3. http://10.0.0.0/24 > 4. mailto:pasik@iki.fi > 5. http://wiki.debian.org/BridgeNetworkConnections > 6. http://10.0.0.3/24 > 7. http://10.0.0.3/24 > 8. http://10.0.0.0/24 > 9. mailto:pasik@iki.fi > 10. mailto:pasik@iki.fi > 11. mailto:pasik@iki.fi > 12. http://wiki.debian.org/Xen > 13. mailto:pasik@iki.fi > 14. http://wiki.debian.org/Xen > 15. mailto:pasik@iki.fi > 16. mailto:pasik@iki.fi > 17. http://wiki.debian.org/Xen > 18. mailto:pasik@iki.fi > 19. http://wiki.debian.org/Xen > 20. http://wiki.debian.org/BridgeNetworkConnections > 21. http://10.0.0.3/24 > 22. http://10.0.0.3/24 > 23. http://10.0.0.0/24 > 24. mailto:pasik@iki.fi > 25. mailto:pasik@iki.fi > 26. mailto:pasik@iki.fi > 27. http://wiki.debian.org/Xen > 28. mailto:pasik@iki.fi > 29. http://wiki.debian.org/Xen > 30. mailto:pasik@iki.fi > 31. mailto:pasik@iki.fi > 32. http://wiki.debian.org/Xen > 33. mailto:pasik@iki.fi > 34. http://wiki.debian.org/Xen_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks Fajar and Pasi,
I''m not sure how to add my IP to the bridge. It tells me 10.0.0.3 is
not an
interface. I''m sorry if I don''t know much about networking.
Here''s my /etc/network/interface
# more /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
#NetworkManager#iface eth0 inet dhcp
# brctl show
bridge name bridge id STP enabled interfaces
br0 8000.000000000000 no
# ip ad sh br0
4: br0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
# ip ad sh eth0
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UNKNOWN qlen 1000
link/ether 00:25:22:8d:84:b2 brd ff:ff:ff:ff:ff:ff
inet 10.0.0.3/24 brd 10.0.0.255 scope global eth0
inet6 fe80::225:22ff:fe8d:84b2/64 scope link
valid_lft forever preferred_lft forever
On Wed, Feb 23, 2011 at 6:47 AM, Fajar A. Nugraha <list@fajar.net> wrote:
> On Wed, Feb 23, 2011 at 6:57 PM, Ted Brenner <griztown@gmail.com>
wrote:
> > Thanks Pasi,
> >
> > I did that but now the internet doesn''t work on either domU
or dom0.
> Here''s
> > my bridge status.
> >
> > # /etc/xen/scripts/network-bridge status
>
> Why would you run that command? You commented-out the script from
> xend.sxp earlier, right?
>
> > bridge name bridge id STP enabled interfaces
> > br0 8000.0025228d84b2 no eth0
> >
vif1.0
> >
> > 10.0.0.0/24 dev eth0 proto kernel scope link src 10.0.0.3 metric 1
> > default via 10.0.0.1 dev eth0 proto static
> >
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref
Use
> > Iface
> > 10.0.0.0 0.0.0.0 255.255.255.0 U 1 0
0
> eth0
> > 0.0.0.0 10.0.0.1 0.0.0.0 UG 0 0
0
> eth0
>
> That''s wrong. Let''s start with some simple things:
> - if you use OS network script do NOT touch
> /etc/xen/scripts/network-bridge again. Ever.
> - The sample http://wiki.debian.org/BridgeNetworkConnections is good,
> although it uses both eth0 and eth1. You most likely only need one
> (eth0).
> - Put your dom0 IPs on the bridge (in your case, br0), and NOT the
> interface member (eth0).
>
> The wiki provides good example for both dhcp and static ip address on
> br0. Why aren''t you following that? From the output you sent it
looks
> like you''re still putting IP addresses on eth0, not br0.
>
> Go back and create a correct config for dom0 bridge using
> /etc/network/interfaces. Don''t start any domU yet. Verify network
> connection is running fine on dom0. THEN create a domU.
>
> If you''re still having problems, paste:
> - your /etc/network/interfaces
> - output of "brctl show", "ip ad sh br0", "ip ad
sh eth0" (to make
> sure interfaces are up and properly configured)
> - netstat -nr (to make sure routing is properly configured)
>
> --
> Fajar
>
--
Ted Brenner
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On Wed, Feb 23, 2011 at 8:38 PM, Ted Brenner <griztown@gmail.com> wrote:> Thanks Fajar and Pasi, > > I''m not sure how to add my IP to the bridge. It tells me 10.0.0.3 is not an > interface. I''m sorry if I don''t know much about networking. > > Here''s my /etc/network/interface > > # more /etc/network/interfaces > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > # The loopback network interface > auto lo > iface lo inet loopback > > # The primary network interface > allow-hotplug eth0 > #NetworkManager#iface eth0 inet dhcpThat''s it? No mention about br0 whatsoever on /etc/network/interfaces? Then start by following the example /etc/network/interfaces on the debian wiki. It should be clear enough. You HAVE, read the wiki page, right? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yes, I had. I know it''s hard to believe but this stuff isn''t as obvious to everyone. Here''s what the wiki says: This will add the two interfaces eth0 and eth1 to bridge br0. Simple enough. There’s no distinction with how you add the bridges, or what order you do it, or any special commands you have to add to distinguish them. So don’t worry about that. Well, now we have our bridges, so bring all the interfaces up, *and you’ll be set!* The next part, which addresses the interface, makes it sound like you do that if you want it to work at boot but I couldn''t get it to work at all so I didn''t think I was at that stage yet. Anyway, clearly a misunderstanding. I think I also don''t understand what it means to "bring all the interfaces up" but now I think I do. I do appreciate the help, thanks for taking the time. Ted On Wed, Feb 23, 2011 at 7:42 AM, Fajar A. Nugraha <list@fajar.net> wrote:> On Wed, Feb 23, 2011 at 8:38 PM, Ted Brenner <griztown@gmail.com> wrote: > > Thanks Fajar and Pasi, > > > > I''m not sure how to add my IP to the bridge. It tells me 10.0.0.3 is not > an > > interface. I''m sorry if I don''t know much about networking. > > > > Here''s my /etc/network/interface > > > > # more /etc/network/interfaces > > # This file describes the network interfaces available on your system > > # and how to activate them. For more information, see interfaces(5). > > > > # The loopback network interface > > auto lo > > iface lo inet loopback > > > > # The primary network interface > > allow-hotplug eth0 > > #NetworkManager#iface eth0 inet dhcp > > That''s it? No mention about br0 whatsoever on /etc/network/interfaces? > > Then start by following the example /etc/network/interfaces on the > debian wiki. It should be clear enough. You HAVE, read the wiki page, > right? > > -- > Fajar >-- Ted Brenner _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for your help and patience everyone. I set up the interfaces file as described and everything worked. The only note is the pan0 still exists. Not sure where that''s coming from. Any ideas? Just leave it? On Wed, Feb 23, 2011 at 7:42 AM, Fajar A. Nugraha <list@fajar.net> wrote:> On Wed, Feb 23, 2011 at 8:38 PM, Ted Brenner <griztown@gmail.com> wrote: > > Thanks Fajar and Pasi, > > > > I''m not sure how to add my IP to the bridge. It tells me 10.0.0.3 is not > an > > interface. I''m sorry if I don''t know much about networking. > > > > Here''s my /etc/network/interface > > > > # more /etc/network/interfaces > > # This file describes the network interfaces available on your system > > # and how to activate them. For more information, see interfaces(5). > > > > # The loopback network interface > > auto lo > > iface lo inet loopback > > > > # The primary network interface > > allow-hotplug eth0 > > #NetworkManager#iface eth0 inet dhcp > > That''s it? No mention about br0 whatsoever on /etc/network/interfaces? > > Then start by following the example /etc/network/interfaces on the > debian wiki. It should be clear enough. You HAVE, read the wiki page, > right? > > -- > Fajar >-- Ted Brenner _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Feb 25, 2011 at 3:13 AM, Ted Brenner <griztown@gmail.com> wrote:> Thanks for your help and patience everyone. I set up the interfaces file as > described and everything worked. The only note is the pan0 still exists. > Not sure where that''s coming from. Any ideas? Just leave it?Just leave it. IIRC pan0 is related to bluetooth. -- Fajar> > On Wed, Feb 23, 2011 at 7:42 AM, Fajar A. Nugraha <list@fajar.net> wrote: >> >> On Wed, Feb 23, 2011 at 8:38 PM, Ted Brenner <griztown@gmail.com> wrote: >> > Thanks Fajar and Pasi, >> > >> > I''m not sure how to add my IP to the bridge. It tells me 10.0.0.3 is >> > not an >> > interface. I''m sorry if I don''t know much about networking. >> > >> > Here''s my /etc/network/interface >> > >> > # more /etc/network/interfaces >> > # This file describes the network interfaces available on your system >> > # and how to activate them. For more information, see interfaces(5). >> > >> > # The loopback network interface >> > auto lo >> > iface lo inet loopback >> > >> > # The primary network interface >> > allow-hotplug eth0 >> > #NetworkManager#iface eth0 inet dhcp >> >> That''s it? No mention about br0 whatsoever on /etc/network/interfaces? >> >> Then start by following the example /etc/network/interfaces on the >> debian wiki. It should be clear enough. You HAVE, read the wiki page, >> right? >> >> -- >> Fajar > > > > -- > Ted Brenner >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks, good to know. Two follow up issues. After my guest is up and running, if I type ''xm shutdown guest'', it will shutdown the OS but xen doesn''t seem to realize this. When I go in through the console it shows that it has halted but when I type xm list, the state shows it still running. When I try and delete it, it says "Error, domain is not halted". When I shutdown my computer, dom0, it hangs when its trying to shutdown the guests. My guess is waiting for the guests to shutdown. I can connect to my guests graphically using vncviewer but the resolution is 800x600. How do I configure my guest to display full screen? Thanks, Ted On Thu, Feb 24, 2011 at 4:14 PM, Fajar A. Nugraha <list@fajar.net> wrote:> On Fri, Feb 25, 2011 at 3:13 AM, Ted Brenner <griztown@gmail.com> wrote: > > Thanks for your help and patience everyone. I set up the interfaces file > as > > described and everything worked. The only note is the pan0 still exists. > > Not sure where that''s coming from. Any ideas? Just leave it? > > Just leave it. IIRC pan0 is related to bluetooth. > > -- > Fajar > > > > > > On Wed, Feb 23, 2011 at 7:42 AM, Fajar A. Nugraha <list@fajar.net> > wrote: > >> > >> On Wed, Feb 23, 2011 at 8:38 PM, Ted Brenner <griztown@gmail.com> > wrote: > >> > Thanks Fajar and Pasi, > >> > > >> > I''m not sure how to add my IP to the bridge. It tells me 10.0.0.3 is > >> > not an > >> > interface. I''m sorry if I don''t know much about networking. > >> > > >> > Here''s my /etc/network/interface > >> > > >> > # more /etc/network/interfaces > >> > # This file describes the network interfaces available on your system > >> > # and how to activate them. For more information, see interfaces(5). > >> > > >> > # The loopback network interface > >> > auto lo > >> > iface lo inet loopback > >> > > >> > # The primary network interface > >> > allow-hotplug eth0 > >> > #NetworkManager#iface eth0 inet dhcp > >> > >> That''s it? No mention about br0 whatsoever on /etc/network/interfaces? > >> > >> Then start by following the example /etc/network/interfaces on the > >> debian wiki. It should be clear enough. You HAVE, read the wiki page, > >> right? > >> > >> -- > >> Fajar > > > > > > > > -- > > Ted Brenner > > >-- Ted Brenner _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Feb 25, 2011 at 10:13 AM, Ted Brenner <griztown@gmail.com> wrote:> Thanks, good to know. > > Two follow up issues. After my guest is up and running, if I type ''xm > shutdown guest'', it will shutdown the OS but xen doesn''t seem to realize > this. When I go in through the console it shows that it has halted but when > I type xm list, the state shows it still running. When I try and delete it, > it says "Error, domain is not halted". When I shutdown my computer, dom0, > it hangs when its trying to shutdown the guests. My guess is waiting for > the guests to shutdown.This one might be on old or Debian-specific bug. I''ve tested "xm shutdown" with Xen 4.0.1 on RHEL5, with RHEL and Ubuntu PV domU, and both shutdown just fine. It also works for Windows 2008r2 domU with GPLPV. Is your domU Debian? If yes, I suggest you try using RHEL/Centos and Ubuntu as PV domU, at least to make sure whether the bug is on Xen side or domU side. As a temporary workaround, you should be able to run "xm destroy" instead of "xm shutdown".> > I can connect to my guests graphically using vncviewer but the resolution is > 800x600. How do I configure my guest to display full screen?You can try searching the archive (IIRC 1024x768 is possible), but the general answer is don''t bother. Don''t use domU GUI for anything other than admin purposes. Use some kind of remote acess (NX/VNC/X forwarding/rdesktop) setup on domU, and accessed by client (which could be dom0 or other machines on the network) to get the resolution you need. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Feb 24, 2011 at 9:21 PM, Fajar A. Nugraha <list@fajar.net> wrote:> On Fri, Feb 25, 2011 at 10:13 AM, Ted Brenner <griztown@gmail.com> wrote: > > Thanks, good to know. > > > > Two follow up issues. After my guest is up and running, if I type ''xm > > shutdown guest'', it will shutdown the OS but xen doesn''t seem to realize > > this. When I go in through the console it shows that it has halted but > when > > I type xm list, the state shows it still running. When I try and delete > it, > > it says "Error, domain is not halted". When I shutdown my computer, > dom0, > > it hangs when its trying to shutdown the guests. My guess is waiting for > > the guests to shutdown. > > This one might be on old or Debian-specific bug. I''ve tested "xm > shutdown" with Xen 4.0.1 on RHEL5, with RHEL and Ubuntu PV domU, and > both shutdown just fine. It also works for Windows 2008r2 domU with > GPLPV. > > Is your domU Debian? If yes, I suggest you try using RHEL/Centos and > Ubuntu as PV domU, at least to make sure whether the bug is on Xen > side or domU side. > > As a temporary workaround, you should be able to run "xm destroy" > instead of "xm shutdown". >Yeah, I''ve been using xm destroy which is fine unless I''m shutting down the whole system. I''ve got Debian squeeze for dom0 and Ubuntu Maverick for domU. I''ll ping the debian folks to see if this is a known bug.> > > > > I can connect to my guests graphically using vncviewer but the resolution > is > > 800x600. How do I configure my guest to display full screen? > > You can try searching the archive (IIRC 1024x768 is possible), but the > general answer is don''t bother. Don''t use domU GUI for anything other > than admin purposes. Use some kind of remote acess (NX/VNC/X > forwarding/rdesktop) setup on domU, and accessed by client (which > could be dom0 or other machines on the network) to get the resolution > you need. > > I''ve been trying to connect using xm vncviewer. Are you suggesting I run aseparate vncserver on the domU and connect to it separately, outside of Xen? Thanks!> -- > Fajar >-- Ted Brenner _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Feb 25, 2011 at 10:37 AM, Ted Brenner <griztown@gmail.com> wrote:>> Don''t use domU GUI for anything other >> than admin purposes. Use some kind of remote acess (NX/VNC/X >> forwarding/rdesktop) setup on domU, and accessed by client (which >> could be dom0 or other machines on the network) to get the resolution >> you need. >> > I''ve been trying to connect using xm vncviewer. Are you suggesting I run a > separate vncserver on the domU and connect to it separately, outside of Xen?Yup. Although personally I like xrdp or NX better than vnc, the consep is the same: you run it domU instead of relying on Xen''s vfb. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Feb 24, 2011 at 9:50 PM, Fajar A. Nugraha <list@fajar.net> wrote:> On Fri, Feb 25, 2011 at 10:37 AM, Ted Brenner <griztown@gmail.com> wrote: > >> Don''t use domU GUI for anything other > >> than admin purposes. Use some kind of remote acess (NX/VNC/X > >> forwarding/rdesktop) setup on domU, and accessed by client (which > >> could be dom0 or other machines on the network) to get the resolution > >> you need. > >> > > I''ve been trying to connect using xm vncviewer. Are you suggesting I run > a > > separate vncserver on the domU and connect to it separately, outside of > Xen? > > Yup. > > Although personally I like xrdp or NX better than vnc, the consep is > the same: you run it domU instead of relying on Xen''s vfb. > >Thanks. How are these differ performance wise? Is vnc through Xen faster? How does these compare graphically to say, running an OS in Virtual Box? --> Fajar >-- Ted Brenner _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Fri, Feb 25, 2011 at 9:20 PM, Ted Brenner <griztown@gmail.com> wrote:>> Although personally I like xrdp or NX better than vnc, the consep is >> the same: you run it domU instead of relying on Xen''s vfb. >> > > Thanks. How are these differ performance wise? Is vnc through Xen faster? > How does these compare graphically to say, running an OS in Virtual Box?If you''re going to use it for desktop/laptop then I suggest go with virtualbox instead. It''s far ahead of Xen, being able to do seamless and scale desktop. Acessing vnc/xrdp/nx running in a domU is no different than acessing vnc/xrdp/nx running in a physical server on the network. Good, but not as good as virtualbox''s seamless window. vnc access thru domU''s vfb should really only be use for administrative purposes. Sometimes you''ll get mismatched mouse pointer or other problems. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I know this is an old thread, but wanted to clear things up into this tidy little note. When installing Xen 4 on debian squeeze, the networking needs to be configured: /etc/network/interfaces auto lo iface lo inet loopback # The primary network interface auto eth0 allow-hotplug eth0 iface eth0 inet dhcp And that will get rid of the Line 240 error. Simple as that. What is going on is the new NetworkManager doesn''t work well with Xen. You can do yourself a favor by removing it: $ sudo aptitude purge network-manager -- View this message in context: http://xen.1045712.n5.nabble.com/trouble-installing-tp3393681p5715141.html Sent from the Xen - User mailing list archive at Nabble.com.