qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laszlo Ersek <lersek@redhat.com>
To: Fabio Fantoni <fabio.fantoni@m2r.biz>
Cc: xen-devel <xen-devel@lists.xensource.com>,
	Ian Campbell <ian.campbell@citrix.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	seabios <seabios@seabios.org>,
	mjt@tls.msk.ru, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	pkg-qemu-devel@lists.alioth.debian.org,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] Test report for xen-unstable and qemu-xen
Date: Tue, 13 Aug 2013 13:09:59 +0200	[thread overview]
Message-ID: <520A1407.1060301@redhat.com> (raw)
In-Reply-To: <520A0B5E.8080405@m2r.biz>

On 08/13/13 12:33, Fabio Fantoni wrote:
> Il 13/08/2013 12:04, Laszlo Ersek ha scritto:
>> CC'ing Gerd and the seabios list:
>>
>> On 08/13/13 11:16, Fabio Fantoni wrote:
>>> Il 12/08/2013 17:04, Fabio Fantoni ha scritto:

>>>> New issue:
>>>> - domU not start with qemu 1.5.1 and more that 2 gb of ram:
>>>>    tested on w7 64 bit domU with 4 gb of ram, with built-in qemu 1.3 it
>>>> works,
>>>>    while with qemu 1.5.1 doesn't (stops at the beginning, spice client
>>>> show only the lines of seabios version and machine UUID;
>>>>    qemu log show nothing more that 2 gb test), while with 2 gb of ram
>>>> works also with qemu 1.5.1
>>>> -------------------------
>>> Added qemu-devel and debian maintainers to cc for this regression about
>>> upstream qemu.
>>> If you need more details and tests tell me and I'll do/post them.
>> As a superficial guess, this could be fixed by the seabios-1.7.3.1
>> release:
>>
>> http://thread.gmane.org/gmane.comp.emulators.qemu/227536
>>
>> http://code.coreboot.org/p/seabios/source/commit/2a9aeabdfb34374ecac25e7a8d21c9e368618cd4/
>>
>>
>> Laszlo
> 
> Thanks for reply, i did fast test adding this patch that you linked:
> http://code.coreboot.org/p/seabios/source/commit/2a9aeabdfb34374ecac25e7a8d21c9e368618cd4/
> 
> Same result, the problem remains, should I test full seabios 1.7.3.1?

No idea, it was just a random shot, sorry... You're probably down to
bisecting qemu :(

Laszlo

  reply	other threads:[~2013-08-13 11:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5208F96D.3010101@m2r.biz>
2013-08-13  9:16 ` [Qemu-devel] Test report for xen-unstable and qemu-xen Fabio Fantoni
2013-08-13 10:04   ` Laszlo Ersek
2013-08-13 10:33     ` Fabio Fantoni
2013-08-13 11:09       ` Laszlo Ersek [this message]
2013-08-13 13:26         ` Fabio Fantoni
2013-08-13 23:58           ` Kevin O'Connor
2013-08-14  9:19             ` Fabio Fantoni
2013-08-14  9:56               ` Laszlo Ersek
2013-08-14 10:54                 ` Fabio Fantoni
2013-08-14 11:16                   ` Laszlo Ersek
2013-08-14 11:21                     ` Michael S. Tsirkin
2013-08-16 13:59                       ` Fabio Fantoni
2013-08-14 12:29                   ` Kevin O'Connor
2013-08-14 12:50                     ` Fabio Fantoni

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=520A1407.1060301@redhat.com \
    --to=lersek@redhat.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=fabio.fantoni@m2r.biz \
    --cc=ian.campbell@citrix.com \
    --cc=kraxel@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=pkg-qemu-devel@lists.alioth.debian.org \
    --cc=qemu-devel@nongnu.org \
    --cc=seabios@seabios.org \
    --cc=xen-devel@lists.xensource.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).