[Pkg-xen-devel] Xen status in lenny?

[Laurent Léonard]

Le jeudi 25 septembre 2008 à 11:36, Paul van der Vlis a écrit :
> My first message was refused because it was to long. Another try...
>
> Bastian Blank schreef:
> > > On Thu, Sep 18, 2008 at 11:52:09AM +0200, Paul van der Vlis wrote:
> >> >> I have it running on my amd64 machine!
> > >
> > > Okay.
>
> I use now the try4 packages (amd64) on the dom0. I did not have problems
> with the try3-packages.
>
> >> >> - the VM's do not start automatically, but they start with "xm
>
> create".
>
> > > Hmm. Please show the xend log (/var/log/xen/xend.log) from before the
> > > manual start.
>
> When I start a VM once with "xm create", the next time it starts
> automatically.
>
> >> >> - I can ping and SSH the VM from the dom0, not from the internet.
> > >
> > > Please use wireshark/tshark/tcpdump to find the interface where is gets
> > > lost.
>
> My problem is that I don't have a xenbr-device:
> [2008-09-22 10:49:20 3031] INFO (XendNetwork:114) Not recreating missing
> unmanaged network xenbr1
>
> Special on my machine is that I use eth1 and not eth0:
> ------
> xen:/var/log/xen# ifconfig
> eth1      Link encap:Ethernet  HWaddr 00:30:48:93:50:3d
>           inet addr:91.198.178.10  Bcast:91.198.178.255  Mask:255.255.255.0
>           inet6 addr: fe80::230:48ff:fe93:503d/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:12572 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:7291 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:9428884 (8.9 MiB)  TX bytes:738404 (721.0 KiB)
>
> 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:48 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:48 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:4365 (4.2 KiB)  TX bytes:4365 (4.2 KiB)
>
> peth1     Link encap:Ethernet  HWaddr 00:30:48:93:50:3d
>           inet6 addr: fe80::230:48ff:fe93:503d/64 Scope:Link
>           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>           RX packets:12757 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:7343 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           RX bytes:9626551 (9.1 MiB)  TX bytes:739319 (721.9 KiB)
>           Memory:e8200000-e8220000
>
> vif1.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>           RX packets:615 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:2619 errors:0 dropped:8 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:37966 (37.0 KiB)  TX bytes:168744 (164.7 KiB)
>
> vif2.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>           RX packets:1 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:2534 errors:0 dropped:6 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:28 (28.0 B)  TX bytes:162432 (158.6 KiB)
>
> vif3.0    Link encap:Ethernet  HWaddr fe:ff:ff:ff:ff:ff
>           inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
>           UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
>           RX packets:1 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:2530 errors:0 dropped:6 overruns:0 carrier:0
>           collisions:0 txqueuelen:32
>           RX bytes:28 (28.0 B)  TX bytes:162200 (158.3 KiB)
> -----
>
> > > Please make sure that the domains are restarted and not only
> > > restored.
>
> I rebooted the machine, is that enough?
>
> > > Also please show the output of xm dmesg and dmesg.
>
> My message became too long. You can see them here:
> http://www.vandervlis.nl/log
>
> With regards,
> Paul van der Vlis.

You have to add a xenbr0 bridge in your network configuration 
(/etc/network/intefaces) : 

iface xenbr0 inet [dhcp|static]
	bridge_ports YOUR_PHYSICAL_INTERFACE

The Xen daemon will use it to bridge network connections of virtual machines, 
it's the default xend configuration in Debian. 

-- 
Laurent Léonard
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20081007/61d6ff61/attachment.pgp