xen August 2007

xen@lists.fedoraproject.org

42 participants
41 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

Possible to skip reboot with virt-install?
by David Mueller 31 Aug '07

31 Aug '07

Is it possible to tell virt-install to skip the reboot it does after completing the OS install to a guest? I'm writing some shell scripts to automate creating and running of virtual machines, and the reboot after the install is just slowing things down as I have to wait for it to boot up, then shut it down before I can continue. I'm using a customized Fedora 7 installer creating using Revisor and a kickstart file, so if it's a change I need to do there (thinking perhaps that the command to restart rather than shut down is coming from the guest) I can. I noticed that using virt-manager, when the install finished and I hit restart, the guest simply shut down. - David

2 1

libvir: Xen error on Guest install - Fedora 6 64-bit
by achan＠jonathan360.com 30 Aug '07

30 Aug '07

I'm having difficulties getting Xen to run on Fedora 6 64-bit. The host system is a dual core opteron server with 1gb of ram. This server does not have X installed and is only reachable via ssh, so any graphical tools can't be used. I have the following installed xen-3.0.3-9 libvirt-0.3.1-1 kernel-xen-2.6.20-1.3001 The xen kernel loads fine: Linux removed.removed.com 2.6.20-1.3001.fc6xen #1 SMP Thu Aug 9 16:18:42 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux and domU is up and running: Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 723 2 r----- 30.9 When i use virt-install i get the following virt-install --nographic Would you like a fully virtualized guest (yes or no)? This will allow you to run unmodified operating systems. yes What is the name of your virtual machine? ostrich How much RAM should be allocated (in megabytes)? 256 What would you like to use as the disk (path)? /usr/virtualServers/ostrich.iso How large would you like the disk (/usr/virtualServers/ostrich.iso) to be (in gigabytes)? 4 What is the virtual CD image, CD device or install location? http://mirrors.kernel.org/fedora/releases/7/Fedora/x86_64/os/ Starting install... libvir: Xen error : Domain not found: xenUnifiedDomainLookupByUUID Retrieving file Fedora... 286 kB 00:01 Retrieving file boot.iso. 100% |=========================| 7.8 MB 00:17 libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName Creating storage file... 100% |=========================| 4.0 GB 00:00 Creating domain... 0 B 00:01 Domain installation still in progress. You can reconnect to the console to complete the installation process. At this point I get dumped back to a command prompt. If i try to reconnect to the console, I get: xenconsole: Could not read tty from store: No such file or directory I have no idea what to do from this point. I have checked log files however I can't find what's wrong. xend.log shows [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:472) hotplugStatusCallback /local/domain/0/backend/vbd/3/768/hotplug-status. [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:486) hotplugStatusCallback 1. [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for devices irq. [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for devices vkbd. [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for devices vfb. [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for devices pci. [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for devices ioports. [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for devices tap. [2007-08-30 10:48:31 xend 3449] DEBUG (DevController:143) Waiting for devices vtpm. [2007-08-30 10:48:31 xend 3449] INFO (XendDomain:370) Domain ostrich (3) unpaused. and the qemu-dm log says domid: 1 qemu: the number of cpus is 1 shared page at pfn:ffff, mfn: 8cef buffered io page at pfn:fffd, mfn: 8cf1 xs_read(): vncpasswd get error. /vm/6416a433-45ac-af5d-5a04-6f23be199dc4/vncpasswd. Could not initialize SDL - exiting I've spent three days with this and I haven't been able to find any help. I've found a lot of hints but nothing has worked. If someone can offer some assistance I'd greatly appreciate it!

1 1

ANNOUNCE: virt-top 0.3.2.5 released
by Richard W.M. Jones 29 Aug '07

29 Aug '07

I'm pleased to announce a new release of virt-top, which is a utility like 'top' that works for virtual machines. Many keys and command line options are the same as for ordinary top. Thanks to all the people who have been playing with it and sending me feedback. This version adds block device and network statistics (if supported by the hypervisor and libvirt). This version also fixes a bug where it would fail silently if unable to contact the hypervisor. Main page: http://et.redhat.com/~rjones/virt-top/ Source and binaries for several architectures available from: http://et.redhat.com/~rjones/virt-top/download.html If you have Fedora 7, this will probably work: yum --enablerepo=development install virt-top Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903

1 0

FC7 as guest on FC6 dom0?
by Robin Bowes 29 Aug '07

29 Aug '07

Hi, I have a FC6 machine: Linux wast.sitepen.com 2.6.20-1.2952.fc6xen #1 SMP Wed May 16 18:37:05 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux I have several guests running, including FC6, Windows Server 2003, and CentOS5. I want to install a FC7 guest but when I run the following virt-install command the installation freezes: virt-install --nographics --name=skeggles --file=/dev/vg_guests/lv_skeggles --ram=512 --location=http://mirrors.kernel.org/fedora/releases/7/Fedora/x86_64/os/ --extra-args="ip=172.29.172.50 netmask=255.255.255.0 gateway=172.29.172.1 dns=192.168.2.203,192.168.2.204 ks=http://dev.robinbowes.com/kickstart/sitepen/skeggles-FC7.cfg" It boots into the FC7 install but only gets as far as: Write protecting the kernel read-only data: 938k Then it hangs. Any idea what's up? R.

2 3

fedora4 guest iso
by paul 26 Aug '07

26 Aug '07

can you please give me an address where a fedora core 4 xen guest installation iso is. I have a bootable dvd but it does not seem to work properly!

2 1

Re: [Fedora-xen] Fedora 7 - missing dummy interfaces
by David Mueller 25 Aug '07

25 Aug '07

I'm making progress, but I've run into a couple issues. I've created the following three xml files for the three networks (I'm only worrying about one of the virtual machines now; once I get it working I should be able to replicate it for the other): <network> <name>emu0</name> <uuid>8d18febd-e295-4e67-9373-a8b2a5855e60</uuid> <bridge name='emubr0' stp='on' forwardDelay='0' /> <ip address='128.10.0.253' netmask='255.255.255.0' /> </network> <network> <name>emu2</name> <uuid>8d18febd-e295-4e67-9373-a8b2a5855e62</uuid> <bridge name='emubr2' stp='on' forwardDelay='0' /> </network> <network> <name>emu3</name> <uuid>8d18febd-e295-4e67-9373-a8b2a5855e63</uuid> <bridge name='emubr3' stp='on' forwardDelay='0' /> </network> emu2 and emu3 networks I didn't assign an IP address to since the host doesn't need one; they will be exclusively for VM to VM communcation. emu0 (and in the future emu1) will be used for communication between host and VM -- each will be a different subnet. And here is the xml dump of the VM, taken while its running: <domain type='kvm' id='5'> <name>emu0</name> <uuid>9b517b2c-b315-62fc-626b-2525e2576217</uuid> <memory>262144</memory> <currentMemory>262144</currentMemory> <vcpu>1</vcpu> <os> <type>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>destroy</on_crash> <devices> <emulator>/usr/bin/qemu-kvm</emulator> <disk type='file' device='disk'> <source file='/home/david/emu/kvm/f7_emu0.img'/> <target dev='hda'/> </disk> <interface type='network'> <mac address='1e:11:11:11:11:10'/> <source network='emu0'/> <target dev='vnet0'/> </interface> <interface type='network'> <mac address='1e:11:11:11:11:11'/> <source network='emu2'/> <target dev='vnet1'/> </interface> <interface type='network'> <mac address='1e:11:11:11:11:12'/> <source network='emu3'/> <target dev='vnet2'/> </interface> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='5900' listen='127.0.0.1'/> </devices> </domain> The first problem is that I can't get the guest VM to communicate with the host. I assign an address to the interface with this command: # /sbin/ifconfig eth0 128.10.0.1/24 up Then I attempt to ping the host, but get an error message Destinamtion Host Unreachable. The same happens if I try to ping the guest from the host. I did notice an additional oddity. While the three interfaces all show their correct MAC addresses in the Hardware tab of the Virtual Machine Details tab, if I run ifconfig within the guest, all three show the same address, 1E:11:11:11:11:12 (which should be eth2's MAC address). - David On 8/22/07, Daniel P. Berrange <berrange(a)redhat.com> wrote: > On Wed, Aug 22, 2007 at 07:04:55PM -0700, David Mueller wrote: > > On 8/22/07 Daniel P. Berrange wrote: > > >virt-manager will happily use bridging for KVM guests if you setup > > >your host so that its physical interfaces are part of a bridge. > > > > Actually, that's not quite what I need. The final setup will have two > > guest machines, each with an eth0 to communicate with the Domain 0 host. > > Each also will have a virtual eth1 and and eth2 that is used for > > communication between the two VMs. The virtual machines need to > > commuincate only with each other and the host; they don't actually need > > to connect to the network. Because this will run in an isolated network > > not connected to the Internet, we're not restricted to private address > > space and it would be much more work to remap all the addresses we use > > to be only in private address space. > > Ok, that makes sense. virt-manager restricts you to only allow private > address spaces - we could relax that to a warning. In the mean time you > could use 'virsh net-define' to setup a virtual network using a public > IP address range, and virsh doesn't enforce addresing policy. Use the > take a look at /usr/share/libvirt for an example XML file you can tweak. > For an isolated network, simply remove the <forward/> tag. > > Dan. > -- > |=- 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 > -=| >

3 4

Re: [Fedora-xen] Problems running xp guest
by Falk Zimmermann 24 Aug '07

24 Aug '07

Thanks a lot, this fixed the problem. Cheers, Falk Cole Robinson schrieb: > Falk Zimmermann wrote: > > >> <disk type='file' device='cdrom'> >> <driver name='file'/> >> <source file=''/> >> <target dev='hdc'/> >> <readonly/> >> </disk> >> > > This section is what is causing the error. With windows guests, the > tools try to do some funky stuff so that windows can still have access > to the install cd for the second stage of the install (after the first > reboot.) It probably shouldn't be erroring like that so there is a bug > somewhere, just not sure where in the chain it is. > > In the interim, you can get your guest to work with access to your iso > image with: > > - virsh dumpxml <xmdomain> > somefile.xml > - replace <source file=''/> with <source file='/path/to/win.iso'/> in > the above block in somefile.xml > - virsh undefine <xmdomain> > - virsh define somefile.xml > > If you don't need access to the iso in the guest, you can go to the > details section of the domain in virt-manager and remove hdc, which will > get rid of the block of xml without needing to undefine/define. > > - Cole > >

1 0

domUs become unaccessible running 2.6.20-1.2962.fc6xen on host
by Asrai khn 23 Aug '07

23 Aug '07

Hi, We have recently update kernel-xen on all of our hosts (3) and its vms all running fc6. kernel-xen 2.6.20-1.2962.fc6xen is doing good on two hosts and all its vms (10), however its giving lot of problem on third host. when i reboots the host into latest kernel-xen the domUs become unaccessible in a while hardly run for 10 minutes, 'xm list' still shows there status but i can't access it from outside. We are using loop back files for domUs File system, for testing i rebooted host into last working kernel 2.6.20-1.2952.fc6xen and domUs into latest kernel-xen and its doing pretty good, which mean latest kernel-xen is only giving problem at host side. when running 2.6.20-1.2962 on host it giving this in /var/log/messages Jul 12 10:42:45 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:42:50 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:42:50 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:42:55 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:42:55 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:00 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:00 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:05 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:05 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:10 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:10 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:15 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:15 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:20 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:20 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:25 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:25 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:30 xxxx kernel: printk: 4 messages suppressed. Jul 12 10:43:30 xxxx kernel: xen_net: Memory squeeze in netback driver. Jul 12 10:43:35 xxxx kernel: printk: 4 messages suppressed. Thanks. Askar

1 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xen August 2007