virt June 2009

virt@lists.centos.org

17 participants
10 discussions

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

fully virt Xen DomU network question
by Coert Waagmeester 08 Jul '09

08 Jul '09

Hello all fellow CentOS users! I have a working xen setup with 3 paravirt domUs and one Windblows 2003 fully virt domU. There are to virtual networks. As far as I can tell in the paravirt Linux DomUs I have gigabit networking, but not in the fully virt Windows 2003 domU.... Is there a setting for this, or is it not yet supported? I run xen-3.0.3-64.el5_2.3 Kind regards, Coert

9 16

kvm packages update
by Farkas Levente 30 Jun '09

30 Jun '09

hi, i update all of my kvm related packages for centos-5 in: http://www.lfarkas.org/linux/packages/centos/5/x86_64/virt/ http://www.lfarkas.org/linux/packages/centos/5/i386/virt/ the changes i follow fedora package naming so there is no kvm packages but qemu (which is actually qemu-kvm) and i switch both with the kmod and qemu package to the stable branch (although the old kvm-xx and kmod-kvm-xx packages are still there). so the new packages: - kmod-kvm-2.6.30 - qemu-0.10.5 and a few related packages: - bochs-* - etherboot-5.4.4 - gtk-vnc-0.3.8 - gtkglext-1.2.0 - libvirt-0.6.4 - python-virtinst-0.400.3 - vgabios-0.6b - virt-manager-0.7.0 - virt-viewer-0.0.3 i haven't got time to test them, but feel free to comment it. -- Levente "Si vis pacem para bellum!"

1 0

ConVirt 1.1 is released.
by jd 25 Jun '09

25 Jun '09

Hi We are extremely pleased to announce ConVirt 1.1. For more details on this release, please visit http://www.convirture.com/blog/2009/announcements/convirt-11-is-now-availab… ConVirt Team.

1 0

Re: [CentOS-virt] fully virt Xen DomU network question
by Christopher G. Stach II 24 Jun '09

24 Jun '09

----- "Coert Waagmeester" <lgroups(a)waagmeester.co.za> wrote: > Hello all fellow CentOS users! > > I have a working xen setup with 3 paravirt domUs and one Windblows > 2003 > fully virt domU. > > > There are to virtual networks. > > As far as I can tell in the paravirt Linux DomUs I have gigabit > networking, but not in the fully virt Windows 2003 domU.... > > Is there a setting for this, or is it not yet supported? Are you talking about the virtual network interface appearing to be 100Mbps? If so, that's just how it is because the qemu driver is written to emulate a Realtek card, which happens to be 100Mbps. A PV interface will look exactly like the underlying hardware. -- Christopher G. Stach II

1 0

32bit host and guest, TLS
by fmb fmb 22 Jun '09

22 Jun '09

Host and guest are both CentOS 5.3 32 bit. When I populate the root partition of the guest I noticed that the tls directory is empty. I installed the Base package only. However, in my host machine I have these two files /usr/lib/tls /usr/lib/perl5/5.8.8/i386-linux-thread-multi/asm/ioctls.ph /usr/lib/perl5/5.8.8/i386-linux-thread-multi/bits/ioctls.ph Not having TLS in the guest, is this normal? Is it still important to mv the tls in the host? Excuse me, but what is this TLS issue all about?

1 0

About using KVM with centos 5.x
by carlopmart 18 Jun '09

18 Jun '09

Hi all, Somebody have tried latest kvm release (kvm-85) under test or production environments?? I need some inputs about using kvm to deploy varios linux vm guests (centos, rhel, sles and ubuntu) and windows guests (windows 2003 and 2008) using kvm. Any special considerations?? Any tips?? Thanks. -- CL Martinez carlopmart {at} gmail {d0t} com

1 0

Xen with multiple virtual network interfaces with one bond
by Coert Waagmeester 18 Jun '09

18 Jun '09

Hello all, I have been running xen for a while now with two interfaces: dummy0 for host only communication, and eth0 for the outside network. my script looks like this: (/etc/xen/scripts/network-bridge-more) ------------------------------------------------------------------ #! /bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=dummy0 bridge=xenbr0 "$dir/network-bridge" "$@" vifnum=1 netdev=eth0 bridge=xenbr1 ------------------------------------------------------------------ now i have a newer setup where eth0 and eth1 are bonded. If i change eth0 in the above script to bond0 it messes up the bond completely and stops working. I have use /etc/xen/scripts/network-bridge-bonding, and that works, but then I can only have one virtual network for my domU I have tried this: ------------------------------------------------------------------ #! /bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 netdev=dummy0 bridge=xenbr0 "$dir/network-bridge-bonding" "$@" vifnum=1 netdev=bond0 bridge=xenbr1 ------------------------------------------------------------------ but that also does not work. It also messes up my bond. Any tips would be greatly appreciated. Kind regards, Coert

2 1

Xen vs. iSCSI
by Bill McGonigle 17 Jun '09

17 Jun '09

[previously sent to rhelv5 list, apologies to those on both] I've got a problem I can reproduce easily enough, but really I fail to understand what's going wrong. I've got a 5.3 Dom0, which is running three guests. One is Fedora 10, that runs with local flat files, and works fine. One is Nexenta 2 (opensolaris-based), and that runs off of physical partitions, and seems to work great. The third runs Fedora 11 and and has for its disks, iSCSI devices that are exported from Nexenta (ZFS-backed). I have the Dom0 mapping the two iSCSI devices, one for /boot and one for /. They're showing up initially as /dev/sdc and /dev/sdd. If I go after the iSCSI devices in Dom0, with dd, for instance, they work fine all day. I can read and write the entire devices to and from local files without error. iSCSI seems to work properly in that regard. I'm getting about 38MB/s. I've scrubbed the disk pool and no errors were found and long SMART self-test passed on each of the disks. I've also been able to mount both iSCSI devices and run bonnie++ on them successfully from Dom0. So, I specify those devices in the Xen config for the domU (tried both real device name and /dev/disk/by-path/ names) and the DomU boots and operates as I'd expect. Installation worked fine and typical operations (low volume) work. However, then I try to do something, which I'm assuming is more disk intensive, like running a yum update, and iSCSI seems to fall over. In the DomU, I'll see a lock-up, and then filesystem errors. e.g.: Installing : kernel [############################################ ] 1/33EXT3-fs error (device xvda1) in ext3_ordered_writepage: IO failure In the Dom0, I'll see: sd 6:0:0:0: timing out command, waited 360s sd 6:0:0:0: SCSI error: return code = 0x06050000 end_request: I/O error, dev sdc, sector 37319 sd 7:0:0:0: timing out command, waited 360s sd 7:0:0:0: SCSI error: return code = 0x06000000 end_request: I/O error, dev sdd, sector 29792137 sd 7:0:0:0: timing out command, waited 360s sd 7:0:0:0: SCSI error: return code = 0x06000000 end_request: I/O error, dev sdd, sector 29792313 Both (all) iSCSI devices are failed. Under iostat I see activity to the iSCSI block devices, and the whole machine acts mostly I/O blocked (even the Fedora 10 DomU running on flat files will start throwing nagios into a tizzy). If I do 'service iscsi stop' everything picks right back up (though the DomU using them as its disks is obviously unhappy). When I start iscsi again I can pick right back up (after repairing filesystems in the DomU), and I can repeat the process at will. Sometimes the disks will come back as, e.g. sdd and sde, leaving me to think something still has a handle on sdc. But lsof shows nothing in dom0. One thing that stood out were some of the block and sector number errors being right on power of two boundries: scsi 7:0:0:0: SCSI error: return code = 0x00010000 end_request: I/O error, dev sdd, sector 32768 Buffer I/O error on device sdd, logical block 4096 Buffer I/O error on device sdd, logical block 4097 Buffer I/O error on device sdd, logical block 4098 Buffer I/O error on device sdd, logical block 4099 Buffer I/O error on device sdd, logical block 4100 Buffer I/O error on device sdd, logical block 4101 Buffer I/O error on device sdd, logical block 4102 Buffer I/O error on device sdd, logical block 4103 Buffer I/O error on device sdd, logical block 4104 Buffer I/O error on device sdd, logical block 4105 scsi 7:0:0:0: rejecting I/O to dead device but as I opened with, I'm sort of at as loss as to what is actually causing the problem. Any suggestions for further troubleshooting and/or ideas about what's happening appreciated. Thanks, -Bill -- Bill McGonigle, Owner Work: 603.448.4440 BFC Computing, LLC Home: 603.448.1668 http://www.bfccomputing.com/ Cell: 603.252.2606 Twitter, etc.: bill_mcgonigle Page: 603.442.1833 Email, IM, VOIP: bill(a)bfccomputing.com Blog: http://blog.bfccomputing.com/ VCard: http://bfccomputing.com/vcard/bill.vcf

3 6

Fenker, Oliver is out of the office.
by oliver.fenker＠bayerbbs.com 16 Jun '09

16 Jun '09

Ich werde ab 11.06.2009 nicht im Büro sein. Ich kehre zurück am 29.06.2009. I will be out of the office starting 2009-06-11 and will not return until 2009-06-29

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt June 2009