Re: [Xen-devel] q35 support in Xen

On Sun, 17 Sep 2017 10:49:12 +0800 Yi Sun <yi.y@linux.intel.com> wrote: > On 17-09-15 23:12:58, Alexey G wrote: > > On Thu, 14 Sep 2017 16:39:32 +0800 > > Yi Sun <yi.y@linux.intel.com> wrote: > > > > > Hi, Alexey, > > > > > &

Re: [Xen-devel] q35 support in Xen

Hi, On Thu, 14 Sep 2017 16:39:32 +0800 Yi Sun <yi.y@linux.intel.com> wrote: > Hi, Alexey, > > Have you submitted the patches? If yes, could you please share the link? Sorry, had a lot of work recently -- so far I've managed to submit only the bugfix for mentioned xen

Re: [Xen-devel] "MMIO emulation failed" from booting OVMF on Xen v4.9.0

On Thu, 17 Aug 2017 11:56:06 +0100 Andrew Cooper wrote: > On 17/08/17 09:49, Jan Beulich wrote: > On 16.08.17 at 20:47, wrote: > >> Hey, > >> > >> As per Andrew [Cooper]'s suggestion, writing here instead of #xen on > >> Freenode. > >> > >> I'm

Re: [Xen-devel] Xen on Intel Atom E3815: crash, no output

Hi Stefano, On Mon, 31 Jul 2017 16:39:37 -0700 (PDT) Stefano Stabellini wrote: > I noticed that Xen does not boot on Intel Atom E3815. The system is a > Dell Edge Gateway 3003: > >

Re: [Xen-devel] [Bug] Intel RMRR support with upstream Qemu

On Tue, 25 Jul 2017 15:13:17 +0100 Igor Druzhinin wrote: > >> The algorithm implemented in hvmloader for that is not complicated and > >> can be moved to libxl easily. What we can do is to provision a hole big > >> enough to include all the initially assigned PCI

Re: [Xen-devel] [Bug] Intel RMRR support with upstream Qemu

On Mon, 24 Jul 2017 21:39:08 +0100 Igor Druzhinin wrote: > > But, the problem is that overall MMIO hole(s) requirements are not known > > exactly at the time the HVM domain being created. Some PCI devices will > > be emulated, some will be merely passed through and yet

Re: [Xen-devel] [Bug] Intel RMRR support with upstream Qemu

On Mon, 24 Jul 2017 18:01:39 +0100 Andrew Cooper <andrew.coop...@citrix.com> wrote: > On 24/07/17 17:42, Alexey G wrote: > > Hi, > > > > On Mon, 24 Jul 2017 10:53:16 +0100 > > Igor Druzhinin <igor.druzhi...@citrix.com> wrote: > >>> [Zhang, Xion

Re: [Xen-devel] [Bug] Intel RMRR support with upstream Qemu

Hi, On Mon, 24 Jul 2017 10:53:16 +0100 Igor Druzhinin wrote: > > [Zhang, Xiong Y] Thanks for your suggestion. > > Indeed, if I set mmi_hole >= 4G - RMRR_Base, this could fix my issue. > > For this I still have two questions, could you help me ? > > 1) If hvmloader do

Re: [Xen-devel] [Bug] Intel RMRR support with upstream Qemu

Hi, On Mon, 24 Jul 2017 08:07:02 + "Zhang, Xiong Y" wrote: > [Zhang, Xiong Y] Thanks for your suggestion. > Indeed, if I set mmi_hole >= 4G - RMRR_Base, this could fix my issue. > For this I still have two questions, could you help me ? > 1) If hvmloader do low

Re: [Xen-devel] [Bug] Intel RMRR support with upstream Qemu

> On Fri, 21 Jul 2017 10:57:55 + > "Zhang, Xiong Y" wrote: > > > On an intel skylake machine with upstream qemu, if I add > > "rdm=strategy=host, policy=strict" to hvm.cfg, win 8.1 DomU couldn't > > boot up and continues reboot. > > > > Steps to reproduce this

Re: [Xen-devel] [Bug] Intel RMRR support with upstream Qemu

Hi, On Fri, 21 Jul 2017 10:57:55 + "Zhang, Xiong Y" wrote: > On an intel skylake machine with upstream qemu, if I add > "rdm=strategy=host, policy=strict" to hvm.cfg, win 8.1 DomU couldn't boot > up and continues reboot. > > Steps to reproduce this issue: > > 1)

Re: [Xen-devel] [PATCH] xen-mapcache: Fix the bug when overlapping emulated DMA operations may cause inconsistency in guest memory mappings

On Wed, 19 Jul 2017 11:00:26 -0700 (PDT) Stefano Stabellini wrote: > My expectation is that unlocked mappings are much more frequent than > locked mappings. Also, I expect that only very rarely we'll be able to > reuse locked mappings. Over the course of a VM lifetime, it

Re: [Xen-devel] [PATCH] xen-mapcache: Fix the bug when overlapping emulated DMA operations may cause inconsistency in guest memory mappings

Stefano, On Tue, 18 Jul 2017 15:17:25 -0700 (PDT) Stefano Stabellini wrote: > > The patch modifies the behavior in which MapCacheEntry's are added to > > the list, avoiding duplicates. > > I take that the idea is to always go through the whole list to check for >

[Xen-devel] [PATCH] xen-mapcache: Fix the bug when overlapping emulated DMA operations may cause inconsistency in guest memory mappings

ch uses it is still active. The above example must be extended by one more DMA transfer in order to allow unmapping as the first mapping in the list is sort of resident. The patch modifies the behavior in which MapCacheEntry's are added to the list, avoiding duplicates. Signed-off-by: Alexey Gerasi

Re: [Xen-devel] q35 support in Xen

Hi, > I saw Anthony's patch, but your extension patch seems still in > development. Do you have plan to upstream it? I'm also interested in > this basically I want full PCI-e passthru capability (Current Xen does > support passthru a PCI-e device but guest can't see configuration offset >

Re: [Xen-devel] q35 support in Xen

Hi, > >> On Mon, Jun 26, 2017 at 01:55:56PM -0400, Jason Dickens wrote: > >>> I would like to inquire about q35 support in Xen? As far as I have been > >>> able to tell, this has not been done? In the Xen version that I've been > >>> working with (4.4), libxl_dm overrides any "-machine"

Re: [Xen-devel] [Qemu-devel] [RFC/BUG] xen-mapcache: buggy invalidate map cache?

On Tue, 11 Apr 2017 15:32:09 -0700 (PDT) Stefano Stabellini wrote: > On Tue, 11 Apr 2017, hrg wrote: > > On Tue, Apr 11, 2017 at 3:50 AM, Stefano Stabellini > > wrote: > > > On Mon, 10 Apr 2017, Stefano Stabellini wrote: > > >> On Mon, 10 Apr

Re: [Xen-devel] [Qemu-devel] [RFC/BUG] xen-mapcache: buggy invalidate map cache?

On Mon, 10 Apr 2017 00:36:02 +0800 hrg wrote: Hi, > On Sun, Apr 9, 2017 at 11:55 PM, hrg wrote: > > On Sun, Apr 9, 2017 at 11:52 PM, hrg wrote: > >> Hi, > >> > >> In xen_map_cache_unlocked(), map to guest memory maybe in

[Xen-devel] null domains | xen4.4

Hi, all! We are once again faced with the null-domains problem. At this moment we have xen node with 49 null-domains and if I create new domain and shutdown it I w'll get a new one null-domain. All blkback and netback kernel process are exists. There is no qemu process running. I can't

Re: [Xen-devel] null domains | xen4.4

+0300, Alexey wrote: Hi, all! We are once again faced with the null-domains problem. At this moment we have xen node with 49 null-domains and if I create new domain and shutdown it I w'll get a new one null-domain. All blkback and netback kernel process are exists. There is no qemu process running

Re: [Xen-devel] null domains | xen4.4

What does xenstore-ls -fp say? # xenstore-ls -fp /tool =(n0) /tool/xenstored =(n0) /local =(n0) /local/domain =(n0) /local/domain/0 =(n0) /local/domain/0/name = Domain-0 (n0) /local/domain/0/domid = 0 (n0) /local/domain/0/libxl =(n0) /local/domain/0/libxl/disable_udev

[Xen-devel] [PATCH] xen-netback: do not report success if xenvif_alloc() fails

-off-by: Alexey Khoroshilov khoroshi...@ispras.ru --- drivers/net/xen-netback/xenbus.c | 15 +-- 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/drivers/net/xen-netback/xenbus.c b/drivers/net/xen-netback/xenbus.c index 4e56a27f9689..fab0d4b42f58 100644 --- a/drivers/net/xen

Re: [Xen-devel] [PATCH] xen-netback: do not report success if xenvif_alloc() fails

On 24.11.2014 13:00, Wei Liu wrote: On Sat, Nov 22, 2014 at 01:56:28AM +0300, Alexey Khoroshilov wrote: If xenvif_alloc() failes, netback_probe() reports success as well as online uevent is emitted. It does not make any sense, but it just Sorry, I don't follow. KOBJ_ONLINE event is not emitted

[Xen-devel] [PATCH] xen-netback: do not report success if backend_create_xenvif() fails

-by: Alexey Khoroshilov khoroshi...@ispras.ru --- drivers/net/xen-netback/xenbus.c | 15 +-- 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/drivers/net/xen-netback/xenbus.c b/drivers/net/xen-netback/xenbus.c index 4e56a27f9689..fab0d4b42f58 100644 --- a/drivers/net/xen-netback