Bugs item #2019608, was opened at 2008-07-16 11:03 Message generated for change (Comment added) made by sharms You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2019608&group_id=180599
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: intel Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Johannes Truschnigg (c0l0) Assigned to: Nobody/Anonymous (nobody) Summary: Ubuntu 8.04.1 (IA32 && x86_64) - cannot install bootloader Initial Comment: CPU: Intel Core 2 Quad Q6600 (4 cores) Distro, kernel: Gentoo GNU/Linux ~amd64, Kernel 2.6.25-r6 Bitness, compiler: x86_64, GCC 4.3.1 KVM versions: kvm-70, kvm-71 When trying to install Ubuntu) either 32bit or 64bit) in a KVM guest, grub-install croaks with. The guest kernel debug ringbuffer shows the following messages: (Please see http://pasted.at/9d7e95f873.html or the attached file!) Windows XP also hangs at installing, actually before anthing substantial other than copying installation files gets done. The first phase of the install completes, however - the "graphical installer" that's started after the first reboot hangs indefinitely. Worked fine with version <= kvm-69 with the very same settings. I'm happy to provide additional information upon request. ---------------------------------------------------------------------- Comment By: Steven Harms (sharms) Date: 2008-08-08 10:34 Message: Logged In: YES user_id=2083355 Originator: NO I can confirm this using KVM 72 on the host and trying a SLES 10 SP2 x86_64 guest. ---------------------------------------------------------------------- Comment By: Johannes Truschnigg (c0l0) Date: 2008-08-08 05:21 Message: Logged In: YES user_id=1987269 Originator: YES FYI: As of kvm-72 (Kernel 2.6.26), this issue still is NOT resolved. ---------------------------------------------------------------------- Comment By: Alexander Graf (awwy) Date: 2008-07-28 03:03 Message: Logged In: YES user_id=376328 Originator: NO Ok, so the problem was the SYSENTER transition. I posted a patch to resolve this issue on the KVM mailinglist. Please try and see if it works for you. Also please close this bug if it works. ---------------------------------------------------------------------- Comment By: Alexander Graf (awwy) Date: 2008-07-28 02:34 Message: Logged In: YES user_id=376328 Originator: NO Ok this is SYSENTER, so things _should_ work actually: The address we're faulting in is: Pid: 1, comm: grub Not tainted 2.6.16.60-0.21-default #1 RIP: 0010:[<000000008011c8fc>] [<000000008011c8fc>] Looking at the same address extended by 0xffffffff gives us: (gdb) x /i 0xffffffff8011c8fc 0xffffffff8011c8fc <ia32_sysenter_target>: swapgs when I break at the wrong address (gdb) b *0x8011c8fc Breakpoint 1 at 0x8011c8fc The breakpoint jumps in in long mode: (qemu) info registers RAX=0000000000000024 RBX=00000000f7ee1ff4 RCX=00000000fff985f0 RDX=0000000000000001 RSI=0000000000000000 RDI=00000000fff98674 RBP=00000000fff985ac RSP=0000000000000000 R8 =0000000000000000 R9 =0000000000000000 R10=0000000000000000 R11=0000000000000200 R12=0000000000000000 R13=0000000000000000 R14=0000000000000000 R15=0000000000000000 RIP=000000008011c8fc RFL=00200002 [-------] CPL=0 II=0 A20=1 SMM=0 HLT=0 but has this really weird IP. Shouldn't SYSENTER be completely handled by VMX? ---------------------------------------------------------------------- Comment By: Alexander Graf (awwy) Date: 2008-07-25 07:53 Message: Logged In: YES user_id=376328 Originator: NO The address we're seeing the fault in actually belongs to SYSCALL. When I remove the SYSCALL capability from the reportedly supported bits and run the VM with -no-kvm, I receive #UD exceptions. Apparently something calls SYSCALL even if it's not supported. ---------------------------------------------------------------------- Comment By: Alexander Graf (awwy) Date: 2008-07-24 09:36 Message: Logged In: YES user_id=376328 Originator: NO I bisected it down to commit cc91437d10770328d0b32f200399569a0ad22792, which lies between kvm-60 and kvm-61. I can't really make out any obvious problem that patch may rise though. Nevertheless it seems to be userspace in fault here. ---------------------------------------------------------------------- Comment By: Alexander Graf (awwy) Date: 2008-07-24 01:56 Message: Logged In: YES user_id=376328 Originator: NO I am getting exactly the same error on SLES10 SP2. Running a 32-bit binary in an x86_64 SLES10SP2 guest generates a #DF on a RIP, that looks like a 32-bit mangled kernel space address (0000000080228ca0 vs. ffffffff80228ca0). Apparently something truncates it - I'll try to bisect. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2019608&group_id=180599 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
