xen November 2007

xen@lists.fedoraproject.org

39 participants
39 discussions

How is network bridging for Xen handled in F7?
by Christian Reiter 06 Feb '08

06 Feb '08

Hi! Can anybody tell me where i can find docs about handling network bridges for xen domUs in Fedora 7? Something changed since FC6, so i cannot figure out how to create simple bridges without dhcp for my xen domUs. All what i want is: xenbrINTERNET should bridge to eth1 xenbrLAN should bridge to eth0 eth0 and eth1 of my dom0 should also have an IP Address. I do not want routing or nat for my domUs. Thanks! regards, christian

3 7

Guest VM dropping connection.
by Ubaidul Khan 15 Jan '08

15 Jan '08

I am running RHEL5 Guest and Host. The guest OS is dropping network connections occasionally(I noticed my ssh session suddenly terminated). The guest is configured with private network interface and a public network interface. Following are the bridge/network settings for the host: bridge name bridge id STP enabled interfaces xenbr0 8000.feffffffffff no vif2.0 vif1.0 peth0 vif0.0 xenbr1 8000.fefffffffffe no vif2.1 peth1 vif0.3 xenbr1 is dedicated to provide the private network link for the guest os. Following is the guest OS configuration: # Automatically generated xen config file name = "saleen_webvm0" memory = "1000" disk = [ 'tap:aio:/vms/img/redhat/linux/es/5.0/x86_64/saleen_webvm0.img,xvda,w','phy:/dev/sdc,xvdb,w' ] vif = [ 'mac=00:16:3e:2e:6f:e1, bridge=xenbr0','mac=00:16:3e:2f:9e:b1, bridge=xenbr1',] # vif = [ 'mac=00:16:3e:2e:6f:e1, bridge=xenbr0',] vfb = ["type=vnc,vncunused=1"] uuid = "122374dc-26a3-cb0d-99f8-3393e2481777" bootloader="/usr/bin/pygrub" vcpus=2 on_reboot = 'restart' on_crash = 'restart' Following is the output of ifconfig: eth0 Link encap:Ethernet HWaddr 00:14:4F:40:D8:70 inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.255 Mask:255.255.255.0 inet6 addr: fe80::214:4fff:fe40:d870/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:79313 errors:0 dropped:0 overruns:0 frame:0 TX packets:1167 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6619719 (6.3 MiB) TX bytes:115448 (112.7 KiB) eth1 Link encap:Ethernet HWaddr 00:14:4F:40:D8:71 inet addr:xxx.xxx.xxx.xxx Bcast:xxx.xxx.xxx.255 Mask:255.255.255.0 inet6 addr: fe80::214:4fff:fe40:d871/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:720 (720.0 b) 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:105404 errors:0 dropped:0 overruns:0 frame:0 TX packets:13455 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9122426 (8.6 MiB) TX bytes:1997833 (1.9 MiB) Base address:0x8c00 Memory:fa5e0000-fa600000 peth1 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FE inet6 addr: fe80::fcff:ffff:feff:fffe/64 Scope:Link UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:9239102 errors:0 dropped:0 overruns:0 frame:0 TX packets:5337342 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:12420212276 (11.5 GiB) TX bytes:523849820 (499.5 MiB) Base address:0x8800 Memory:fa5c0000-fa5e0000 vif1.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:2174 errors:0 dropped:0 overruns:0 frame:0 TX packets:80032 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:446031 (435.5 KiB) TX bytes:6941997 (6.6 MiB) vif2.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:10084 errors:0 dropped:0 overruns:0 frame:0 TX packets:89284 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:1186096 (1.1 MiB) TX bytes:7380350 (7.0 MiB) vif2.1 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:5337343 errors:0 dropped:0 overruns:0 frame:0 TX packets:9239082 errors:0 dropped:20 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:403712612 (385.0 MiB) TX bytes:12383227754 (11.5 GiB) Any help is greately appreciated. _________________________________________________________________ http://liveearth.msn.com

3 3

recompile for using sdl and vnc
by nooroon 05 Dec '07

05 Dec '07

Hello, I'm using fedora 7 with xen 3.1 from binaries rpm. I try to use the sdl display, but when i configure my VM with *<graphics type='sdl'/> * no window pops up. Thanks to goolgle, I've found someone how got the same issue, and it seems that qemu-dm was not compile whith sdl support. What is the best way to recompile qemu-dm whith sdl support? In fact, I'd like to have sdl for local display of my VM, and vnc for remote access to it. What configuration should I use to do so? Thanks

4 5

Xen : virsh error
by unixfoo 04 Dec '07

04 Dec '07

Greetings, When I try to use "virsh", I get the below error. ( xm list returns details though ). I use Fedora 8 and xen. [root@un1xf00 ~]# virsh virsh: error: failed to connect to the hypervisor [root@un1xf00 ~]# xm list Name ID Mem VCPUs State Time(s) Domain-0 0 4885 4 r----- 399430.4 webhttp10000 11 2048 2 -b---- 65141.6 webhttp10001 18 2560 2 -b---- 358.0 webhttp10002 14 2048 2 -b---- 81720.5 [root@un1xf00 ~]# Any configuration to be done for virsh. Please help -unixfoo http://unixfoo.blogspot.com

5 9

Best practices questions
by Lopez, Denise 03 Dec '07

03 Dec '07

Hi all, I am in the process of building a new Xen server from scratch and wanted to ask a couple of questions about best practices. First, should the guest domains be image files or LVM's or just regular ext3 partitions? What are the pros and/or cons of each? Second, since the Dom0 is supposed to be kept secure, and most of my servers I don't install any X11 server on, is there any security risk installing an X11 server on the Dom0 in order to take advantage of the virt-manager GUI interface? Thank you in advance for any thoughts and or opinions. Denise Lopez UCLA - Center for Digital Humanities Network Services Linux Systems Engineer 337 Charles E. Young Drive East PPB 1020 Los Angeles, CA 90095-1499 310/206-8216

6 6

FYI: The plan for Xen kernels in Fedora 9
by Daniel P. Berrange 01 Dec '07

01 Dec '07

This is a friendly alert of the major plans we have for Xen kernels in Fedora 9 timeframe... Since we first added Xen in Fedora Core 5, our kernels have been based on a forward-port of XenSource's upstream Xen kernels, to new LKML. For a long time we ported their 2.6.16 tree to 2.6.18. Now we do ports of their 2.6.18 tree to 2.6.21/22/23, etc. At the same time, upstream Linux gained Xen support for i386 DomU, and shortly x86_64 DomU, and is generally getting ever more virtualization capabilities. As everyone knows, we have tended to lag behind Fedora's state-of-the-art bare metal kernels by several releases due to the effort required to port Xen to newer LKML releases. Despite our best efforts, this lag has been getting worse, not better. We have taken the decision, that this situation is unacceptable for Fedora 9. We simply cannot spend more time forward porting Xen kernels. Either Xen has to be dropped entirely, or we need a different strategy for dealing with the kernels. Since people seeem to use Xen, we have decided not to drop it :-) So the plan is to re-focus 100% of all Xen kernel efforts onto paravirt_ops. LKML already has i386 pv_ops + Xen DomU. We intend to build on this to add: - x64_64 pv_ops - x86_64 Xen DomU on pv_ops - i386 & x86_64 Xen Dom0 on pv_ops - memory balloon - paravirt framebuffer - save/restore All of this based on same LKML release as Fedora bare metal. If all goes to plan it may even be in the base kernel RPM, instead of kernel-xen, but thats a minor concern compared to the actual coding. Getting all this done for Fedora 9 is seriously ambitious, but it is the only long term sustainable option, other than dropping Xen entirely. What this means though, is that Fedora 9 Xen will certainly be going through periods of instability and will certainly be even buggier than normal. F9 may well end up lacking features compared to Xen in Fedora 8 & earlier (eg no PCI device passthrough, or CPU hotplug). On the plus side though we will be 100% back in sync with bare metal kernel versions & hopefully even have a lot of this stuff merged in LKML to make ongoing maintainence sustainable. Short term pain; Long term gain! I have not got any ETA on when any of these kernel changes will appear in rawhide - some time before the F9 feature freeze date is best guesstimate. We will alert people when the time comes. There is a F9 feature page with some amount of info about the plan... http://fedoraproject.org/wiki/Features/XenPvops In terms of Fedora 6/7/8 maintainence... The kernel-xen in these existing releases already lags behind the bare metal kernel version by 2-3 releases. We do not intend to continue trying to rebase the kernel-xen in existing Fedora releases. It will be essentially important bug-fix mode only. This is neccessary to enable maximum resources to be focused on the critical Fedora 9 Xen work. Regards, Dan ...on behalf of some very busy Fedora Xen kernel developers :-) -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|

5 6

Fedora Core 8 + Xenbr0 + network bridging?
by David Levinger 30 Nov '07

30 Nov '07

Hello all, I was working with Xen and Cent OS and by default a virtual networking driver called Xenbr0 was created that acted as a "pass through" for the virtual machine. IE that machine contacted our real DHCP server and requested an IP address and all was well. However, on Fedora Core 8 it seems that the default networking setup is to use virbr0 and to have a totally different subnet and the host machine assigning IP addresses to the guests... How can I get back to just a pure network bridge that had the guests contact our DHCP server for leases? Thanks! David **************************************************************************** Checked by MailWasher server (www.Firetrust.com) WARNING. No FirstAlert account found. To reduce spam further activate FirstAlert. This message can be removed by purchasing a FirstAlert Account. ****************************************************************************

4 7

Cannot create domU with virt-install when VT is enabled on DELL PowerEdge 1950
by Anne Facq 30 Nov '07

30 Nov '07

Hello I've got a dom0 on Fedora 8 running on a DELL PowerEdge 1950 ** With "Virtulization Technology" enabled in the BIOS of the DELL PowerEdge 1950, I've got problems using virt-install These problems are on Fedora 8 32 bits and on Fedora 8 64 bits : - with 'virt-install --parav ...' installation freezes randomly - with 'virt-install --hvm ...' the domU freezes after "Creating domain..." : ------------------------ Starting install... libvir: Xen Daemon error : GET operation failed: Retrieving file fedora.cs 100% |=========================| 2.8 kB 00:00 Retrieving file boot.iso. 100% |=========================| 9.2 MB 00:01 libvir: Xen Daemon error : GET operation failed: Creating domain... 0 B 00:01 ------------------------ - NB : with virt-manager the installation the domU freezes after clicking the "Finish" button ** With "VT" disabled in the BIOS, I've successfully created a Fedora 8 domU (with virt-install). And if I reboot the PowerEdge with VT enabled, I can start a domU (created with VT disabled). So the problem with VT is only during the installation phase. Any ideas ? Did anybody succeed in installing domU whith "Virtualization Technology" enabled on a PowerEdge 1950 Thanks in advance Anne Facq -- Anne Facq System Engineer CRPP - Centre de Recherche Paul Pascal Mel : annefacq(a)crpp-bordeaux.cnrs.fr Tel : 05 56 84 56 62 Fax : 05 56 84 56 00 http://www.crpp-bordeaux.cnrs.fr/~annefacq

1 0

Problems with fedora 7 paravirtualize
by neohtm 30 Nov '07

30 Nov '07

I'm using Fedora 7 with xen's virt-manager. I'd manage to install a full virtualized WinXp domU after changing the settings in .xml files. Now I would like to try to install the paravirtualize fedora 7 using virt-manager I'm using this install media address > http://download.fedora.redhat.com/pub/fedora/linux/core/6/i386/os/ And the virt-manager console was managed to show up the installation screen. After the normal steps of the installation, the console was hanged when it shows the 'Retrieving image2' I even had tried to used the Fedora 7 installation DVD as the installation media but it's cant detect the cdrom when the installation begins. I'd googled and find out that I can export the DVD using a FTP/NFS/HTTP from dom0 host, but how to do this? According to Sadique, the Fedora 8 seems to have a better and easy virt-manager to manipulate the Xen virtualization. How to upgrade the fedora 7's virt-manager to fedora 8's? --Stephen Neohtm,Malaysia

2 1

Slightly off-topic question about Xen+LVM
by Aaron Metzger 29 Nov '07

29 Nov '07

First let me say that I love the way virtualization has been integrated into Fedora! Thanks to all who have done this work. I have a simple question which is a little off-topic but I know that the experience is contained in this group of folks. Using the final release of Fedora 8 plus all released patches, I created an LVM volume group and an Ext3 logical volume upon which I am storing all of my Xen virtual machine images as normal files. I tried to use the system-config-lvm tool to create a snapshot of the logical volume and assigned it to a mount point that I created under "/mnt/vmbackups" and checked the box to have it mounted at boot time. When I rebooted the machine, the boot failed when It tried to access the snapshot logical volume. I'm not going to include the specific errors here because my question is much more general. Do snapshots of logical volumes work under Fedora 8? Google revealed some historical discussions about snapshots not working in the transition from LVM1 to LVM2. Is that the case? Is anyone successful creating logical volume snapshots under Fedora 8? Alternatively, is there any other reliable way to make a self-consistent copy of a running Xen virtual machine image for the case where the Xen virtual machine is held in a regular file system file? Is LVM my only option? Thanks in advance for any and all help. -- Aaron

6 10

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen November 2007