xen January 2007

xen@lists.fedoraproject.org

57 participants
51 discussions

initscripts, xen and bonding
by Axel Thimm 04 Mar '07

04 Mar '07

Hi, I'm having a hard time getting bonding to work on FC5t3. It looks like the bond0 interface bond0 is renamed to pbond0 by xen [*] and the enslaving does not work anymore then. It works if I log on the terminal and ifenslave the devices to pbond0 instead of bond0 after the boot process has finished. But I want this to be handled automatically during reboots, so I tried assigning the bonding slaves to pbond0 as a master in the ifcfg-eth{0,1} scripts, but that doesn't work. What is causing the bond0 rename and should this renaming be considered by initscript? Is this a user error or should I file this against bugzilla? xen or initscripts? Thanks! [*] The only reference I found was a Japanese site and google's translation of it. http://translate.google.com/translate?hl=en&sl=ja&u=http://hoop.euqset.org/… -- Axel.Thimm at ATrpms.net

3 8

Re: [Fedora-xen] VLANs on DomU domains
by Bertho Stultiens 26 Feb '07

26 Feb '07

> I am setting up a box with FC6 + xen with FC6 for the DomU guests. > I have a server with 4 gigabit ports and I want to use 802.1Q vlans on > one of the gig ports. > I have the VLANs configured in Dom0 without any addresses attached to > them. > How do I make the VLANs available to the guests? I want to make 4 > VLANs available to each guest. I have thought of a few alternatives > but I cannot get any to work. The easy way; I have installed FC6 with 802.1Q and 4 guests. It works very nicely. For each guest do: 1 - You need to enable vlans /etc/sysconfig/network. NETWORKING=yes VLAN=yes NETWORKING_IPV6=no HOSTNAME=xenbox2.example.com GATEWAY=192.168.42.1 2 - create a subinterface by file editting /etc/sysconfig/network-scripts/ifcfg-eth0.42: DEVICE=eth0.42 BOOTPROTO=static ONBOOT=yes IPADDR=192.168.42.102 NETMASK=255.255.255.0 TYPE=Ethernet 3 - depending on whether you want untagged packets on the same interface, you need to edit the /etc/.../ifcfg-eth0 file too. (note: the parent interface must be up for the tagged interface to work.) The lines commented out will assign an IP address to the untagged interface: DEVICE=eth0 BOOTPROTO=none ONBOOT=yes TYPE=Ethernet # BOOTPROTO=static # IPADDR=172.16.42.102 # NETMASK=255.255.255.0 4 - make sure that your /etc/hosts setup is correct. If you have DNS available 24/7, then only define localhost[.localdomain} as 127.0.0.1 and not the hostname itself. When you restart the network in the guest, then your guest will default to use the tagged interface vlan 42 (above example). If you want the untagged interface as default, then you can change the gateway and assign an IP address to it. On the host, you need to do a similar thing. Create a subinterface eth0.42 and assign an IP address to it. Once that is done, you can talk to your guests via dot1Q from your host. Beware of iptables! If you have a firewall setup, then you need to make sure that it is done right. Doing it right, though, is a though job with dot1Q in place. I have the firewall completely disabled on the host and guests. My firewall is placed physically separated on another box. > 1. Bridge the tagged 802.1Q stream from the Gig port through to the > guests and configure eth0.x. on the guests This would be above scenario. > 2. Create a bridge on Dom0 for each VLAN so that they appear as > eth0...eth3 on the guests. The xenbrX interfaces on the host already transport all packets because they are L2 bridges (see brctl). The bridge does not care whether the packets are .1Q tagged or not. The only thing you need is to instruct the kernel to look for/act on specifics by creating (sub-)interfaces. Now, if you want the guests not to know that they are connected to a VLAN, then you need a brigde-interface to do (un-)tagging for you. That means that you need to create a dot1Q subinterface on the host's physical peth[0-3] and add the subinterface to a new bridge. Normal scenario: peth0 -> xenbr0 -> vif0.0(host eth0) vif1.0(guest1 eth0) Dot1Q scenario: peth0.42 -> xenbr42 -> vif1.0(guest1 eth0) i.e.: # brctl addbr xenbr42 # ip link set xenbr42 up # vconfig add peth0 42 # ip link set peth0.42 up # brctl addif xenbr42 peth0.42 In the VM config you have now something like: vif = [ 'mac=00:16:3e:11:22:33, bridge=xenbr42', ] The VM's eth0 interface is created as part of bridge that will fowrard to a subinterface. The kernel will now do the tagging/untagging (note: slow) and the VM cannot see that it is attached to a VLAN. Theoretically it should work, but I was not able to make this scenario work as expected though. I suspect that the hosts peth0 -> eth0 bridge is interfering (which has a tagged interface too in my setup). Or maybe my fingers were too fast at typing and I forgot a simple thing... > The xen documentation is minimal for configuring VLANs. Is there a > (FC6) supported way of configuring them? Vlans is a no-issue for xen. It is layered in the network and xen only passes the packets. -- Greetings Bertho Bertho Stultiens Senior Systems Manager Mobilethink A/S

3 5

Vanishing Harddisk
by sjafri＠purdue.edu 25 Feb '07

25 Feb '07

Hello All, I hope some one can help me. I have xen running on Fedora Core 6, now when I try to add a guest os using virt-manager there are no hard disks detected. the whole process goes fine until I have to pick a partition for installation. I tried using both a file as avirtual disk and also a partition, in both cases I come to stop because no hard disks or partitions are selected. Ali

3 2

destroydevice
by Jordi Prats 23 Feb '07

23 Feb '07

Hi, It seems there's a problem on 2.6.19-1.2895.fc6xen xen kernel and the xm tool: creating a new VM it aborts showing this error: [root@inf16 ~]# xm create /etc/xen/rata.cfg Using config file "/etc/xen/rata.cfg". Error: destroyDevice() takes exactly 3 arguments (2 given) [root@inf16 ~]# Anyone knows what is causing this? On the xen-users list there's some other messages related to this isue (one mine). Mats Petersson say that this may be causes by a backport. There's something broken on the package? There's any easy workarround? Thank you, -- ...................................................................... __ / / Jordi Prats Català C E / S / C A Departament de Sistemes /_/ Centre de Supercomputació de Catalunya Gran Capità, 2-4 (Edifici Nexus) · 08034 Barcelona T. 93 205 6464 · F. 93 205 6979 · jprats(a)cesca.es ...................................................................... pgp:0x5D0D1321 ......................................................................

3 6

DomU boot on Fedora 6 fails with 'no root found' error.
by K T Ligesh 01 Feb '07

01 Feb '07

I am trying to get Xen running on Fedora 6, which I thought would be easy, but I guess not. I am using the standard image from jailtime.org and my domU configuration file is below. I am using the same kernel of the host itself. ------------ kernel = '/boot/vmlinuz-2.6.19-1.2895.fc6xen' ramdisk = '/boot/initrd-2.6.19-1.2895.fc6xen.img' memory = 512 name = 'test.vm' vif = ['vifname=vif-test0, mac=aa:00:f6:f4:06:1a'] vnc = 0 vncviewer = 0 serial = 'pty' disk = ['file:/home/test.vm//root.img,sda1,w', 'file:/home/test.vm//vm.swap,sda2,w'] root = '/dev/sda1 ro' ------------------ ------------------- Loading dm-zero.ko module Loading dm-snapshot.ko module Making device-mapper control node Scanning logical volumes Reading all physical volumes. This may take a while... No volume groups found Activating logical volumes Volume group "VolGroup00" not found Creating root device. Mounting root filesystem. mount: could not find filesystem '/dev/root' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! -------------------------- The above is the error I got. It seems the initrd is searching for volGroup00, which is how the '/' of the HOST is mounted, but I have explicitly given 'root =' in the config file. So I am confused. Is there anyone here who has experienced this beforehand? Thanks in advance.

5 26

"4gb seg fixup, process X" on FC6 dom0
by Jim McBeath 31 Jan '07

31 Jan '07

I am running a stock FC6 xen, with all yum updates through today, on a Shuttle box with a Core 2 Duo and 2GB of memory. I am getting "4gb seg fixup" for plenty of programs, including X, sh, ls, date, grep, less, ssh, su and vim. This is in dom0, with no domU running. The worst offender is X: in /var/log/messages, every five seconds it consistently logs something like this: Jan 18 19:34:59 gumby kernel: printk: 30302 messages suppressed. Jan 18 19:34:59 gumby kernel: 4gb seg fixup, process X (pid 4383), cs:ip 73:47150f2a 20,000 is typical for the number of messages suppressed. It varies in different five-second intervals from about 10,000 to 89,000. I have poked around on the net and searched through the archives for this group, without finding an answer. I have seen a few posts about 4gb-seg-fixup messages in domU, or from mono programs, or from older OSs that needed a "nosegneg" file in /etc/ld.so.conf.d, but none of those seem to apply here. Any suggestions? -- Jim McBeath [root@gumby ~]# uname -a Linux gumby.local 2.6.19-1.2895.fc6xen #1 SMP Wed Jan 10 19:47:12 EST 2007 i686 i686 i386 GNU/Linux [root@gumby ~]# ls /etc/ld.so.conf.d kernelcap-2.6.18-1.2869.fc6.conf mysql-i386.conf kernelcap-2.6.19-1.2895.fc6.conf qt-i386.conf [root@gumby ~]# cat /etc/ld.so.conf.d/kernelcap-2.6.19-1.2895.fc6.conf # This directive teaches ldconfig to search in nosegneg subdirectories # and cache the DSOs there with extra bit 0 set in their hwcap match # fields. In Xen guest kernels, the vDSO tells the dynamic linker to # search in nosegneg subdirectories and to match this extra hwcap bit # in the ld.so.cache file. hwcap 0 nosegneg [root@gumby ~]#

5 7

Poor Network Performance between dom-0 and dom-u
by Harald Schwier 30 Jan '07

30 Jan '07

Hi, i have problems concerning the network performance between dom-0 and a dom-u host. Messurement using iperf show [ 4] 1.0- 2.0 sec 7.85 MBytes 65.8 Mbits/sec Network performance between dom-0 and an external maschine shows gigabit speed. [ 5] 0.0- 1.0 sec 112 MBytes 938 Mbits/sec i am using Fedora core 6 on the dom-0 host and redhat 4.4 on the dom-u guest. Dom-u is fully virtualized. (Dual Xeon 5150 2.66GHz.) Any hints that could help to improve the performance are greatly appreciated. -- Harald

1 0

Broadcom Ethernet interface broken under kernel-xen (module issue?)
by Naoki 29 Jan '07

29 Jan '07

I just noticed this (and I think reported in fedora-devel) that under a new FC6 install using kernel-xen-2.6.18-1.2798.fc6 the 'eth0' device would DHCP and obtain an IP address, but then would be unable to ping even the default route, and would not respond to 'ethtool' commands, only stating "Link: Yes". 'mii-tool' just barfs saying "Operation not supported". Problem also seems to be in kernel-xen-2.6.19-1.2895.fc6 although I have some problems blocking testing there. I have seen this on an IBM server and a Dell desktop, both using Broadcom adaptors. Sounds to be the same issues as http://lists.xensource.com/archives/html/xen-users/2006-07/msg00599.html http://lists.xensource.com/archives/html/xen-users/2006-08/msg00553.html Working (until IRQ bug kills it) 2.6.19-1.2895.fc6 alias eth0 tg3 # lspci |grep -i eth 02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 01) Working 2.6.18-1.2798.fc6 alias eth0 bnx2 # lspci |grep -i eth 04:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 11) 06:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet (rev 11) And this BZ looks like the same problem, I'll add my info there unless anybody tells me I'm on the wrong track.. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=213991

1 0

FC6: guest's with link in /etc/xen/auto not startet after xen update
by Thomas von Steiger 29 Jan '07

29 Jan '07

Hello, I have updated fc6 to xen-3.0.3-3 and kernel-xen 2.6.19-1.2895 without any problem. After reboot all the guest's with a link in /etc/xen/auto don't start automatically. How I can autostart the guest with this xen releases ? If I try to start the guest's with "xm create rhel41" for example, all the guest's are running without problem. Many Thanks for any Tips, Thomas -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.432 / Virus Database: 268.17.6/646 - Release Date: 23.01.2007 03:36

3 4

NetBSD 3.1 on fc6 xen 3.0.3
by Timothy D. Keanini Sr. 29 Jan '07

29 Jan '07

Hello, I've been trying to setup a instance of NetBSD-3.1 on a fc6xen Dom-0 Linux testlab 2.6.18-1.2849.fc6xen #1 SMP Fri Nov 10 12:57:36 EST 2006 x86_64 x86_64 x86_64 GNU/Linux [root@testlab netbsd]# xm info host : testlab release : 2.6.18-1.2849.fc6xen version : #1 SMP Fri Nov 10 12:57:36 EST 2006 machine : x86_64 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 2 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 2189 hw_caps : 178bfbff:e3d3fbff: 00000000:00000010:00000001:00000000:00000003 total_memory : 16319 free_memory : 512 xen_major : 3 xen_minor : 0 xen_extra : .3-rc5-1.2849.f xen_caps : xen-3.0-x86_64 xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.1 20061011 (Red Hat 4.1.1-30) cc_compile_by : brewbuilder cc_compile_domain : build.redhat.com cc_compile_date : Fri Nov 10 12:30:42 EST 2006 xend_config_format : 2 What follows is my process and at the end my errors when I go to 'xm create' the dom-U ## setup storage space for our new netbsd instance /usr/sbin/lvcreate -L4g -n lvnetbsd31 vg --- Logical volume --- LV Name /dev/vg/lvnetbsd31 [deleted] #### download the kernels ## I tried both the Oct 31 2006 build and the Jan 6 2007 build of 3.1 from HEAD ## First try at using NetBSD-3.1 distrubution ftp.netbsd.org:/pub/NetBSD/NetBSD-3.1/i386/binary/kernel> -rw-r--r-- 1 1369 netbsd 1762990 Oct 31 05:10 netbsd-XEN3_DOMU.gz -r--r--r-- 1 1369 netbsd 1673944 Oct 31 05:12 netbsd- INSTALL_XEN3_DOMU.gz [root@testlab netbsd]# openssl dgst md5 netb* MD5(netbsd-INSTALL_XEN3_DOMU)= 68f054de424d9f3b2151a28ab125fc92 MD5(netbsd-XEN3_DOMU)= 5c9c409593ed552e97853f7d34539623 ## Second Try at this using the HEAD distrubtion ftp.netbsd.org:/pub/NetBSD/NetBSD-daily/HEAD/200701040000Z/i386/ binary/kernel> MD5(netbsd-INSTALL_XEN3_DOMU)= c80ab0a7bda7617a936a3f3244b86a8a MD5(netbsd-XEN3_DOMU)= eb7483c4604c6c57615d94ce4b078d7f [root@testlab netbsd]# file * netbsd-INSTALL_XEN3_DOMU: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, for NetBSD 4.99.7, not stripped netbsd-XEN3_DOMU: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), statically linked, for NetBSD 4.99.7, not stripped #### Simple configuration [root@testlab netbsd]# cat /etc/xen/netbsd.cfg # main configuration name = "netbsd31" kernel = "/data/xenimages/netbsd/netbsd-INSTALL_XEN3_DOMU" root="/dev/hda1" memory = 512 disk = [ 'phy:/dev/vg/lvnetbsd31,0x3,w' ] #network information ip = "10.10.80.60" netmask = "255.255.255.0" gateway = "10.10.80.1" ##### [root@testlab netbsd]# cp netbsd.cfg /etc/xen/netbsd.cfg [root@testlab netbsd]# xm create -c /etc/xen/netbsd.cfg Using config file "/etc/xen/netbsd.cfg". Error: (22, 'Invalid argument') ## xend.log output [2007-01-09 11:45:05 xend.XendDomainInfo 2291] DEBUG (XendDomainInfo: 190) XendDomainInfo.create(['vm', ['name', 'netbsd31'], ['memory', 512], ['vcpus', 1], ['image', ['linux', ['kernel', '/data/xenimages/ netbsd/netbsd-INSTALL_XEN3_DOMU'], ['ip', '10.10.80.60:1.2.3.4:10.10.80.1:255.255.255.0::eth0:off'], ['root', '/ dev/hda1'], ['vncunused', 1], ['xauthority', '/root/.Xauthority']]], ['device', ['vbd', ['uname', 'phy:/dev/vg/lvnetbsd31'], ['dev', '0x3'], ['mode', 'w']]]]) [2007-01-09 11:45:05 xend.XendDomainInfo 2291] DEBUG (XendDomainInfo: 296) parseConfig: config is ['vm', ['name', 'netbsd31'], ['memory', 512], ['vcpus', 1], ['image', ['linux', ['kernel', '/data/xenimages/ netbsd/netbsd-INSTALL_XEN3_DOMU'], ['ip', '10.10.80.60:1.2.3.4:10.10.80.1:255.255.255.0::eth0:off'], ['root', '/ dev/hda1'], ['vncunused', 1], ['xauthority', '/root/.Xauthority']]], ['device', ['vbd', ['uname', 'phy:/dev/vg/lvnetbsd31'], ['dev', '0x3'], ['mode', 'w']]]] [2007-01-09 11:45:05 xend.XendDomainInfo 2291] DEBUG (XendDomainInfo: 395) parseConfig: result is {'shadow_memory': None, 'uuid': None, 'on_crash': None, 'on_reboot': None, 'localtime': None, 'image': ['linux', ['kernel', '/data/xenimages/netbsd/netbsd- INSTALL_XEN3_DOMU'], ['ip', '10.10.80.60:1.2.3.4:10.10.80.1:255.255.255.0::eth0:off'], ['root', '/ dev/hda1'], ['vncunused', 1], ['xauthority', '/root/.Xauthority']], 'on_poweroff': None, 'bootloader_args': None, 'cpus': None, 'name': 'netbsd31', 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features': None, 'vcpu_avail': None, 'memory': 512, 'device': [('vbd', ['vbd', ['uname', 'phy:/dev/vg/lvnetbsd31'], ['dev', '0x3'], ['mode', 'w']])], 'bootloader': None, 'cpu': None, 'maxmem': None} [2007-01-09 11:45:05 xend.XendDomainInfo 2291] DEBUG (XendDomainInfo: 1253) XendDomainInfo.construct: None [2007-01-09 11:45:05 xend.XendDomainInfo 2291] DEBUG (XendDomainInfo: 1285) XendDomainInfo.initDomain: 21 1.0 [2007-01-09 11:45:05 xend 2291] INFO (image:214) configuring linux guest [2007-01-09 11:45:06 xend 2291] DEBUG (balloon:127) Balloon: 525000 KiB free; need 524288; done. [2007-01-09 11:45:06 xend 2291] INFO (image:138) buildDomain os=linux dom=21 vcpus=1 [2007-01-09 11:45:06 xend 2291] DEBUG (image:193) dom = 21 [2007-01-09 11:45:06 xend 2291] DEBUG (image:194) image = / data/xenimages/netbsd/netbsd-INSTALL_XEN3_DOMU [2007-01-09 11:45:06 xend 2291] DEBUG (image:195) store_evtchn = 1 [2007-01-09 11:45:06 xend 2291] DEBUG (image:196) console_evtchn = 2 [2007-01-09 11:45:06 xend 2291] DEBUG (image:197) cmdline = ip=10.10.80.60:1.2.3.4:10.10.80.1:255.255.255.0::eth0:off root=/dev/hda1 [2007-01-09 11:45:06 xend 2291] DEBUG (image:198) ramdisk = [2007-01-09 11:45:06 xend 2291] DEBUG (image:199) vcpus = 1 [2007-01-09 11:45:06 xend 2291] DEBUG (image:200) features = [2007-01-09 11:45:06 xend.XendDomainInfo 2291] ERROR (XendDomainInfo: 202) Domain construction failed Traceback (most recent call last): File "/usr/lib64/python2.4/site-packages/xen/xend/ XendDomainInfo.py", line 195, in create vm.initDomain() File "/usr/lib64/python2.4/site-packages/xen/xend/ XendDomainInfo.py", line 1363, in initDomain raise VmError(str(exn)) VmError: (22, 'Invalid argument') ### xend-debug.log output ## ERROR: Kernel not a Xen-compatible Elf image. ERROR: Error constructing guest OS ERROR: Kernel not a Xen-compatible Elf image. ERROR: Error constructing guest OS ERROR: Kernel not a Xen-compatible Elf image. ERROR: Error constructing guest OS

4 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen January 2007