From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] NetBSD doesn't boot under KVM
Date: Tue, 21 Mar 2017 17:24:53 +0100 [thread overview]
Message-ID: <6ef847f2-1072-f6c9-dc15-f9d42cad4f3a@redhat.com> (raw)
In-Reply-To: <CAFEAcA9Z0X_nnYo7xEDY0arO0QF-REXxBNRqXv9vL8DhSikiyw@mail.gmail.com>
On 21/03/2017 17:14, Peter Maydell wrote:
> So if you try to boot NetBSD inside KVM:
>
>
> qemu-img create -f qcow2 disk.qcow2 15G
> wget http://cdn.netbsd.org/pub/NetBSD/NetBSD-7.1/images/NetBSD-7.1-amd64.iso
> qemu-system-x86_64 -m 2048 -enable-kvm \
> -drive if=virtio,file=disk.qcow2,format=qcow2 \
> -netdev user,id=mynet0,hostfwd=tcp::7722-:22 \
> -device e1000,netdev=mynet0 \
> -cdrom NetBSD-7.1-amd64.iso
>
> the guest kernel hangs during boot. This works fine for
> running on real h/w (I assume), and also if you run in
> TCG by dropping -enable-kvm.
>
> It also works if you add -smp 2 -cpu kvm64,-sse2,-cx8
> because the bit that causes problems seems to be
> http://cvsweb.netbsd.org/bsdweb.cgi/src/sys/arch/x86/x86/patch.c?rev=1.2.4.3&content-type=text/x-cvsweb-markup
> where x86_patch() patches various bits of the guest kernel,
> and turning off those cpuid features causes it to skip the
> patching.
>
> Any ideas? Does this sound like a KVM bug, or a guest bug?
It sounds like a weird bug. :) I'm downloading the image.
> (Tested on 4.4.0-31-generic #50-Ubuntu x86-64 host kernel
> and QEMU emulator version 2.5.0 (Debian 1:2.5+dfsg-5ubuntu10.8).
> Yes, I know that's really old...)
>
> thanks
> -- PMM
>
next prev parent reply other threads:[~2017-03-21 16:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 16:14 [Qemu-devel] NetBSD doesn't boot under KVM Peter Maydell
2017-03-21 16:24 ` Paolo Bonzini [this message]
2017-03-21 16:33 ` Peter Maydell
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=6ef847f2-1072-f6c9-dc15-f9d42cad4f3a@redhat.com \
--to=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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 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).