All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Dietmar Maurer <dietmar@proxmox.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] pxe boot problems
Date: Thu, 30 Jan 2014 12:38:28 +0100	[thread overview]
Message-ID: <52EA39B4.4070204@redhat.com> (raw)
In-Reply-To: <24E144B8C0207547AD09C467A8259F755936D961@lisa.maurer-it.com>

On 01/30/14 07:37, Dietmar Maurer wrote:
>> Does it work with TCG? 
> 
> It simply hangs a bit later if I use TCG, without any output on the console.

Strange. How recent qemu happens this with? The relevant emulation code
(under "ljmp Ev" in "target-i386/translate.c") has been changed as
recently as commit 78261634 (not in any release yet).

> But It works perfectly when I switch back to the pxe-XX.rom files.
> 
>> Also, can you try with a NIC model different from the default e1000?
> 
> same behavior with e1000, rtl8139, pcnet

These do match my results.

Please allow me to summarize the rest of the thread:

- New builds of iPXE contain funny jmp instructions.

- They are only present in the qemu tree in the efi-*.rom files,
  the pxe-*.rom builds date back to much earlier.

- When running the funny jmp instructions in a KVM guest, you either
  need "unrestricted_guest" support from the host CPU (check the
  "/sys/module/kvm_intel/parameters/unrestricted_guest" file when
  kvm-intel.ko is inserted), *or* you need to ask KVM to emulate invalid
  guest state, by passing "emulate_invalid_guest_state=1" to
  kvm-intel.ko -- check your module options under /etc/modprobe.d.
  (Note that you should rebuild the initramfs with dracut if you change
  those options.)

- In the latter case (ie. unrestricted_guest==0 &&
  emulate_invalid_guest_state==1), you will still run into an emulation
  problem on a current RHEL-6 host *later* (a different jmp insn in
  the iPXE builds). I filed RHBZ#1059496 for this and posted the
  backport last night. Gleb's upstream patches in question are e35b7b9c
  and ea79849d.

Laszlo

  reply	other threads:[~2014-01-30 11:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 11:49 [Qemu-devel] pxe boot problems Dietmar Maurer
2014-01-29 13:01 ` Laszlo Ersek
2014-01-29 17:34   ` Laszlo Ersek
2014-01-29 17:47     ` Paolo Bonzini
2014-01-29 18:09       ` Laszlo Ersek
2014-01-29 18:13         ` Paolo Bonzini
2014-01-30  0:07           ` Laszlo Ersek
2014-01-30  6:37   ` Dietmar Maurer
2014-01-30 11:38     ` Laszlo Ersek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-01-29  7:59 Dietmar Maurer

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=52EA39B4.4070204@redhat.com \
    --to=lersek@redhat.com \
    --cc=dietmar@proxmox.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.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.