Re: [CentOS-virt] Bug in reboot phase : workaround or patch ?
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::0010:2001::011f 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=0x8000 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:er...@mas.nom.fr |_/ ___| | \___\__/ ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Bug in reboot phase : workaround or patch ?
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:er...@mas.nom.fr |_/ ___| | \___\__/ ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Libvirt NAT-based network 2x-4x faster than Libvirt routed network?
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@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
