WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Laptop networking confusion (incl. HVM)

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Laptop networking confusion (incl. HVM)
From: John Robson <jrobson@xxxxxxxxxxxxxx>
Date: Sun, 09 Mar 2008 03:32:11 +0000
Delivery-date: Sat, 08 Mar 2008 19:34:57 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Organization: Fontenergy
Reply-to: jrobson@xxxxxxxxxxxxxx
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I'm now thoroughly lost in a maze of twisty passages, all alike.

Or at least that's the way it seems...

I'm going to try to lay this mail out somewhat logically, at the
inevitable cost of greater length (but hopefully avoiding missing too
many critical pieces of data).

In the interest of reader focus the final questions are:
 - Where do I go from here?
 - What information did I miss to make your life easier?
I'm out of google-fu, and my powers of deduction have weakened, I'd love
to see a "This how to configure Xen on a laptop page", but I can't find
it if it exists - any other pointers/suggestions also welcome.

# The Aim:
I've got a shiny laptop (Toshiba: Core2 Duo 2.6 (VT enabled), 4GB RAM),
running Ubuntu (64 bit Gutsy -  kernel: 2.6.22-14-xen #1 SMP).
I'd like to be able to run various test machines (various deb based
linuxes) and at least one instance of Windows under Xen.

# The Issue: Networking
I've installed Xen and it's running. I have created both Windows and
Linux domU's, which I can log into using either "vnc 127.0.0.1" (for the
windows dom) or "xm console linux01" (for the Linux dom)

However I can't get any form of networking to work - Bridged, NAT or
Routed - the domU's simply can't talk to anything - they do occasionally
think that their nic has a link.

# Thoughts:
I actually don't much care what network layout the thing uses, except of
course that as a laptop the machines overall connectivity is changeable.
I can easily reserve a /24 RFC1918 subnet for virtual boxes - and think
that this might be the way to go, using NAT on the laptop for outside
access. HOWEVER I'm willing to hear other ideas/opinions...

# The Config:
This is, I think, mostly modified from:
http://virt.kernelnewbies.org/XenWifiNetwork - I've been through too
many sites trying to figure this out!

----console dump----
jrobson@baldur:/$ cat /etc/xen/xend-config.sxp
# -*- sh -*-
# Xend configuration file.

(xend-relocation-server yes)
(xend-relocation-hosts-allow '^localhost$ ^localhost\\.localdomain$')

(network-script 'network-route bridge=xenbr0 netdev=dummy0')
(vif-script     vif-route)

(dom0-min-mem 196)
(dom0-cpus 0)

(vncpasswd '')
jrobson@baldur:/$ cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto dummy0
iface dummy0 inet static
        address 172.16.252.254
        broadcast 172.16.252.255
        netmask 255.255.255.0
root@baldur:/# cat /etc/xen/winXP 
kernel = "/usr/lib/xen-ioemu-3.1/boot/hvmloader"
builder = 'hvm'
device_model = '/usr/lib/xen-ioemu-3.1/bin/qemu-dm'
memory = 512
name = "winXP"
vcpus = 1
apic = 0
acpi = 0
vif = [ 'type=ioemu' ]
disk =
['phy:/dev/xendisks/winXP,ioemu:hda,w','file:/images/Microsoft/WinXP.iso,hdc:cdrom,r']
boot='c'
vnc=1
on_reboot = 'destroy'
 root@baldur:/# cat /etc/xen/linux01 
# Configuration file for the Xen instance linux01, created
# by xen-tools 3.5 on Sat Mar  8 14:00:39 2008.
#  Kernel + memory size
kernel      = '/boot/vmlinuz-2.6.22-14-xen'
ramdisk     = '/boot/initrd.img-2.6.22-14-xen'
memory      = '512'
#  Disk device(s).
root        = '/dev/sda1 ro'
disk        = [ 'phy:xendisks/linux01.johnat.homeip.net-disk,sda1,w' ]
#  Hostname
name        = 'linux01'
#  Networking
#dhcp        = 'dhcp'
vif         = [ '' ]
#  Behaviour
on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'
# See http://www.nabble.com/can't-connect-to-console-td15021849.html
extra = "TERM=xterm xencons=tty console=tty1"
root@baldur:/# 

## Note to reader: The following is after a reboot, no VMs started:
root@baldur:/# ip addr show
1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: vif0.0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
3: veth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
4: vif0.1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
5: veth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
6: vif0.2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
7: veth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
8: vif0.3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
9: veth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
10: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast
qlen 1000
    link/ether 00:15:b7:94:bc:f3 brd ff:ff:ff:ff:ff:ff
11: wmaster0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc ieee80211
qlen 1000
    link/ieee802.11 00:1d:e0:50:bb:e3 brd ff:ff:ff:ff:ff:ff
12: wlan0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen
1000
    link/ether 00:1d:e0:50:bb:e3 brd ff:ff:ff:ff:ff:ff
    inet 192.168.10.142/24 brd 192.168.10.255 scope global wlan0
    inet6 fe80::21d:e0ff:fe50:bbe3/64 scope link 
       valid_lft forever preferred_lft forever
13: dummy0: <BROADCAST,NOARP,UP,10000> mtu 1500 qdisc noqueue 
    link/ether be:d6:76:8b:aa:a7 brd ff:ff:ff:ff:ff:ff
    inet 172.16.252.254/24 brd 172.16.252.255 scope global dummy0
    inet6 fe80::bcd6:76ff:fe8b:aaa7/64 scope link 
       valid_lft forever preferred_lft forever
14: xenbr0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::200:ff:fe00:0/64 scope link 
       valid_lft forever preferred_lft forever
15: xen-br0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc noqueue 
    link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::200:ff:fe00:0/64 scope link 
       valid_lft forever preferred_lft forever
root@baldur:/# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
192.168.10.0    *               255.255.255.0   U     0      0        0
wlan0
172.16.252.0    *               255.255.255.0   U     0      0        0
dummy0
link-local      *               255.255.0.0     U     1000   0        0
dummy0
default         192.168.10.1    0.0.0.0         UG    0      0        0
wlan0
root@baldur:/#  brctl show
bridge name     bridge id               STP enabled     interfaces
xen-br0         8000.000000000000       no
xenbr0          8000.000000000000       no
root@baldur:/#
----end console dump----

Many thanks,

John


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

<Prev in Thread] Current Thread [Next in Thread>