virt August 2009

virt@lists.centos.org

12 participants
12 discussions

High CPU usage when running a CentOS guest in VirtualBox
by Sagi Bashari 16 Nov '09

16 Nov '09

Hi, I am running CentOS 5.3 32bit as a VirtualBox 3.0.0 guest running on Windows XP. The Windows host CPU usage is constantly at 50% although the CentOS guest is completely idle (i.e. 0.00 load average). I know this is a common problem related to the 1000Hz frequency that the CentOS kernel runs at. With previous versions of CentOS, I used the kernel-vm package [1] and it solved my problem. However, according to the README [2] this isn't necessary as of CentOS 5.3 and therefore these packages are not maintained anymore (the latest released kernel-vm is 2.6.18-92.1.22). >From what I understand, as of CentOS 5.3 it is possible to use the "divider=10 clocksource=acpi_pm" to reduce the frequency to 100Hz. I tried this setting, and it made no difference at all. I also tried to install the VirtualBox guest extensions, and still, the host CPU never goes below 50%. Is there any way to solve this issue without resorting to a custom kernel build? Thanks, Sagi [1] http://people.centos.org/tru/kernel-vm/ [2] http://people.centos.org/tru/kernel-vm/readme.txt

17 55

domU shutdown with cx88 crashes dom0
by Christian Schuermann 10 Oct '09

10 Oct '09

Hi, I've got a big problem with a cx88 DVB card. It is passed through to a CentOS 5.3 domU (dom0 is CentOS 5.3 as well), but when I shutdown the domU, this happens: cx88[0]: mpeg risc op code error cx88[0]: mpeg - dma channel status dump cx88[0]: cmds: initial risc: 0xffffffff cx88[0]: cmds: cdt base : 0xffffffff cx88[0]: cmds: cdt size : 0xffffffff cx88[0]: cmds: iq base : 0xffffffff cx88[0]: cmds: iq size : 0xffffffff cx88[0]: cmds: risc pc : 0xffffffff cx88[0]: cmds: iq wr ptr : 0xffffffff cx88[0]: cmds: iq rd ptr : 0xffffffff cx88[0]: cmds: cdt current : 0xffffffff cx88[0]: cmds: pci target : 0xffffffff cx88[0]: cmds: line / byte : 0xffffffff cx88[0]: risc0: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: risc1: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: risc2: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: risc3: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: iq 0: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: iq 1: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: iq 2: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: iq 3: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: iq 4: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: iq 5: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: iq 6: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: iq 7: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: iq 8: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: iq 9: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: iq a: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: iq b: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: iq c: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: iq d: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: iq e: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: iq f: 0xffffffff [ INVALID sol eol irq2 irq1 23 22 21 20 19 18 cnt1 cnt0 resync 14 13 12 count=4095 ] cx88[0]: fifo: 0x00186400 -> 0x187400 cx88[0]: ctrl: 0x001807c0 -> 0x180820 cx88[0]: ptr1_reg: 0xffffffff cx88[0]: ptr2_reg: 0xffffffff cx88[0]: cnt1_reg: 0xffffffff cx88[0]: cnt2_reg: 0xffffffff This loops forever eating every available cpu cycle. The dom0 becomes unusably slow until I manually destroy the domU. The domU runs 2.6.18-128.1.10.el5xen with video4linux-kmdl-2.6.18-128.1.10.el5xen-20090415-88.0.4.el5 (there are no video4linux-kmdls for the latest kernel yet). Manually unloading the modules before shutting down has no effect. Without video4linux-kmdl installed, everything works fine. I hope you can help me. Regards, Chris

1 2

Cluster failover
by Paras pradhan 01 Sep '09

01 Sep '09

hi, I have 3 nodes of CentOS 5.3 running xen virtual machines as virtual machine service. This cluster is working fine. One thing I would like to know that how to make failover only to third node. What I mean to say is: I have 3 virtual machine running on node 1 and 2 virtual machines running on node 2. Now if node 1 fails I want my the node1 virtual machines to be stared only on node 3 but not on node2. Similary if node2 breaks, I want virtual machines to be started on node3 but never on node 1. Thanks ! Paras.

2 1

Migrate windows VM from i386 Host to x86_64 host
by James Roman 01 Sep '09

01 Sep '09

Somehow one of our Xen servers ended up loaded with the i686 xen kernel, instead of the x86_64. The host has one windows VM running on it. The OS partition is file-based, but it also has a logical volume partition assigned for data. We would like to migrate the host server to a 64-bit kernel, which means moving the VM to one of our other 64-bit host servers. We tried simply copying the OS partition and using dd to move the LVM partition to a new host unsuccessfully. I'm pretty sure that dd may not be appropriate when moving between kernel architectures. However, even without the LVM partition specified in the vm config file, we are unable to boot the windows system. It looks like it is blue screening immediately, since we never get a console connection. Are there any instructions anywhere for moving VMs from one host architecture to another? Current Host: Centos 5.3 i686 kernel 2.6.18-128.2.1.el5 Xen 3.0.3-80.el5_3.3 Destination Host: Centos 5.3 x86_64 kernel 2.6.18-128.2.1.el5 Xen 3.0.3-80.el5_3.3

2 1

domU reboot leaves VM crashing continually
by Robert E. Moser 01 Sep '09

01 Sep '09

Greetings, Im new to xen virtualization on CentOS, but I have been unable to find the answer to this problem Im experiencing. My setup: AMD quad core (64bit), 8Gb ram. CentOS 5.3 dom0, CentOS 5.3 domUs (paravirtualized). Dom0 is set up with two NICs, the built-in and a PCI card, and I set up xen bridging on both interfaces. My domUs seem to boot up fine, run fine, and shutdown fine. However, if I attempt a reboot operation, they go into a state where they continually crash on startup. I have been unable to ascertain why this happens, and I do not know how to fix it when it does happen. So, my question is twofold: 1) How do I get it out of the continual boot/crash cycle? Xm destroy doesnt work, none of the GUI tools work. So far the only answer has been rebooting dom0, which is not a good answer L 2) Has anyone else seen this/solved this? Besides being able to manually fix it from #1 above, it sure would be nice to have it able to reboot as expected. I havent worked with any fully virtualized guests yet, but I will try that pretty soon and see if it evidences the same behavior. Uname a è Linux prathis.localdomain 2.6.18-128.7.1.el5xen #1 SMP Mon Aug 24 09:14:33 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux Please let me know what additional information would be helpful or what I can do to facilitate debugging this issue. Thanks!

1 1

Performance tunning CentOS / Xen
by Ryan Chan 24 Aug '09

24 Aug '09

Hello, I have followed standard documents to install CentOS 5.3 & Xen. After playing around, stuffs are OK. So I move forward to tune the performance, are there any recommended documents/tutorial that specialized on performance tuning VM host/guest, on CentOS / Xen architecture? Thanks

2 2

virtio
by Kanwar Ranbir Sandhu 24 Aug '09

24 Aug '09

Hello Everyone, Can I use virtio modules for network and block devices in CentOS 5.3 VMs when using the KVM packages from the "lfarkas" repo? I've tried change an existing VM to virtio for disk and network, but each time I start it, I get this error: error: Failed to start domain popdns02 error: internal error unsupported disk type 'vda' I don't know why this is happening. From what I've read, virtio should be available. Can someone please tell me what I'm doing wrong? Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.27.29-170.2.78.fc10.x86_64 x86_64 GNU/Linux 11:32:58 up 6 days, 12:29, 4 users, load average: 0.26, 0.21, 0.33

1 1

libvirtd and kvm from lfarkas repo
by Kanwar Ranbir Sandhu 12 Aug '09

12 Aug '09

Hi All, Can I use virt-manager from a Fedora 11 box to manage Qemu/KVM VMs, or is this crazy (re: incompatible)? Regards, Ranbir -- Kanwar Ranbir Sandhu Linux 2.6.27.29-170.2.78.fc10.x86_64 x86_64 GNU/Linux 21:36:22 up 4 days, 20:37, 4 users, load average: 0.22, 0.20, 0.18

1 0

Ubuntu guest
by Paras pradhan 09 Aug '09

09 Aug '09

Can I install a ubuntu guest in a para virt mode from an ISO file in CentOS Dom0 without using debootstarp? I have an appliance based on ubuntu which I need to install as a para virt guest. Thanks ! Paras.

4 6

OpenBSD 4.5 in HVM domU network timeouts
by Sergey Smirnov 05 Aug '09

05 Aug '09

Hi all, I am trying to install openbsd 4.5 amd64 in HVM domU. dom0 runs CentOS 5.3 x86_64 with xen 3.4.0 During installation process everything is looks good except network.. When I've configured the network parameters I began to receive multiple messages like this - re0: watchdog timeout and ping from dom0 to that domU is looks awesome: $ ping 10.10.10.10 PING 10.10.10.10 (10.10.10.10) 56(84) bytes of data. 64 bytes from 10.10.10.10: icmp_seq=1 ttl=255 time=3764 ms 64 bytes from 10.10.10.10: icmp_seq=2 ttl=255 time=2756 ms 64 bytes from 10.10.10.10: icmp_seq=3 ttl=255 time=1756 ms 64 bytes from 10.10.10.10: icmp_seq=4 ttl=255 time=5756 ms ... --- 10.10.10.10 ping statistics --- 974 packets transmitted, 972 received, 0% packet loss, time 972996ms rtt min/avg/max/mdev = 1831.964/3849.323/7833.997/1421.748 ms, pipe 8 Does anybody know what's the problem? Is there any workaround? I've googled for something about "model=ne2k_pci" options in xen domain config, but haven't tried it yet (installation still in the progress..). Any hints? Thanks -- Sergey Smirnov email/xmpp: Sergey.A.Smirnov(a)Gmail.com

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt August 2009