xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Fabio Fantoni <fabio.fantoni@m2r.biz>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	Stefano Stabellini <stefano.stabellini@citrix.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Don Slutz <dslutz@verizon.com>
Subject: Re: [PATCH] libxl: fix cirrus vga video memory setting with upstream qemu
Date: Fri, 09 May 2014 16:24:50 +0200	[thread overview]
Message-ID: <536CE532.10107@m2r.biz> (raw)
In-Reply-To: <alpine.DEB.2.02.1405091456210.14596@kaball.uk.xensource.com>

Il 09/05/2014 16:03, Stefano Stabellini ha scritto:
> On Fri, 9 May 2014, Ian Campbell wrote:
>> On Fri, 2014-05-09 at 10:01 +0200, Fabio Fantoni wrote:
>>> Il 08/05/2014 17:19, Ian Campbell ha scritto:
>>>> On Thu, 2014-05-08 at 17:03 +0200, Fabio Fantoni wrote:
>>>>> Il 08/05/2014 13:33, Ian Campbell ha scritto:
>>>>>> On Thu, 2014-05-08 at 12:41 +0200, Fabio Fantoni wrote:
>>>>>>
>>>>>>> About qemu version when vgamem_mb property is added is qemu 1.3, I
>>>>>>> already did detailed reply about it in stdvga patch:
>>>>>>> http://lists.xen.org/archives/html/xen-devel/2014-05/msg00259.html
>>>>>>> Or you mean something other?
>>>>>> "in the commit message" is the bit you keep missing.
>>>>> I not found 1399030886.32736.63.camel@kazak.uk.xensource.com with google
>>>>> or thunderbird on mail archive, I not understand what post you refer :(
>>>> mid.gmane.org is a good way to find these things. e.g.:
>>>> http://mid.gmane.org/<1399030886.32736.63.camel@kazak.uk.xensource.com>
>>>>
>>>> Note that the <> which I quoted *are* part of the message id.
>>>>
>>>> The questions there were:
>>>>           Is this change correct for all versions of mainline qemu which
>>>>           people might be using with Xen?
>>> vgamem_mb property was added in qemu 1.3 (same for stdvga patch),
>> How was the video RAM size controller in qemu prior to that? Or was it
>> not possible?
>>
>>>   xen
>>> 4.4 from source use qemu 1.6, and from distributions package is newer
>>> all case I saw, then FWIK there should be no problems. Xen 4.4 if I
>>> remember good change other important qemu value for hvm domUs that
>>> require qemu>=1.6. (1.6.1 because 1.6.0 have critical regression for all
>>> hvm domUs)
>> Stefano/Anthony -- can you confirm that we already depend on qemu >=
>> 1.6.x (or otherwise that it is OK to depend on qemu >= 1.3)?
>  From upstream QEMU POV anything older than 1.7 is "ancient" and
> unmaintained.
>
>  From Xen POV the upstream QEMU version that we released with Xen 4.2 was
> based on QEMU v1.0.1, the one we released with Xen 4.3 was based on
> v1.3.0.
>
> Given that upstream QEMU with Xen 4.2 was a tech preview and that if I
> am not mistaken we don't maintain Xen 4.2 anymore, it should be OK to
> depend on QEMU >= 1.3.

If I remember good the machine/pv qemu parameters part changed by 
Anthony in xen 4.4 require at least qemu 1.6.
In that case xen >=4.4 need already qemu>=1.6.1 (1.6.1 because 1.6.0 
have critical regression for all
hvm domUs)

>
>
>> An ack from you guys on this change would be appreciated.
> I think the change is OK but I wonder if we should write down somewhere,
> maybe in the 4.5 release notes or on the wiki, that we depend on QEMU >=
> 1.3.
>
>
>> It's also been proposed that we backport this to stable branches, how
>> far back would it be safe/acceptable for us to go with that?
>> [...]
> Anything newer than 4.2 should be OK.

  parent reply	other threads:[~2014-05-09 14:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-19 12:16 [PATCH] libxl: fix cirrus vga video memory setting with upstream qemu Fabio Fantoni
2014-04-22 13:11 ` Ian Jackson
2014-04-22 13:21   ` Fabio Fantoni
2014-04-24 10:33     ` Fabio Fantoni
2014-05-02  9:11       ` Fabio Fantoni
2014-05-02 11:41 ` Ian Campbell
2014-05-02 19:44   ` Don Slutz
2014-05-02 20:04     ` Fabio Fantoni
2014-05-07 12:20       ` Fabio Fantoni
2014-05-08 10:10         ` Ian Campbell
2014-05-08 10:41           ` Fabio Fantoni
2014-05-08 11:33             ` Ian Campbell
2014-05-08 15:03               ` Fabio Fantoni
2014-05-08 15:19                 ` Ian Campbell
2014-05-09  8:01                   ` Fabio Fantoni
2014-05-09  9:09                     ` Ian Campbell
2014-05-09 14:03                       ` Stefano Stabellini
2014-05-09 14:08                         ` Ian Campbell
2014-05-09 14:24                         ` Fabio Fantoni [this message]
2014-05-09 14:48                           ` 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=536CE532.10107@m2r.biz \
    --to=fabio.fantoni@m2r.biz \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=dslutz@verizon.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --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).