virt December 2008

virt@lists.centos.org

13 participants
10 discussions

kmod-kvm-2.6.18-92.1.18.el5-72-1.x86_64.rpm outdated, need on for 2.6.18-92.1.22.el5
by Michael Schenck 28 May '09

28 May '09

CentOS Virt, I'm looking for an RPM for the kmod-kvm processor specific modules (kvm-intel or kvm-amd). I've been using L. Farkas's repository, but after the recent kernel updates, I'm out of luck. Best Regards, Michael Schenck

4 7

patched kernel addressing timekeeping issues under vmware
by Akemi Yagi 06 Feb '09

06 Feb '09

People at vmware have provided patches for RHEL 5 that aim to fix timekeeping issues in vmware guests. https://bugzilla.redhat.com/show_bug.cgi?id=463573 Description of problem (excerpt) : "In a virtual environment, timekeeping for RHEL 64 bit kernels can be problematic, since time is kept by counting timer interrupts for this kernel. The problem arises when the VM is descheduled for some portion of time. When the VM is rescheduled, the hypervisor needs to "catch up" delivering timer interrupts so that the kernel can determine the correct time. Until the VM is caught up, the kernel's time will be behind, causing short term divergence of the kernel's time with wallclock time. Additionally, under certain overcommitment conditions, it may not be possible for the hypervisor to fully catch up. In this case, the kernel time can fall behind over the long term. The solution is to change the kernel's timekeeping algorithm to keep time based on how much time has elapsed according to a time counter rather than by counting interrupts. This is similar to the timeofday algorithm used by clocksource enabled mainline kernels or the RHEL5 32bit kernel." They were hoping to get them into the RHEL 5.3 kernel but unfortunately this is not going to happen. It looks like the patches will be in the RHEL 5.4 kernel. Using the patches provided in the bugzilla, I have rebuilt the latest test kernel (-125) that is available from http://people.redhat.com/dzickus. You can download the patched kernel from: http://centos.toracat.org/kernel/centos5/vmware463573/ I have test-installed it on a couple of CentOS-5 x86_64 guests. Still too early to say anything about the clock issue, but so far so good. If you get a chance to give it a try, please share what you find. Thanks, Akemi (nick: toracat)

1 1

Warning on VirtualBox 2.1.0 on CentOS 5.2: Kernel Panic
by Todd and Margo Chester 23 Jan '09

23 Jan '09

Hi All, I just removed Virtual Box 2.1.0 from my system. When you boot up an XP guest, you will get a kernel panic. See http://www.virtualbox.org/ticket/2827 for details. I hope I saved someone else from the hassle I just had to go through. -T Now for FSCK on my hard drive!

1 3

stability issues with KVM 82
by Michael Schenck 13 Jan '09

13 Jan '09

CentOS Virt, I'm using Farkas' repository, as I'm sure you've guessed. I seem to be having stability issues. The parent distro is CentOS 5.2 patched all the way to current, as well as centos 5.2 for the KVM virtuals. I have been having random crashes such that the virtual is non-responsive. Has anyone else been seeing this? - Michael Schenck

2 2

LVM->DRBD->Xen Kernel panic after DRBD connection broken
by Maros TIMKO 22 Dec '08

22 Dec '08

Hi all! We are testing a setup of Xen virtualisation platform using CentOS distribution DRBD 8.2.6. We are having kernel panics and reboots of the primary node just seconds after we plug out the dedicated DRBD (crossover) connection. The failure is occuring all the time when we pull out the cable if DRBD devices are primary and Xen VMs are running. I thought upgrade/downgrade could solve it, but 8.0.13, 8.0.14, 8.2.7, 8.3 are acting exactly the same way. So it seems like the failure is not DRBD-related but more into Xen/xenified kernel. I have not found CentOS kernel related user list so I am trying this one. I would like to ask the audience if anyone has the same experience or if there are some hints, how to solve such issue. Our setup uses PV -> LVM -> DRBD -> Xen hierarchy. Do you think we could solve it if we would change it into PV -> DRBD -> LVM -> Xen? Dell PowerEdge 1950 with 2 Broadcom bnx2 NICs CentOS 5.2: Linux 2.6.18-92.1.18.el5xen #1 SMP Wed Nov 12 09:48:10 EST 2008 x86_64 x86_64 x86_64 GNU/Linux The console output using DRBD 8.3: (XEN) Freed 100kB init memory. kernel direct mapping tables up to f32be000 @ 1646000-2584000 PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved PCI: Not using MMCONFIG. Bridge firewalling registered virbr0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature. xenbr0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature. audit(1229950558.868:3): dev=vif0.0 prom=256 old_prom=0 auid=4294967295 ses=4294967295 audit(1229950561.088:4): dev=peth0 prom=256 old_prom=0 auid=4294967295 ses=4294967295 audit(1229950585.285:5): dev=vif1.0 prom=256 old_prom=0 auid=4294967295 ses=4294967295 kernel direct mapping tables up to 20800000 @ d7b000-f87000 blkback: ring-ref 8, event-channel 6, protocol 1 (x86_64-abi) blkback: ring-ref 9, event-channel 7, protocol 1 (x86_64-abi) blkback: ring-ref 10, event-channel 8, protocol 1 (x86_64-abi) blkback: ring-ref 11, event-channel 9, protocol 1 (x86_64-abi) drbd3: PingAck did not arrive in time. drbd3: short read expecting header on sock: r=-512 drbd2: PingAck did not arrive in time. drbd2: short read expecting header on sock: r=-512 drbd0: PingAck did not arrive in time. drbd0: short read expecting header on sock: r=-512 drbd1: PingAck did not arrive in time. drbd1: short read expecting header on sock: r=-512 drbd3: helper command: /sbin/drbdadm fence-peer minor-3 exit code 5 (0x500) drbd2: helper command: /sbin/drbdadm fence-peer minor-2 exit code 5 (0x500) drbd0: helper command: /sbin/drbdadm fence-peer minor-0 exit code 5 (0x500) drbd1: helper command: /sbin/drbdadm fence-peer minor-1 exit code 5 (0x500) Unable to handle kernel paging request at ffff8800eabba000 RIP: [<ffffffff802124c2>] csum_partial+0x219/0x4bc PGD 1646067 PUD 1c4a067 PMD 1da0067 PTE 0 Oops: 0000 [1] SMP last sysfs file: /module/drbd/parameters/cn_idx CPU 5 Modules linked in: xt_physdev netloop netbk blktap blkbk bridge drbd(U) ipv6 xfrm_nalgo crypto_api ipt_REJECT xt_state xt_tcpudp iptable_filter ipt_MASQUERADE iptable_nat ip_nat ip_conntrack nfnetlink ip_tables x_tables dm_multipath video sbs backlight i2c_ec i2c_core button battery asus_acpi ac parport_pc lp parport ide_cd e1000e bnx2 shpchp cdrom i5000_edac edac_mc serio_raw sg pcspkr dm_snapshot dm_zero dm_mirror dm_mod ata_piix libata megaraid_sas sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd Pid: 0, comm: swapper Tainted: G 2.6.18-92.1.18.el5xen #1 RIP: e030:[<ffffffff802124c2>] [<ffffffff802124c2>] csum_partial+0x219/0x4bc RSP: e02b:ffff880009df3b78 EFLAGS: 00010202 RAX: 0000000000000006 RBX: 0000000000000000 RCX: ffff8800eabba040 RDX: 0000000000000000 RSI: 0000000000000588 RDI: ffff8800eabba000 RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000015 R10: 0000000000000016 R11: 00000000000000b1 R12: 0000000000000054 R13: 0000000000000054 R14: ffff8800e9280670 R15: 00000000ce876505 FS: 00002b4db957e340(0000) GS:ffffffff805af280(0000) knlGS:0000000000000000 CS: e033 DS: 002b ES: 002b Process swapper (pid: 0, threadinfo ffff880001454000, task ffff8800016260c0) Stack: 0000000000000588 0000000000000588 ffffffff8023d16d 2ea7df79eaa7c080 0000000000000020 00000040ef6760cc ffff8800000005dc 0000000000000001 ffff8800e9280670 ffff8800ef6760cc Call Trace: <IRQ> [<ffffffff8023d16d>] skb_checksum+0x123/0x271 [<ffffffff8040a3d9>] skb_checksum_help+0x71/0xd0 [<ffffffff8831233e>] :iptable_nat:ip_nat_fn+0x56/0x1c3 [<ffffffff882ee50d>] :ip_conntrack:ip_conntrack_in+0x374/0x46a [<ffffffff883126cf>] :iptable_nat:ip_nat_local_fn+0x32/0xb7 [<ffffffff802351ae>] nf_iterate+0x41/0x7d [<ffffffff80428040>] dst_output+0x0/0xe [<ffffffff802588e4>] nf_hook_slow+0x58/0xbc [<ffffffff80428040>] dst_output+0x0/0xe [<ffffffff80235662>] ip_queue_xmit+0x431/0x4a1 [<ffffffff80222990>] tcp_transmit_skb+0x64a/0x682 [<ffffffff804320f4>] tcp_retransmit_skb+0x53d/0x638 [<ffffffff8043362a>] tcp_write_timer+0x0/0x699 [<ffffffff80433aa2>] tcp_write_timer+0x478/0x699 [<ffffffff80292b1e>] run_timer_softirq+0x13f/0x1c6 [<ffffffff802127c7>] __do_softirq+0x62/0xde [<ffffffff80260da0>] call_softirq+0x1c/0x27c [<ffffffff8026dcd2>] do_softirq+0x31/0x98 [<ffffffff8026db4d>] do_IRQ+0xec/0xf5 [<ffffffff803a0a98>] evtchn_do_upcall+0x86/0xe0 [<ffffffff802608d2>] do_hypervisor_callback+0x1e/0x2c <EOI> [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000 [<ffffffff802063aa>] hypercall_page+0x3aa/0x1000 [<ffffffff8026f139>] raw_safe_halt+0x84/0xa8 [<ffffffff8026c683>] xen_idle+0x38/0x4a [<ffffffff8024aa45>] cpu_idle+0x97/0xba Code: 4c 03 07 4c 13 47 08 4c 13 47 10 4c 13 47 18 4c 13 47 20 4c RIP [<ffffffff802124c2>] csum_partial+0x219/0x4bc RSP <ffff880009df3b78> CR2: ffff8800eabba000 <0>Kernel panic - not syncing: Fatal exception (XEN) Domain 0 crashed: rebooting machine in 5 seconds.

1 0

Xen 3.3 and pv-grub
by Kai Schaetzl 21 Dec '08

21 Dec '08

Has anyone been successful with moving a PV guest from using pygrub as a bootloader to pv-grub? Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

1 0

Crash with qemu install: 5.2 as host and 5.2 as guest
by Michael Kress 16 Dec '08

16 Dec '08

Hi, I'm trying to install a CentOS 5.2 guest with virt-manager/qemu on a CentOS 5.2 system (X86_x64, 3ware 9650SE, 2 x Intel VT capable xeon cpus, 8 GB) Unfortunately I'm getting a crash in the guest install process. Other systems are installing smoothely, even Windows xp, but the above combination won't install. What works, too: CentOS 5.2 xen unmodified (i.e. fully virtual) guest, but no luck with qemu. I already tried the kernel-xen kernel from centosplus. Have you got any idea? TIA Regards Michael PS: Here's the crash, I hope I typed everything right. ;-) (I didn't want to bother you with a gif). I couldn't get further up in order to grab more from the screen. Shift - PgUp doesn't work. -- Michael Kress, kress(a)hal.saar.de http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L

5 13

Xen Dom0 network fails to start at boot
by Adam Huffman 15 Dec '08

15 Dec '08

I have a server running Centos 5.2 as a Xen host. A problem that's shown up recently is that at boot, the dom0 interface eth0 doesn't come up properly, with the result that the host is only accessible via remote console. If I execute 'service network restart', eth0 comes up normally, with an IP address and the correct routing. Three guests have been created via virt-manager and I haven't changed any of the defaults, so I'm not sure what's causing this. Here's ifconfig output after boot: lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:20 errors:0 dropped:0 overruns:0 frame:0 TX packets:20 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1308 (1.2 KiB) TX bytes:1308 (1.2 KiB) 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:31844 errors:0 dropped:0 overruns:0 frame:0 TX packets:15 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4639017 (4.4 MiB) TX bytes:4898 (4.7 KiB) Interrupt:16 Memory:da000000-da012100 vif0.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:24 errors:0 dropped:0 overruns:0 frame:0 TX packets:31489 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6891 (6.7 KiB) TX bytes:4490222 (4.2 MiB) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:84 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:16250 (15.8 KiB) xenbr0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:31060 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:4035093 (3.8 MiB) TX bytes:0 (0.0 b) and again once I've restarted networking and have a guest running: eth0 Link encap:Ethernet HWaddr 00:1E:C9:CD:C7:0A inet addr:10.99.91.151 Bcast:10.99.255.255 Mask:255.255.0.0 inet6 addr: fe80::21e:c9ff:fecd:c70a/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15836 errors:0 dropped:0 overruns:0 frame:0 TX packets:10303 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2136620 (2.0 MiB) TX bytes:33113077 (31.5 MiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:6676 errors:0 dropped:0 overruns:0 frame:0 TX packets:6676 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:33006844 (31.4 MiB) TX bytes:33006844 (31.4 MiB) 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:63781 errors:0 dropped:0 overruns:0 frame:0 TX packets:27001 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9142626 (8.7 MiB) TX bytes:34301305 (32.7 MiB) Interrupt:16 Memory:da000000-da012100 tap0 Link encap:Ethernet HWaddr F2:C4:14:A0:43:50 inet6 addr: fe80::f0c4:14ff:fea0:4350/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:26853 errors:0 dropped:0 overruns:442 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 b) TX bytes:25995823 (24.7 MiB) tap1 Link encap:Ethernet HWaddr 96:9D:94:41:A1:C9 inet6 addr: fe80::949d:94ff:fe41:a1c9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:26851 errors:0 dropped:0 overruns:443 carrier:0 collisions:0 txqueuelen:500 RX bytes:0 (0.0 b) TX bytes:25995669 (24.7 MiB) vif0.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:10327 errors:0 dropped:0 overruns:0 frame:0 TX packets:63318 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:33119968 (31.5 MiB) TX bytes:8871385 (8.4 MiB) vif1.0 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF UP BROADCAST NOARP MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) vif1.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:16 errors:0 dropped:0 overruns:0 frame:0 TX packets:8820 errors:0 dropped:1 overruns:0 carrier:0 collisions:0 txqueuelen:32 RX bytes:1584 (1.5 KiB) TX bytes:24001390 (22.8 MiB) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 inet6 addr: fe80::200:ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:35 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:10384 (10.1 KiB) xenbr0 Link encap:Ethernet HWaddr 96:9D:94:41:A1:C9 UP BROADCAST RUNNING NOARP MTU:1500 Metric:1 RX packets:53695 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:6909244 (6.5 MiB) TX bytes:0 (0.0 b)

2 1

Running Fedora 10 (and rawhide) Xen guests/domUs on CentOS 5 dom0
by Pasi Kärkkäinen 14 Dec '08

14 Dec '08

Hi list! Now when Fedora 10 is out, I thought of writing here what's needed to run Fedora 10 Xen domUs on CentOS 5 dom0. Fedora 10 does not have separate kernel-xen, but instead Xen domU support is included in the normal kernel-PAE.i686 and kernel.x86_64 (based on the pv_ops Xen support included in the mainline/vanilla Linux kernels). RHEL 5.3 beta (and final obviously too) includes needed fixes to run Fedora 10 domUs. If you can't wait for CentOS 5.3 upgrade for your dom0, here is the list of modifications you need to make for CentOS 5.2 dom0: In CentOS 5.2 dom0 you should be able to run Fedora 10 domUs/guests if you first upgrade two packages: - libxc (needed for supporting bzImage kernels in F10) https://bugzilla.redhat.com/show_bug.cgi?id=457199 - python-virtinst (needed for F10 treeinfo parsing) https://bugzilla.redhat.com/show_bug.cgi?id=460585 Someone with access to RHEL 5.3 beta sources might want to put those packages available somewhere online.. or even better; compile binary RPMs too :) Packages: python-virtinst-0.300.2-11.el5 xen-3.0.3-73.el5 I might take a look at it myself later when I have more extra time.. :) -- Pasi

3 7

KVM-70 + rpms in CentOS or extra repository
by jd 02 Dec '08

02 Dec '08

Hi Does anyone know when KVM-70 or higher would be available in CentOs or CentoOS extras repository. (for version CentOS 5.x) The only place that I know of is here. http://www.lfarkas.org/linux/packages/centos/5/ Thanks /Jd

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt December 2008