virt May 2009

virt@lists.fedoraproject.org

24 participants
40 discussions

Guest kernel hanging at '...trying to set up timer as Virtual Wire IRQ...'
by Richard W.M. Jones 13 May '09

13 May '09

I've got the guest kernel hanging randomly at: ACPI: Core revision 20090320 ftrace: converting mcount calls to 0f 1f 44 00 00 ftrace: allocating 18780 entries in 37 pages ..TIMER: vector=0x30 apic1=0 pin1=0 apic2=-1 pin2=-1 ..MP-BIOS bug: 8254 timer not connected to IO-APIC ...trying to set up timer (IRQ0) through the 8259A ... ..... (found apic 0 pin 0) ... ....... failed. ...trying to set up timer as Virtual Wire IRQ... This is the very latest on Rawhide. Full packages, versions, etc in the build log here: http://koji.fedoraproject.org/koji/getfile?taskID=1351416&name=root.log http://koji.fedoraproject.org/koji/getfile?taskID=1351416&name=build.log Rich. -- Richard Jones, Emerging Technologies, Red Hat http://et.redhat.com/~rjones Read my programming blog: http://rwmj.wordpress.com Fedora now supports 75 OCaml packages (the OPEN alternative to F#) http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora

3 10

Virtualization Test Day
by Mark McLoughlin 07 May '09

07 May '09

Hey, The F11 Test Day for virtualization is next week (Thurs May 7). https://fedoraproject.org/wiki/Test_Day:2009-05-07_Virtualization Please join us for the day on #fedora-qa (irc.freenode.net) to help with testing Fedora's virt tools, writing test cases, filing bugs and debugging issues. On the day, you'll have the opportunity to work closely with other Fedora developers and contributors to make a real impact on the quality of Fedora's virtualization features. Preferably, anyone planning on joining us for the test day will have a full updated rawhide host machine installed in advance. The wiki page contains a first cut at listing test areas which we will cover on the day. Each test area will have a set of test cases. We plan to flesh out these test cases as part of the test day, but if people could dive in now and start writing some test cases, that would make a huge difference. Chris Lalancette is leading the way here with test cases for Xen DomU testing: https://fedoraproject.org/wiki/Test_Day:2009-05-07_Virtualization:XenDomU See you on IRC next week! Thanks, Mark.

1 3

Re: [fedora-virt] Virtualization Test Day
by Dale Bewley 07 May '09

07 May '09

----- "Chris Lalancette" <clalance(a)redhat.com> wrote: > Dale Bewley wrote: > > Already been poking![1] But now it's bed time. Hopefully I can do > some more testing tomorrow. > > > > [1] > http://fedoraproject.org/wiki/User:Dale/Test_Day:2009-05-07_Virtualization:… > > Thanks a lot for starting in on this! Quick question about your > ballooning > results; did you remember to balloon down the dom0 before trying to > balloon up > your guest? It doesn't do it automatically on when you run the "virsh > setmem" > command. Actually I did not modify the dom0. Can you take a peek at the discussion page[1]? Perhaps the test case could be clarified a little bit. Is step 1 run in the dom0? Is step 2 modifying xend to affect dom0 or a guest config? I assumed the latter but guest configs aren't there anymore. Just in case, I did try shrinking Domain-0 and testing again. [root@felix tmp]# virsh dominfo Domain-0 ... Max memory: no limit Used memory: 5181440 kB [root@felix tmp]# virst setmem Domain-0 $(( 1024 * 3000 )) [root@felix tmp]# virsh dominfo Domain-0 ... Max memory: no limit Used memory: 3072000 kB But I could not setmem to a value higher than <maxmem> of the domU config. [root@felix tmp]# virsh setmem f11-32 $(( 1024 * 2000 )) error: Invalid value of 2048000 for memory size I could balloon to values between <currentMemory> and <maxmem>, and 'xm list f11-32' would show the expected value, but the guest would not show more than <currentMemory>. So apparently I misunderstood the meaning of that element. I just tested another domU and I'll update my notes later, but: * If it's assumed that <currentMemory> should not be used for this test (contrary to what I put on the discusson page), and that you can't balloon a guest beyond <maxmem> then everything works fine. I can shrink and grow below <maxmem> with no issues. * If it's expected you can balloon to values between <currentMemory> and <maxmem>, then something may be wrong. [1] http://fedoraproject.org/wiki/QA_talk:Testcase_Virtualization_XenDomU_Memor… > -- > Chris Lalancette

2 1

Re: [fedora-virt] Virtualization Test Day
by Dale Bewley 07 May '09

07 May '09

Already been poking![1] But now it's bed time. Hopefully I can do some more testing tomorrow. [1] http://fedoraproject.org/wiki/User:Dale/Test_Day:2009-05-07_Virtualization:… -- Dale Bewley - Unix Administrator - Shields Library - UC Davis GPG: 0xB098A0F3 0D5A 9AEB 43F4 F84C 7EFD 1753 064D 2583 B098 A0F3 ----- "Mark McLoughlin" <markmc(a)redhat.com> wrote: > On Thu, 2009-04-30 at 21:57 +0100, Mark McLoughlin wrote: > > Hey, > > The F11 Test Day for virtualization is next week (Thurs May 7). > > > > https://fedoraproject.org/wiki/Test_Day:2009-05-07_Virtualization > > > > Please join us for the day on #fedora-qa (irc.freenode.net) to > help > > with testing Fedora's virt tools, writing test cases, filing bugs > and > > debugging issues. > > Just a reminder to folks - today is test day! :-) > > Cheers, > Mark. > > _______________________________________________ > Fedora-virt mailing list > Fedora-virt(a)redhat.com > https://www.redhat.com/mailman/listinfo/fedora-virt

2 1

Fedora 11 (rawhide) success with Xen pv_ops dom0 kernel (2.6.30-rc3)
by Pasi Kärkkäinen 06 May '09

06 May '09

Hello! Earlier I was testing Xen pv_ops dom0 kernel with Fedora 10, and after I got it working I decided to repeat the tests with Fedora 11 (rawhide). There was problems with the latest pv_ops dom0 xen-tip/next kernel tree for a while, but those problems are now resolved, and I got my Fedora 11 testbox working, so I decided to write here about my success. My setup: - Fedora 11 (rawhide as of 2009-05-05) - Xen included in F11, no external patches (xen-3.3.1-11.fc11) - xen-tip/next pv_ops dom0 kernel as of 2009-05-06, Linux 2.6.30-rc3. - All the rest was standard stuff included in Fedora 11 aswell With this setup I'm able to run Xen paravirtual (PV) domUs, install new domUs using virt-install and also install and manage domains with virt-manager. Current limitations: - Xen HVM support is not yet working with pv_ops dom0 kernel Earlier problems with VGA text console have also been fixed, so grub menu.lst entry like this now works: title Fedora Xen pv_ops dom0-test (2.6.30-rc3-tip) root (hd0,0) kernel /xen-3.3.gz dom0_mem=1024M loglvl=all guest_loglvl=all module /vmlinuz-2.6.30-rc3-tip ro root=/dev/vg00/lv01 module /initrd-2.6.30-rc3-tip.img Or if you want to have serial console, use this: title Fedora Xen pv_ops dom0-test (2.6.30-rc3-tip) / serial console root (hd0,0) kernel /xen-3.3.gz dom0_mem=1024M loglvl=all guest_loglvl=all com1=19200,8n1 console=com1 module /vmlinuz-2.6.30-rc3-tip ro root=/dev/vg00/lv01 console=hvc0 earlyprintk=xen module /initrd-2.6.30-rc3-tip.img Hopefully someone finds this information interesting! :) -- Pasi

1 0

Virt Test Day - Added doc links
by James Laska 06 May '09

06 May '09

Greetings, Just a heads up, I've added a documentation section to the Virtualization test day wiki. https://fedoraproject.org/wiki/Test_Day:2009-05-07_Virtualization#Documenta… Thanks to Rahul Sundaram for the "getting started" link. Please feel free to add any introductory/getting_started docs to this section. Thanks, James

1 0

Virt Test Day - PCI device assignment test cases
by Mark McLoughlin 06 May '09

06 May '09

Hi, I've posted some test cases for testing KVM PCI device assignment: https://fedoraproject.org/wiki/Test_Day:2009-05-07_Virtualization_KVM_PCI_D… The test cases are: 1. libvirt nodedev operations 2. assigning a device using libvirt 3. assigning a device using virt-manager 4. virt-install --host-device Note the "known bugs" section. It seems this feature has acquired some blocker bugs. Cheers, Mark

2 1

Virt Test Day - Graphics console test case review
by James Laska 06 May '09

06 May '09

Greetings folks, I've stubbed out a few test cases for the Fedora11 ImprovedVirtConsole feature [1]. I can't help but think more is needed, but I'm experiencing writers block. What does the group think? https://fedoraproject.org/wiki/Test_Day:2009-05-07_Virtualization_Graphical… * Should there be a test to confirm that older os-types continue to have the absolute pointer? * Should the tests explicitly try different virt types (e.g. KVM, qemu and xen)? * What else needs to be confirmed with this feature? Thanks, James

2 1

does f11 preview fix the network install issue?
by Robert P. J. Day 04 May '09

04 May '09

can anyone verify that the newly-unleashed f11 preview will no longer try to install a virtual image over the network when you select the DVD? thanks. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Annoying Kernel Pedantry. Web page: http://crashcourse.ca Linked In: http://www.linkedin.com/in/rpjday Twitter: http://twitter.com/rpjday ========================================================================

4 6

Fedora virt status
by Mark McLoughlin 04 May '09

04 May '09

2009-05-12 Compose & Stage Release Candidate (7 days) Truly we are in the final countdown to the Fedora 11 release. This coming Thursday (May 7th) we are holding a Fedora Test Day in an attempt to fully test all aspects of Fedora's virtualization support. More below details on how to join in the test day. Virt Test Day ============= On May 7th, the Fedora 11 Virtualization Test Day will take place on #fedora-qa (irc.freenode.net) http://www.redhat.com/archives/fedora-virt/2009-April/msg00287.html Please join us for the day on #fedora-qa (irc.freenode.net) to help with testing Fedora's virt tools, writing test cases, filing bugs and debugging issues. On the day, you'll have the opportunity to work closely with other Fedora developers and contributors to make a real impact on the quality of Fedora's virtualization features. In advance of the test day, a wiki page is being prepared listing the various areas which will be tested on the day and individual test cases for each of the test areas: https://fedoraproject.org/wiki/Test_Day:2009-05-07_Virtualization Currently, the Xen DomU test area has the most comprehensive set of test cases, but hopefully folks won't be long rectifying that! Fedora 12 ========= F12 tracker bugs have been created. See the wiki page for more details: https://fedoraproject.org/w/index.php?title=Virtualization_bugs The F12 blocker and target bugs depend on the F11 counterparts. The idea is that if we don't fix a bug in F11, it's automatically on the F12 tracker but we still have a list of bugs worth fixing in a post-GA F11 update. Also, dist-f12 now has builds of kvm-85 and libvirt-0.6.3. As soon as the F11 release has been composed, rawhide will switch to being composed from dist-f12 and these packages will appear in rawhide. FWN === Dale Bewley has contributed two more excellent virtualization sections to Fedora Weekly News: https://fedoraproject.org/wiki/FWN/Issue174#Virtualization https://fedoraproject.org/wiki/FWN/Issue173#Virtualization Schroedinger's VM ================= Jerry James experienced the same confusion many other people must have had when he went away leaving his kernel compile running in a VM and came back to find it wouldn't progress unless we was actually watching the VM window: http://www.redhat.com/archives/fedora-virt/2009-April/msg00207.html Is this expected? Do KVM-based VMs have to be looked at to do anything? If so, is there an option somewhere along the lines of RunEvenWhenIAmNotLookingAtYou=true? A much more rational explanation was forthcoming :-) http://www.redhat.com/archives/fedora-virt/2009-April/msg00212.html When using the SDL backend (i.e. instead of qemu-kvm -vnc), if you switch workspaces using Ctrl-Alt-Arrow, then SDL tries to grab the pointer and fails and keeps retrying until you switch back to the workspace. Fully gory details, here: https://bugzilla.redhat.com/480065 libguestfs ========== Rich Jones continued his progress with libguestfs and released version 1.0.0 followed by several more release. He also posted a number of interesting guestfish recipes, demonstrating the power of libguestfs: http://et.redhat.com/~rjones/libguestfs/recipes.html Dom0 Kernels ============ Michael Young posted some updated Dom0 kernel builds: http://www.redhat.com/archives/fedora-virt/2009-April/msg00243.html http://www.redhat.com/archives/fedora-virt/2009-May/msg00016.html Dan Berrange reported some success testing these kernels under Xen in a KVM guest. Bugs ==== DOOM-O-METER: 178 bugs open two weeks ago, 182 this week. Blockers: https://bugzilla.redhat.com/496298 F11 Beta :: under KVM anaconda detect cdrom media because udev doesn't probe for filesystem type Further progress was made on figuring out why anaconda fails to install packages from DVD media on KVM. The difference from baremetal turns out to be that qemu doesn't implement GPCMD_READ_DISC_INFO. https://bugzilla.redhat.com/493692 Creating new VM; SELinux prevents opening iso image of install media When starting a VM, sVirt re-labels a disk image with the svirt_image_t:MCS label so that only that VM may access the image. However, we weren't doing this for readonly images like ISOs. Dan Berrange and Dan Walsh worked together to come up with a patch to fix this - readonly images will now be re-labelled virt_content_t:s0 when the VM is started. https://bugzilla.redhat.com/497602 Virtualization group doesn't pull in qemu or kvm When the qemu package was split, we decided to have the Virtualization package group install qemu-kvm via a Provides on the qemu-system-x86 package. It turns out that yum groupinstall will only install packages, not rpm provides. To fix this, it was decided to make qemu-kvm a meta-package requiring the qemu-system-x86 package. https://bugzilla.redhat.com/497429 pwritev writes ramdom junk Very serious data corruptor which thankfully only affects latest development qemu upstream. Jakub already has a fix. https://bugzilla.redhat.com/492838 kvm: PTHREAD_PRIO_INHERIT mutexes fail to unlock sometimes (canberra-gtk-play crash locks desktop metacity bugbuddy) An odd issue whereby PTHREAD_PRIO_INHERIT mutexs fail to unlock on i386 KVM guests. Manifests itself as pulseaudio related desktop app segfaults. qemu: https://bugzilla.redhat.com/496642 qemu qcow2 image corruption Gleb pointed out another qcow2 corruption fix upstream and this was also included for F11. https://bugzilla.redhat.com/498405 qemu disk image corruption with qcow2/virtio QCOW2 image corruption seen with latest Fedora 11 and virtio-blk. Also reproducible with the latest upstream qemu-kvm stable branch. https://bugzilla.redhat.com/497170 qemu segfaults with "raw_aio_remove: aio request not found!" Rich Jones discovered a qemu-kvm segv when using read-only images. Patches have been identified upstream and ported to the stable branch. We'll pull them into an F12 update in due course. https://bugzilla.redhat.com/498242 QEMU should set CLONE_IO flag when creating any threads Dan Berrange suggests that qemu should use CLONE_IO for each of its threads so that all qemu threads share the same I/O priority so that ionice can be used with qemu. https://bugzilla.redhat.com/497341 Make the /dev/kvm device world accessible to all users by default After some discussion with the KVM maintainers, we've concluded that we should make /dev/kvm world accessible by default in F12. https://bugzilla.redhat.com/496627 qemu-kvm es1370 sound card emulation segfault https://bugzilla.redhat.com/495964 qemu locks up at shutdown with sdl audio driver Debugging issues with qemu's various sound backends continues. It looks like the pulseaudio backend might work better for people. libvirt: https://bugzilla.redhat.com/460649 libvirtd requires restart in order to detect new capabilities like KVM support Cole has come up with a patch to have libvirtd automatically detect if qemu-kvm is installed. Hopefully we'll have this patch in before the F12 release. https://bugzilla.redhat.com/474182 LVs created in an existing VG have wrong SELinux label https://bugzilla.redhat.com/497131 svirt fails to relabel qcow2 backing files sVirt re-labels images before it starts a guest, but it doesn't re-label qcow2 backing files. https://bugzilla.redhat.com/496945 libvirt should own /var/cache/libvirt in spec file libvirt not owning this directory causes it to be mislabelled which, in turn, causes virDomainPeek() to fail. virtinst: https://bugzilla.redhat.com/496340 Creating guests where the .iso image is on a NFS share doesn't work anymore Much discussion on the what svirt needs to do to support images on NFS shares. Cole resolved this by only warning if selinux labeling appears to be wrong. grub: https://bugzilla.redhat.com/479760 [PATCH] add support for virtio_blk devices to grub-install Jan ONDREJ came across this problem when testing the preview release and prompted Peter Jones to commit this patch. https://bugzilla.redhat.com/498416 Unable to boot Fedora11-Preview Jan also reports that on his F10 system, with F11 virt packages, he could boot a newly installed F11 Beta guest but not an F11 Preview guest. It looks most likely to be a grub issue, but this has not been reported on an F10 host yet. etherboot: https://bugzilla.redhat.com/498230 virtio PXE Roms "No IP address" Another report of etherboot PXE ROMs failing, but this time it seems that virtio is failing as well as e1000. xen: https://bugzilla.redhat.com/493103 Network periodically hangs during install of xen guest This problem has magically been resolved.

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

virt May 2009