Hello people, first of all this is my first mail and I am new to Xen
so be nice with me :-)
OK, I installed a Centos 5.5 in a system.
Used yum groupinstall "Virtualization" to install anything related to
Xen.
Those packages installed:
=======================================================================================================================================================================
Package Arch
Version
Repository Size
=======================================================================================================================================================================Installing:
gnome-applet-vm x86_64
0.1.2-1.el5 base
76 k
kernel-xen x86_64
2.6.18-194.11.3.el5 updates
20 M
libvirt i386
0.6.3-33.el5_5.3 updates
2.0 M
libvirt x86_64
0.6.3-33.el5_5.3 updates
2.0 M
virt-manager x86_64
0.6.1-12.el5 base
1.5 M
virt-viewer x86_64
0.0.2-3.el5 base
25 k
xen x86_64
3.0.3-105.el5_5.5 updates
1.9 M
and of course any dependencies for those.
I am trying to get vif-route to work.
On a default install it just doesn''t work.
With the default qemu-ifup and the default vif-route I get:
[root@]# xm create /root/win.cfg
Using config file "/root/win.cfg".
Error: Device 0 (vif) could not be connected.
/etc/xen/scripts/vif-route failed; error detected.
Nothing in /var/log/messages and in /var/log/xen/ the qemu log I got:
domid: 17
qemu: the number of cpus is 1
Watching /local/domain/17/logdirty/next-active
Watching /local/domain/0/device-model/17/command
/etc/xen/qemu-ifup: could not launch network script
Could not initialize device ''tap''
Searching the internet I found that I had to comment out in qemu-ifup
this line: brctl addif $2 $1
and then again it crashes but in qemu log I get this:
domid: 14
qemu: the number of cpus is 1
Watching /local/domain/14/logdirty/next-active
Watching /local/domain/0/device-model/14/command
char device redirected to /dev/pts/1
qemu_map_cache_init nr_buckets = 10000
shared page at pfn 7ffff
buffered io page at pfn 7fffd
xs_read(/vm/e3b3d593-4f9b-2c6f-b951-9c2af99d2ecf/rtc/timeoffset): read error
I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0
Triggered log-dirty buffer switch
but again,
Error: Device 0 (vif) could not be connected.
/etc/xen/scripts/vif-route failed; error detected.
That''s a start...
Searching the internet found a few patched versions of qemu-ifup and vif-route.
I tried them without success.
Like this: (qemu-ifup)
ifconfig $1 0.0.0.0 up
#brctl addif $2 $1
gwip=`ip -4 -o addr show primary dev "$2" | awk ''$3 ==
"inet" {print
$4;exit}''| sed ''s#/.*##''`
ip link set "$1" up arp on
ip addr add $gwip dev "$1"
Anyway, in any combination that I tried, (stock vif-route with pathced
qemu-ifup, stock qemu with patched vif-route, patched with patched)
I am getting the same error:
Error: Device 0 (vif) could not be connected.
/etc/xen/scripts/vif-route failed; error detected.
That''s why in the first place I wrote the packages with their version
number may be it''s a conflict or
a "bug" which caused by a package (libvirt for example?)
Of course if I comment out the vif line in the cfg it works but
without network :-)
Speaking for vif, I also tried messing around with the syntax like
vif = [''type=ioemu, ip=x.x.x.x'']
vif = [''type=ioemu, ip=x.x.x.x, mac=xx:xx:xx'']
vif = [''type=ioemu, ip=x.x.x.x, bridge=xxx''] and so on
but still nothing.
any ideas ? I forgot something or should I try something else ?
By the way I use:
[root@ ~]# xm dmesg
__ __ _____ _ ____ _ ___ _ _ _ _ _____ _ ____
\ \/ /___ _ __ |___ / / | |___ \ / |/ _ \| || | / / | |___ / ___| | ___|
\ // _ \ \047_ \ |_ \ | | __) |__| | (_) | || |_ | | | |_ \
/ _ \ |___ \
/ \ __/ | | | ___) || |_ / __/|__| |\__, |__ _|| | |_ ___) | __/ |___) |
/_/\_\___|_| |_| |____(_)_(_)_____| |_| /_/ |_|(_)_|_(_)____(_)___|_|____/
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 3.1.2-194.11.3.el5 (mockbuild@centos.org) (gcc version
4.1.2 20080704 (Red Hat 4.1.2-48)) Mon Aug 30 16:11:29 EDT 2010
Latest ChangeSet: unavailable
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
