From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: efi Grub2 of Ubuntu 10.10 x64 fails to execute on qemu with -enable-kvm
Date: Thu, 11 Nov 2010 16:44:06 +0100 [thread overview]
Message-ID: <4CDC0F46.7010109@gmail.com> (raw)
In-Reply-To: <AANLkTink3sL6F_f3s=0JONAuH9YY=cbr2ARhUL=7H7BZ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3880 bytes --]
On 11/11/2010 04:33 AM, Adhyas Avasthi wrote:
> I am trying to run Ubuntu 10.10 x64 on qemu with OVMF EFI BIOS.
> Everything is fresh off the tree. While I can boot into the Bootloader
> and the bootloader can boot into OS if I have disabled kvm using
> -no-kvm option when I start the VM.
> The qemu system crashes with the following error if I enable kvm in
> the VM.
KVM like any kind of acceleration is imprecise. Because of it results of
testing under kvm not always reflect the real state of things. For
testing bootloader capabilities speed doesn't matter. When testing
userspace firmware shouldn't matter and if you boot using
coreboot-on-qemu+grub or grub-as-qemu-firmware you can check for
firmware independance (you need to boot in graphics mode).
EFI is only a pain. While it's important to check that GRUB works with
it on real machines and faithful emulators, there is really no point in
using it when you don't need to.
It's better to just use SeaBIOS with qemu if you need to use Ubuntu in VM.
This being said I was able to load Linux amd64 on kvm 0.12.5 using
64-bit tianocore and 1.99~beta0 GRUB on Intel(R) Core(TM) i5 CPU M
540 @ 2.53GHz.
While if someone figures it out and offers a sane workaround (not a
"fix", it's not our bug, but inherent disadvantage of kvm) it can be
accepted, there is no point in spending time on it
>
> !!!! X64 Exception Type - 000000000000000D !!!!
> ExceptionData - 0000000000000000
> RIP - 000000001FFA937A, RFL - 0000000000010206
> RAX - 000000001FF351C0, RCX - 0000000000000000, RDX - 000000001FFBB1B0
> RBX - 000000001FF35400, RSP - 000000001FF97540, RBP - 000000001FFBB1B0
> RSI - 000000001FFBB1F0, RDI - 000000001FF35200
> R8 - 0000000000000000, R9 - 000000001FFBB1EF, R10 - 000000001E5E1728
> R11 - 000000001FF973D8, R12 - 000000001FFB6810, R13 - 0000000000000070
> R14 - 000000001DDBAFFF, R15 - 0000000000000060
> CS - 0028, DS - 0008, ES - 0008, FS - 0008, GS - 0008, SS - 0008
> GDT - 000000001FF1CE98; 003F, IDT -
> 000000001FE88BC0; 0FFF
> LDT - 0000000000000000, TR - 0000000000000000
> CR0 - 0000000080000023, CR2 - 0000000000000000, CR3 - 000000001FF36000
> CR4 - 0000000000000668, CR8 - 0000000000000000
> DR0 - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000
> DR3 - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400
>
> This is a pain, because without the kvm the installation and booting
> is really really slow. I tried to debug it from the EFI BIOS a little
> bit and it seems that the boot loader crashed with this exception
> immediately after it was started.
> Other developers on OVMF and EDK2 development (EFI BIOS) have also
> pointed out that in order to use Ubuntu 10.10 with EFI, you have to
> disable kvm. This seems to be an issue.
>
> If there are any pointers (or any other debug help you want from me)
> in order to help root cause the issue, that would be helpful. Also, I
> can drop into the EFI Shell and start the bootloader efi image
> manually, which results in the same crash. Can I pass some parameters
> to the boot loader image to get some more information about the crash
> or the boot loader progress before the crash?
>
> I have downloaded the Grub2 sources and am trying to look into this
> issue. If someone has been able to reproduce the issue, do let me know.
>
> --
> Adhyas
> ********************************************************************
> Two types have compatible type if their types are the same.
> — ANSI C Standard, 3.1.2.6.
> ********************************************************************
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2010-11-11 15:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 3:33 efi Grub2 of Ubuntu 10.10 x64 fails to execute on qemu with -enable-kvm Adhyas Avasthi
2010-11-11 15:44 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-11-11 18:54 ` Adhyas Avasthi
2010-11-11 22:26 ` Vladimir 'φ-coder/phcoder' Serbinenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CDC0F46.7010109@gmail.com \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.