qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ilya Maximets <i.maximets@samsung.com>
To: peterx@redhat.com
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel]  Are FreeBSD guest images working?
Date: Thu, 15 Nov 2018 14:06:36 +0300	[thread overview]
Message-ID: <c07f77c0-a746-90c8-1e06-6dd5dc836a57@samsung.com> (raw)
In-Reply-To: CGME20181115110637eucas1p29916ac0e321b6379d44270b87257a0b2@eucas1p2.samsung.com

> Hi, the list,
> 
> I am trying to boot a FreeBSD guest but failed.  It hangs at the
> kernel booting phase:
> 
> /boot/ker]el/kernel text=0x14ed860 data=0x132538+0x4baa68 syms=[0x8+0x159ee8+0x8
> Booting...
> (nothing more)
> 
> It's just as simple as downloading the image and boot so I can't think
> of anything strange within my procedures so far:
> 
> https://wiki.qemu.org/Hosts/BSD#FreeBSD
> 
> I also tried the latest image here:
> 
> https://download.freebsd.org/ftp/releases/VM-IMAGES/11.2-RELEASE/amd64/Latest/FreeBSD-11.2-RELEASE-amd64.qcow2.xz
> 
> but it's having the same problem as 11.0.
> 
> Am downloading an fresh ISO, but before I continue I'm just curious on
> whether anyone is using these images and whether there's quick answers
> to what I have encountered.
> 
> Thanks in advance,
> 
> -- 
> Peter Xu

Hi,
I have one VM with FreeBSD-11.2-RELEASE-amd64.qcow2 image and it works
fine under qemu 2.12.1. But it's controlled by libvirt + virt-manager,
so it has a bit more cmdline arguments than in wiki.

In general, those images has serial console disabled by default.

Creating the following file in VM fs:
[root@freebsd ~]# cat /boot/loader.conf 
boot_multicons="YES"
boot_serial="YES"
comconsole_speed="115200"
console="comconsole,vidconsole"

allows me to successfully boot with:
# qemu-system-x86_64 -machine accel=kvm -m 2048  \
      -cpu host -enable-kvm -nographic -smp 2 \
      -drive if=virtio,file=./FreeBSD-11.2-RELEASE-amd64.qcow2,format=qcow2

Best regards, Ilya Maximets.

       reply	other threads:[~2018-11-15 11:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20181115110637eucas1p29916ac0e321b6379d44270b87257a0b2@eucas1p2.samsung.com>
2018-11-15 11:06 ` Ilya Maximets [this message]
2018-11-16  2:50   ` [Qemu-devel] Are FreeBSD guest images working? Peter Xu
2018-11-15  8:58 Peter Xu
2018-11-15 10:05 ` Philippe Mathieu-Daudé
2018-11-16  2:53   ` Peter Xu
2018-11-16  3:24     ` Warner Losh
2018-11-16  5:01       ` Peter Xu
2018-11-16  9:47         ` Peter Maydell
2018-11-16 12:30           ` Gerd Hoffmann
2018-11-16 14:25             ` Warner Losh
2018-11-16 10:45         ` Andrea Bolognani

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=c07f77c0-a746-90c8-1e06-6dd5dc836a57@samsung.com \
    --to=i.maximets@samsung.com \
    --cc=peterx@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 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).