virt May 2010

virt@lists.centos.org

20 participants
13 discussions

4 CPU with WinXP on Centos 5.5 KVM?
by Marcelino Mata 28 May '10

28 May '10

Has anyone had any success getting WinXP 32bit to use 4 CPU's under Centos 5.5 KVM? I have tried everything and the best I can get is 2 CPU's. I tried everything listed here http://www.linux-kvm.com/content/running-windows-smp-guests I am using the VIRTIO drivers. Is this known limitation of KVM-83-164 (Centos5 release) with WinXP 32bit? I think there are reports of it working with 32bit Windows 2003 (or was it Windows 2008?). I know KVM is granting the 4 CPU's since Linux VM can use 4 CPU's on the same computer. Thanks, Marcelino Marcelino Mata Engineering Technology Specialist Multimatic Technical Centre 85 Valleywood Drive Markham, ON Canada L3R 5E5 Tel. +1 905 470 0025 CONFIDENTIALITY NOTE: This email (and attachments, if any) contain(s) information that is PRIVATE and CONFIDENTIAL, and may be LEGALLY PRIVILEGED or otherwise exempt from disclosure under applicable law. All copyright is reserved, and no right or license is granted to duplicate or publish the content of this email or to forward it to third parties, without, in each case, specific permission. If you have received this email in error, you must not copy, distribute, retain or use this email or the information contained in it for any purpose (other than to notify the sender). If you believe that you are not the intended recipient of this email, please contact the sender immediately and delete this email from your computer system (including any archive or other storage facilities). Thank you.

5 6

Libvirt NAT-based network 2x-4x faster than Libvirt routed network?
by Kenni Lund 28 May '10

28 May '10

Hi Is it expected behaviour that a libvirt NAT-based network is faster than a libvirt routed network? I would guess that the routed network would be the fastest one in all cases, but I'm seeing the opposite in my setup. On a 100mbit internet connection, the routed network tops at 4mbyte/sec, while the nat-based network goes all the way to 10mbyte/sec. I've spend the last 6 hours on trying to figure out the cause of this, changing settings, reinstalling the system, but the problem persists and I can't find the cause of it. It is a clean and fairly simple setup: - Clean installation of CentOS 5.5 - Installation of kvm+libvirt+virt-manager+xorg - iptables service disabled - 1 public IP for the host (xxx.yyy.zzz.215) on a /32 subnet with xxx.yyy.zzz.193 as gateway - 3 public IP for the routed network (xxx.yyy.zzz.251-253) on a /26 subnet with the same gateway as the host - 1 virtual machine with either the NAT or the routed libvirt network assigned I have no networking connection errors or similar, it works perfectly with both the NAT and the routed network, but the routed network is just 2-4 times slower than the NAT one. Do you have any suggestions of what the problem might be? When I look at the iptables rules generated by libvirt, and the routing table, everything looks fine AFAICT. Traceroute from guest doesn't reveal anything either. Ping times from the two networks are similar, so the main issue seems to be throughput. Any help or pointers to what I should look at, is highly appreciated... :) I've copy pasted some of my relevant system configuration into pastebin: http://pastebin.com/jtTrHLqA Thank you, Kenni

4 6

How to connect a guest to a fixed routable address?
by James B. Byrne 27 May '10

27 May '10

I am experimenting with kvm on a quad x86_64 running CentOS-5.5. I have created my first virtual guest and it seems to run fine. Now I wish to assign that particular guest to a fixed, public IP address. There seems to be at least two ways to proceed and I am soliciting comments on the preferred approach. In the first instance I can use brctl to create a bridged 'shared physical device' and presumably add that device to the network configuration of the guest, assigning the IP connection details there. In the second, I can continue to use the virtual networking system, albeit with fixed private as opposed to DHCP assigned addresses. In this case I gather that I must use ifconfig to add public IP addresses to the eth0 interface of the host and use iptables to route the public to the private address. Firstly, are my inferences correct? Are there any other approaches that I cannot discern? If these are the only two methods then which is the preferred one? I get the sense that bridging works in a manner that permits only one guest to access that physical device, however the documentation is not explicit on the matter. I have looked extensively for guidance but I suspect that a great deal of what I have read is somewhat dated and likely to cause me more trouble than help. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3

2 2

Xen 3.4 on CentOS 5.5
by C.J. Adams-Collier 26 May '10

26 May '10

Hey all, I'm trying to get Xen working well on CentOS 5.5. We currently build from source, and this is causing me all sorts of problems. What steps would be required to build an "official" CentOS 5.5 package of Xen 3.4? I am aware of the one on Gitmo, but this is not official. Looking forward to your responses, C.J.

2 1

Bug in reboot phase : workaround or patch ?
by Erwan MAS 26 May '10

26 May '10

Hello , I use Centos 5.4 , with the redhat version of xen . I need for some guest to change the hardware for the network . So in my xen config i add the model option in the vif line . When the guest boot , i had the right emulation , but after a reboot , the guest loose the configuration . Someone can confirm the bug in centos 5.5 ? Have someone a patch ? Extract of my config : builder = "hvm" vif = [ 'type=ioemu, mac=00:16:3e:50:10:45, bridge=xenbr0, model=ne2k_pci'] device_model = "/usr/lib64/xen/bin/qemu-dm" #grep spa.*/usr/lib64/xen/bin/qemu-dm /var/log/xen/xend.log [2010-05-24 11:47:23 xend 3782] INFO (image:434) spawning device models: /usr/lib64/xen/bin/qemu-dm ['/usr/lib64/xen/bin/qemu-dm', '-d', '75', '-m', '192', '-boot', 'dc', '-serial', 'pty', '-vcpus', '1', '-k', 'fr', '-domain-name', 'orange', '-net', 'nic,vlan=1,macaddr=00:16:3e:50:10:45,model=pcnet', '-net', 'tap,vlan=1,bridge=xenbr0', '-vnc', '127.0.0.45:1'] [2010-05-24 11:47:40 xend 3782] INFO (image:434) spawning device models: /usr/lib64/xen/bin/qemu-dm ['/usr/lib64/xen/bin/qemu-dm', '-d', '76', '-m', '192', '-boot', 'dc', '-serial', 'pty', '-vcpus', '1', '-k', 'fr', '-domain-name', 'orange', '-net', 'nic,vlan=1,macaddr=00:16:3e:50:10:45,model=rtl8139', '-net', 'tap,vlan=1,bridge=xenbr0', '-vnc', '127.0.0.45:1'] #rpm -qa | grep ^xen xen-libs-3.0.3-94.el5_4.2 xen-3.0.3-94.el5_4.2 #xm info host : james.mas.nom.fr release : 2.6.18-164.6.1.el5.centos.plusxen version : #1 SMP Wed Nov 4 10:10:32 EST 2009 machine : x86_64 nr_cpus : 2 nr_nodes : 1 sockets_per_node : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 2104 hw_caps : 178bfbff:ebd3fbff:00000000:00000010:00002001:00000000:0000011f total_memory : 4078 free_memory : 1738 node_to_cpu : node0:0-1 xen_major : 3 xen_minor : 1 xen_extra : .2-164.6.1.el5. xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-46) cc_compile_by : mockbuild cc_compile_domain : centos.org cc_compile_date : Wed Nov 4 09:23:54 EST 2009 xend_config_format : 2 -- ____________________________________________________________ / Erwan MAS /\ | mailto:erwan@mas.nom.fr |_/ ___|________________________________________________________ | \___________________________________________________________\__/

2 3

Re: [CentOS-virt] CentOS-virt Digest, Vol 33, Issue 9
by Musil Stanislav 25 May '10

25 May '10

S pozdravem Stan.M. On 25.5.2010, at 18:00, centos-virt-request(a)centos.org wrote: > Send CentOS-virt mailing list submissions to > centos-virt(a)centos.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.centos.org/mailman/listinfo/centos-virt > or, via email, send a message with subject or body 'help' to > centos-virt-request(a)centos.org > > You can reach the person managing the list at > centos-virt-owner(a)centos.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of CentOS-virt digest..." > > > Today's Topics: > > 1. Re: open-vm-tools 20100425 rpm (David Hollis) > 2. Bug in reboot phase : workaround or patch ? (Erwan MAS) > 3. Re: Bug in reboot phase : workaround or patch ? (Pasi K?rkk?inen) > 4. Re: Bug in reboot phase : workaround or patch ? (Erwan MAS) > 5. Libvirt NAT-based network 2x-4x faster than Libvirt routed > network? (Kenni Lund) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 24 May 2010 16:02:06 -0400 > From: David Hollis <dhollis(a)davehollis.com> > Subject: Re: [CentOS-virt] open-vm-tools 20100425 rpm > To: centos-virt(a)centos.org > Message-ID: <4BFADB3E.80701(a)davehollis.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On 05/23/2010 04:02 PM, Fernando Gleiser wrote: > >> Do they require any special repos besides the base ones? I'm trying >> to build them on a 32-bit centos 5.4 VM on top of vmware server and >> the build doesn't even start, it fails with: >> >> [root@localhost SPECS]# rpmbuild -ba open-vm-tools-kmod.spec >> error: Failed build dependencies: >> uriparser-devel is needed by open-vm-tools- >> kmod-0-1.20100425.i386 >> kernel-devel-i386 = 2.6.18-164.15.1.el5 is needed by open-vm- >> tools-kmod-0-1.20100425.i386 >> >> the kernel-devel rpm is installed: >> >> [root@localhost SPECS]# rpm -qa | grep kernel >> kernel-headers-2.6.18-194.3.1.el5 >> kernel-2.6.18-164.el5 >> kernel-devel-2.6.18-194.3.1.el5 >> kernel-2.6.18-53.el5 >> >> but uriparser-devel is not in the standard repos: >> >> [root@localhost SPECS]# yum search all | grep uriparser >> [root@localhost SPECS]# >> >> Is anything here I'm missing? > > uriparser-devel is in the EPEL repo. > To rebuild it against a specific kernel, use the kversion define like: > > rpmbuild -ba --define 'kversion 2.6.18-194.3.1.el5' open-vm-tools- > kmod.spec > > > > > ------------------------------ > > Message: 2 > Date: Mon, 24 May 2010 23:16:56 +0200 > From: Erwan MAS <erwan(a)mas.nom.fr> > Subject: [CentOS-virt] Bug in reboot phase : workaround or patch ? > To: centos-virt(a)centos.org > Message-ID: <20100524211656.GB19993(a)voyageur.mas.nom.fr> > Content-Type: text/plain; charset=us-ascii > > Hello , > > I use Centos 5.4 , with the redhat version of xen . > I need for some guest to change the hardware for the network . > So in my xen config i add the model option in the vif line . > > When the guest boot , i had the right emulation , but after a > reboot , the guest loose the configuration . > > Someone can confirm the bug in centos 5.5 ? > > Have someone a patch ? > > > > Extract of my config : > > builder = "hvm" > vif = [ 'type=ioemu, mac=00:16:3e:50:10:45, bridge=xenbr0, > model=ne2k_pci'] > device_model = "/usr/lib64/xen/bin/qemu-dm" > > #grep spa.*/usr/lib64/xen/bin/qemu-dm /var/log/xen/xend.log > > [2010-05-24 11:47:23 xend 3782] INFO (image:434) spawning device > models: /usr/lib64/xen/bin/qemu-dm ['/usr/lib64/xen/bin/qemu-dm', '- > d', '75', '-m', '192', '-boot', 'dc', '-serial', 'pty', '-vcpus', > '1', '-k', 'fr', '-domain-name', 'orange', '-net', > 'nic,vlan=1,macaddr=00:16:3e:50:10:45,model=pcnet', '-net', > 'tap,vlan=1,bridge=xenbr0', '-vnc', '127.0.0.45:1'] > [2010-05-24 11:47:40 xend 3782] INFO (image:434) spawning device > models: /usr/lib64/xen/bin/qemu-dm ['/usr/lib64/xen/bin/qemu-dm', '- > d', '76', '-m', '192', '-boot', 'dc', '-serial', 'pty', '-vcpus', > '1', '-k', 'fr', '-domain-name', 'orange', '-net', > 'nic,vlan=1,macaddr=00:16:3e:50:10:45,model=rtl8139', '-net', > 'tap,vlan=1,bridge=xenbr0', '-vnc', '127.0.0.45:1'] > > #rpm -qa | grep ^xen > xen-libs-3.0.3-94.el5_4.2 > xen-3.0.3-94.el5_4.2 > > #xm info > host : james.mas.nom.fr > release : 2.6.18-164.6.1.el5.centos.plusxen > version : #1 SMP Wed Nov 4 10:10:32 EST 2009 > machine : x86_64 > nr_cpus : 2 > nr_nodes : 1 > sockets_per_node : 1 > cores_per_socket : 2 > threads_per_core : 1 > cpu_mhz : 2104 > hw_caps : 178bfbff:ebd3fbff: > 00000000:00000010:00002001:00000000:0000011f > total_memory : 4078 > free_memory : 1738 > node_to_cpu : node0:0-1 > xen_major : 3 > xen_minor : 1 > xen_extra : .2-164.6.1.el5. > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0- > x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > cc_compiler : gcc version 4.1.2 20080704 (Red Hat 4.1.2-46) > cc_compile_by : mockbuild > cc_compile_domain : centos.org > cc_compile_date : Wed Nov 4 09:23:54 EST 2009 > xend_config_format : 2 > > -- > ____________________________________________________________ > / Erwan MAS /\ > | mailto:erwan@mas.nom.fr |_/ > ___|________________________________________________________ | > \___________________________________________________________\__/ > > > ------------------------------ > > Message: 3 > Date: Tue, 25 May 2010 10:43:23 +0300 > From: Pasi K?rkk?inen <pasik(a)iki.fi> > Subject: Re: [CentOS-virt] Bug in reboot phase : workaround or patch ? > To: Discussion about the virtualization on CentOS > <centos-virt(a)centos.org> > Message-ID: <20100525074323.GD17817(a)reaktio.net> > Content-Type: text/plain; charset=us-ascii > > On Mon, May 24, 2010 at 11:16:56PM +0200, Erwan MAS wrote: >> Hello , >> >> I use Centos 5.4 , with the redhat version of xen . >> I need for some guest to change the hardware for the network . >> So in my xen config i add the model option in the vif line . >> >> When the guest boot , i had the right emulation , but after a >> reboot , the guest loose the configuration . >> > > So when you first "xm create" it, it's ok, and after you reboot the > guest, > the NIC model has changed? > >> Someone can confirm the bug in centos 5.5 ? >> > > Did you search Redhat bugzilla? > > > -- Pasi > > >> Have someone a patch ? >> >> >> >> Extract of my config : >> >> builder = "hvm" >> vif = [ 'type=ioemu, mac=00:16:3e:50:10:45, bridge=xenbr0, >> model=ne2k_pci'] >> device_model = "/usr/lib64/xen/bin/qemu-dm" >> >> #grep spa.*/usr/lib64/xen/bin/qemu-dm /var/log/xen/xend.log >> >> [2010-05-24 11:47:23 xend 3782] INFO (image:434) spawning device >> models: /usr/lib64/xen/bin/qemu-dm ['/usr/lib64/xen/bin/qemu-dm', '- >> d', '75', '-m', '192', '-boot', 'dc', '-serial', 'pty', '-vcpus', >> '1', '-k', 'fr', '-domain-name', 'orange', '-net', >> 'nic,vlan=1,macaddr=00:16:3e:50:10:45,model=pcnet', '-net', >> 'tap,vlan=1,bridge=xenbr0', '-vnc', '127.0.0.45:1'] >> [2010-05-24 11:47:40 xend 3782] INFO (image:434) spawning device >> models: /usr/lib64/xen/bin/qemu-dm ['/usr/lib64/xen/bin/qemu-dm', '- >> d', '76', '-m', '192', '-boot', 'dc', '-serial', 'pty', '-vcpus', >> '1', '-k', 'fr', '-domain-name', 'orange', '-net', >> 'nic,vlan=1,macaddr=00:16:3e:50:10:45,model=rtl8139', '-net', >> 'tap,vlan=1,bridge=xenbr0', '-vnc', '127.0.0.45:1'] >> >> #rpm -qa | grep ^xen >> xen-libs-3.0.3-94.el5_4.2 >> xen-3.0.3-94.el5_4.2 >> >> #xm info >> host : james.mas.nom.fr >> release : 2.6.18-164.6.1.el5.centos.plusxen >> version : #1 SMP Wed Nov 4 10:10:32 EST 2009 >> machine : x86_64 >> nr_cpus : 2 >> nr_nodes : 1 >> sockets_per_node : 1 >> cores_per_socket : 2 >> threads_per_core : 1 >> cpu_mhz : 2104 >> hw_caps : 178bfbff:ebd3fbff: >> 00000000:00000010:00002001:00000000:0000011f >> total_memory : 4078 >> free_memory : 1738 >> node_to_cpu : node0:0-1 >> xen_major : 3 >> xen_minor : 1 >> xen_extra : .2-164.6.1.el5. >> xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0- >> x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 >> xen_pagesize : 4096 >> platform_params : virt_start=0xffff800000000000 >> xen_changeset : unavailable >> cc_compiler : gcc version 4.1.2 20080704 (Red Hat >> 4.1.2-46) >> cc_compile_by : mockbuild >> cc_compile_domain : centos.org >> cc_compile_date : Wed Nov 4 09:23:54 EST 2009 >> xend_config_format : 2 >> >> -- >> ____________________________________________________________ >> / Erwan MAS /\ >> | mailto:erwan@mas.nom.fr |_/ >> ___|________________________________________________________ | >> \___________________________________________________________\__/ >> _______________________________________________ >> CentOS-virt mailing list >> CentOS-virt(a)centos.org >> http://lists.centos.org/mailman/listinfo/centos-virt > > > ------------------------------ > > Message: 4 > Date: Tue, 25 May 2010 10:59:38 +0200 > From: Erwan MAS <erwan(a)mas.nom.fr> > Subject: Re: [CentOS-virt] Bug in reboot phase : workaround or patch ? > To: Discussion about the virtualization on CentOS > <centos-virt(a)centos.org> > Message-ID: <20100525085938.GC19993(a)voyageur.mas.nom.fr> > Content-Type: text/plain; charset=iso-8859-1 > > On Tue, May 25, 2010 at 10:43:23AM +0300, Pasi K?rkk?inen wrote: >> On Mon, May 24, 2010 at 11:16:56PM +0200, Erwan MAS wrote: >>> Hello , >>> >>> I use Centos 5.4 , with the redhat version of xen . >>> I need for some guest to change the hardware for the network . >>> So in my xen config i add the model option in the vif line . >>> >>> When the guest boot , i had the right emulation , but after a >>> reboot , the guest loose the configuration . >>> >> >> So when you first "xm create" it, it's ok, and after you reboot the >> guest, >> the NIC model has changed? > > It's a very old bug :-( . > Cf http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=867 > >>> Someone can confirm the bug in centos 5.5 ? >>> > > Centos 5.5 use a new version of xen , and i hope than my bug is > fixed in it , but before upgrade i want > a confirmation . > >> Did you search Redhat bugzilla? > > Yes . > > -- > ____________________________________________________________ > / Erwan MAS /\ > | mailto:erwan@mas.nom.fr |_/ > ___|________________________________________________________ | > \___________________________________________________________\__/ > > > ------------------------------ > > Message: 5 > Date: Tue, 25 May 2010 15:34:17 +0200 > From: Kenni Lund <kenni(a)kelu.dk> > Subject: [CentOS-virt] Libvirt NAT-based network 2x-4x faster than > Libvirt routed network? > To: Discussion about the virtualization on CentOS > <centos-virt(a)centos.org> > Message-ID: > <AANLkTilVG9SoFwr45o_GY-UD-q0htqEnFyuuizNT2JZZ(a)mail.gmail.com> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi > > Is it expected behaviour that a libvirt NAT-based network is faster > than a libvirt routed network? > > I would guess that the routed network would be the fastest one in all > cases, but I'm seeing the opposite in my setup. On a 100mbit internet > connection, the routed network tops at 4mbyte/sec, while the nat-based > network goes all the way to 10mbyte/sec. I've spend the last 6 hours > on trying to figure out the cause of this, changing settings, > reinstalling the system, but the problem persists and I can't find the > cause of it. > > It is a clean and fairly simple setup: > - Clean installation of CentOS 5.5 > - Installation of kvm+libvirt+virt-manager+xorg > - iptables service disabled > - 1 public IP for the host (xxx.yyy.zzz.215) on a /32 subnet with > xxx.yyy.zzz.193 as gateway > - 3 public IP for the routed network (xxx.yyy.zzz.251-253) on a /26 > subnet with the same gateway as the host > - 1 virtual machine with either the NAT or the routed libvirt > network assigned > > I have no networking connection errors or similar, it works perfectly > with both the NAT and the routed network, but the routed network is > just 2-4 times slower than the NAT one. > > Do you have any suggestions of what the problem might be? When I look > at the iptables rules generated by libvirt, and the routing table, > everything looks fine AFAICT. Traceroute from guest doesn't reveal > anything either. Ping times from the two networks are similar, so the > main issue seems to be throughput. > > Any help or pointers to what I should look at, is highly > appreciated... :) > > I've copy pasted some of my relevant system configuration into > pastebin: > http://pastebin.com/jtTrHLqA > > Thank you, > Kenni > > > ------------------------------ > > _______________________________________________ > CentOS-virt mailing list > CentOS-virt(a)centos.org > http://lists.centos.org/mailman/listinfo/centos-virt > > > End of CentOS-virt Digest, Vol 33, Issue 9 > ******************************************

1 0

open-vm-tools 20100425 rpm
by David Hollis 24 May '10

24 May '10

All, I've updated the open-vm-tools packages that have been floating around to the latest release - 4/25/2010 - for those that are interested. There is quite a bit of new additions/changes over the past year such as the addition of a fuse driver for vmblock devices, vmxnet3, pvscsi, etc. SRPMS and .spec's available here: http://www.davehollis.com/packages/open-vm-tools-kmod.spec http://www.davehollis.com/packages/open-vm-tools.spec http://www.davehollis.com/packages/open-vm-tools-kmod-0-1.20100425.el5.src.… http://www.davehollis.com/packages/open-vm-tools-0-1.20100425.el5.src.rpm

3 4

Choices for shared network storage, NFS vs iSCSI
by Steven Ellis 19 May '10

19 May '10

Has anyone here ran performance comparisons between NFS and iSCSI when using network storage for KVM based guests. Also which have people found to be easier for managing live migrates etc. Steve -- Steven Ellis - Bulletin.Net Inc - http://www.bulletin.net

3 2

SPICE anyone?
by compdoc 19 May '10

19 May '10

There was mention of some support for SPICE in RHEL 5.4, and mention again of improved support in 5.5, but it sounds like their main goal is to implement it in RHEV. Is there an easy way to implement SPICE with 5.5? Or should I download the source and compile it from spice-space.org? Thanks...

1 0

Slightly OT - Grub fallback option
by Ben M. 18 May '10

18 May '10

Does anyone have a standard install of CentOS virtualization grub.conf working in a proven state with the FALLBACK option? If so, can you post your grub.conf? I mistakenly updated to 5.5 and am concerned about nvidia driver comments in the release notes. I did not have protectbase configured on this machine. It is a remote device that will reboot.

2 1

RHEL 5.5 Xen fixes
by Pasi Kärkkäinen 15 May '10

15 May '10

Hello, RHEL 5.5 has been released, and it contains many Xen related fixes. Here's the most important of the them.. fixing a dom0 caching bug which could cause domU disk corruption when the domU disk was accessed from dom0 after the domU was shutdown. Most people noticed this bug when pygrub used wrong (cached) information. "pygrub uses cached and eventually outdated grub.conf, kernel and initrd": https://bugzilla.redhat.com/show_bug.cgi?id=466681 And some more: "Xen hypervisor doesn't mask xsave feature from the guest; Fedora 11 PV domU kernel crashes": https://bugzilla.redhat.com/show_bug.cgi?id=524719 "[RHEL-5 Xen]: F-11 Xen 64-bit domU cannot be started with > 2047MB of memory": https://bugzilla.redhat.com/show_bug.cgi?id=502826 " Boot hang when installing HVM DomU": https://bugzilla.redhat.com/show_bug.cgi?id=524052 "[RHEL5 Xen]: PV guest crash on poweroff": https://bugzilla.redhat.com/show_bug.cgi?id=540811 "[RHEL5 Xen]: Cpu frequency scaling is broken on Intel": https://bugzilla.redhat.com/show_bug.cgi?id=553324 RHEL 5.5 kernel changelog: http://rhn.redhat.com/errata/RHSA-2010-0178.html Work-in-progress (Not yet in 5.5): "Grub2 guest support for RHEL5 Xen pygrub": https://bugzilla.redhat.com/show_bug.cgi?id=577511 -- Pasi

6 10

Simulate Network Cable Disconnect
by Tait Clarridge 13 May '10

13 May '10

Hello All, I am having trouble simulating a network cable disconnect with KVM. I would like to test active backup bonding for a switch IOS upgrade in a production environment. Basically I have the VM running on a bridged network which is also tied into GNS3 simulating a small-scale version of the production environment. I have tried bringing down the vnetX interface and the actual virtual network itself (virbrX) with no luck. Has anyone had to do this before/maybe knows some tips? If more info is required about my setup, I can give it. Thanks! Tait

2 3

Maximum disks to allocate on kvm guests
by carlopmart 03 May '10

03 May '10

Hi all, Somebody knows how many virtio disks can be allocated for one kvm guest?? I am searching on redhat's docs about this without luck. Thanks. -- CL Martinez carlopmart {at} gmail {d0t} com

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt May 2010