virt April 2009

virt@lists.fedoraproject.org

33 participants
72 discussions

how can i see if the running kernel has kvm support?
by Robert P. J. Day 10 Apr '09

10 Apr '09

i'm curious as to how to examine a running kernel to see what it has in the way of kvm support. i can see that "make menuconfig" gives me the options: KVM (KVM) KVM for Intel (KVM_INTEL) KVM for AMD (KVM_AMD) first question: technically, i can select generic KVM support without selecting either INTEL or AMD support. can i assume that that's a pointless thing to do? the help text for CONFIG_KVM does seem to suggest that you really need to additionally select a processor module to make any sense; i was just wondering if there's some obscure scenario where having only that generic KVM support had any value. next, regardless of whether kvm support is built-in or whether it's modular and the modules have been loaded, is there some indication -- say under /proc or /sys -- that shows the current state of kvm support in the kernel? if i had the config file for the running kernel, i could of course look at that, but let's assume that i have no such thing, and that kvm support is built-in so i can't even check for, say, /sys/module/kvm. is there a userspace way to probe and determine kvm support? rday p.s. just to be clear, kvm support in the kernel doesn't count if that kernel is running on a system without HW virt support, for which kvm support obviously has no value since it can't be used. in a case like that, i'd like to get the answer that there is *no* support. ======================================================================== 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 8

Fedora virtualization status
by Mark McLoughlin 09 Apr '09

09 Apr '09

2009-04-14 Final freeze It's only a matter of days until the F11 tree freezes and we the list of bugs isn't getting any shorter! https://bugzilla.redhat.com/showdependencytree.cgi?id=F11VirtBlocker&hide_r… https://bugzilla.redhat.com/showdependencytree.cgi?id=F11VirtTarget&hide_re… Now is a good time for people to jump in and help out :-) FWN === Dale Bewley continues to churn out useful virtualization sections for Fedora Weekly News. This weeks edition is here: http://fedoraproject.org/wiki/FWN/Issue170#Virtualization Update Process ============== Dan Berrange posted an excellent write up on the soul searching some of us have been doing around our update process for Fedora packages: http://www.redhat.com/archives/fedora-virt/2009-April/msg00008.html The upshot of this is: 1) We will continue to immediately push the latest upstream releases to rawhide 2) We will create a "virt preview" yum repository which will contain the latest rawhide packages rebuilt for the current Fedora stable branch 3) We will try a lot harder to keep the Fedora stable branch ... well ... stable. That means we'll only rebase to a newer upstream version in exceptional circumstances and we'll do our best to backport important fixes to the stable branch. Three cheers for sanity prevailing! libvirt-TCK ========== Dan didn't stop there. Later on in the week he posted details of his efforts to lay the groudwork for serious automated testing of libvirt. He calls it the libvirt Technology Compatibility Kit (TCK) and compares it to the Java TCK: http://www.redhat.com/archives/libvir-list/2009-April/msg00176.html The libvirt TCK provides a framework for performing testing of the integration between libvirt drivers, the underlying virt hypervisor technology, related operating system services and system configuration. The idea (and name) is motivated by the Java TCK In particular the libvirt TCK is intended to address the following scenarios - Validate that a new libvirt driver is in compliance with the (possibly undocumented!) driver API semantics - Validate that an update to an existing driver does not change the API semantics in a non-compliant manner - Validate that a new hypervisor release is still providing compatability with the corresponding libvirt driver usage - Validate that an OS distro deployment consisting of a hypervisor and libvirt release is configured correctly Thus the libvirt TCK will allow developers, administrators and users to determine the level of compatability of their platform, and evaluate whether it will meet their needs, and get awareness of any regressions that may have occurred since a previous test run KVM Autotest ============ In a similar vein, upstream KVM developers have been working to create an automated testing harness for KVM called kvm-autotest. Fedora virtualization users can help improve KVM by running kvm-autotest on their own hardware using Fedora's version of KVM: https://fedoraproject.org/wiki/Testing_KVM_with_kvm_autotest Things are looking up on the QA front for virtualization! libguestfs ========== As mentioned last week, Rich Jones is working on to create an API to allow accessing and modifing guest images. Well, Rich blogged this week about the progress he is making: Rich Jones blogged on his libguestfs progress: http://rwmj.wordpress.com/2009/04/08/libguestfs-ocaml-bindings/ http://rwmj.wordpress.com/2009/04/08/libguestfs-perl-bindings/ http://rwmj.wordpress.com/2009/04/07/libguestfs-lvm-support/ http://rwmj.wordpress.com/2009/04/04/more-libguestfs-progress/ http://rwmj.wordpress.com/2009/04/04/libguestfs-modifying-a-guest-image/ He also posted some details of how he has integrated Augeus with libguestfs to simplify the task of editing config files in guest images: http://www.redhat.com/archives/fedora-virt/2009-April/msg00045.html Vote +1 :: Rich Jones For Sponsor ================================= Rich has requested to be approved as a Fedora Package Sponsor: https://fedorahosted.org/fesco/ticket/130 Clearly this is just a formality, but just in case ... we think everyone should email their local FESCo representative and threaten severe retribution if they don't "Vote +1 for Rich!" :-) (I got carried away? Really?) Virt Tutorial ============= Robert P. J. Day posted to the fedora-virt detailing his intention to write a beginner's guide to virtualization on Fedora: http://www.redhat.com/archives/fedora-virt/2009-April/msg00009.html Discussion continued later in the week discussing what the "Fedora virtualization experience" should be: http://www.redhat.com/archives/fedora-virt/2009-April/msg00049.html sVirt ===== Dan Berrange edged sVirt closer to perfection this week with a couple of fixes to python-virtinst: * Fri Apr 3 2009 Daniel P. Berrange <berrange(a)redhat.com> - 0.400.3-4.fc11 - Attempt to fix SELinux labelling on CDROM ISOs used for installation * Fri Apr 3 2009 Daniel P. Berrange <berrange(a)redhat.com> - 0.400.3-3.fc11 - Set SELinux context on $HOME/.virtinst to make kernel/initrd boot work (rhbz #491052) Dan Walsh also posted his thoughts on a configuration file for sVirt: http://www.redhat.com/archives/libvir-list/2009-April/msg00107.html gPXE ==== Dell's Matth Domsch requested add support in QEMU for booting gPXE boot ROMs so as to allow PXE booting directly from an iSCSI LUN: https://bugzilla.redhat.com/457979 Update QEMU to use gPXE roms for iSCSI boot support Glauber has been working away at the problem. First he got a patch into upstream QEMU which creates enough ROM space to allow gPXE to be used. However, it turns out this breaks QEMU's '-vga std' option: https://bugzilla.redhat.com/494376 qemu ROM space increase breaks WinXP guests He has posted a patch upstream to fix this issue, but the patch has triggered a debate which might lead to the original patch for gPXE being reverted temporarily until a "perfect" solution is found some time in the future. Also, Glauber tracked down a kvm.ko bug which prevented gPXE ROMs for booting: https://bugzilla.redhat.com/494469 qemu-kvm fails to boot gPXE ROMs He has posted a number of patches upstream to resolve this issue, and the debates are ongoing. Contributing to the Fedora Kernel ================================= Marcelo had some patches from upstream to KVM's timer interrupt injection code which he wanted to get into F11 in order to fix: https://bugzilla.redhat.com/491625 Unable to run RHEL-5 Xen within KVM guest Marcelo decided it was time to bite the bullet and figure out the fairly involved list of steps to allow him to commit fixes to the Fedora kernel i.e.: - Get a FAS account - Accept the CLA - Download a cert for Koji - Upload an SSH key for CVS - Request commit access to the kernel package - Email the proposed patch to fedora-kernel-list - Check the kernel out from CVS - Add the patch to the spec file and commit - Tag and build in Koji Whew! And after figuring all that out, we realised the kernel folks already had written up some notes on this process: https://fedoraproject.org/wiki/Kernel#Contributing_to_the_Fedora_kernel It seems these kernel folks aren't so nasty after all ... Bugs ==== DOOM-O-METER: 192 bugs last week, 184 this week. Yeah! Okay, it's holiday time so I couldn't be bothered making the bugs summary a bit more palatable :-) https://bugzilla.redhat.com/487720 qemu-kvm segfaults on startup in SDL_memcpyMMX/SSE The fix from upstream has been backported to rawhide and is available in SDL-1.2.3-9.fc11. https://bugzilla.redhat.com/494005 Unable to create a new guest using a Live iso from a directory storage pool Looks like a case where a the ISO was copied into the pool's directory and, so, not seen by virt-manager. Solution could be to have virt-manager refresh before probing. https://bugzilla.redhat.com/473154 Virtual machine fails to start without cdom - qemu: could not open disk image /dev/sr0 Common problem with Windows guests not starting when no cdrom is available because virtinst must leave it attached post-install. Cole dug in and found that the problem was in qemu itself - relying on the cdom device path being /dev/cd - and came up with a straightforward patch. https://bugzilla.redhat.com/494286 Unable to boot because libvirt uses '-cpu qemu32' with x86_64 virtual machine Somewhere along the line libvirt or virtinst was creating guest configuration files with arch='i686' on x86_64 hosts. This worked fine in the past because we just ignored the arch, but now it's biting us in the ass. It's still not clear where the original bug was. https://bugzilla.redhat.com/493518 Fedora 9 does not have virtio PXE ROM - PXE booting Fedora 10 guests under virt-manager fails We've rebased virt-manager in Fedora 9 and the new version tries to PXE boot guests with virtio. Problem is that QEMU in F9 does not have virtio PXE ROM. https://bugzilla.redhat.com/491943 qemu-img crashes creating 5TB qcow2 file cdub posted his patch to qemu-devel and Anthony committed to the stable branch. Glauber cherry-picked into rawhide. https://bugzilla.redhat.com/477035 EFI BIOS support in qemu This weeks Fedora Test Day is testing Fedora's EFI support. This would be a lot easier if qemu had EFI support. A link to xen related code supposedly implementing this was posted to the bug. https://bugzilla.redhat.com/493410 Windows installs (ex: Win 2008) reboot media as soon as install starts Looks like Win2008 under QEMU sees the cdrom as being ejected for some reason. https://bugzilla.redhat.com/491683 virt-viewer no longer auto adjusts to guest screen size Jesse provided more info for Cole on how to reproduce this problem. https://bugzilla.redhat.com/494075 openbios bug causes qemu-system-ppc "invalid/unsupported opcode" failure It looks like an openbios bug is breaking qemu's ppc target. A potential fix has been identified upstream. https://bugzilla.redhat.com/494002 qemu vga segfault under kvm-autotest Avi followed up his huge patch for this issue with a beautiful one line fix which has now been built in rawhide. https://bugzilla.redhat.com/494739 KVM isn't used by qemu launched by Virtual Machine Manager A report of kvm_intel not being loaded at boot. Further confusion by libvirtd not noticing kvm is available after it had been loaded as per bug #460649. https://bugzilla.redhat.com/494541 E1000 PXE boot fails with "No IP address" Apparently etherboot's e1000 PXE ROM is failing to acquire a DHCP address. https://bugzilla.redhat.com/478414 Server down after 1-2 days, many of processes in state "D". (xen domU) A hard to reproduce issue on F10 xen pv_ops DomU guests where some processes get stuck in uninterruptible sleep. https://bugzilla.redhat.com/487735 virt-manager/virtinst should not set a keymap unless one is explicitly requested Cole has now fixed this in rawhide - virtinst and virt-manager don't specify a keymap for qemu to use unless explicitly asked to do so by the user. Now, the raw scancode extension should be used by default, fixing keyboard issues seen by several people. https://bugzilla.redhat.com/493408 Can't use API to create virtual floppy drive with correct device name Cole cherry-picked the fix for upstream into rawhide. Now virtinst should properly create floppy drives for guests.

1 0

qemu+kvm obsoletes kqemu?
by Robert P. J. Day 08 Apr '09

08 Apr '09

(just another in a long list of trivial questions) since there is no available kqemu package for f11, i'm assuming that bundling qemu and kvm makes a separate kqemu package redundant, is that correct? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Annoying Kernel Pedantry. http://crashcourse.ca http://www.linkedin.com/in/rpjday ========================================================================

7 8

remaining userspace kvm packages?
by Robert P. J. Day 08 Apr '09

08 Apr '09

given that, in userspace in f11, kvm has been folded into qemu (or is it the other way around?), what's left in userspace related to kvm that someone might need to install manually? AFAICT, there's qemu-kvm-tools for debugging and diagnostics, and not a lot more. is that about right? everything else kvm-related pretty much comes with your qemu install. rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Annoying Kernel Pedantry. http://crashcourse.ca http://www.linkedin.com/in/rpjday ========================================================================

2 3

does "qemu-launcher" really need "qemu" as a dependency?
by Robert P. J. Day 08 Apr '09

08 Apr '09

for the sake of anal-retentive and pedantic testing, i decided to remove a random qemu system emulation package (in this case, qemu-system-arm) with: # yum remove qemu-system-arm and the result was to remove qemu-launcher as well. was that really necessary? does qemu-launcher really need the entire "qemu" meta package as a dependency? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Annoying Kernel Pedantry. http://crashcourse.ca http://www.linkedin.com/in/rpjday ========================================================================

2 2

Losing mouse focus
by Bill Davidsen 07 Apr '09

07 Apr '09

I have asked this on both Fedora and KVM lists, and I get back a mix of "it's you, I don't have the problem" and "mee, too" responses, so sorry if you saw this elsewhere. I have been running little machines using KVM from command line. Lots of little machines, CentOS, FC9, 10, and now 11. I run them on machine like i6600, e9400, and Athlon dual core, using FC9, FC10, and FC6 with recent kernel and KVM. Since I see the problem on multiple places I assume it isn't unique. The problem is that I lose mouse (but not keyboard) focus, running in a window or full screen. I will be typing, mail or documentation, and all of a sudden while the keyboard input going where it should, there's another mouse pointer, and it's not bound to the VM I'm using. The VM mouse cursor just sits there... I don't see any fixes listed anywhere, using "nomodeset" was suggested, but it didn't help. This was mildly annoying when I was testing, now that I'm running many production images it's unproductive. Any thoughts or pointers? -- bill davidsen <davidsen(a)tmr.com> CTO TMR Associates, Inc "You are disgraced professional losers. And by the way, give us our money back." - Representative Earl Pomeroy, Democrat of North Dakota on the A.I.G. executives who were paid bonuses after a federal bailout.

3 3

is there a more newbie-level mailing list for fedora virt?
by Robert P. J. Day 06 Apr '09

06 Apr '09

i ask since i'm probably doing a virtualization seminar at a local linux fest later this year, and i'd like to gear it towards beginners. i realize that there is abundant online documentation on this topic, but it's just not geared for people who are starting out. for example, if one reads the online 'Getting started with virtualization" here: https://fedoraproject.org/wiki/Getting_started_with_virtualization the second paragraph reads as follows: "Xen supports para-virtualized guests as well as fully virtualized guests with para-virtualized drivers. Para-virtualization is faster than full virtualization but does not work with non-Linux operating systems or Linux operating system without the Xen kernel extensions. Xen fully virtualized are slower than KVM fully virtualized guests." i'm sorry, but that's not for beginners. it just isn't. so is there a forum where i can chat with folks about putting together something really and truly designed for an audience who might be linux-savvy but need to be walked into virtualization slowly and gently? rday p.s. i was planning on recording my thoughts here: http://www.crashcourse.ca/wiki/index.php/Virtualization_on_Fedora but i'm more than happy to help with something officially fedora if it's more attuned to what i'm trying to do. ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry: Have classroom, will lecture. http://crashcourse.ca Waterloo, Ontario, CANADA ========================================================================

2 1

Using kvm-autotest to test Fedora KVM
by Mark McLoughlin 03 Apr '09

03 Apr '09

Hi, Upstream KVM developers are working hard on a suite of regression tests for KVM. It would be hugely helpful if people could run kvm-autotest on their own machines to try and catch as many KVM issues as possible. I've written up some notes here: https://fedoraproject.org/wiki/Testing_KVM_with_kvm_autotest I've just run this myself on rawhide using qemu-0.10-5.fc11 and it succeeded. Cheers, Mark.

1 0

Fedora virtualization status report
by Mark McLoughlin 03 Apr '09

03 Apr '09

The F11 final development freeze is getting very close: 2009-04-14 Final freeze (12 days) There's a huge pile of bug-fixing and polish work to do in that time. If you're looking to help out, there's no better place to start than the F11VirtBlocker/F11VirtTarget tracker bugs: https://bugzilla.redhat.com/showdependencytree.cgi?id=F11VirtBlocker&hide_r… https://bugzilla.redhat.com/showdependencytree.cgi?id=F11VirtTarget&hide_re… F11 Beta Release ================ The Fedora 11 Beta was announced last week: http://www.redhat.com/archives/fedora-announce-list/2009-March/msg00012.html Please do take the time to try it out and file bugs! Fedora Weekly News ================== Another week, another FWN issue with a virtualization section from Dale Bewley: http://fedoraproject.org/wiki/FWN/Issue169#Virtualization F11 QEMU ======== There has been confusion all round on what version of QEMU will be included in the Fedora 11 release. The confusion stems from the fact that qemu is now being built from a kvm-userspace tarball, not the recently release qemu-0.10.1 tarball. The plan for F11 is to release with an official kvm-userspace tarball released from the upstream stable branch which is based on qemu-0.10.x. However, since upstream KVM hasn't made that release quite yet, rawhide contains a snapshot of the upstream stable branch of kvm-userspace. The upstream stable branch was only created this week, and Glauber promptly went ahead and replaced the snapshot of the development branch in rawhide with a snapshot of the stable branch. He also needed to backport the VNC SASL patches and some gcc build fixes. Everyone should keep an eye out for regressions! In other news, FESCo rubber-stamped the kvm/qemu merge feature for F11: https://fedoraproject.org/wiki/Features/KVM_and_QEMU_merge This just means the feature will now be pimped in the release notes. On the bugs front, the GCC bug affecting qemu was fixed this week: https://bugzilla.redhat.com/490512 segfault in stw_kernel when qemu is run https://bugzilla.redhat.com/490509 GCC register allocation wrongly using ebp The gcc bug has been fixed, so qemu should be fixed since qemu-0.10-0.12.kvm20090323git.fc11 Also: https://bugzilla.redhat.com/457979 Update QEMU to use gPXE roms for iSCSI boot support Glauber posted a patch upstream to allow enough ROM space for gPXE. The fix was accepted upstream and Glauber cherry-picked it into rawhide. https://bugzilla.redhat.com/471000 QEMU processes input from arrow keys incorrectly glommer backported the evdev patch to F-10 qemu-kvm and pushed to updates-testing. Please test and update its karma! https://bugzilla.redhat.com/492075 qemu package missing debuginfo for qemu-img Glauber's patch upstream prompted a configure --disable-strip option to be added. Latest rawhide qemu is building with this option and we have debuginfo back again. F11 Translations ================ The Fedora i18n team created a bunch of bugs against virt-manager, virt-df, virt-mem and virt-top to allow them to submit translations for Fedora 11: https://bugzilla.redhat.com/493795 (virt-manager) https://bugzilla.redhat.com/493797 (virt-df) https://bugzilla.redhat.com/493798 (virt-mem) https://bugzilla.redhat.com/493799 (virt-top) Fedora 12 Development ===================== Some people are mighty impatient and already eager to start working towards Fedora 12. To that end, Jesse announced that maintainers can request their packaged be branched for F12: http://www.redhat.com/archives/fedora-devel-list/2009-March/msg02029.html The kernel guys have started building the 2.6.30-rc0 kernels and they can be downloaded from Koji. Again, the virt features already planned for F12 are listed here: https://fedoraproject.org/wiki/Category:F12_Virt_Features Shared Network Interface ======================== In a similar vein, Laine Stump and David Lutterkort have been pushing ahead with the network interface configuration support that's planned for libvirt in Fedora 12. Laine posted an API proposal to libvir-list: http://www.redhat.com/archives/libvir-list/2009-March/thread.html#00397 More details on the F12 feature can be found here: https://fedoraproject.org/wiki/Features/Shared_Network_Interface libvirt Release Schedule ======================== Daniel Veillard posted his plans for the next libvirt release and this prompted a healthy discussion on libvirt's release process and schedule. Among the options being discussed are monthly releases, feature freezes and stable releases: http://www.redhat.com/archives/libvir-list/2009-March/thread.html#00425 Related is the question of whether every new release of libvirt (and other virt packets) should be pushed to stable Fedora releases. More on this soon. libguestfs ========== Rich Jones posted a blog about a new project he is working on to create an API to allow accessing and modifing guest images. True to form, Rich's idea is firmly in the crazy-but-might-just-work category: http://rwmj.wordpress.com/2009/04/01/libguestfs-access-and-modify-virtual-m… ... Now step aside for a minute and think about virtual machine disk images. From the host, they look like files or partitions, but they contain a partition table, partitions, perhaps LVM, a variety of filesystems like ext3 or NTFS or btrfs, and the whole lot might be wrapped in a tricky container such as qcow2. For virt-df we actually wrote new code that can decode a lot of this, but it’s a massive effort to keep up with changes in the formats. What we need to use is the Linux kernel code directly. The way I’m going to do this is to boot a Linux kernel. A small, you might say “minimal” Linux distro, with a bit of userspace. The whole thing runs inside a qemu container, and we talk from a small library to the userspace inside qemu, giving it instructions like “edit this file”, “run this program”, “install this device driver”. Xen Dom0 ======== Michael Young continued updating his test kernels and posted a URL for yum repo: http://fedorapeople.org/~myoung/dom0/ Pasi Kärkkäinen reports that CONFIG_HIGHPTE is broken on some machines and Michael has disabled this in his latest build. Upstream, Jeremy Fitzhardinge pushed the dom0 changes directly to Linus, which seems to have got Ingo all riled up: http://lkml.org/lkml/2009/3/31/362 It looks like Linus may have just ignored the pull request. Time will tell. Bugs ==== DOOM-O-METER: 185 bugs last week, 192 this week. Bah! (On a side note - this metric includes NEEDINFO bugs; we should probably do a run through to clean those up) https://bugzilla.redhat.com/490266 virtio_net tx stall with segmentation offload Guest->remote GSO failure with 2.6.29 host, but not 2.6.27. Herbert's fix was pulled into rawhide from upstream. https://bugzilla.redhat.com/492082 anaconda "unitialized drive" warning is a little too terrifying Further discussion on anaconda's "YOU WILL LOSE ALL DATA" warning. The current suggestion is that virtinst should add an empty partition table to the disks it creates. https://bugzilla.redhat.com/492523 [Fedora Xen]: pvops kernels won't boot on processors without the NX bit https://bugzilla.redhat.com/480880 f10 x86_64 xen guests fail to boot on f8 host (NX issue) Chis Lalance investigated the pv_ops NX issue some more and poked upstream into action. It looks like Chuck Ebbert is going to include the fix from upstream for F11. https://bugzilla.redhat.com/478734 selinux blocks kvm network configuration script (e.g. /etc/qemu-ifup) Some configurations currently require an /etc/qemu-ifup script, but this is blocked by SELinux. Plan is to support these configurations in libvirt directly. https://bugzilla.redhat.com/492829 virt-manager console should only scale console when maximised or fullscreen https://bugzilla.redhat.com/469830 RFE: Let details view remember the View->Scale display state Resolved by the "Graphical Console Scaling" preference. https://bugzilla.redhat.com/493692 Creating new VM; SELinux prevents opening iso image of install media Sounds like an sVirt related problem. https://bugzilla.redhat.com/493256 network install gives "Permission denied: '/var/lib/libvirt/boot/virtinst-.treeinfo.XIYNd_" An F10 bug with latest virt-manager. Another SELinux issue? https://bugzilla.redhat.com/493258 "Disk is already in use by another guest!" Latest virt-manager warning that another guest is using disk image, when the previous guest has been deleted. https://bugzilla.redhat.com/493408 Can't use API to create virtual floppy drive with correct device name Issue with providing floppy drives to guests using virt-install. Fix is upstream and looks easy to cherry-pick into rawhide. https://bugzilla.redhat.com/493414 Windows installs require manual reboot in the middle During an install using virt-install, Windows is seen to shut down rather than reboot. May be a generic KVM reboot issue with Windows. https://bugzilla.redhat.com/492523 xen pvops kernels won't boot on processors without the NX bit What looks like a fix for this issue is in Jeremy's queue

1 0

Copy & paste
by Gianluca Sforna 02 Apr '09

02 Apr '09

Is there a way to copy&paste to/from a virtual machine? -- Gianluca Sforna http://morefedora.blogspot.com http://www.linkedin.com/in/gianlucasforna

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

virt April 2009