xen December 2006

xen@lists.fedoraproject.org

51 participants
68 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

Simple testing results for Xen and VMX on FC5-test2.
by You, Yongkang 12 Jan '07

12 Jan '07

Hi all, I have done a simple checking for Xen and VMX on FC5-test2. Basically, I can create VMX on FC5-test2 IA32. But FC5-test2 IA32e (x86-64) doesn't provide Xen and Xen0 kernel, so didn't do Xen and VMX testing for it. Beside of testing Xen and VMX, I also found some issues about installation, which I have updated the bug #179078 as a NB. The following is the testing results only for Xen and VMX. ========================= 1. *** IA32E hasn't RPMS about Xen hypervisor and Xen0/XenU kernels. __FAIL__ 2. *** In order to boot up IA32 Xen0, I have to add pci=noacpi as the boot parameters of Xen0 kernel, or system will hang when initial PCI. I don't know if it is only related to my Machine. __FAIL__ 3. After install IA32 Xen RPMs, I can see /boot/grub/grub.conf has been changed with Xen kernels. __PASS__ 4. *** /usr/lib/xen/boot/vmxloader isn't in the RPM package, so VMX Guest couldn't be created. I suspected build system hasn't bcc, it is from DEV86 package. __FAIL__ 5. After copy a useable vmxloader to the destination, IA32 VMX Guest can be created successfully! __PASS__ 6. VMX has good network connection and Xwindows started. __PASS__ 7. XenU can be created and works well. __PASS__ 8. Couldn't get Xen Changeset by "xm info" or "xm dmesg". 9. The new kernel names of Xen/Xen0/XenU seemed a little confused. E.g. the Xen0 name is like vmlinuz-2.6.15-1.29_FC5hypervisor. I thought hypervisor is for Xen.gz. Xen0 is the Service OS. ========================== Any comments please let me know. But I will have 8 days holiday from tomorrow, so emails reply might be slow and occasional. [FYI] We are planning to do more testing for FC5-test3. Best Regards, Yongkang (Kangkang) 永康

4 4

treating logical volumes as physical drives
by Justin Wickett 09 Jan '07

09 Jan '07

I would like to use a logical volume as a "physical" drive on which I can install a fedora operating system. As of now, when I run xenguest- installer, it treats the install location that I specified ( which is an unformatted logical volume that I had just created ) as a physical drive (named "xvda") and allows me to perform a basic install on it. When I look at that logical volume, it comes up as a "foreign" device, because it contains a /boot directory, and a volume group consisting of a / directory and a swap directory. I was wondering how to mimic that effect without using my xenguest-installer program, so that when I pop a CD in and the installer starts up, I can specify a logical volume and let the installer treat it as a physical drive just like the xenguest-installer program does. I am trying to accomplish this because I was unable to install FC4 via the xenguest-installer. I had mounted the image as a loopback device to /var/ftp/pub and specified the /pub directory in FTP server's root folder as my "Installation source", and was greeted by an error from my FTP server (vsftpd) saying "550 Failed to change directory". When I do the exact same thing except mount the FC6 iso instead of the FC4 iso, everything works fine. What could I be doing wrong? If all else fails, I guess I can just specify in my /etc/xen/xm- fc4-001 file the kernel and the ramdisk parameters, and install FC4 on an ext3 formatted logical volume specified as the / directory, and thus reuse my existing /boot directory instead of trying to use the pygrub bootloader with a new /boot directory. In this case, where could I find a compiled xenU kernel and an appropriate initrd image for FC4? Thank you very much and happy new years to all! Justin Wickett Duke 2010 http://www.duke.edu/~jyw2

2 3

starting a vm with virt-manager
by Henning Sprang 02 Jan '07

02 Jan '07

Hi, Somehow I'd expect such a nice graphical tool as virt.manager, that, if I can install, (and start the installed machine directly after install), stop, restore, and do all the other nice things with a xen vm, I must also be able to simply start a vm for which I have a config lying around. But I see nowhere any "start a vm" option. The only thing that is there is a "restore vm" option, but when I chose a normal vm config file, it always says "error restring domain - is the domain already running". I assume, this function is really only for domains that I saved (not the same as opposed to shut down, at leat in xen terminology). Is that right? Am I right that virt.manager has no functionality to simply start a vm with it's config file, and I must do this manually? Henning

4 5

FC6 Xen stability?
by Tony Coffman 28 Dec '06

28 Dec '06

Can anybody offer their experience running a production FC6/Xen environment? I'm looking for big uptimes for a mix of FC5/FC6 paravirtualized guests. I'm currently running FC5 as the host using the non-PAE 2133 kernel. I had issues (random lockups and network failures after 2-3 days) with the next 3-4 kernels that shipped after 2133 so I got off the upgrade treadmill but as a result I'm pretty far behind. I'd like to get current and switch to PAE but I'm really not looking forward to more problems so I'm wondering about the stability of current FC6? In particular if you have a favorite kernel/Xen version that's produced high uptimes I'd love to hear about it. Thanks, --Tony

1 0

winxp from cdrom
by Shirazi, Goodarz 27 Dec '06

27 Dec '06

Hi folks, how can I install winxp from cdrom the drive assembly? Virtual Machine Manager auf FC6 says: Install location must be an NFS, HTTP or FTP install source

2 1

Format of guest image files?
by Philip Rhoades 27 Dec '06

27 Dec '06

People, Firstly, congratulations on some nice work! - I could not get inter-guest or host-guest networking on FC5 but it started working immediately on FC6 - thanks! On a FC6 host I have created a FC6 guest minimal install (everything checked off except for text networking) in a 1.5GB image file. What is the format of this image? Is it possible to somehow use a loopback switch to mount it like iso9660? - I want to be able to make a copy of the image file; in the image, edit the /etc/sysconfig/network and /etc/sysconfig/network-scripts/ifcfg-eth0 files; add an appropriate /etc/xen config file and then be able to boot a second guest. Is this possible somehow? Thanks, Phil. -- Philip Rhoades Pricom Pty Limited (ACN 003 252 275 ABN 91 003 252 275) GPO Box 3411 Sydney NSW 2001 Australia Mobile: +61:(0)411-185-652 Fax: +61:(0)2-8221-9599 E-mail: phil(a)pricom.com.au

3 3

Using large disk in DomU
by Robin Bowes 27 Dec '06

27 Dec '06

Hi, I'm running Xen 3.0.3 on FC6 with FC6 DomU guests. On the Dom0 machine, I have 8 x 500GB disks running as a RAID6 array with lvm on top of that. There is one partition available: /dev/vg_media/lv_media which has an ext3 FS on it. I want to make this available to a DomU guest, so I put this in the xen config file: disk = [ 'phy:/dev/vg_host/lv_slim,xvda,w', 'phy:/dev/vg_media/lv_media,sda1,w', ] The disk appears in the DomU guest, but if I fsck it, this is what I see: # fsck /dev/sda1 fsck 1.39 (29-May-2006) e2fsck 1.39 (29-May-2006) The filesystem size (according to the superblock) is 732575744 blocks The physical size of the device is 195704832 blocks Either the superblock or the partition table is likely to be corrupt! Abort<y>? yes Any idea what's going on here? Am I doing something wrong? R.

2 11

Problems on Core 2 Duo
by Adam Huffman 26 Dec '06

26 Dec '06

I have reported https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=220134 because the current Xen kernel is unusable on a Vaio SZ3WXP - the clock runs twice as fast as it should and applications crash. Is anyone else experiencing similar symptoms with this sort of hardware? Adam

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen December 2006