>>> On 19.11.15 at 10:43, wrote:
> --- a/xen/arch/x86/hvm/hvm.c
> +++ b/xen/arch/x86/hvm/hvm.c
> @@ -2452,6 +2452,13 @@ int hvm_vcpu_initialise(struct vcpu *v)
> if ( rc != 0 )
> goto fail6;
>
> +if ( is_viridian_domain(d) )
> +{
> +rc =
On Thu, Nov 19, 2015 at 10:30:30AM +, Ian Campbell wrote:
> On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
> > On 18/11/15 15:49, Wei Liu wrote:
> > > Hi Juergen
> > >
> > > Looks like there is something we missed after all.
> > >
> > > On Wed, Nov 18, 2015 at 02:31:57PM +,
This run is configured for baseline tests only.
flight 38308 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38308/
Perfect :-)
All tests in this flight passed
version targeted for testing:
ovmf 386cdfbecbbacb600ffc8e2ffa8c7af1b3855a61
baseline version:
This run is configured for baseline tests only.
flight 38307 qemu-mainline real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38307/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl 21
Hi,
> > Another area of extension is how to expose a framebuffer to QEMU for
> > seamless integration into a SPICE/VNC channel. For this I believe we
> > could use a new region, much like we've done to expose VGA access
> > through a vfio device file descriptor. An area within this new
> >
Cosmetics: most of the variables used in vif-bridge are already quoted.
Add quoting also to the remaining shell variables.
Signed-off-by: Olaf Hering
Cc: Ian Jackson
Cc: Stefano Stabellini
Cc: Ian Campbell
>>> On 19.11.15 at 08:44, wrote:
>
>> -Original Message-
>> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
>> Sent: Wednesday, November 18, 2015 6:11 PM
>> To: Wu, Feng ; Jan Beulich
>> Cc: Tian, Kevin
From: Joe Perches
Perl 5.22 emits a deprecated message when "\C" is used in a regex. Perl
5.24 will disallow it altogether.
Fix it by using [A-Z] instead of \C.
[ Upstream commit ce8155f7a3d59ce868ea16d8891edda4d865e873 ]
Signed-off-by: Olaf Hering
Cc: Ian
flight 64723 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/64723/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-multivcpu 6 xen-boot fail REGR. vs. 64320
Commit-ID: 581b7f158fe0383b492acd1ce3fb4e99d4e57808
Gitweb: http://git.kernel.org/tip/581b7f158fe0383b492acd1ce3fb4e99d4e57808
Author: Andrew Cooper
AuthorDate: Wed, 3 Jun 2015 10:31:14 +0100
Committer: Thomas Gleixner
CommitDate: Thu, 19
On 18/11/15 20:02, Konrad Rzeszutek Wilk wrote:
> On Tue, Nov 17, 2015 at 05:30:59PM +, Andrew Cooper wrote:
>> On 17/11/15 17:04, Jan Beulich wrote:
>> On 03.11.15 at 18:58, wrote:
--- a/xen/common/grant_table.c
+++ b/xen/common/grant_table.c
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Thursday, November 19, 2015 4:44 PM
> To: Wu, Feng
> Cc: Andrew Cooper ; ian.campb...@citrix.com;
> wei.l...@citrix.com; george.dun...@eu.citrix.com;
>
On 18/11/15 19:14, Boris Ostrovsky wrote:
> After commit 8c058b0b9c34 ("x86/irq: Probe for PIC presence before
> allocating descs for legacy IRQs") early_irq_init() will no longer
> preallocate descriptors for legacy interrupts if PIC does not
> exist, which is the case for Xen PV guests.
>
>
The Microsoft Hypervisor Top Level Functional Spec. (section 3.4) defines
two bits in CPUID leaf 0x4004:EAX for the hypervisor to recommend
whether or not to issue a hypercall for local or remote TLB flush.
Whilst it's doubtful whether using a hypercall for local TLB flush would
be any more
In commit a85da715cf ("x86/IO-APIC: adjust setting of destinations") I
made a pretty blatant mistake: get_apic_id() can be used there only
when running APICs in physical mode. For both flat and clustered modes
the change was wrong, causing different kinds of boot problems on
affected systems.
Hi,
Thanks Tianyang for the report and for the patch, and Meng for helping
getting the patch itself on the list and to me, and for commenting.
On Wed, 2015-11-18 at 22:38 -0500, Meng Xu wrote:
> [cc. Dario...]
>
> 2015-11-18 22:24 GMT-05:00 Tianyang Chen :
> > In nested
On 18/11/15 20:02, Konrad Rzeszutek Wilk wrote:
> On Tue, Nov 17, 2015 at 05:30:59PM +, Andrew Cooper wrote:
>> On 17/11/15 17:04, Jan Beulich wrote:
>> On 03.11.15 at 18:58, wrote:
--- a/xen/common/grant_table.c
+++ b/xen/common/grant_table.c
Am 19.11.15 um 11:38 schrieb Andrew Cooper:
On 19/11/15 10:24, Jan Beulich wrote:
On 19.11.15 at 00:17, wrote:
The disassembly of do_IRQ now looks like a plausible function, but the
consistently faulting address has no plausible way of generating a
double fault. I
flight 64733 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/64733/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-pvops 3 host-install(3) broken REGR. vs. 59254
branch xen-unstable
xenbranch xen-unstable
job test-amd64-amd64-xl-pvh-amd
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
On 2015-11-19 12:46, Juan Rossi wrote:
Hi
I am sending this due the change of behaviour in some parts, and
perhaps it needs some code amendments, unsure if the devel list is the
best place, fell free to point me to the right place for this. Let me
know if I should load a bug instead.
I'm
> -Original Message-
> From: xen-devel-boun...@lists.xen.org [mailto:xen-devel-
> boun...@lists.xen.org] On Behalf Of Huaitong Han
> Sent: Monday, November 16, 2015 6:32 PM
> To: jbeul...@suse.com; andrew.coop...@citrix.com; Nakajima, Jun
> ; Dong, Eddie
On 2015年11月19日 20:16, Ian Campbell wrote:
On Thu, 2015-11-19 at 11:55 +, Ian Campbell wrote:
On Thu, 2015-11-19 at 11:48 +, Ian Campbell wrote:
On Thu, 2015-11-19 at 11:33 +, Andrew Cooper wrote:
The majority of those are cases are not appropriate uses of exit().
AFAIIR, the
From: Shuai Ruan
This patch exposes xsaves/xgetbv1/xsavec to hvm guest.
The reserved bits of eax/ebx/ecx/edx must be cleaned up
when call cpuid(0dh) with leaf 1 or 2..63.
According to the spec the following bits must be reserved:
For leaf 1, bits 03-04/08-31 of ecx is
From: Shuai Ruan
Changes in v11:
* Address comments from Jan:
* Using alternative asm on xrstor side.
For xsave side(alternative asm), I will send a seperate patch to do this.
Changes in v10:
* Address comments from Jan:
* Add two new macros to handle alternative asm
This patch enables xsaves for hvm guest, includes:
1.handle xsaves vmcs init and vmexit.
2.add logic to write/read the XSS msr.
Add IA32_XSS_MSR save/rstore support.
Signed-off-by: Shuai Ruan
Reviewed-by: Jan Beulich
---
xen/arch/x86/hvm/hvm.c
This patch uses xsaves/xrstors/xsavec instead of xsaveopt/xrstor
to perform the xsave_area switching so that xen itself
can benefit from them when available.
For xsaves/xrstors/xsavec only use compact format. Add format conversion
support when perform guest os migration. Also, pv guest will not
This new field in libxlDomainObjPrivate is named "config"
and is kept while the domain is active. For now, "config"
will be used in libxlDomainStartCallback to set
network interface names based on domid and
libxl_device_nic devid that is set in the config on domain
create.
Signed-off-by: Joao
. to a more generic name i.e. libxlDomainStartCallback,
since it will now cover another case other than the console.
Signed-off-by: Joao Martins
---
src/libxl/libxl_domain.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Hey,
As discussed yesterday, this patch series implements virDomainInterfaceStats
but based on "ConsoleCallback" as opposed of doing it in libxlDomainStart.
The series is divided as following: Patch 1 adds up domain config to
libxlDomainObjPrivate, Patch 2 renames console callback to something
Introduce support for domainInterfaceStats API call for querying
network interface statistics. Consequently it also enables the
use of `virsh domifstat ` command plus
seeing the interfaces names instead of "-" when doing
`virsh domiflist `.
After succesful guest creation we fill the network
On 19/11/2015 20:02, Atom2 wrote:
> Am 19.11.15 um 02:06 schrieb Andrew Cooper:
>> Thanks! That is what I was looking for.
>>
>> Sadly, it is less useful than I was hoping. The guest is not appearing
>> to do anything interesting which causes the bad state; it is almost a
>> full second between
Xen staging-4.6 crashes when booting on VMware Fusion 8.0.2 (with VT-x/EPT
enabled), with 4 virtual CPUs:
Loading xen-4.6-amd64.gz... ok
Loading vmlinuz-3.14.51-grsec-dock... ok
Loading initrd.img-3.14.51-grsec-dock... ok
(XEN) Xen version 4.6.1-pre (Debian 4.6.1~pre-1skyport1) (
flight 64861 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/64861/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-checkfail never pass
test-armhf-armhf-xl 12
Hi Kevin,
On Thu, 2015-11-19 at 04:06 +, Tian, Kevin wrote:
> > From: Alex Williamson [mailto:alex.william...@redhat.com]
> > Sent: Thursday, November 19, 2015 2:12 AM
> >
> > [cc +qemu-devel, +paolo, +gerd]
> >
> > On Tue, 2015-10-27 at 17:25 +0800, Jike Song wrote:
> > > Hi all,
> > >
> >
Am 19.11.15 um 02:06 schrieb Andrew Cooper:
Thanks! That is what I was looking for.
Sadly, it is less useful than I was hoping. The guest is not appearing
to do anything interesting which causes the bad state; it is almost a
full second between the previous action of note, and the crash.
Can
On Fri, Oct 9, 2015 at 12:34 AM, Jan Beulich wrote:
On 08.10.15 at 21:36, wrote:
>> Signed-off-by: Mark Pryor
>
> Without any description I cannot see what is being fixed here, or why
> there are _different_ comment changes on the
After 32-bit syscall rewrite, and specifically after commit 5f310f739b4c
("x86/entry/32: Re-implement SYSENTER using the new C path"), the stack
frame that is passed to xen_sysexit is no longer a "standard" one (i.e.
it's not pt_regs).
Since we end up calling xen_iret from xen_sysexit we don't
As result of commit "x86/xen: Avoid fast syscall path for Xen PV guests"
irq_enable_sysexit pv op is not called by Xen PV guests anymore and since
they were the only ones who used it we can safely remove it.
Signed-off-by: Boris Ostrovsky
---
On Thu, Nov 19, 2015 at 04:55:44PM -0500, Boris Ostrovsky wrote:
> The first patch fixes Xen PV regression introduced by 32-bit rewrite. Unlike
> the
> earlier version it uses ALTERNATIVE instruction and avoids using xen_sysexit
> (and sysret32 in compat mode) pv ops, as suggested by Andy.
>
>
The first patch fixes Xen PV regression introduced by 32-bit rewrite. Unlike the
earlier version it uses ALTERNATIVE instruction and avoids using xen_sysexit
(and sysret32 in compat mode) pv ops, as suggested by Andy.
As result of this patch irq_enable_sysexit and usergs_sysret32 pv ops are not
On Thu, Nov 19, 2015 at 1:55 PM, Boris Ostrovsky
wrote:
> The first patch fixes Xen PV regression introduced by 32-bit rewrite. Unlike
> the
> earlier version it uses ALTERNATIVE instruction and avoids using xen_sysexit
> (and sysret32 in compat mode) pv ops, as
flight 64750 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/64750/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-rumpuserxen-i386 10 guest-start fail REGR. vs. 64035
On 19/11/2015 09:40, Gerd Hoffmann wrote:
>> > But this code should be
>> > minor to be maintained in libvirt.
> As far I know libvirt only needs to discover those devices. If they
> look like sr/iov devices in sysfs this might work without any changes to
> libvirt.
I don't think they will
> -Original Message-
> From: xen-devel-boun...@lists.xen.org [mailto:xen-devel-
> boun...@lists.xen.org] On Behalf Of Olaf Hering
> Sent: 18 November 2015 09:45
> To: George Dunlap
> Cc: xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] missing block script support for qemu in libxl
>
>
The Microsoft Hypervisor Top Level Functional Spec. (section 3.4) defines
two bits in CPUID leaf 0x4004:EAX for the hypervisor to recommend
whether or not to issue a hypercall for local or remote TLB flush.
Whilst it's doubtful whether using a hypercall for local TLB flush would
be any more
flight 38310 distros-debian-wheezy real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38310/
Perfect :-)
All tests in this flight passed
baseline version:
flight 38270
jobs:
build-amd64 pass
build-armhf
On 19/11/15 11:30, Ian Campbell wrote:
> On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
>> On 18/11/15 15:49, Wei Liu wrote:
>>> Hi Juergen
>>>
>>> Looks like there is something we missed after all.
>>>
>>> On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
flight
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: 19 November 2015 10:18
> To: Paul Durrant
> Cc: Andrew Cooper; Ian Campbell; Wei Liu; Ian Jackson; Stefano Stabellini;
> xen-de...@lists.xenproject.org; Keir (Xen.org)
> Subject: Re: [PATCH v1] x86/hvm/viridian:
On Thu, 2015-11-19 at 11:48 +, Ian Campbell wrote:
> On Thu, 2015-11-19 at 11:33 +, Andrew Cooper wrote:
> >
> > The majority of those are cases are not appropriate uses of exit().
> > AFAIIR, the *only* valid use of exit() in a library is to clean up in a
> > child process from a
On Wed, Nov 18, 2015 at 12:21:56PM -0800, Andy Lutomirski wrote:
> Could we make this a little less subtle:
>
> ALTERNATIVE "testl %eax, %eax; lz .Lsyscall_32_done", "jmp
> .Lsyscasll_32_done", X86_FEATURE_XENPV
>
> Borislav, what do you think?
I don't mind either.
I would've said your version
On 19/11/15 13:19, Wei Liu wrote:
> On Thu, Nov 19, 2015 at 12:47:41PM +0100, Juergen Gross wrote:
>> On 19/11/15 11:30, Ian Campbell wrote:
>>> On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
On 18/11/15 15:49, Wei Liu wrote:
> Hi Juergen
>
> Looks like there is something
On Thu, Nov 19, 2015 at 01:29:01PM +0100, Juergen Gross wrote:
[...]
> > To be precise, the problem is in mini-os, which is used by rump kernel
> > as well. :-(
> >
> >> pvgrub is making assumptions about the page table allocation scheme
> >> of the toolset starting pvgrub. It is calculating the
>>> On 19.11.15 at 13:33, wrote:
> +case HvFlushVirtualAddressSpace:
> +case HvFlushVirtualAddressList:
> +{
> +cpumask_var_t pcpu_mask;
cpumask_t * (or else ... [skip next comment]
> +struct vcpu *v;
> +
> +struct {
Stray blank
create !
title it libxl exit() on ENOMEM incompatible with gc'd languages
thanks
On Thu, 2015-11-19 at 10:55 +, Andrew Cooper wrote:
> On 19/11/15 09:20, Ian Campbell wrote:
> > On Wed, 2015-11-18 at 18:32 +, Martin Osterloh wrote:
> >
> > > I wanted to inquire about the current state of
Processing commands for x...@bugs.xenproject.org:
> create !
Created new bug #51 rooted at `<1447932195.5647.46.ca...@citrix.com>'
Title: `Re: [Xen-devel] Current LibXL Status'
> title it libxl exit() on ENOMEM incompatible with gc'd languages
Set title for #51 to `libxl exit() on ENOMEM
On 19/11/15 11:30, Ian Campbell wrote:
> On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
>> On 18/11/15 15:49, Wei Liu wrote:
>>> Hi Juergen
>>>
>>> Looks like there is something we missed after all.
>>>
>>> On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
flight
On Thu, 2015-11-19 at 11:33 +, Andrew Cooper wrote:
>
> The majority of those are cases are not appropriate uses of exit().
> AFAIIR, the *only* valid use of exit() in a library is to clean up in a
> child process from a library-initiated fork().
... or (in this case) in the
On Wed, Nov 18, 2015 at 03:06:16PM -0500, Boris Ostrovsky wrote:
> The first patch fixes Xen PV regression introduced by 32-bit rewrite. Unlike
> the
> earlier version it uses ALTERNATIVE instruction and avoids using xen_sysexit
> (and sysret32 in compat mode) pv ops, as suggested by Andy. (I
On Thu, 2015-11-19 at 11:55 +, Ian Campbell wrote:
> On Thu, 2015-11-19 at 11:48 +, Ian Campbell wrote:
> > On Thu, 2015-11-19 at 11:33 +, Andrew Cooper wrote:
> > >
> > > The majority of those are cases are not appropriate uses of exit().
> > > AFAIIR, the *only* valid use of
libxl__exec() doesn't ever return. Inform the compiler of this, and
remove all dead code.
No functional change.
Signed-off-by: Andrew Cooper
---
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
This is a follow of commit 90f2e2a307fc6a6258c39cc87b3b2bf9441c0fa7 "use
masking operation instead of test_bit for MCSF bits" where the ARM
changes were missing.
Signed-off-by: Julien Grall
---
xen/arch/arm/domain.c | 4 ++--
1 file changed, 2 insertions(+), 2
On 19/11/15 11:23, Ian Campbell wrote:
> create !
> title it libxl exit() on ENOMEM incompatible with gc'd languages
> thanks
Can this be extended to "should not use exit() in general" ?
andrewcoop@andrewcoop:/local/xen.git/xen$ git grep exit\( --
:/tools/libxl/libxl*
On Thu, Nov 19, 2015 at 12:47:41PM +0100, Juergen Gross wrote:
> On 19/11/15 11:30, Ian Campbell wrote:
> > On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
> >> On 18/11/15 15:49, Wei Liu wrote:
> >>> Hi Juergen
> >>>
> >>> Looks like there is something we missed after all.
> >>>
> >>> On
>>> On 19.11.15 at 00:17, wrote:
> The disassembly of do_IRQ now looks like a plausible function, but the
> consistently faulting address has no plausible way of generating a
> double fault. I suspect therefore that something has caused memory
> corruption in Xen .text
On 18/11/15 15:49, Wei Liu wrote:
> Hi Juergen
>
> Looks like there is something we missed after all.
>
> On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
>> flight 64494 xen-unstable real [real]
>> http://logs.test-lab.xenproject.org/osstest/logs/64494/
>>
>> Regressions
On Thu, Nov 19, 2015 at 9:20 AM, Ian Campbell wrote:
> On Wed, 2015-11-18 at 18:32 +, Martin Osterloh wrote:
>
>> I wanted to inquire about the current state of LibXL and in particular
>> if there are any issues with using it in long-running processes.
>
> It is
On 19/11/15 10:24, Jan Beulich wrote:
On 19.11.15 at 00:17, wrote:
>> The disassembly of do_IRQ now looks like a plausible function, but the
>> consistently faulting address has no plausible way of generating a
>> double fault. I suspect therefore that something
On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
> On 18/11/15 15:49, Wei Liu wrote:
> > Hi Juergen
> >
> > Looks like there is something we missed after all.
> >
> > On Wed, Nov 18, 2015 at 02:31:57PM +, osstest service owner wrote:
> > > flight 64494 xen-unstable real [real]
> > >
On 19/11/15 09:20, Ian Campbell wrote:
> On Wed, 2015-11-18 at 18:32 +, Martin Osterloh wrote:
>
>> I wanted to inquire about the current state of LibXL and in particular
>> if there are any issues with using it in long-running processes.
> It is currently being used by libvirtd which I think
On Thu, Nov 19, 2015 at 09:55:00AM -0500, Neil Sikka wrote:
> Is there any documentation about planned interfaces and API contracts for
> people building around the virtio/9pfs layers? For example, while this is
I assume that you're interested in getting 9pfs to work but don't care
much about how
On Mon, Nov 16, 2015 at 08:02:35PM -0700, Linda wrote:
> Hi Wei,
>
> On 11/16/2015 10:35 AM, Wei Liu wrote:
> >On Mon, Nov 16, 2015 at 10:22:41AM -0700, Linda wrote:
> ...
> >>
> >>The bug is a timing issue: During virtio's probe step, on the front end, it
> >>initialized the mount path. Since
On Thu, 2015-11-19 at 10:50 +, Wei Liu wrote:
> On Thu, Nov 19, 2015 at 10:30:30AM +, Ian Campbell wrote:
> > On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
> > > On 18/11/15 15:49, Wei Liu wrote:
> > > > Hi Juergen
> > > >
> > > > Looks like there is something we missed after
On Thu, Nov 19, 2015 at 10:55:13AM +, Ian Campbell wrote:
> On Thu, 2015-11-19 at 10:50 +, Wei Liu wrote:
> > On Thu, Nov 19, 2015 at 10:30:30AM +, Ian Campbell wrote:
> > > On Thu, 2015-11-19 at 11:24 +0100, Juergen Gross wrote:
> > > > On 18/11/15 15:49, Wei Liu wrote:
> > > > > Hi
On 11/19/2015 11:52 PM, Alex Williamson wrote:
On Thu, 2015-11-19 at 15:32 +, Stefano Stabellini wrote:
On Thu, 19 Nov 2015, Jike Song wrote:
Hi Alex, thanks for the discussion.
In addition to Kevin's replies, I have a high-level question: can VFIO
be used by QEMU for both KVM and Xen?
flight 64765 xen-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/64765/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-migrupgrade 21 guest-migrate/src_host/dst_host fail like 64434
flight 64755 xen-4.6-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/64755/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i386-prev 5 xen-buildfail in 64352 REGR. vs. 63449
build-amd64-prev
On 11/19/2015 07:09 PM, Paolo Bonzini wrote:
On 19/11/2015 09:40, Gerd Hoffmann wrote:
But this code should be
minor to be maintained in libvirt.
As far I know libvirt only needs to discover those devices. If they
look like sr/iov devices in sysfs this might work without any changes to
flight 64762 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/64762/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-libvirt 5 libvirt-build fail REGR. vs. 63340
Tests which did not
On Fri, 2015-11-20 at 10:58 +0800, Jike Song wrote:
> On 11/19/2015 11:52 PM, Alex Williamson wrote:
> > On Thu, 2015-11-19 at 15:32 +, Stefano Stabellini wrote:
> >> On Thu, 19 Nov 2015, Jike Song wrote:
> >>> Hi Alex, thanks for the discussion.
> >>>
> >>> In addition to Kevin's replies, I
On 11/20/2015 12:22 PM, Alex Williamson wrote:
On Fri, 2015-11-20 at 10:58 +0800, Jike Song wrote:
On 11/19/2015 11:52 PM, Alex Williamson wrote:
On Thu, 2015-11-19 at 15:32 +, Stefano Stabellini wrote:
On Thu, 19 Nov 2015, Jike Song wrote:
Hi Alex, thanks for the discussion.
In
> From: Song, Jike
> Sent: Friday, November 20, 2015 1:52 PM
>
> On 11/20/2015 12:22 PM, Alex Williamson wrote:
> > On Fri, 2015-11-20 at 10:58 +0800, Jike Song wrote:
> >> On 11/19/2015 11:52 PM, Alex Williamson wrote:
> >>> On Thu, 2015-11-19 at 15:32 +, Stefano Stabellini wrote:
> On
On Thu, 19 Nov 2015, Paolo Bonzini wrote:
> On 19/11/2015 16:32, Stefano Stabellini wrote:
> > > In addition to Kevin's replies, I have a high-level question: can VFIO
> > > be used by QEMU for both KVM and Xen?
> >
> > No. VFIO cannot be used with Xen today. When running on Xen, the IOMMU
> > is
On Wed, 21 Oct 2015, Ian Campbell wrote:
> (Trimming CCs a bit)
>
> On Wed, 2015-10-21 at 16:22 +0100, Ian Campbell wrote:
> >
> [...]
> > Still to come would be libraries for specific out of tree purposes
> > (device model, kexec), which would be adding new library at the same
> > level as
Hi Wei,
On 11/19/2015 8:03 AM, Wei Liu wrote:
On Thu, Nov 19, 2015 at 09:55:00AM -0500, Neil Sikka wrote:
Is there any documentation about planned interfaces and API contracts for
people building around the virtio/9pfs layers? For example, while this is
I assume that you're interested in
flight 64766 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/64766/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-libvirt-raw 7 host-ping-check-xen fail REGR. vs. 64150
>>> On 19.11.15 at 20:51, wrote:
> In terms of non-standard options passed to gcc I have tried to make sense of
> what flags are actually being used during the build process. I am not
> absolutely sure, but I think the options passed to gcc are as follows:
>
> I do have
> From: Gerd Hoffmann [mailto:kra...@redhat.com]
> Sent: Thursday, November 19, 2015 4:41 PM
>
> Hi,
>
> > > Another area of extension is how to expose a framebuffer to QEMU for
> > > seamless integration into a SPICE/VNC channel. For this I believe we
> > > could use a new region, much like
> From: Alex Williamson [mailto:alex.william...@redhat.com]
> Sent: Friday, November 20, 2015 4:03 AM
>
> > >
> > > The proposal is therefore that GPU vendors can expose vGPUs to
> > > userspace, and thus to QEMU, using the VFIO API. For instance, vfio
> > > supports modular bus drivers and
On Thu, 19 Nov 2015, Jike Song wrote:
> Hi Alex, thanks for the discussion.
>
> In addition to Kevin's replies, I have a high-level question: can VFIO
> be used by QEMU for both KVM and Xen?
No. VFIO cannot be used with Xen today. When running on Xen, the IOMMU
is owned by Xen.
>>> On 19.11.15 at 14:19, wrote:
> The Microsoft Hypervisor Top Level Functional Spec. (section 3.4) defines
> two bits in CPUID leaf 0x4004:EAX for the hypervisor to recommend
> whether or not to issue a hypercall for local or remote TLB flush.
>
> Whilst it's
On Thu, Nov 19, 2015 at 11:23 AM, Ian Campbell wrote:
> create !
> title it libxl exit() on ENOMEM incompatible with gc'd languages
> thanks
Actually, can I suggest that someone send a new thread with an
appropriate title, so that people who aren't directly following the
George,
could I please get an ack or otherwise on
http://lists.xenproject.org/archives/html/xen-devel/2015-11/msg00764.html
http://lists.xenproject.org/archives/html/xen-devel/2015-11/msg00765.html
? While the latter has been reviewed by Andrew, it would feel wrong
to commit it without your ack,
On 19/11/2015 16:32, Stefano Stabellini wrote:
> > In addition to Kevin's replies, I have a high-level question: can VFIO
> > be used by QEMU for both KVM and Xen?
>
> No. VFIO cannot be used with Xen today. When running on Xen, the IOMMU
> is owned by Xen.
I don't think QEMU command line
On Thu, 2015-11-19 at 15:32 +, Stefano Stabellini wrote:
> On Thu, 19 Nov 2015, Jike Song wrote:
> > Hi Alex, thanks for the discussion.
> >
> > In addition to Kevin's replies, I have a high-level question: can VFIO
> > be used by QEMU for both KVM and Xen?
>
> No. VFIO cannot be used with
Today mini-os is making assumptions how the page tables it is started
with are being allocated. Especially it is using the number of page
table frames to calculate which is the first unmapped pfn.
Instead of relying on page table number assumptions just look into the
page tables to find the first
On 19/11/15 13:19, Paul Durrant wrote:
> @@ -561,10 +584,81 @@ int viridian_hypercall(struct cpu_user_regs *regs)
> switch ( input.call_code )
> {
> case HvNotifyLongSpinWait:
> +/*
> + * See Microsoft Hypervisor Top Level Spec. section 18.5.1.
> + */
>
Commit 81a76e4b12961a9f54f5021809074196dfe6dbba ("libxc: rework of
domain builder's page table handler") dropped a special case for pvh
resulting in page tables being mapped read-only. This led to a panic
of the domain in early boot.
Correct this error.
Signed-off-by: Juergen Gross
c/s abdf3c5b "libxc: create p2m list outside of kernel mapping if supported"
introduces a use which Coverity objects to; an int used to mask a uint64_t.
The result needs to be signed to allow ~XC_DOM_PAGE_SIZE() to function
correctly, and long long to function properly in 32bit builds.
Is there any documentation about planned interfaces and API contracts for
people building around the virtio/9pfs layers? For example, while this is
still getting debugged/checked in, in order to build DomU support for these
devices, the expected API contracts/interfaces would need to be known.
On
1 - 100 of 117 matches
Mail list logo