From: "Richard W.M. Jones" <rjones@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: marc.mari.barcelo@gmail.com, ehabkost@redhat.com, mst@redhat.com,
qemu-devel@nongnu.org, kraxel@redhat.com, pbonzini@redhat.com,
rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v4.1] Add optionrom compatible with fw_cfg DMA version
Date: Mon, 4 Apr 2016 16:21:12 +0100 [thread overview]
Message-ID: <20160404152112.GT32728@redhat.com> (raw)
In-Reply-To: <20160404150204.GB13632@stefanha-x1.localdomain>
On Mon, Apr 04, 2016 at 04:02:04PM +0100, Stefan Hajnoczi wrote:
> (1) initrd loading is broken, kernel complains it finds only gibberish:
>
> [ 0.934582] Unpacking initramfs...
> [ 1.166983] Initramfs unpacking failed: junk in compressed archive
> [ 1.168458] Freeing initrd memory: 32812k freed
That's strange. I certainly never saw anything like this. I wonder
if it's because your initrd is particularly large?
> (2) going back to non-dma boot via -M pc-$old doesn't work, appearently
> fw_cfg dma is enabled even for old machine types.
IIRC there was a thread about how we accidentally added DMA to old
machine types. Does this matter?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
virt-df lists disk usage of guests without needing to install any
software inside the virtual machine. Supports Linux and Windows.
http://people.redhat.com/~rjones/virt-df/
next prev parent reply other threads:[~2016-04-04 15:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 12:43 [Qemu-devel] [PATCH v4.1] Add optionrom compatible with fw_cfg DMA version Richard W.M. Jones
2016-04-01 12:43 ` Richard W.M. Jones
2016-04-04 15:02 ` Stefan Hajnoczi
2016-04-04 15:21 ` Richard W.M. Jones [this message]
2016-04-05 7:29 ` Gerd Hoffmann
2016-04-22 12:23 ` Richard W.M. Jones
2016-04-05 12:51 ` Laszlo Ersek
2016-04-05 13:09 ` Paolo Bonzini
2016-04-07 8:54 ` Marc Marí
2016-04-04 15:12 ` Michael S. Tsirkin
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=20160404152112.GT32728@redhat.com \
--to=rjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kraxel@redhat.com \
--cc=marc.mari.barcelo@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=stefanha@gmail.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 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).