virt

virt@lists.centos.org

1608 discussions

Running Xen domU hangs until service xend is restarted
by Mikael Fridh 16 Oct '08

16 Oct '08

xen-3.0.3-64.el5_2.1 Here's the scenario: Name ID Uptime Domain-0 0 128 days, 17:31:11 piranga_xen01 1 128 days, 17:30:13 piranga_xen02 39 96 days, 15:47:10 piranga_xen03 35 96 days, 16:39:52 piranga_xen04 59 16 days, 17:30:35 3 hours ago, xen04 stopped responding. xm list showed it was constantly in State "r" and Time steadily increasing for xen04 while all other domU's kept going unharmed: Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 5052 4 r----- 296971.7 piranga_xen01 1 263 1 -b---- 1588245.8 piranga_xen02 39 255 1 -b---- 26560.5 piranga_xen03 35 255 1 -b---- 17036.2 piranga_xen04 59 511 1 r----- 15560.6 xenconsoled wasn't showing up in dom0 processlist. After service xend restart the xen04 domU went back to normal again. I've seen previous posts about (and experienced myself) the case where xm list, xm create, xm restart stops working because of a botched xend/xenconsoled, but this is the first time a domU just hangs for me. Anyone else experienced this? -- Mike

1 0

domU Windows XP tcpip.sys bluescreen
by Justin Lim 15 Oct '08

15 Oct '08

I am currently running Centos 5.2 with 2.6.18-92.1.13.el5xen with 2 domu's One another Centos 5.2 and another Windows XP. The Centos DomU works fine and I never have any problems however my XP DomU crashes every so often with the bluescreen DRIVER_IRQL_NOT_LESS_OR_EQUAL then under the technical information tcpip.sys addres xxxxxx base at xxxxx datetime Xxxxxxxxx Is there a driver pack for XP that provides better integration into XEN or something? Or am I missing anything ? The XP domU is just Windows XP fully patched to the most update patches no external drivers added. Thanks

3 2

XEN: pc reboots when tries to start up X while running the xen kernel
by walied arulandu 13 Oct '08

13 Oct '08

Hi All, Has anyone had this issue. I performed a basic install of centos 5.2 then install kernel-xen xen virt-manager. When I reboot the pc to us the xen kernal as soon as it tries to start X the pc reboots. I then disable X on start by editing teh /etc/inittab file. No it boot in runlevel 3 but when I start up X from the command line it does the same the pc reboots. I am running a an Intel Johannesburg Executive series motherboard with onboard graphics and an Intel E8400 processor which supputs VT tech and is recommended by Red Hat linux. Does anyone why it would just reboot when starting X. Please advise. thx.

1 0

Unstable VMware 1.0.5 host after 4.7 upgrade
by Jeff 09 Oct '08

09 Oct '08

After upgrading to 4.7 x86_64 on all our boxes (from 4.6), we have 3 VMware Server 1.0.5 hosts that are unstable. Sometimes they spontaneously reboot, other times they freeze and require a hard reset. Under 4.6, they were rock solid. Failures tend to be associated with a guest start-up event, but are often at random times as well. There is no useful evidence in either the vmware or messages log files on the host. The other thing that changed when we upgraded is that we upgraded our CentOS 4.6 (x86) guests to 4.7 and instead of recompiling a new kernel with HZ=100, we tested and implemented the newly available divider=10 kernel parameter. Initially, everything was fine with the divider option, but now I'm not so sure. Probably not a coincidence is the fact that the 3 hosts that are affected do NOT have VT capable processors. Our quad-core Xeon boxes with VT have not been a problem. I'm in the process of going back to an HZ=100 kernel. Of course, my first guest system reboot with the new kernel triggered a host reboot. Arrrggghhh. Does anyone have similar experiences? Does anyone have a *stable* VMware Server 1.0.x host on 2.6.9-78.0.1 with non-VT processors? Is anyone else using divider=10 with VMware 1.0.x? -- Jeff

2 3

io writes very slow when using vmware server
by Paul Bijnens 07 Oct '08

07 Oct '08

We are struggling with a strange problem. When we have some VMWare clients running (mostly MS windows clients), than the IO-write performance on the host becomes very bad. The guest os's do not do anything, just having them started, sitting at the login prompt, is enough to trigger the problem. The host has plenty of 4G of RAM, and all clients fit easily into the space. The disksystem is a RAID5 (ok, not the fastest choice). Both hosts are running the latest CentOS 5.2 (but the problem was already present in 5.0 as well), and running the latest production version of VMWare server 1.0.7 (but when running 1.0.5 the problem was there too). One host as an adaptec 2820 with 4 SATA drives, and uses the aacraid driver. Another host is a proliant with a smart array E200, battery backed cache of 128 MB using the cciss driver. Filesystem is ext3 on both hosts. When measuring the write performance, I try to avoid measuring the use the buffer cache like this, writing a 4.2gb file: $ sync; time sh -c 'dd if=/dev/zero of=large bs=8k count=500k; sync' (Ignore the times that dd reports because those are including the buffer cache; divide 4.2gb by the number of seconds reported by "time".) To verify, I also open a another terminal and run there: $ iostat -kx /dev/sda 5 1000 On my own workstation with a single sata drive, I get about 54 MB/s. On the hosts having the RAID5 disks, and without any vmware client running, I get about 20MB/s. As said, not really fast, but it should be good enough for our purpose. However when I start one vmclient and repeat the test, the write speed drops to half to about 10MB/s. With 2 clients the write speed drops even more to about 5 MB/s. With 3 clients only 2 MB/s, and with 4 MB/s I get only 0.5-1 MB/s write speed. The iostat shows the disk is 100% utilized, and the processor is spending most of it's time (99-100%!) in iowait. Here is some output of iostat on an actually "idle" machine, running 3 MS Windows clients, all guest OS's are just sitting doing almost nothing, not even a antivirus program installed: Device: rrqm/s wrqm/s r/s w/s rkB/s wkB/s avgrq-sz avgqu-sz await svctm %util sda 0.00 33.80 0.60 76.80 2.40 443.20 11.51 110.46 1269.85 12.93 100.04 avg-cpu: %user %nice %system %iowait %steal %idle 0.10 0.00 1.50 75.98 0.00 22.42 Device: rrqm/s wrqm/s r/s w/s rkB/s wkB/s avgrq-sz avgqu-sz await svctm %util sda 0.00 75.00 0.20 86.40 0.80 630.40 14.58 105.74 1466.97 11.55 100.06 avg-cpu: %user %nice %system %iowait %steal %idle 0.10 0.00 8.09 14.89 0.00 76.92 Device: rrqm/s wrqm/s r/s w/s rkB/s wkB/s avgrq-sz avgqu-sz await svctm %util sda 0.00 27.00 0.60 32.60 2.40 346.40 21.01 19.10 1079.57 10.57 35.10 avg-cpu: %user %nice %system %iowait %steal %idle 0.10 0.00 2.50 16.12 0.00 81.28 Device: rrqm/s wrqm/s r/s w/s rkB/s wkB/s avgrq-sz avgqu-sz await svctm %util sda 0.00 82.40 0.40 24.80 1.60 285.60 22.79 26.31 430.37 12.52 31.54 avg-cpu: %user %nice %system %iowait %steal %idle 0.10 0.00 0.70 6.71 0.00 92.49 Device: rrqm/s wrqm/s r/s w/s rkB/s wkB/s avgrq-sz avgqu-sz await svctm %util sda 0.00 7.40 0.40 24.20 1.60 271.20 22.18 7.12 918.03 8.59 21.14 Has anyone ever seen this before? Any tips to find the cause? -- Paul

2 3

amazon web services and CentOS
by Karanbir Singh 29 Sep '08

29 Sep '08

hi, Over the last few months, based on the fact that people were asking me about it, I was in turn asking Amazon what they are doing to make CentOS available on their EC2 platform. After much conversation to / from their end, they are in a situation where they have offered me some access and credits to make the whole CentOS on AWS happen. This is the sort of thing right up the VirtSIG alley, so am wondering if there are people here who would like to help out at all ? -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

4 4

powernow error in Xen VM with new kernel
by Kai Schaetzl 27 Sep '08

27 Sep '08

I just upgraded my first Xen guest to the latest 5.2 kernel (2.6.18- 92.1.13.el5xen) and got a kernel error on reboot: powernow-k8: BIOS error - no PSB or ACPI _PSS objects No problems seen yet. I would think that the guest should not try to do any powernow stuff at all. Has anyone else noticed this? Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

1 0

redhat's Qumranet acquisition
by Karanbir Singh 24 Sep '08

24 Sep '08

http://www.redhat.com/about/news/prarchive/2008/qumranet.html I am sure most people would have already seen this, but posting for those who havent already. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

12 20

how do I access an LV on a xen dom0?
by Tom Diehl 23 Sep '08

23 Sep '08

Hi, I have a machine running several domU's. It has an LV that is currently mounted on dom0, that I would like to access from one of the domU's. If I umount the LV and remove it from the fstab on the dom0, is there a way I can mount it in one of the domU's? If there is a doc that describes how to do this, a pointer would be appreciated. I have tried google but so far no joy. Regards, -- Tom Diehl tdiehl(a)rogueind.com Spamtrap address mtd123(a)rogueind.com

2 2

PCI passthrough problems
by Enderson Maia 23 Sep '08

23 Sep '08

Hello, I'm having a problem, I've seen other people with the same problem, but with USB. Some people solved this with the pciback.permissive option, but in my case it's ignored. I'm using CentOS 5.2 - 2.6.18-92.1.10.el5.centos.plusxen The error return from the console starting the domU is below. I've tried swiotlb=force, pciback.permissive like I said. My configs are: /etc/modprobe.conf ... options pciback hide=(03:01.0) # cat /etc/xen//firewall name = "firewall" uuid = "cd5f6ad8-0682-73fd-3268-fb4a7b85c0ec" maxmem = 256 memory = 256 vcpus = 1 bootloader = "/usr/bin/pygrub" boot = "swiotlb=force" on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" vfb = [ "type=vnc,vncunused=1" ] disk = [ "phy:/dev/VolGroup00/firewall.disk,xvda,w" ] vif = [ "mac=00:16:3e:0e:53:5a,bridge=virbr0" ] pci = [ '0000:03:01.0' ] # rpm -qa | grep xen xen-libs-3.0.3-64.el5_2.1 xen-3.0.3-64.el5_2.1 kernel-xen-2.6.18-92.el5 kernel-xen-2.6.18-92.1.10.el5.centos.plus --- Iniciando interface eth0: [ OK ] Iniciando interface eth1: Determinando informação IP para o eth1...Fatal DMA error! Please use 'swiotlb=force' ------------[ cut here ]------------ kernel BUG at arch/i386/kernel/pci-dma-xen.c:401! invalid opcode: 0000 [#1] SMP last sysfs file: /class/net/eth1/address Modules linked in: xennet ip_conntrack_netbios_ns ipt_REJECT xt_state ip_conntrack nfnetlink iptable_filter ip_tables ip6t_REJECT xt_tcpudp ip6table_filter ip6_tables x_tables ipv6 xfrm_nalgo crypto_api dm_mirror dm_multipath dm_mod parport_pc lp parport 3c59x pcspkr mii xenblk ext3 jbd uhci_hcd ohci_hcd ehci_hcd CPU: 0 EIP: 0061:[<c040a39c>] Not tainted VLI EFLAGS: 00010292 (2.6.18-92.el5xen #1) EIP is at dma_map_single+0x12d/0x147 eax: 0000002f ebx: 00000000 ecx: 00000001 edx: f5416000 esi: 38f59e02 edi: 00000001 ebp: 0000004e esp: c071bdbc ds: 007b es: 007b ss: 0069 Process swapper (pid: 0, ti=c071b000 task=c066e2c0 task.ti=c06e6000) Stack: c0621abd c07fc448 008a8e02 00000000 cf914400 cf5db200 c07fc448 00000140 d1232e6e 00000001 c08a8e02 cf914000 cf88c200 00000002 cf5db200 0000004e d126c000 cf914000 0000004e c08a8e02 cf88c140 cf88c140 cf88c200 c07c4c88 Call Trace: [<d1232e6e>] boomerang_start_xmit+0x141/0x352 [3c59x] [<c05aec59>] dev_hard_start_xmit+0x198/0x1ee [<c05bcaf6>] __qdisc_run+0xe4/0x19a [<c05b0544>] dev_queue_xmit+0x1e0/0x2e8 [<c05b4b24>] neigh_resolve_output+0x1b2/0x1dc [<d136eb2e>] ip6_output2+0x256/0x2a7 [ipv6] [<d136f656>] ip6_output+0x9c7/0x9f3 [ipv6] [<d137c8c0>] dst_output+0x0/0x7 [ipv6] [<c05c3d12>] nf_hook_slow+0x3a/0x90 [<d137c8c0>] dst_output+0x0/0x7 [ipv6] [<d137e4d6>] ndisc_send_ns+0x3a8/0x47a [ipv6] [<c06090d8>] _spin_lock_irqsave+0x8/0x28 [<c042914a>] lock_timer_base+0x15/0x2f [<d1375ddb>] addrconf_dad_timer+0xc3/0xdf [ipv6] [<c0434244>] hrtimer_run_queues+0x14b/0x163 [<d1375d18>] addrconf_dad_timer+0x0/0xdf [ipv6] [<c0429600>] run_timer_softirq+0x101/0x15c [<c042613e>] __do_softirq+0x5e/0xc3 [<c0406edf>] do_softirq+0x56/0xaf [<c0406e80>] do_IRQ+0xa5/0xae [<c0549913>] evtchn_do_upcall+0x64/0x9b [<c04055d9>] hypervisor_callback+0x3d/0x48 [<c0408632>] raw_safe_halt+0x8c/0xaf [<c040321a>] xen_idle+0x22/0x2e [<c0403339>] cpu_idle+0x91/0xab [<c06eb9f5>] start_kernel+0x37a/0x381 ======================= Code: c0 74 07 8b 08 8b 58 04 eb 05 83 c9 ff 31 db 89 da 89 c8 f7 d2 f7 d0 21 fa 21 f0 89 d1 09 c1 74 13 68 bd 1a 62 c0 e8 de 7b 01 00 <0f> 0b 91 01 9e 1a 62 c0 5d f0 83 04 24 00 83 c4 0c 89 f0 89 fa EIP: [<c040a39c>] dma_map_single+0x12d/0x147 SS:ESP 0069:c071bdbc <0>Kernel panic - not syncing: Fatal exception in interrupt --- If you need more information, just tell -- Enderson Maia

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