From: Gerd Hoffmann <kraxel@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: marc.mari.barcelo@gmail.com, ehabkost@redhat.com, mst@redhat.com,
Stefan Hajnoczi <stefanha@gmail.com>,
qemu-devel@nongnu.org, pbonzini@redhat.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v4.1] Add optionrom compatible with fw_cfg DMA version
Date: Tue, 05 Apr 2016 09:29:28 +0200 [thread overview]
Message-ID: <1459841368.2037.9.camel@redhat.com> (raw)
In-Reply-To: <20160404152112.GT32728@redhat.com>
On Mo, 2016-04-04 at 16:21 +0100, Richard W.M. Jones wrote:
> 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?
I've simply used /boot/initramfs-$version from the host. It's 33M. Not
exactly small, but given this is a standard RHEL-7 install I also
wouldn't rate this as unusual big.
> > (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?
That one should be fixed meanwhile.
cheers,
Gerd
next prev parent reply other threads:[~2016-04-05 7:29 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
2016-04-05 7:29 ` Gerd Hoffmann [this message]
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=1459841368.2037.9.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=ehabkost@redhat.com \
--cc=marc.mari.barcelo@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
--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 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.