virt October 2010

virt@lists.centos.org

27 participants
11 discussions

How to debug Ubuntu 8.04 LTS guest crash during install?
by Neil Aggarwal 04 Nov '25

04 Nov '25

Hello: I am using kvm on a CentOS 5.4 server. I am trying to install the TunkeyLinux Core appliance found here: http://www.turnkeylinux.org/core I downloaded the ISO file from the web site. Then, I used this command to intall it: virt-install -n tkl-core -r 512 --vcpus=1 --check-cpu --os-type=linux --os-variant=ubuntuhardy -v --accelerate -c /tmp/turnkey-core-2009.10-hardy-x86.iso -f /var/lib/libvirt/images/tkl-core.img -s 15 -b br0 --vnc noautoconsole When I connect to the VNC console, I get the Turnkey linux options screen. I select Install to hard disk from there and it seems to start the install but crashes during the installer startup. This is repeatable so there has to be a way to debug it. I tried turning on the debug option for virt-install but that did not give me any useful info. Any ideas how to debug this? Thanks, Neil -- Neil Aggarwal, (281)846-8957, http://UnmeteredVPS.net/cpanel cPanel/WHM preinstalled on a virtual server for only $40/month! No overage charges, 7 day free trial, PayPal, Google Checkout

3 4

Xen on Centos 5.5 vs 5.3 and stability issues
by Steven Ellis 01 Nov '10

01 Nov '10

I've recently upgraded a Centos 5.3 machine to Centos 5.5. The hardware isn't HVM capabile so I'm only running para-virt guests. Using a vanilla i386 kernel boots without, but the newer kernel-xen locks up the Dom0 after a couple of minute. I'm only booting into single user mode for these tests so no VMs are active. *kernel-xen-2.6.18-128.1.10.el5 - no issues *kernel-xen-2.6.18-194.17.4.el5 - lock up *kernel-2.6.18-194.17.4.el5 - no issues For the moment I've switched back to the older Xen kernel, athough I'm still running the newer Xen Hypervisor. My current Xen packages are *xen-3.0.3-105.el5_5.5 *kernel-xen-2.6.18-194.17.4.el5 *kernel-xen-2.6.18-128.1.10.el5 *kmod-xfs-xen-0.4-2 *xen-libs-3.0.3-105.el5_5.5 *kernel-xen-devel-2.6.18-194.17.4.el5 *kernel-xen-devel-2.6.18-128.1.10.el5 *xen-devel-3.0.3-105.el5_5.5 Prior to the upgrade I had the following installed under Centos 5.3 *kernel-xen-devel-2.6.18-128.1.6.el5 *kernel-xen-2.6.18-128.1.10.el5 *xen-libs-3.0.3-80.el5_3.2 *xen-devel-3.0.3-80.el5_3.2 *kmod-xfs-xen-0.4-2 *kernel-xen-2.6.18-128.1.6.el5 *kernel-xen-devel-2.6.18-128.1.10.el5 *xen-3.0.3-80.el5_3.2 Booting Dom0 with kernel-xen-2.6.18-128.1.10.el5 everything appears to work normally and all of my Guests are up and running. If I boot with kernel-xen-2.6.18-194.17.4.el5 the boot normally gets to around udev and the system locks up. On a couple of occasions it did mange to boot but reported some files were corrupted. I'm worried that there is an issue running this kernel where the root file system is LVM on top of Raid 1. Anyone on this list have tips on diagnosing the issue, or come across a similar problem themselves. Steve

4 6

Best way to give guest promiscuous interface?
by David Knierim 29 Oct '10

29 Oct '10

I am using CentOS 5.5 with KVM as a host and have a need for one guest to be able to have promiscuous read access to one port on the physical host (which is an HP BL460 G6 blade server with Intel 2 port 1Gb ethernet mezzanine card.) I initially tried to use PCI passthrough, but I was unable to get it to work. I set everything up as documented in RHEL documentation (http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Virtualiz…, but I got the following error message: # virsh start c7e1b6_g1 error: Failed to start domain c7e1b6_g1 error: this function is not supported by the hypervisor: Device 0000:0b:00.0 is behind a switch lacking ACS and cannot be assigned Does anyone have PCI passthrough working on a BL460 G6 with CentOS 5.5? I then tried to connect the guest to a bridge. This worked once I did a "brctl setageingtime 0" on the bridge. However, I don't know the best way to make this change persistent. Any suggestions? Is there a better way to do this? Thanks for any input, David

1 0

performance differences between kvm/xen
by Karanbir Singh 28 Oct '10

28 Oct '10

hi guys, Just wondering if anyone has done any performance testing between kvm and xen on CentOS-5 ( using centos as host and vm in every case ) ? Regards, -- Karanbir Singh London, UK | http://www.karan.org/ | twitter.com/kbsingh ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax GnuPG Key : http://www.karan.org/publickey.asc

12 30

VMWare 4.1 and CentOS
by Drew Kollasch 28 Oct '10

28 Oct '10

Is there any known issues when trying to run CentOS (x86 or x64) on a fresh install of vmware 4.1? Details as to why I am asking are here in the CentOS forums: https://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&order=DESC… Thanks! -Drew

8 12

problem: kvm host locks up for some seconds
by Momonth 25 Oct '10

25 Oct '10

Hi All, I'm running: kvm-qemu-img-83-164.el5 kvm-83-164.el5 kernel-2.6.18-194.8.1.el5 libvirt-python-0.6.3-33.el5 virt-viewer-0.0.2-3.el5 kernel-2.6.18-194.el5 etherboot-zroms-kvm-5.4.4-13.el5.centos kmod-kvm-83-164.el5 kernel-devel-2.6.18-194.8.1.el5.centos.plus libvirt-0.6.3-33.el5 python-virtinst-0.400.3-9.el5 kvm-tools-83-164.el5 virt-manager-0.6.1-12.el5 on HP ProLiant DL380 G6. Basically it works ok, quite stably running 10 VMs .. the only problem I've got is the following: Sometime initiating 'shutdown' from guest OS (linux only), kvm host locks up for several seconds (15-30) and also all of the VMs hosted on this host become inaccessible as well. In 100% cases if I do 'Force shutdown' (from Virtual Machine Manager) of a VM, consequent VMs re-start results in kvm host locking up for some seconds as well .. Does anybody experience something similar ? I've tested Ubuntu Server 10.04.1 LTS on the same hardware with 'latest/greatest' kernel | kvm and it doesn't have this problem. Regards, Vladimir

1 0

KVM instance keep crashing
by Poh Yong Hwang 17 Oct '10

17 Oct '10

Hi, I have one KVM instance (centos 5) that keeps crashing and i see the message log with the following: Oct 14 16:24:48 localhost kernel: psmouse.c: Explorer Mouse at isa0060/serio1/input0 lost synchronization, throwing 1 bytes away. Oct 14 16:24:49 localhost kernel: BUG: soft lockup - CPU#0 stuck for 12s! [ntpd:2363] Oct 14 16:24:49 localhost kernel: CPU 0: Oct 14 16:24:49 localhost kernel: Modules linked in: backupdriver(PU) ipv6 xfrm_nalgo crypto_api autofs4 hidp rfcomm l2cap bluetooth lockd sunrpc talpa_pedevice(U) dm_mirror dm_multipath scsi_dh video backlight sbs power_meter hwmon i2c_ec dell_wmi wmi button battery asus_acpi acpi_memhotplug ac parport_pc lp parport floppy virtio_balloon virtio_pci ide_cd i2c_piix4 virtio_ring 8139too cdrom 8139cp pcspkr i2c_core virtio mii serio_raw dm_raid45 dm_message dm_region_hash dm_log dm_mod dm_mem_cache ata_piix libata sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd Oct 14 16:24:49 localhost kernel: Pid: 2363, comm: ntpd Tainted: P 2.6.18-194.3.1.el5 #1 Oct 14 16:24:49 localhost kernel: RIP: 0010:[<ffffffff80064b50>] [<ffffffff80064b50>] _spin_unlock_irqrestore+0x8/0x9 Oct 14 16:24:49 localhost kernel: RSP: 0018:ffffffff80446ee0 EFLAGS: 00000296 Oct 14 16:24:49 localhost kernel: RAX: 00000000000002fd RBX: ffff81007cb46b40 RCX: ffff81006975b978 Oct 14 16:24:49 localhost kernel: RDX: 0000000000000060 RSI: 0000000000000296 RDI: ffffffff80348e58 Oct 14 16:24:49 localhost kernel: RBP: ffffffff80446e60 R08: ffff81007cb46a70 R09: 0000000000000020 Oct 14 16:24:49 localhost kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffffffff8005dc8e Oct 14 16:24:49 localhost kernel: R13: 000000000000003d R14: ffffffff8007820e R15: ffffffff80446e60 Oct 14 16:24:49 localhost kernel: FS: 00002b3519a1c030(0000) GS:ffffffff803ca000(0000) knlGS:0000000000000000 Oct 14 16:25:06 localhost kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Oct 14 16:25:06 localhost kernel: CR2: 00002b4f3abac3d8 CR3: 0000000069726000 CR4: 00000000000006e0 Oct 14 16:25:06 localhost kernel: Oct 14 16:25:06 localhost kernel: Call Trace: Oct 14 16:25:06 localhost kernel: <IRQ> [<ffffffff80209e43>] i8042_interrupt+0x92/0x1e9 Oct 14 16:25:06 localhost kernel: [<ffffffff80010bd1>] handle_IRQ_event+0x51/0xa6 Oct 14 16:25:07 localhost kernel: [<ffffffff800baec9>] __do_IRQ+0xa4/0x103 Oct 14 16:25:07 localhost kernel: [<ffffffff8006ca11>] do_IRQ+0xe7/0xf5 Oct 14 16:25:07 localhost kernel: [<ffffffff8005d615>] ret_from_intr+0x0/0xa Oct 14 16:25:07 localhost kernel: <EOI> [<ffffffff8002f73b>] dev_queue_xmit+0x0/0x271 Oct 14 16:25:07 localhost kernel: [<ffffffff881987c6>] :8139cp:cp_start_xmit+0x4ef/0x511 Oct 14 16:25:07 localhost kernel: [<ffffffff8819842d>] :8139cp:cp_start_xmit+0x156/0x511 Oct 14 16:25:07 localhost kernel: [<ffffffff8022eede>] dev_hard_start_xmit+0x1b7/0x28a Oct 14 16:25:08 localhost kernel: [<ffffffff8023f0b8>] __qdisc_run+0x136/0x1f9 Oct 14 16:25:08 localhost kernel: [<ffffffff8002f88b>] dev_queue_xmit+0x150/0x271 Oct 14 16:25:08 localhost kernel: [<ffffffff80031f87>] ip_output+0x2ae/0x2dd Oct 14 16:25:08 localhost kernel: [<ffffffff8024d651>] ip_push_pending_frames+0x37d/0x465 Oct 14 16:25:08 localhost kernel: [<ffffffff8025daad>] udp_push_pending_frames+0x21e/0x243 Oct 14 16:25:08 localhost kernel: [<ffffffff8005297d>] udp_sendmsg+0x4d8/0x5ef Oct 14 16:25:08 localhost kernel: [<ffffffff80055336>] sock_sendmsg+0xf8/0x14a Oct 14 16:25:09 localhost kernel: [<ffffffff800a0abe>] autoremove_wake_function+0x0/0x2e Oct 14 16:25:09 localhost kernel: [<ffffffff80098f3b>] __dequeue_signal+0x12d/0x193 Oct 14 16:25:09 localhost kernel: [<ffffffff8009899d>] recalc_sigpending+0xe/0x25 Oct 14 16:25:09 localhost kernel: [<ffffffff8009a0db>] dequeue_signal+0x47/0xcd Oct 14 16:25:09 localhost kernel: [<ffffffff80070b89>] init_fpu+0x62/0x7f Oct 14 16:25:09 localhost kernel: [<ffffffff8006beee>] math_state_restore+0x23/0x4c Oct 14 16:25:09 localhost kernel: [<ffffffff8005dde9>] error_exit+0x0/0x84 Oct 14 16:25:09 localhost kernel: [<ffffffff802264ac>] sys_sendto+0x11c/0x14f Oct 14 16:25:10 localhost kernel: [<ffffffff8006b011>] __switch_to+0xfe/0x22f Oct 14 16:25:10 localhost kernel: [<ffffffff80062ff8>] thread_return+0x62/0xfe Oct 14 16:25:10 localhost kernel: [<ffffffff80043b84>] sys_rt_sigreturn+0x323/0x356 Oct 14 16:25:10 localhost kernel: [<ffffffff8005d28d>] tracesys+0xd5/0xe0 Oct 14 16:25:10 localhost kernel: Afterwhich the instance become very sluggish and unresponsive. Please advise what could be the issue. Thanks YongSan

3 5

Re: [CentOS-virt] performance differences between kvm/xen
by John L. Magee 16 Oct '10

16 Oct '10

One thing to possibly consider with PostgreSQL performance especially, is that when using KVM VMs for some applications, PostgreSQL could be run native. This is a viable approach with KVM that could never work with Xen.

3 3

Jack Van Ham is out of the office (on vacation)
by jack.vanham＠agfa.com 15 Oct '10

15 Oct '10

I will be out of the office starting 10/15/2010 and will not return until 11/01/2010. for urgent matter, please contact: Scott Morley (scott.morley(a)agfa.com) or Don Dennison (don.dennison(a)agfa.com) I will not be replying to any messages until I return. Have a great day!

1 0

vmware datastore mounted by NFS
by Ted Miller 09 Oct '10

09 Oct '10

I recently moved my vmware datastore from a local disk partition to an NFS share (in preparation for some other system changes that are still in progress). In the init sequence, vmware loads before the NFS share gets mounted, so it checks the datastore, and finds it empty. Makes it hard to start a VM. :( As a temporary fix, I added the line service vmware restart to rc.local, but I consider that a kludge. I find in rc3.d the files S19vmware and S25netfs. Questions: 1. If I change S19vmware to S27vmware, that should bring up the NFS file system before VMware starts, correct? 2. Are the NFS file systems mounted at that point in init? 3. If I change the boot order of vmware, will vmware change it back to 19 next time I have to run vmware-config.pl? Ted Miller Indiana, USA

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt October 2010