From: Dario Faggioli <dario.faggioli@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Ian.Jackson@eu.citrix.com
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Paul Durrant <Paul.Durrant@citrix.com>, ajax <ajax@redhat.com>,
"anthony.perard" <anthony.perard@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>,
Roger Pau Monne <roger.paumonne@citrix.com>
Subject: Re: Wondering about cirris and stdvga
Date: Fri, 17 Mar 2017 16:51:03 +0100 [thread overview]
Message-ID: <1489765863.15340.5.camel@citrix.com> (raw)
In-Reply-To: <20170317141947.GA18067@char.us.oracle.com>
[-- Attachment #1.1: Type: text/plain, Size: 1266 bytes --]
On Fri, 2017-03-17 at 10:19 -0400, Konrad Rzeszutek Wilk wrote:
> --- a/tools/libxl/libxl_create.c
> +++ b/tools/libxl/libxl_create.c
> @@ -225,7 +225,7 @@ int libxl__domain_build_info_setdefault(libxl__gc
> *gc,
> if (b_info->device_model_version ==
> LIBXL_DEVICE_MODEL_VERSION_NONE)
> b_info->u.hvm.vga.kind =
> LIBXL_VGA_INTERFACE_TYPE_NONE;
> else
> - b_info->u.hvm.vga.kind =
> LIBXL_VGA_INTERFACE_TYPE_CIRRUS;
> + b_info->u.hvm.vga.kind =
> LIBXL_VGA_INTERFACE_TYPE_STD;
> }
>
For what is worth, I'd agree.
If I remember correct, though, there was the concern of what happens
when migrating a domain from Xen 4.8 --which would have been build with
cirrus by default-- to Xen 4.9 --which, with this, would build the
receiver domain with stdvga... Or is this not an issue / does not
happen?
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-17 15:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 18:04 Wondering about cirris and stdvga Dario Faggioli
2016-11-19 10:56 ` Pasi Kärkkäinen
2016-11-21 8:34 ` Paul Durrant
2016-11-21 17:47 ` Stefano Stabellini
2016-11-21 9:04 ` Dario Faggioli
2016-11-25 18:17 ` Dario Faggioli
2016-11-29 4:55 ` Konrad Rzeszutek Wilk
2017-03-17 14:19 ` Konrad Rzeszutek Wilk
2017-03-17 15:51 ` Dario Faggioli [this message]
2017-03-17 16:08 ` Konrad Rzeszutek Wilk
2017-03-20 14:13 ` Roger Pau Monné
2017-03-20 14:21 ` Paul Durrant
2017-03-20 14:25 ` Roger Pau Monne
2017-04-04 20:18 ` Konrad Rzeszutek Wilk
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=1489765863.15340.5.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Paul.Durrant@citrix.com \
--cc=ajax@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=roger.paumonne@citrix.com \
--cc=sstabellini@kernel.org \
--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 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.