virt

virt@lists.centos.org

1608 discussions

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

Need Help with Xen Please
by Jason Taylor 28 Nov '08

28 Nov '08

Hello: I am new to Xen and have been having problems getting it to run properly on CentOS 5.2. One thing to note is that the base Xen installs fine it seems but when trying to create the virtual instance (domU) it says it cannot connect to the console. I have looked up the error but cannot find anything specific to try. I currently only have access to the server remotely via SSH, if this matters at all. qemu: the number of cpus is 1 *** image /local/domain/0/backend/vbd/5/768 format raw driver 0x80e7940 *** image /local/domain/0/backend/vbd/5/5632 format raw driver 0x80e7940 Watching /local/domain/5/logdirty/next-active Could not initialize SDL - exiting I would really appreciate any assistance from anyone who knows Xen and CentOS. Thanks Jason

9 27

Re: [CentOS-virt] Running Fedora 10 (and rawhide) Xen guests/domUs on CentOS 5 dom0
by Scott Dowdle 27 Nov '08

27 Nov '08

Pasi, ----- "Pasi Kärkkäinen" <pasik(a)iki.fi> wrote: > Now when Fedora 10 is out, I thought of writing here what's needed to > run Fedora 10 Xen domUs on CentOS 5 dom0. Just wanted to mention that I built OpenVZ OS Templates for Fedora 10 i386/x86_64 default/minimal and posted them on the OpenVZ site in the contrib directory to coincide with the Fedora 10 release. They can be found here: http://download.openvz.org/template/precreated/contrib/ fedora-10-i386-default.tar.gz 23-Nov-2008 20:20 171M fedora-10-i386-minimal.tar.gz 23-Nov-2008 23:30 83M fedora-10-x86_64-default.tar.gz 23-Nov-2008 22:50 202M fedora-10-x86_64-minimal.tar.gz 23-Nov-2008 23:32 84M No special instructions needed... just create a container as usual. TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work]

1 0

Vista will install but not load in virt-manager
by Larry Patterson 26 Nov '08

26 Nov '08

Hi All I have successfully installed vista ultimate as a virtual image using the CentOS 5.2 virt-manager. It appears to completely install but as soon as I log in for the first time it reboots and then can not file it's boot image file. It appears to find the mbr but then stop, this is what is on the screen when it stops (the /etc/xen config file is given below) Booting 'Windows Vista' acpi Vista Loader 2.1.1 ACPI: Reclaim Memory not found! Done! fallback 1 find --set-root /bootmgr (hd0,0) Filesystem type is ntfs, partition type 0x7 chainloader /bootmgr Will boot NTLDR from drive-0x80, partiotn=0x0(hidden sectors=0x800) /etc/xen config file 'vista2' name = "vista2" uuid = "1ae9835e-4cb5-8785-e951-683a88cb5492" maxmem = 1506 memory = 512 vcpus = 2 builder = "hvm" kernel = "/usr/lib/xen/boot/hvmloader" boot = "c" pae = 1 acpi = 1 apic = 1 localtime = 1 on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" device_model = "/usr/lib64/xen/bin/qemu-dm" usbdevice = "tablet" sdl = 0 vnc = 1 vncunused = 1 keymap = "en-us" disk = [ "file:/var/lib/xen/images/vista2.img,hda,w", "file:/install/vista.iso,hdc:cdrom,r" ] vif = [ "mac=00:16:3e:5b:de:f1,bridge=virbr0" ] serial = "pty" Any help is much appreciated Thanks

1 0

Re: [CentOS] Stop the FUD Xen is not deprecated
by Brett Serkez 25 Nov '08

25 Nov '08

On Tue, Nov 25, 2008 at 10:45 AM, Vandaman <vandaman2002-sk(a)yahoo.co.uk> wrote: > Do people have wet underwear for nothing over XEN? > > See http://www.redhat.com/promo/qumranet/ > > As far as CentOS is concerned saying Xen is deprecated is > jumping the gun. CentOS ships with Xen and as long as upstream > supports it, CentOS by extension supports it. Thank you for the clarification. What isn't clear from reading the above referenced material is if Xen will be included in future CentOS releases. Brett

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt