From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: Jan Beulich <JBeulich@suse.com>
Cc: anthony.perard@citrix.com,
xen-devel <xen-devel@lists.xenproject.org>,
ian.jackson@eu.citrix.com, Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: qemu update?
Date: Wed, 25 Sep 2013 10:16:28 +0200 [thread overview]
Message-ID: <52429BDC.7060204@m2r.biz> (raw)
In-Reply-To: <5242A6B602000078000F6130@nat28.tlf.novell.com>
Il 25/09/2013 09:02, Jan Beulich ha scritto:
>>>> On 23.09.13 at 14:19, Ian Campbell <ian.campbell@citrix.com> wrote:
>> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> Speaking of which - an up-rev of our qemu-upstream tree is likely
> on order then too?
I think it is very important to us to keep qemu updated at latest stable
version (1.6).
I'm keeping tested qemu latest versions and the only critical regression
was fixed with the path below:
http://git.qemu.org/?p=qemu.git;a=commit;h=04d7bad8a4fb23e6d9af9d06ce3ddc28a251d94d
About the other critical problem regarding vga, it was fixed on xen 4.3.
No other regression found here but again I think it is always good
practice to keep updated qemu on xen-unstable and testing it frequently.
>
> Jan
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-09-25 8:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 12:19 [PATCH] tools: update to SeaBIOS 1.7.3.1 Ian Campbell
2013-09-25 7:02 ` qemu update? (was: [PATCH] tools: update to SeaBIOS 1.7.3.1) Jan Beulich
2013-09-25 8:16 ` Fabio Fantoni [this message]
2013-09-25 10:37 ` qemu update? Anthony PERARD
2013-10-16 12:46 ` [PATCH] tools: update to SeaBIOS 1.7.3.1 Ian Campbell
2013-10-16 14:05 ` [PATCH] tools: update to SeaBIOS 1.7.3.1 [and 1 more messages] Ian Jackson
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=52429BDC.7060204@m2r.biz \
--to=fabio.fantoni@m2r.biz \
--cc=JBeulich@suse.com \
--cc=anthony.perard@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xenproject.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).