Here's a response I received from Steffen Winterfelt (the author of gfxboot). I think this confirms that it's a KVM issue. I'm going to open an issue on the KVM SourceForge tracker.
> Could you point to either where this check is happening, the proper place to > ask, or the revision control system for gfxboot so I can find the patchset > myself? The short answer: the check you mention no longer exists. It is enssential to distinguish between pre-SL-10.2 gfxboot and post- SL-10.2. Up to SL 10.1/SLES10 gfxboot used to pass 4GB selectors to real mode to access memory. That didn't work in Xen, so I added a check that verified the selector. Partly due to this I rewrote the code entirely for 10.2 to run in PM all the time. So the check was no longer required. -- Gutsy Tribe 5 (KVM GUEST) needs -no-kvm to install https://bugs.launchpad.net/bugs/140713 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
