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] Newbie network configuration

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Newbie network configuration
From: jonas kellens <jonas.kellens@xxxxxxxxxx>
Date: Thu, 10 Dec 2009 15:23:19 +0100
Delivery-date: Thu, 10 Dec 2009 06:23:58 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hello !

I'm new to Xen and new to this mailinglist.

I have always used VirtualBox for virtualisation and now I'm experimenting with Xen on CentOS 5.3 64bit.

Networking in Xen is not that easy, surely not if you're used to VirtualBox.

This is my problem :


I have manually created a disk-image and a configuration file.

This is my configuration file :

[root@xen ~]# cat /etc/xen/endian.cfg
import os, re
arch = os.uname()[4]

kernel = "/boot/vmlinuz-2.6.18-164.6.1.el5xen"

memory = 512
shadow_memory = 8
name = "endian"
vif = [ 'type=ioemu, bridge=eth0' ]
disk = [ 'file:/var/vm/endian/endian.img,hda,w', 'file:/tmp/endian/endian.iso,hdc:cdrom,r' ]
device_model = '/usr/lib/xen-default/bin/qemu-dm'
# boot on floppy (a), hard disk (c) or CD-ROM (d)
# default: hard disk, cd-rom, floppy
boot="dc"

sdl=0
vnc=1
vnclisten="0.0.0.0"
vncconsole=1
vncpasswd='endian'
stdvga=0
serial='pty'
usbdevice='tablet'


on_reboot   = 'restart'
on_crash    = 'restart'

When I start my vm, I get the following error :

[root@xen ~]# xm create endian.cfg
Using config file "/etc/xen/endian.cfg".
Error: Device 0 (vif) could not be connected. Hotplug scripts not working.

These are my network interfaces :

[root@xen ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:22:B0:68:73:B9 
          inet6 addr: fe80::222:b0ff:fe68:73b9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:13151 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1558 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1507358 (1.4 MiB)  TX bytes:156621 (152.9 KiB)

eth1      Link encap:Ethernet  HWaddr 00:24:21:54:70:22 
          inet addr:192.168.1.10  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::224:21ff:fe54:7022/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8300 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5475 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:819918 (800.7 KiB)  TX bytes:1188729 (1.1 MiB)
          Interrupt:253 Base address:0xc000

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:1463 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1463 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2405572 (2.2 MiB)  TX bytes:2405572 (2.2 MiB)

peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:13151 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1558 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1559962 (1.4 MiB)  TX bytes:172357 (168.3 KiB)
          Interrupt:17

vif0.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 
          inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:1558 errors:0 dropped:0 overruns:0 frame:0
          TX packets:13151 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:156621 (152.9 KiB)  TX bytes:1507358 (1.4 MiB)

virbr0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00 
          inet addr:192.168.122.1  Bcast:192.168.122.255  Mask:255.255.255.0
          inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:51 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:11001 (10.7 KiB)

xenbr0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF 
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:12538 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1220739 (1.1 MiB)  TX bytes:0 (0.0 b)

eth0 is connected to the internet, and I want the interface of my xen vm to be directly connected to the internet.
So I state : vif = [ 'type=ioemu, bridge=eth0' ]
which should mean that the virtual network interface of my endian-vm is connected with the 'real' network interface eth0 of dom0 and traffic flowing into eth0 is passed to my endian-vm.

I don't specify an IP-address because I get one through dhcp (of my isp).

Can someone advise on these network-troubles ??

Thank you !

Jonas.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>