From: "Michael S. Tsirkin" <mst@redhat.com>
To: Bret Ketchum <Bret_Ketchum@dell.com>
Cc: "Qemu-devel@nongnu.org" <Qemu-devel@nongnu.org>,
"kraxel@redhat.com" <kraxel@redhat.com>
Subject: Re: [Qemu-devel] Q35 FreeBSD install status
Date: Tue, 10 Sep 2013 20:29:34 +0300 [thread overview]
Message-ID: <20130910172934.GB3913@redhat.com> (raw)
In-Reply-To: <bb883ee7bf0743388ac3b3c57746e3f2@mspexmb2.Beer.Town>
On Tue, Sep 10, 2013 at 04:16:35PM +0000, Bret Ketchum wrote:
>
>
> I’m looking for some guidance with regards to constructing a VM using a
> later version of FreeBSD. In reference to a qemu-devel posting:
>
> http://lists.nongnu.org/archive/html/qemu-devel/2012-08/msg03329.html
>
> I reran with both 1.6.0.rc3 and 1.6.50 the q35 FreeBSD tests with 9.0, 9.1
> and 10-CURRENT using the following command line:
>
> qemu-kvm \
>
> -hda /home/ehv/images/126802.img -enable-kvm -m 1G -monitor stdio -M q35 \
> -vnc 127.0.0.1:1 -vga cirrus -monitor stdio \
> -cdrom /home/ehv/images/FreeBSD-9.0-RELEASE-amd64-dvd1.iso -boot order=d
>
> Note the command line parameter changes necessary for the current versions of
> qemu. I'm running this on a Fedora 17/3.4.4 host and I've tried specifying
> SeaBios 1.7.3 with -bios and -acpitable command line options. Note also that
> both the ide and ahci tests (pc-i440fx-1.6) worked as advertised on this host.
> My trouble is that the bios does not see either the HDD image nor the cdrom.
>
> My questions are am I correct to expect the aforementioned q35 test
> (specifically the command line) to work? Am I missing something obvious? Is
> there something to look?
>
> Any insight will be appreciated. Thanks.
>
>
>
> Bret
>
>
-cdrom doesn't work with ahci.
there's a new flag that replaces it, I keep forgetting what it is.
Will look it up tomorrow if no one beats me to it.
--
MST
next prev parent reply other threads:[~2013-09-10 17:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 16:16 [Qemu-devel] Q35 FreeBSD install status Bret Ketchum
2013-09-10 17:29 ` Michael S. Tsirkin [this message]
2013-09-10 17:29 ` Bret Ketchum
2013-09-10 17:49 ` Michael S. Tsirkin
2013-09-16 12:28 ` Bret Ketchum
2013-09-16 12:36 ` Michael S. Tsirkin
2013-09-16 13:03 ` Bret Ketchum
2013-09-16 13:07 ` Bret Ketchum
2013-09-16 12:55 ` Gerd Hoffmann
2013-09-16 12:57 ` Bret Ketchum
2013-09-16 15:15 ` Gerd Hoffmann
2013-09-17 15:25 ` Bret Ketchum
2013-09-17 16:44 ` Michael S. Tsirkin
2013-09-18 12:35 ` Bret Ketchum
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=20130910172934.GB3913@redhat.com \
--to=mst@redhat.com \
--cc=Bret_Ketchum@dell.com \
--cc=Qemu-devel@nongnu.org \
--cc=kraxel@redhat.com \
/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.