From: "H. Peter Anvin" <hpa@zytor.com>
To: For discussion of Syslinux and tftp-hpa <syslinux@zytor.com>
Cc: 592875@bugs.debian.org, 591934@bugs.debian.org,
qemu-devel@nongnu.org, Vagrant Cascadian <vagrant@freegeek.org>
Subject: [Qemu-devel] Re: [syslinux] Bug#592875: pxelinux: incompatible with qemu with kvm enabled
Date: Tue, 24 Aug 2010 14:41:26 -0700 [thread overview]
Message-ID: <4C743C86.60405@zytor.com> (raw)
In-Reply-To: <20100824191526.GA28783@claws.fglan>
On 08/24/2010 12:15 PM, Vagrant Cascadian wrote:
> it seems versions of pxelinux 4.00 and later hangs qemu (0.12.x, 0.13.x) when
> network booting using etherboot or gPXE and qemu's kvm support is enabled.
>
> pxelinux 3.86 and earlier do not appear to trigger the problem. i also didn't
> experience the problem with qemu-kvm (formerly known as kvm). qemu without kvm
> support enabled also seems to work fine.
>
> for more details, please see:
>
> http://bugs.debian.org/592875
> http://bugs.debian.org/591934
>
Any way you can do a git bisect on this one?
-hpa
prev parent reply other threads:[~2010-08-24 22:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 19:15 [Qemu-devel] Re: Bug#592875: pxelinux: incompatible with qemu with kvm enabled Vagrant Cascadian
2010-08-24 21:41 ` H. Peter Anvin [this message]
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=4C743C86.60405@zytor.com \
--to=hpa@zytor.com \
--cc=591934@bugs.debian.org \
--cc=592875@bugs.debian.org \
--cc=qemu-devel@nongnu.org \
--cc=syslinux@zytor.com \
--cc=vagrant@freegeek.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).