flight 129310 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/129310/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf c4f4984c69ab1057a5d297b4557fe6cf733f8584
baseline version:
ovmf d3d97b378fe4d0bfbcbdb
Hi,
We are using xen-4.8 stable version. Our board has only USB-3.0.
We trying to achieve PVUSB. Added following in the DomU config file.
Applied the attached patch for USB front-end driver. Using qemu as back-end.
domu.cfg
*usbctrl=['version=2, ports=8', ]*
*usb=['1.6, controller=0, port=1']*
Hi,
>
> > I am trying to pass-through the display to guest domain. to do through
> > driver needs clocks. I have written simple basic clock pv frontend and
> > backend.
> > So I thought these clocks must be initialised before display driver
> > initialisation.
>
> The graphic driver should request
This run is configured for baseline tests only.
flight 75558 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75558/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
build-amd64-libvirt 6 libvirt-buildfail like 75556
test
branch xen-unstable
xenbranch xen-unstable
job test-amd64-amd64-xl-qemut-win7-amd64
testid xen-boot
Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: qemu git://xenbits.xen.org/qemu-xen-tradit
flight 129266 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/129266/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stopfail like 129176
test-armhf-armhf-libvirt 14 sav
flight 129258 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/129258/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-dmrestrict-amd64-dmrestrict 7 xen-boot fail REGR. vs.
125898
test-amd64-
(+ Wei)
On 11/1/18 9:15 AM, Omkar Bolla wrote:
Hi,
May I ask why you need the dependency on the rootfs?
I am trying to pass-through the display to guest domain. to do through
driver needs clocks. I have written simple basic clock pv frontend and
backend.
So I thought these clocks must be i
On 11/1/18 3:37 AM, Peng Fan wrote:
Hi Julien,
Hi Peng,
-Original Message-
From: Julien Grall [mailto:julien.gr...@arm.com]
Sent: 2018年11月1日 2:52
To: Peng Fan ; xen-devel@lists.xenproject.org; Stefano
Stabellini
Subject: Re: Does XEN ARM support RTC in domu?
On 10/31/18 1:57 PM
Hi,
On 11/1/18 8:40 PM, Stefano Stabellini wrote:
On Thu, 1 Nov 2018, Julien Grall wrote:
Hi,
On 11/1/18 8:31 PM, Stefano Stabellini wrote:
On Wed, 31 Oct 2018, Julien Grall wrote:
Hi,
On 10/24/18 2:18 AM, Stefano Stabellini wrote:
From: Stefano Stabellini
Introduce a device tree binding
On Thu, 1 Nov 2018, Julien Grall wrote:
> Hi,
>
> On 11/1/18 8:31 PM, Stefano Stabellini wrote:
> > On Wed, 31 Oct 2018, Julien Grall wrote:
> > > Hi,
> > >
> > > On 10/24/18 2:18 AM, Stefano Stabellini wrote:
> > > > From: Stefano Stabellini
> > > >
> > > > Introduce a device tree binding for
On Wed, 31 Oct 2018, Julien Grall wrote:
> On 10/23/18 3:03 AM, Stefano Stabellini wrote:
> > domain_build.c is too large.
> >
> > Move all the ACPI specific device tree generating functions from
> > domain_build.c to acpi/domain_build.c.
> >
> > Signed-off-by: Stefano Stabellini
> >
> > ---
>
Hi,
On 11/1/18 1:33 PM, Wei Liu wrote:
Commit 359970fd8b ("tools/libxl: Switch Arm guest type to PVH") missed
changing the type field in c_info. This issue didn't surface until
ef72c93df9 which made creating PV guest on Arm unusable.
Signed-off-by: Wei Liu
Tested-by: Julien Grall
FWIW:
Rev
Hi Stefano,
On 11/1/18 8:20 PM, Stefano Stabellini wrote:
On Wed, 31 Oct 2018, Julien Grall wrote:
On 10/31/18 8:35 PM, Milan Boberic wrote:
Hi,
Interesting. Could you confirm the commit you were using (or the point
release)?
Stefano's number were based on commit "fuzz: update README.afl exa
Hi,
On 11/1/18 8:31 PM, Stefano Stabellini wrote:
On Wed, 31 Oct 2018, Julien Grall wrote:
Hi,
On 10/24/18 2:18 AM, Stefano Stabellini wrote:
From: Stefano Stabellini
Introduce a device tree binding for Xen reserved-memory regions. They
are used to share memory across VMs from the VM config
On Wed, 31 Oct 2018, Julien Grall wrote:
> Hi,
>
> On 10/24/18 2:18 AM, Stefano Stabellini wrote:
> > From: Stefano Stabellini
> >
> > Introduce a device tree binding for Xen reserved-memory regions. They
> > are used to share memory across VMs from the VM config files. (See
> > static_shm confi
On Thu, 1 Nov 2018, Ian Jackson wrote:
> Marek Marczykowski-Górecki writes ("[RFC PATCH v2 13/17] xenconsoled: add
> support for up to 3 secondary consoles"):
> > Based on previous few commits, this adds basic support for multiple
> > consoles in xenconsoled. A static number of them - up to 3 (+ o
On Thu, 1 Nov 2018, Ian Jackson wrote:
> (CCing Stefano's new address.)
Thank you, I am still responsive at my kernel.org address too.
> Marek Marczykowski-Górecki writes ("[RFC PATCH v2 06/17] libxl: create vkb
> device only for guests with graphics output"):
> > The forced vkb device is meant
On Wed, 31 Oct 2018, Julien Grall wrote:
> On 10/31/18 8:35 PM, Milan Boberic wrote:
> > Hi,
> >
> > > Interesting. Could you confirm the commit you were using (or the point
> > > release)?
> > > Stefano's number were based on commit "fuzz: update README.afl example"
> > > 55a04feaa1f8ab6ef7d723fb
branch xen-unstable
xenbranch xen-unstable
job test-amd64-amd64-qemuu-nested-intel
testid xen-boot
Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditi
On Thu, Nov 01, 2018 at 05:31:18PM +, Ian Jackson wrote:
> Marek Marczykowski-Górecki writes ("[RFC PATCH v2 13/17] xenconsoled: add
> support for up to 3 secondary consoles"):
> > Based on previous few commits, this adds basic support for multiple
> > consoles in xenconsoled. A static number
Hi Ian,
Thank you for the detailed answer and the willingness to see OSSTest
changed in this respect.
Let me premise that as much as I would like this to be done, I had a
look at my schedule, and, realistically, I can only volunteer very
little time on this. In regards to the two Xilinx boards, i
On Thu, Nov 01, 2018 at 05:48:37PM +, Ian Jackson wrote:
> libxl has code for waiting for xs watches and domain death and so on
> already.
>
> How about this: provide a new variant of libxenvchan_client_init which
> can give a return indication of the form `this server does not appear
> to be
On Thu, Nov 01, 2018 at 05:35:04PM +, Ian Jackson wrote:
> Marek Marczykowski-Górecki writes ("[RFC PATCH v2 15/17] xenconsoled: add
> support for non-pty output"):
> > Handle 'output' xenstore entry, as qemu does. Right now support only few
> > simple options:
> > - "pty" (unchanged)
> > -
On Thu, 1 Nov 2018, Lars Kurth wrote:
> On 01/11/2018, 11:30, "George Dunlap" wrote:
>
> On Wed, Oct 31, 2018 at 6:46 PM Stefano Stabellini
> wrote:
> > > > ---
> > > > + Baremetal boot from Debian stable or stable-backports:
> > > >
> > > > In order to avoid cross-compi
Marek Marczykowski-Górecki writes ("Re: [RFC PATCH v2 00/17] Add support for
qemu-xen runnning in a Linux-based stubdomain."):
> libxenvchan_server_init is asynchronous.
I went to look and I think what you mean is that it is fast. Ie, it
does not need to wait for anything.
> libxenvchan_client_
Marek Marczykowski-Górecki writes ("Re: [RFC PATCH v2 07/17] libxl: add
save/restore support for qemu-xen in stubdomain"):
> On Thu, Nov 01, 2018 at 05:11:21PM +, Ian Jackson wrote:
> > I think this hardcoded fd is troublesome. For example, we don't have
> > anywhere to write down the list of
Marek Marczykowski-Górecki writes ("[RFC PATCH v2 16/17] libxl: access QMP
socket via console for qemu-in-stubdomain"):
> Add support for talking with qemu in stubdomain via QMP connected to a
> console. Since a console doesn't have out of band connect/disconnect
> signaling, use (new) qmp_reset c
Marek Marczykowski-Górecki writes ("[RFC PATCH v2 15/17] xenconsoled: add
support for non-pty output"):
> Handle 'output' xenstore entry, as qemu does. Right now support only few
> simple options:
> - "pty" (unchanged)
> - "file:path" (overwrite file)
> - "pipe:path" (read-write file/pipe)
> -
On Thu, Nov 01, 2018 at 04:57:18PM +, Ian Jackson wrote:
> Marek Marczykowski-Górecki writes ("Re: [RFC PATCH v2 00/17] Add support for
> qemu-xen runnning in a Linux-based stubdomain."):
> > All the xenconsoled stuff is unchanged (and unlikely to change), so it
> > should be safe to review it
Marek Marczykowski-Górecki writes ("[RFC PATCH v2 13/17] xenconsoled: add
support for up to 3 secondary consoles"):
> Based on previous few commits, this adds basic support for multiple
> consoles in xenconsoled. A static number of them - up to 3 (+ one
> primary).
I'm confused. I thought we alr
Marek Marczykowski-Górecki writes ("[RFC PATCH v2 14/17] xenconsoled:
deduplicate error handling"):
> Signed-off-by: Marek Marczykowski-Górecki
Acked-by: Ian Jackson
___
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.o
Marek Marczykowski-Górecki writes ("[RFC PATCH v2 12/17] xenconsoled: make
console_type->use_gnttab less confusing"):
> Before this commit 'use_gnttab' means xenconsoled should first try
> special GNTTAB_RESERVED_CONSOLE entry, and only then fallback to
> ring-ref xenstore entry (being gfn of actu
Marek Marczykowski-Górecki writes ("[RFC PATCH v2 11/17] xenconsoled: add
support for consoles using 'state' xenstore entry"):
> Add support for standard xenbus initialization protocol using 'state'
> xenstore entry. It will be necessary for secondary consoles.
> For consoles supporting it, read '
On Thu, Nov 01, 2018 at 05:11:21PM +, Ian Jackson wrote:
> Marek Marczykowski-Górecki writes ("[RFC PATCH v2 07/17] libxl: add
> save/restore support for qemu-xen in stubdomain"):
> > Rely on a wrapper script in stubdomain to attach FD 3/4 of qemu to
> > relevant consoles.
> ...
> > if (s
Marek Marczykowski-Górecki writes ("[RFC PATCH v2 07/17] libxl: add
save/restore support for qemu-xen in stubdomain"):
> Rely on a wrapper script in stubdomain to attach FD 3/4 of qemu to
> relevant consoles.
...
> if (state->saved_state) {
> -/* This file descriptor is meant to be us
(CCing Stefano's new address.)
Marek Marczykowski-Górecki writes ("[RFC PATCH v2 06/17] libxl: create vkb
device only for guests with graphics output"):
> The forced vkb device is meant for better performance of qemu access
> (at least according to ebbd2561b4cefb299f0f68a88b2788504223de18 "libxl:
Marek Marczykowski-Górecki writes ("Re: [RFC PATCH v2 00/17] Add support for
qemu-xen runnning in a Linux-based stubdomain."):
> All the xenconsoled stuff is unchanged (and unlikely to change), so it
> should be safe to review it. Patches 06 and 07 also shouldn't change.
Sorry, I missed this repl
flight 129249 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/129249/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-libvirt6 libvirt-buildfail REGR. vs. 128963
Tests which did not suc
flight 129286 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/129286/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-armhf-armhf-xl 1
On 01/11/2018 16:50, Jan Beulich wrote:
Juergen Gross 11/01/18 3:23 PM >>>
>> On 01/11/2018 15:18, Jan Beulich wrote:
>> Juergen Gross 11/01/18 1:34 PM >>>
Currently the size of hypercall buffers allocated via
/dev/xen/hypercall is limited to a default of 64 memory pages. For l
New document-cum-checklist, for helping with hardware procurement.
Signed-off-by: Ian Jackson
CC: in...@xenproject.org
CC: George Dunlap
CC: Stefano Stabellini
CC: Julien Grall https://lists.xenproject.org/mailman/listinfo/xen-devel
Andrew Cooper writes ("Re: [OSSTEST PATCH 2/2] mfi-common: Enable livepatch
tests in 4.10 and 4.11 as intended (!)"):
> On 01/11/18 15:53, Ian Jackson wrote:
> > The pattern xen-4.1* matches xen-4.10-testing, xen-4.11-testing, etc.
> > The right approach is to state the excluded branch names expli
On 01/11/18 15:53, Ian Jackson wrote:
> The pattern xen-4.1* matches xen-4.10-testing, xen-4.11-testing, etc.
> The right approach is to state the excluded branch names explicitly
> as is done elsewhere.
>
> Resulting changes (standalone-generate-dump-flight-runvars):
> * new jobs: test-amd64-{amd
branch_wants_livepatch checks the current Xen version. We don't want
to try enabling livepatch on trees that don't have it. And for the
-prev build we care about forward migration etc., not about
livepatching the previous version.
Resulting changes (standalone-generate-dump-flight-runvars):
ru
The pattern xen-4.1* matches xen-4.10-testing, xen-4.11-testing, etc.
The right approach is to state the excluded branch names explicitly
as is done elsewhere.
Resulting changes (standalone-generate-dump-flight-runvars):
* new jobs: test-amd64-{amd64,i386}-livepatch
* runvar set: enable_livepatc
>>> Juergen Gross 11/01/18 3:23 PM >>>
>On 01/11/2018 15:18, Jan Beulich wrote:
> Juergen Gross 11/01/18 1:34 PM >>>
>>> Currently the size of hypercall buffers allocated via
>>> /dev/xen/hypercall is limited to a default of 64 memory pages. For live
>>> migration of guests this might be too
When an new altp2m view is created very early on guest boot, the
display will freeze (although the guest will run normally). This
may also happen on resizing the display. The reason is the way
Xen currently (mis)handles logdirty VGA: it intentionally
misconfigures VGA pages so that they will fault.
This patch is a pre-requisite for the one fixing VGA logdirty
freezes when using altp2m. It only concerns itself with the
ranges allocation / deallocation / initialization part. While
touching the code, I've switched global_logdirty from bool_t
to bool.
Signed-off-by: Razvan Cojocaru
---
CC: Geo
Hello,
This series aims to prevent the display from freezing when
enabling altp2m and switching to a new view (and assorted problems
when resizing the display). Since the last version of the series,
what was previously the second (and last) patch has been split in
two patches, the first of which o
This patch is a pre-requisite for fixing the logdirty VGA issue
(display freezes when switching to a new altp2m view early in a
domain's lifetime), but sent separately for easier review.
The new ept_set_ad_sync() function has been added to update all
active altp2ms' ept.ad. New altp2ms will inherit
On 01/11/18 14:18, Jan Beulich wrote:
Juergen Gross 11/01/18 1:34 PM >>>
>> Currently the size of hypercall buffers allocated via
>> /dev/xen/hypercall is limited to a default of 64 memory pages. For live
>> migration of guests this might be too small as the page dirty bitmask
>> needs to be
On 01/11/2018 15:18, Jan Beulich wrote:
Juergen Gross 11/01/18 1:34 PM >>>
>> Currently the size of hypercall buffers allocated via
>> /dev/xen/hypercall is limited to a default of 64 memory pages. For live
>> migration of guests this might be too small as the page dirty bitmask
>> needs to b
>>> Juergen Gross 11/01/18 1:34 PM >>>
>Currently the size of hypercall buffers allocated via
>/dev/xen/hypercall is limited to a default of 64 memory pages. For live
>migration of guests this might be too small as the page dirty bitmask
>needs to be sized according to the size of the guest. This
flight 129227 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/129227/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qcow2 7 xen-boot fail like 129105
test-amd64-i386-xl-qemut-stubdom-debia
>>> Razvan Cojocaru 11/01/18 3:04 PM >>>
>On 11/1/18 3:58 PM, Jan Beulich wrote:
> Razvan Cojocaru 11/01/18 11:31 AM >>>
>>> On 10/30/18 8:19 AM, Tian, Kevin wrote:
> From: Alexandru Stefan ISAILA [mailto:aisa...@bitdefender.com]
> Sent: Wednesday, October 24, 2018 5:19 PM
>
>
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: 01 November 2018 13:59
> To: rcojoc...@bitdefender.com
> Cc: brian.wo...@amd.com; suravee.suthikulpa...@amd.com;
> aisa...@bitdefender.com; Andrew Cooper ; Paul
> Durrant ; Wei Liu ;
> jun.nakaj...@intel.com; Kevin
On 11/1/18 3:58 PM, Jan Beulich wrote:
Razvan Cojocaru 11/01/18 11:31 AM >>>
>> On 10/30/18 8:19 AM, Tian, Kevin wrote:
From: Alexandru Stefan ISAILA [mailto:aisa...@bitdefender.com]
Sent: Wednesday, October 24, 2018 5:19 PM
The may_defer var was left with the older bool
>>> Razvan Cojocaru 11/01/18 11:31 AM >>>
>On 10/30/18 8:19 AM, Tian, Kevin wrote:
>>> From: Alexandru Stefan ISAILA [mailto:aisa...@bitdefender.com]
>>> Sent: Wednesday, October 24, 2018 5:19 PM
>>>
>>> The may_defer var was left with the older bool_t type. This patch
>>> changes the type to bool
This run is configured for baseline tests only.
flight 75556 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75556/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
build-amd64-libvirt 6 libvirt-buildfail like 75553
test
Commit 359970fd8b ("tools/libxl: Switch Arm guest type to PVH") missed
changing the type field in c_info. This issue didn't surface until
ef72c93df9 which made creating PV guest on Arm unusable.
Signed-off-by: Wei Liu
Tested-by: Julien Grall
---
Cc: Stefano Stabellini
Cc: Julien Grall
v2: avo
flight 129282 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/129282/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 13 migrate-support-checkfail never pass
test-armhf-armhf-xl 1
This run is configured for baseline tests only.
flight 75554 qemu-mainline real [real]
http://osstest.xensource.com/osstest/logs/75554/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvshim broken
Hi George,
On 01/11/2018 11:03, George Dunlap wrote:
On 11/01/2018 10:16 AM, Julien Grall wrote:
Remove the 2 part comment on top of map_grant_ref:
- The first part mention the return value which has been void since
2006!
- The second part mention a local variable 'addr' which do
Stefano Stabellini writes ("Re: [OSSTEST PATCH] README.hardware-acquisition
[and 1 more messages]"):
> I am suggesting to use Debian for the installer and rootfs, but to use a
> different kernel for it.
osstest already knows how to do that in principle, because it knows
how to insert a Debian bac
Currently the size of hypercall buffers allocated via
/dev/xen/hypercall is limited to a default of 64 memory pages. For live
migration of guests this might be too small as the page dirty bitmask
needs to be sized according to the size of the guest. This means
migrating a 8GB sized guest is already
On 01/11/2018, 11:30, "George Dunlap" wrote:
On Wed, Oct 31, 2018 at 6:46 PM Stefano Stabellini
wrote:
> > > ---
> > > + Baremetal boot from Debian stable or stable-backports:
> > >
> > > In order to avoid cross-compilation, Osstest must be able to install a
> > >
On Wed, Oct 31, 2018 at 6:46 PM Stefano Stabellini
wrote:
> > > ---
> > > + Baremetal boot from Debian stable or stable-backports:
> > >
> > > In order to avoid cross-compilation, Osstest must be able to install a
> > > bare-metal system on the host itself in order to build Linux and Xen
> > > tes
Christian Lindig writes ("[PATCH 1/1] tools/ocaml: Re-introduce
Xenctrl.with_intf wrapper"):
> Commit 81946a73dc975a7dafe9017a8e61d1e64fdbedbf removed
> Xenctrl.with_intf based on its undesirable behaviour of opening and
> closing a Xenctrl connection with every invocation. This commit
> re-introd
On 12/10/18 16:27, Sergey Dyasli wrote:
> diff --git a/xen/include/asm-x86/hvm/nestedhvm.h
> b/xen/include/asm-x86/hvm/nestedhvm.h
> index 9d1c2742b5..e09fa9d47d 100644
> --- a/xen/include/asm-x86/hvm/nestedhvm.h
> +++ b/xen/include/asm-x86/hvm/nestedhvm.h
> @@ -92,4 +92,9 @@ static inline void ne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Xen Security Advisory CVE-2018-18883 / XSA-278
version 2
x86: Nested VT-x usable even when disabled
UPDATES IN VERSION 2
CVE assigned.
ISSUE DESCRIPTION
===
On 11/01/2018 10:16 AM, Julien Grall wrote:
> Remove the 2 part comment on top of map_grant_ref:
> - The first part mention the return value which has been void since
> 2006!
> - The second part mention a local variable 'addr' which does not
> exist anymore.
>
> Signed-off-by: Juli
On Thu, Nov 01, 2018 at 10:26:16AM +, Julien Grall wrote:
> Hi Wei,
>
> On 01/11/2018 08:59, Wei Liu wrote:
> > On Wed, Oct 31, 2018 at 08:16:52PM +, Julien Grall wrote:
> > > Hi Wei,
> > >
> > > On 10/31/18 2:25 PM, Wei Liu wrote:
> > > > Commit 359970fd8b ("tools/libxl: Switch Arm guest
flight 7 distros-debian-wheezy real [real]
http://osstest.xensource.com/osstest/logs/7/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-amd64-wheezy-netboot-pygrub 10 debian-di-install fail blocked
in 75500
test-amd64-i386-i386-wheezy
On 10/30/18 8:19 AM, Tian, Kevin wrote:
>> From: Alexandru Stefan ISAILA [mailto:aisa...@bitdefender.com]
>> Sent: Wednesday, October 24, 2018 5:19 PM
>>
>> The may_defer var was left with the older bool_t type. This patch
>> changes the type to bool.
>>
>> Signed-off-by: Alexandru Isaila
>
> Rev
Hi Wei,
On 01/11/2018 08:59, Wei Liu wrote:
On Wed, Oct 31, 2018 at 08:16:52PM +, Julien Grall wrote:
Hi Wei,
On 10/31/18 2:25 PM, Wei Liu wrote:
Commit 359970fd8b ("tools/libxl: Switch Arm guest type to PVH") missed
changing the type field in c_info. This issue didn't surface until
ef72c
ACPI tables are platform and machine type and even architecture
agnostic, and as such we want to provide an internal ACPI API that
only depends on platform agnostic information.
For the x86 architecture, in order to build ACPI tables independently
from the PC or Q35 machine types, we are moving a
On 01/11/2018 10:16, Julien Grall wrote:
> Remove the 2 part comment on top of map_grant_ref:
> - The first part mention the return value which has been void since
> 2006!
> - The second part mention a local variable 'addr' which does not
> exist anymore.
>
> Signed-off-by: Julien G
Remove the 2 part comment on top of map_grant_ref:
- The first part mention the return value which has been void since
2006!
- The second part mention a local variable 'addr' which does not
exist anymore.
Signed-off-by: Julien Grall
---
xen/common/grant_table.c | 7 ---
1 fil
branch xen-unstable
xenbranch xen-unstable
job test-amd64-i386-xl-qemuu-win10-i386
testid xen-boot
Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: qemu git://xenbits.xen.org/qemu-xen-traditi
flight 129273 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/129273/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf d3d97b378fe4d0bfbcbdb296d06bcf1d09165480
baseline version:
ovmf fd950156738ce878c0ba2
On 01/11/2018 02:29, Tian, Kevin wrote:
>> From: Sergey Dyasli [mailto:sergey.dya...@citrix.com]
>> Sent: Tuesday, October 30, 2018 8:36 PM
>>
>> On 30/10/2018 08:06, Tian, Kevin wrote:
From: Sergey Dyasli [mailto:sergey.dya...@citrix.com]
Sent: Friday, October 12, 2018 11:28 PM
On 01/11/2018 00:40, Tian, Kevin wrote:
>> From: Tian, Kevin
>> Sent: Tuesday, October 30, 2018 3:00 PM
>>
>>> From: Jan Beulich [mailto:jbeul...@suse.com]
>>> Sent: Thursday, October 25, 2018 9:58 PM
>>>
>> On 25.10.18 at 15:02, wrote:
On 25/10/18 13:51, Jan Beulich wrote:
On 15
Hi,
> May I ask why you need the dependency on the rootfs?
I am trying to pass-through the display to guest domain. to do through
driver needs clocks. I have written simple basic clock pv frontend and
backend.
So I thought these clocks must be initialised before display driver
initialisation.
Bu
Commit 81946a73dc975a7dafe9017a8e61d1e64fdbedbf removed
Xenctrl.with_intf based on its undesirable behaviour of opening and
closing a Xenctrl connection with every invocation. This commit
re-introduces with_intf but with an updated behaviour: it maintains a
global Xenctrl connection which is opened
On Wed, Oct 31, 2018 at 08:16:52PM +, Julien Grall wrote:
> Hi Wei,
>
> On 10/31/18 2:25 PM, Wei Liu wrote:
> > Commit 359970fd8b ("tools/libxl: Switch Arm guest type to PVH") missed
> > changing the type field in c_info. This issue didn't surface until
> > ef72c93df9 which made creating PV gu
flight 129209 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/129209/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-libvirt-xsm 12 guest-start fail REGR. vs. 128775
test-amd64-amd64-e
On 01/11/2018 02:22, Tian, Kevin wrote:
>> From: Sergey Dyasli [mailto:sergey.dya...@citrix.com]
>> Sent: Tuesday, October 30, 2018 8:41 PM
>>
>> On 30/10/2018 07:41, Tian, Kevin wrote:
From: Sergey Dyasli [mailto:sergey.dya...@citrix.com]
Sent: Friday, October 12, 2018 11:28 PM
This run is configured for baseline tests only.
flight 75553 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75553/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
build-amd64-libvirt 6 libvirt-buildfail like 75550
test
89 matches
Mail list logo
