On 2015/5/15 14:35, Jan Beulich wrote:
On 15.05.15 at 08:24, wrote:
On 2015/5/15 14:12, Jan Beulich wrote:
On 15.05.15 at 04:33, wrote:
On 2015/4/20 21:46, Jan Beulich wrote:
On 10.04.15 at 11:22, wrote:
--- a/xen/arch/x86/hvm/hvm.c
+++ b/xen/arch/x86/hvm/hvm.c
@@ -4729,7 +4729,6 @@ stati
On 2015/5/15 14:16, Jan Beulich wrote:
On 15.05.15 at 04:57, wrote:
On 2015/4/20 21:51, Jan Beulich wrote:
On 10.04.15 at 11:22, wrote:
--- a/tools/libxl/libxl_dom.c
+++ b/tools/libxl/libxl_dom.c
@@ -787,6 +787,70 @@ out:
return rc;
}
+static int libxl__domain_construct_memmap(lib
On 2015/5/15 14:56, Jan Beulich wrote:
On 15.05.15 at 08:39, wrote:
On 2015/5/15 14:25, Jan Beulich wrote:
On 15.05.15 at 08:11, wrote:
Even we may separate the
low memory to construct memory_map.map[]...
???
Sorry I just mean that the low memory is not represented with only one
memory_m
>>> On 15.05.15 at 08:50, wrote:
> Hi Jan,
>
>> On 28/04/2015 16:37, Wei Wang wrote
This looks wrong - the mail you seem to reply to is dated May 13th
in my inbox. While I realize that I never got to reply to the v1
series (which may indeed have been around the date quoted above)
pinging a patch
On Thu, 2015-05-14 at 22:45 +0200, Stephan Seitz wrote:
> On Wed, May 13, 2015 at 11:57:55AM -0400, Konrad Rzeszutek Wilk wrote:
> >> > according to the documentation the option ucode=scan should tell XEN to
> >> > look for a microcode update in an uncompressed initrd.
> >> >
> >> > While I don’t u
>>> On 15.05.15 at 09:09, wrote:
> On 2015/5/15 14:16, Jan Beulich wrote:
> On 15.05.15 at 04:57, wrote:
>>> On 2015/4/20 21:51, Jan Beulich wrote:
>>> On 10.04.15 at 11:22, wrote:
> --- a/tools/libxl/libxl_dom.c
> +++ b/tools/libxl/libxl_dom.c
> @@ -787,6 +787,70 @@ out:
>>>
El 15/05/15 a les 8.36, Jan Beulich ha escrit:
On 14.05.15 at 17:27, wrote:
>> El 13/05/15 a les 11.53, Jan Beulich ha escrit:
>> On 11.05.15 at 16:57, wrote:
--- a/xen/common/domain.c
+++ b/xen/common/domain.c
@@ -42,6 +42,7 @@
#include
#include
#inclu
>>> On 15.05.15 at 09:11, wrote:
> On 2015/5/15 14:56, Jan Beulich wrote:
> On 15.05.15 at 08:39, wrote:
>>> On 2015/5/15 14:25, Jan Beulich wrote:
>>> On 15.05.15 at 08:11, wrote:
> Even we may separate the
> low memory to construct memory_map.map[]...
???
>>>
>>> Sorr
On 2015/5/15 14:19, Jan Beulich wrote:
On 15.05.15 at 05:18, wrote:
On 2015/4/20 22:21, Jan Beulich wrote:
On 10.04.15 at 11:22, wrote:
--- a/tools/firmware/hvmloader/pci.c
+++ b/tools/firmware/hvmloader/pci.c
@@ -59,8 +59,8 @@ void pci_setup(void)
uint32_t bar_reg;
uin
>>> On 15.05.15 at 09:34, wrote:
> El 15/05/15 a les 8.36, Jan Beulich ha escrit:
> On 14.05.15 at 17:27, wrote:
>>> El 13/05/15 a les 11.53, Jan Beulich ha escrit:
>>> On 11.05.15 at 16:57, wrote:
> --- a/xen/common/domain.c
> +++ b/xen/common/domain.c
> @@ -42,6 +42,7 @@
>>
>>> On 15.05.15 at 09:34, wrote:
> So I think we may need to adjust pci_mem_start like this,
>
> @@ -301,6 +301,19 @@ void pci_setup(void)
> pci_mem_start <<= 1;
> }
>
> +/* Relocate PCI memory that overlaps reserved space, like RDM. */
> +for ( j = 0; j < memory_map.
On 15/05/2015 15:17, Jan Beulich wrote
> >>> On 15.05.15 at 08:50, wrote:
> > Hi Jan,
> >
> >> On 28/04/2015 16:37, Wei Wang wrote
>
> This looks wrong - the mail you seem to reply to is dated May 13th in my
> inbox. While I realize that I never got to reply to the v1 series (which may
> indeed h
John Snow writes:
> On 05/14/2015 10:07 AM, Michael S. Tsirkin wrote:
>> On Thu, May 14, 2015 at 02:02:04PM +0200, Markus Armbruster wrote:
>>> Correct.
>>>
>>> Here's how I think it should be done:
>>>
>>> * Create a machine option to control the FDC
>>>
>>> This is a machine-specific option.
On 2015/5/15 15:32, Jan Beulich wrote:
On 15.05.15 at 09:09, wrote:
On 2015/5/15 14:16, Jan Beulich wrote:
On 15.05.15 at 04:57, wrote:
On 2015/4/20 21:51, Jan Beulich wrote:
On 10.04.15 at 11:22, wrote:
--- a/tools/libxl/libxl_dom.c
+++ b/tools/libxl/libxl_dom.c
@@ -787,6 +787,70 @@ out:
On 2015/5/15 15:34, Jan Beulich wrote:
On 15.05.15 at 09:11, wrote:
On 2015/5/15 14:56, Jan Beulich wrote:
On 15.05.15 at 08:39, wrote:
On 2015/5/15 14:25, Jan Beulich wrote:
On 15.05.15 at 08:11, wrote:
Even we may separate the
low memory to construct memory_map.map[]...
???
Sorry I
>>> On 15.05.15 at 10:00, wrote:
> On 2015/5/15 15:34, Jan Beulich wrote:
> On 15.05.15 at 09:11, wrote:
>>> On 2015/5/15 14:56, Jan Beulich wrote:
>>> On 15.05.15 at 08:39, wrote:
> On 2015/5/15 14:25, Jan Beulich wrote:
> On 15.05.15 at 08:11, wrote:
>>> Even we may se
On 2015/5/15 15:44, Jan Beulich wrote:
On 15.05.15 at 09:34, wrote:
So I think we may need to adjust pci_mem_start like this,
@@ -301,6 +301,19 @@ void pci_setup(void)
pci_mem_start <<= 1;
}
+/* Relocate PCI memory that overlaps reserved space, like RDM. */
+for
On 15/05/2015 09:50, Markus Armbruster wrote:
> --nodefaults must continue to disable all optional parts of the board.
>
> What exactly is optional is for the board / machine type to define. It
> can't be changed once the machine type is released.
>
> When in doubt, make it optional.
I agree
On 15/05/2015 03:12, Yang Hongyang wrote:
>
>>> @@ -467,6 +477,14 @@ static int send_domain_memory_live(struct
>>> xc_sr_context *ctx)
>>> DECLARE_HYPERCALL_BUFFER_SHADOW(unsigned long, dirty_bitmap,
>>> &ctx->save.dirty_bitmap_hbuf);
>>>
>>> +/*
>>>
>>> On 15.05.15 at 10:16, wrote:
> On 2015/5/15 15:44, Jan Beulich wrote:
> On 15.05.15 at 09:34, wrote:
>>> So I think we may need to adjust pci_mem_start like this,
>>>
>>> @@ -301,6 +301,19 @@ void pci_setup(void)
>>>pci_mem_start <<= 1;
>>>}
>>>
>>> +/* Relocat
On 05/15/2015 04:29 PM, Andrew Cooper wrote:
On 15/05/2015 03:12, Yang Hongyang wrote:
@@ -467,6 +477,14 @@ static int send_domain_memory_live(struct
xc_sr_context *ctx)
DECLARE_HYPERCALL_BUFFER_SHADOW(unsigned long, dirty_bitmap,
&ctx->save.dirt
On Mon, May 11, Boris Ostrovsky wrote:
> +++ b/tools/libxl/xl_cmdimpl.c
> @@ -5420,12 +5420,15 @@ static void output_numainfo(void)
>
> static void output_topologyinfo(void)
> +int valid_devs;
> +valid_devs++;
> +if (valid_devs == 0)
This is broken as well, merged as e7
On Thu, 2015-05-14 at 15:21 -0600, Jim Fehlig wrote:
> > FWIW http://logs.test-lab.xenproject.org/osstest/logs/55443/ seems to
> > have two more instances of this (amd64 and i386)
>
> More cases of qemu not starting. I'm not sure how we can get more
> details about that.
FWIW I dug into this a
On Fri, 2015-05-15 at 07:58 +0200, Olaf Hering wrote:
> On Fri, May 15, Jürgen Groß wrote:
>
> > Multi-LUN devices do exist and they are required to be presented as
> > those to the guest.
>
> Ok, this means we need the bus concept. I will see if the API for
> add/remove can be changed that only
On 2015/5/15 16:12, Jan Beulich wrote:
On 15.05.15 at 10:00, wrote:
On 2015/5/15 15:34, Jan Beulich wrote:
On 15.05.15 at 09:11, wrote:
On 2015/5/15 14:56, Jan Beulich wrote:
On 15.05.15 at 08:39, wrote:
On 2015/5/15 14:25, Jan Beulich wrote:
On 15.05.15 at 08:11, wrote:
Even we may se
On Fri, 2015-05-15 at 00:42 +0100, Andrew Cooper wrote:
> On 15/05/2015 00:34, Don Slutz wrote:
> > This allows use of QEMU's VMware emulated video card
> >
> > Signed-off-by: Don Slutz
>
> Nack.
>
> Qemu-trad is currently has remote code execution vulnerabilities in its
> vmware vga model. CVE
On Thu, 2015-05-14 at 18:14 +0100, Ian Jackson wrote:
> The logs and images (including .../logs, .../results, etc.) are now on
> their own filesystem on the production osstest VM, which I have called
> /home/logs.
>
> Changing this in production config will allow us to tidy up by
> removing the sy
On Thu, 2015-05-14 at 18:42 +0100, Ian Jackson wrote:
> Signed-off-by: Ian Jackson
Acked-by: Ian Campbell
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
On Thu, 2015-05-14 at 18:31 +0100, Ian Jackson wrote:
> osstest service user writes ("[ovmf test] 55883: regressions - FAIL"):
> > flight 55883 ovmf real [real]
> > http://logs.test-lab.xenproject.org/osstest/logs/55883/
> >
> > Regressions :-(
> >
> > Tests which did not succeed and are blocking
flight 56374 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/56374/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-win7-amd64 9 windows-install fail REGR. vs. 55331
Tests which are fai
>>> On 15.05.15 at 10:47, wrote:
> On 2015/5/15 16:12, Jan Beulich wrote:
> On 15.05.15 at 10:00, wrote:
>>> On 2015/5/15 15:34, Jan Beulich wrote:
>>> On 15.05.15 at 09:11, wrote:
> On 2015/5/15 14:56, Jan Beulich wrote:
> On 15.05.15 at 08:39, wrote:
>>> On 2015/5/15 1
On Thu, 2015-05-14 at 18:48 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [OSSTEST PATCH 5/6] ts-xen-build-prep: mkfs a new
> /home/osstest, don't resize2fs"):
> > On Wed, 2015-05-13 at 12:15 +0100, Ian Jackson wrote:
> > > + echo '$mapper $dir $fstype defaults 0 0' >>/etc/fstab
> >
> > T
On Thu, 2015-05-14 at 19:01 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [OSSTEST v6 13/24] distros: support PV guest
> install from Debian netinst media."):
> > On Tue, 2015-05-12 at 16:52 +0100, Ian Jackson wrote:
> > > Wrap damage on my screen. I appreciate that you want to retain the
On Fri, 2015-05-15 at 09:32 +0800, Yang Hongyang wrote:
>
> On 05/14/2015 09:05 PM, Ian Campbell wrote:
> > On Thu, 2015-05-14 at 18:06 +0800, Yang Hongyang wrote:
> >> With Remus, the restore flow should be:
> >> the first full migration stream -> { periodically restore stream }
> >>
> >> Signed-
On 2015/5/15 16:54, Jan Beulich wrote:
On 15.05.15 at 10:47, wrote:
On 2015/5/15 16:12, Jan Beulich wrote:
On 15.05.15 at 10:00, wrote:
On 2015/5/15 15:34, Jan Beulich wrote:
On 15.05.15 at 09:11, wrote:
On 2015/5/15 14:56, Jan Beulich wrote:
On 15.05.15 at 08:39, wrote:
On 2015/5/15 1
On 05/15/2015 05:09 PM, Ian Campbell wrote:
On Fri, 2015-05-15 at 09:32 +0800, Yang Hongyang wrote:
On 05/14/2015 09:05 PM, Ian Campbell wrote:
On Thu, 2015-05-14 at 18:06 +0800, Yang Hongyang wrote:
With Remus, the restore flow should be:
the first full migration stream -> { periodically r
On 2015/5/15 16:31, Jan Beulich wrote:
On 15.05.15 at 10:16, wrote:
On 2015/5/15 15:44, Jan Beulich wrote:
On 15.05.15 at 09:34, wrote:
So I think we may need to adjust pci_mem_start like this,
@@ -301,6 +301,19 @@ void pci_setup(void)
pci_mem_start <<= 1;
}
+/*
On Thu, 2015-05-14 at 18:52 +0100, Stefano Stabellini wrote:
> Run QEMU as non-root. Starting from uid 6000, the chosen uid is
> base+domid. If the uid doesn't exist, try just 6000. This is less
> secure: ideally we don't want different domains having their QEMUs
> running with the same uid. Finall
El 12/05/15 a les 12.58, Bob Liu ha escrit:
> After commit 1b1586eeeb8c ("xenbus_client: Extend interface to
> support multi-page ring"), Linux xenbus driver can support multi-page ring.
>
> Based on this interface, we got some impressive improvements by using
> multi-page
> ring in xen-block dri
On Fri, 2015-05-15 at 17:19 +0800, Yang Hongyang wrote:
>
> On 05/15/2015 05:09 PM, Ian Campbell wrote:
> > On Fri, 2015-05-15 at 09:32 +0800, Yang Hongyang wrote:
> >>
> >> On 05/14/2015 09:05 PM, Ian Campbell wrote:
> >>> On Thu, 2015-05-14 at 18:06 +0800, Yang Hongyang wrote:
> With Remus,
On 15/05/15 09:37, Yang Hongyang wrote:
>
>
> On 05/15/2015 04:29 PM, Andrew Cooper wrote:
>> On 15/05/2015 03:12, Yang Hongyang wrote:
>>>
> @@ -467,6 +477,14 @@ static int send_domain_memory_live(struct
> xc_sr_context *ctx)
>DECLARE_HYPERCALL_BUFFER_SHADOW(unsigned long, dirt
>>> On 15.05.15 at 11:21, wrote:
> On 2015/5/15 16:31, Jan Beulich wrote:
> On 15.05.15 at 10:16, wrote:
>>> On 2015/5/15 15:44, Jan Beulich wrote:
>>> On 15.05.15 at 09:34, wrote:
> So I think we may need to adjust pci_mem_start like this,
>
> @@ -301,6 +301,19 @@ void pci_s
On 05/15/2015 10:47 AM, Ian Campbell wrote:
On Fri, 2015-05-15 at 07:58 +0200, Olaf Hering wrote:
On Fri, May 15, Jürgen Groß wrote:
Multi-LUN devices do exist and they are required to be presented as
those to the guest.
Ok, this means we need the bus concept. I will see if the API for
add/r
On 15/05/15 10:27, Ian Campbell wrote:
> On Fri, 2015-05-15 at 17:19 +0800, Yang Hongyang wrote:
>> On 05/15/2015 05:09 PM, Ian Campbell wrote:
>>> On Fri, 2015-05-15 at 09:32 +0800, Yang Hongyang wrote:
On 05/14/2015 09:05 PM, Ian Campbell wrote:
> On Thu, 2015-05-14 at 18:06 +0800, Yang
On 05/15/2015 05:27 PM, Ian Campbell wrote:
On Fri, 2015-05-15 at 17:19 +0800, Yang Hongyang wrote:
On 05/15/2015 05:09 PM, Ian Campbell wrote:
On Fri, 2015-05-15 at 09:32 +0800, Yang Hongyang wrote:
On 05/14/2015 09:05 PM, Ian Campbell wrote:
On Thu, 2015-05-14 at 18:06 +0800, Yang Hongy
On Thu, 2015-05-14 at 19:09 -0400, Daniel De Graaf wrote:
> On 05/14/2015 07:54 AM, Ian Campbell wrote:
> > On Thu, 2015-05-14 at 12:21 +0100, Julien Grall wrote:
> >> Hi Ian,
> >>
> >> On 14/05/15 11:33, Ian Campbell wrote:
> >>> system_u:system_r:domU_t is defined in the default policy and makes
On 05/15/2015 05:31 PM, Andrew Cooper wrote:
On 15/05/15 09:37, Yang Hongyang wrote:
On 05/15/2015 04:29 PM, Andrew Cooper wrote:
On 15/05/2015 03:12, Yang Hongyang wrote:
@@ -467,6 +477,14 @@ static int send_domain_memory_live(struct
xc_sr_context *ctx)
DECLARE_HYPERCALL_BUFFER_
On Fri, 2015-05-15 at 17:34 +0800, Yang Hongyang wrote:
>
> On 05/15/2015 05:27 PM, Ian Campbell wrote:
> > On Fri, 2015-05-15 at 17:19 +0800, Yang Hongyang wrote:
> >>
> >> On 05/15/2015 05:09 PM, Ian Campbell wrote:
> >>> On Fri, 2015-05-15 at 09:32 +0800, Yang Hongyang wrote:
>
> On 0
On Fri, 2015-05-15 at 11:35 +0200, Juergen Gross wrote:
> On 05/15/2015 10:47 AM, Ian Campbell wrote:
> > On Fri, 2015-05-15 at 07:58 +0200, Olaf Hering wrote:
> >> On Fri, May 15, Jürgen Groß wrote:
> >>
> >>> Multi-LUN devices do exist and they are required to be presented as
> >>> those to the g
On Fri, 2015-05-15 at 10:46 +0100, Ian Campbell wrote:
> I'd like to start with seeing an expanded version of the comment in
> libxl.h which begins:
>
> /*
> * Devices
> * ===
>
> which covers this new style API alongside the existing one and sets out
> the expected pattern of naming (both
On 12/05/15 11:58, Bob Liu wrote:
> After commit 1b1586eeeb8c ("xenbus_client: Extend interface to
> support multi-page ring"), Linux xenbus driver can support multi-page ring.
>
> Based on this interface, we got some impressive improvements by using
> multi-page
> ring in xen-block driver. If us
flight 56377 qemu-upstream-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/56377/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail in 55879
pass in 56377
test-amd6
El 12/05/15 a les 13.01, Bob Liu ha escrit:
> The right place for talk_to_blkback() to query backend features and transport
> parameters is after backend entered XenbusStateInitWait. There is no problem
talk_to_blkback doesn't gather any backend features, it just publishes
the features supported b
With Remus, the restore flow should be:
the first full migration stream -> { periodically restore stream }
Signed-off-by: Yang Hongyang
Signed-off-by: Andrew Cooper
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
---
tools/libxc/xc_sr_common.h | 15 +
tools/libxc/xc_sr_restore.c | 133 +++
This patchset implement the Remus support for Migration v2 but without
memory compressing.
Git tree available at:
https://github.com/macrosheep/xen/tree/Remus-newmig-v6
v5->v6:
- refactor send_domain_memory_live()
- introduce buffer_record()
- remove the records buffer size limit
Yang
Split the send_domain_memory_live() into three helper function:
- send_memory_live() do the actually live send
- suspend_and_send_dirty() suspend the guest and send dirty pages
- send_memory_verify()
The motivation of this is that when we send checkpointed stream, we
will skip the actually l
With Remus, the save flow should be:
live migration->{ periodically save(checkpointed save) }
Signed-off-by: Yang Hongyang
CC: Ian Campbell
CC: Ian Jackson
CC: Wei Liu
CC: Andrew Cooper
---
tools/libxc/xc_sr_save.c | 80
1 file changed, 61 ins
On Fri, 15 May 2015, Paolo Bonzini wrote:
> On 15/05/2015 09:50, Markus Armbruster wrote:
>
> > --nodefaults must continue to disable all optional parts of the board.
> >
> > What exactly is optional is for the board / machine type to define. It
> > can't be changed once the machine type is rele
On Wed, 13 May 2015, Fabio Fantoni wrote:
> Il 12/05/2015 16:44, Stefano Stabellini ha scritto:
> > On Tue, 12 May 2015, Stefano Stabellini wrote:
> > > On Tue, 12 May 2015, Fabio Fantoni wrote:
> > > > Il 12/05/2015 12:26, Fabio Fantoni ha scritto:
> > > > > Il 12/05/2015 11:23, Fabio Fantoni ha s
On 05/15/2015 05:51 PM, David Vrabel wrote:
> On 12/05/15 11:58, Bob Liu wrote:
>> After commit 1b1586eeeb8c ("xenbus_client: Extend interface to
>> support multi-page ring"), Linux xenbus driver can support multi-page ring.
>>
>> Based on this interface, we got some impressive improvements by usi
On 15/05/15 11:39, Bob Liu wrote:
>
> On 05/15/2015 05:51 PM, David Vrabel wrote:
>> On 12/05/15 11:58, Bob Liu wrote:
>>> After commit 1b1586eeeb8c ("xenbus_client: Extend interface to
>>> support multi-page ring"), Linux xenbus driver can support multi-page ring.
>>>
>>> Based on this interface,
On Fri, 15 May 2015, Ian Campbell wrote:
> On Thu, 2015-05-14 at 18:52 +0100, Stefano Stabellini wrote:
> > Run QEMU as non-root. Starting from uid 6000, the chosen uid is
> > base+domid. If the uid doesn't exist, try just 6000. This is less
> > secure: ideally we don't want different domains havin
* Introduce a new config option Timezone
* Replace hardcoded Europe/London everywhere with $c{Timezone}
* The default is UTC
* But in production-config-cambridge set it to Europe/London
The overall effect is:
* No change in Cambridge
* Default timezone changes to UTC but can now be overridden
* Pr
On Thu, May 14, 2015 at 03:21:41PM -0600, Jim Fehlig wrote:
> More hint that libvirtd crashed. Have there been any attempts to
> reproduce this outside of the test rig? Or capture a core dump?
Here are two from the OpenStack CI loop:
http://logs.openstack.xenproject.org/10/181110/5/check/dsvm-te
On Wed, 2015-05-13 at 06:01 +0100, wei.l...@citrix.com wrote:
All, _Please_ take note of this important note:
> (Note, please trim your quotes when replying, and also trim the CC list if
> necessary. You might also consider changing the subject line of your reply to
> "Status of (Was: Xen 4.6 De
On Wed, 2015-05-13 at 15:26 +0100, Julien Grall wrote:
> >>> on that vits;
> >>> * On receipt of an interrupt notification arising from Xen's own use
> >>> of `INT`; (see discussion under Completion)
> >>> * On any interrupt injection arising from a guests use of the `INT`
> >>> command; (XXX
On 05/15/2015 06:01 PM, Roger Pau Monné wrote:
> El 12/05/15 a les 13.01, Bob Liu ha escrit:
>> The right place for talk_to_blkback() to query backend features and transport
>> parameters is after backend entered XenbusStateInitWait. There is no problem
>
> talk_to_blkback doesn't gather any back
flight 56376 qemu-upstream-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/56376/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-libvirt 11 guest-start fail REGR. vs. 53803
test-amd64-i386-fre
El 15/05/15 a les 13.03, Bob Liu ha escrit:
>
> On 05/15/2015 06:01 PM, Roger Pau Monné wrote:
>> El 12/05/15 a les 13.01, Bob Liu ha escrit:
>>> The right place for talk_to_blkback() to query backend features and
>>> transport
>>> parameters is after backend entered XenbusStateInitWait. There is
El 12/05/15 a les 13.01, Bob Liu ha escrit:
> Extend xen/block to support multi-page ring, so that more requests can be
> issued
> by using more than one pages as the request ring between blkfront and backend.
> As a result, the performance can get improved significantly.
On Fri, May 15, 2015 at 4:29 PM, Ian Campbell wrote:
> On Wed, 2015-05-13 at 15:26 +0100, Julien Grall wrote:
>> >>> on that vits;
>> >>> * On receipt of an interrupt notification arising from Xen's own use
>> >>> of `INT`; (see discussion under Completion)
>> >>> * On any interrupt injection
On Wed, 2015-05-13 at 21:57 +0530, Vijay Kilari wrote:
> > * On receipt of an interrupt notification arising from Xen's own use
> > of `INT`; (see discussion under Completion)
>
> If INT notification method is used, then I don't think there is need
> for pITS scheduling on CREADER read.
>
>
On Fri, 2015-05-15 at 16:56 +0530, Vijay Kilari wrote:
> On Fri, May 15, 2015 at 4:29 PM, Ian Campbell wrote:
> > On Wed, 2015-05-13 at 15:26 +0100, Julien Grall wrote:
> >> >>> on that vits;
> >> >>> * On receipt of an interrupt notification arising from Xen's own use
> >> >>> of `INT`; (see
On Fri, 2015-05-15 at 11:46 +0100, Stefano Stabellini wrote:
> On Fri, 15 May 2015, Ian Campbell wrote:
> > On Thu, 2015-05-14 at 18:52 +0100, Stefano Stabellini wrote:
> > > Run QEMU as non-root. Starting from uid 6000, the chosen uid is
> > > base+domid. If the uid doesn't exist, try just 6000. T
On Fri, 2015-05-15 at 11:44 +0100, Ian Jackson wrote:
> * Introduce a new config option Timezone
> * Replace hardcoded Europe/London everywhere with $c{Timezone}
> * The default is UTC
> * But in production-config-cambridge set it to Europe/London
>
> The overall effect is:
> * No change in Cambri
On 05/15/2015 07:14 PM, Roger Pau Monné wrote:
> El 15/05/15 a les 13.03, Bob Liu ha escrit:
>>
>> On 05/15/2015 06:01 PM, Roger Pau Monné wrote:
>>> El 12/05/15 a les 13.01, Bob Liu ha escrit:
The right place for talk_to_blkback() to query backend features and
transport
parameters
NOTES:
This patch is a only a fast draft for testing.
Some tests result:
At xl create cdrom empty or not are both working, xl cd-insert is
working, xl cd-eject seems working but on xl command in linux hvm domU
return qmp error of "Device 'ide-N' is locked", in windows 7 instead
don't show the err
El 15/05/15 a les 13.35, Bob Liu ha escrit:
>
> On 05/15/2015 07:14 PM, Roger Pau Monné wrote:
>> El 15/05/15 a les 13.03, Bob Liu ha escrit:
>>>
>>> On 05/15/2015 06:01 PM, Roger Pau Monné wrote:
El 12/05/15 a les 13.01, Bob Liu ha escrit:
> The right place for talk_to_blkback() to query
On Fri, 2015-05-15 at 11:39 +0100, Anthony PERARD wrote:
> On Thu, May 14, 2015 at 03:21:41PM -0600, Jim Fehlig wrote:
> > More hint that libvirtd crashed. Have there been any attempts to
> > reproduce this outside of the test rig? Or capture a core dump?
>
> Here are two from the OpenStack CI l
Ian Campbell writes ("Re: [OSSTEST PATCH] i18n/l10n: Make Timezone configurable
and change the default"):
> On Fri, 2015-05-15 at 11:44 +0100, Ian Jackson wrote:
> > Signed-off-by: Ian Jackson
>
> Acked-by: Ian Campbell
Thanks.
I've made a new version which also documents the variable in READ
On Tue, 2015-05-12 at 16:02 +0100, Ian Campbell wrote:
> I've written up my thinking as a design doc below (it's pandoc and the
> pdf version is also at
> http://xenbits.xen.org/people/ianc/vits/draftA.pdf FWIW).
Here is a second draft based on the feedback so far. Also at
http://xenbits.xen.org/p
On Fri, 2015-05-15 at 12:56 +0100, Ian Jackson wrote:
> Ian Campbell writes ("Re: [OSSTEST PATCH] i18n/l10n: Make Timezone
> configurable and change the default"):
> > On Fri, 2015-05-15 at 11:44 +0100, Ian Jackson wrote:
> > > Signed-off-by: Ian Jackson
> >
> > Acked-by: Ian Campbell
>
> Than
Try to use "xen-qemudepriv-$domname" first, then "xen-qemudepriv-base" +
domid, finally "xen-qemudepriv-shared" and root if everything else fails.
The uids need to be manually created by the user or, more likely, by the
xen package maintainer.
To actually secure QEMU when running in Dom0, we need
On 15/05/15 12:30, Ian Campbell wrote:
>> Handling of Single vITS and multipl pITS can be made simple.
>>
>> All ITS commands except SYNC & INVALL has device id which will
>> help us to know to which pITS it should be sent.
>>
>> SYNC & INVALL can be dropped by Xen on Guest request
>> and let Xen
On 05/15/2015 07:13 PM, Roger Pau Monné wrote:
> El 12/05/15 a les 13.01, Bob Liu ha escrit:
>> Extend xen/block to support multi-page ring, so that more requests can be
>> issued
>> by using more than one pages as the request ring between blkfront and
>> backend.
>> As a result, the performance
Ping?
On 04/30/2015 12:53 PM, Juergen Gross wrote:
Paravirtualized spinlocks produce some overhead even if the kernel is
running on bare metal. The main reason are the more complex locking
and unlocking functions. Especially unlocking is no longer just one
instruction but so complex that it is n
Ping?
On 05/04/2015 10:23 AM, Juergen Gross wrote:
Support 64 bit pv-domains with more than 512GB of memory.
Tested with 64 bit dom0 on machines with 8GB and 1TB and 32 bit dom0 on a
8GB machine. Conflicts between E820 map and different hypervisor populated
memory areas have been tested via a f
On 15/05/15 11:59, Ian Campbell wrote:
AFAIU the process suggested, Xen will inject small batch as long as the
physical command queue is not full.
>>>
Let's take a simple case, only a single domain is using vITS on the
platform. If it injects a huge number of commands, Xen will
Hi Wei,
Thanks you for the review.
On 15/05/15 03:35, Wei Liu wrote:
> On Thu, May 14, 2015 at 06:01:01PM +0100, Julien Grall wrote:
>> The PV network protocol is using 4KB page granularity. The goal of this
>> patch is to allow a Linux using 64KB page granularity working as a
>> network backend
fail_if() and generate_exception_if() could theoretically bypass the
normal flow reaching put_fpu(), and not invoking it would leave the
fpu_exception_callback pointer in place, allowing for the callback to
be called at an unexpected time. Luckily the two
generate_exception_if()-s that would actual
On Fri, May 15, 2015 at 4:58 PM, Ian Campbell wrote:
> On Wed, 2015-05-13 at 21:57 +0530, Vijay Kilari wrote:
>> > * On receipt of an interrupt notification arising from Xen's own use
>> > of `INT`; (see discussion under Completion)
>>
>> If INT notification method is used, then I don't thin
Expecting the ROM BAR to be written with an all ones value when sizing
the region is wrong - the low bit has another meaning (enable/disable)
and bits 1..10 are reserved. The PCI spec also mandates writing all
ones to just the address portion of the register.
Use suitable constants also for initia
The code introduced to address XSA-126 allows simplification of other
code in xen_pt_initfn(): All we need to do is update "cmd" suitably,
as it'll be written back to the host register near the end of the
function anyway.
Signed-off-by: Jan Beulich
--- a/hw/xen/xen_pt.c
+++ b/hw/xen/xen_pt.c
@@
On Fri, May 15, 2015 at 5:33 PM, Julien Grall wrote:
> On 15/05/15 12:30, Ian Campbell wrote:
>>> Handling of Single vITS and multipl pITS can be made simple.
>>>
>>> All ITS commands except SYNC & INVALL has device id which will
>>> help us to know to which pITS it should be sent.
>>>
>>> SYNC &
On 15/05/15 13:47, Vijay Kilari wrote:
>> Aside ignoring the second bullet it's not possible to drop like that a
>> SYNC/INVALL command sent be the guest. How can you decide when a SYNC is
>> required or not? Why dropping "optional" SYNC would be fine? The spec
>> only says "This command specifies
On Fri, 2015-05-15 at 18:17 +0530, Vijay Kilari wrote:
> On Fri, May 15, 2015 at 5:33 PM, Julien Grall wrote:
> > On 15/05/15 12:30, Ian Campbell wrote:
> >>> Handling of Single vITS and multipl pITS can be made simple.
> >>>
> >>> All ITS commands except SYNC & INVALL has device id which will
> >
On 15/05/15 11:17, Yang Hongyang wrote:
> @@ -519,9 +533,15 @@ static int send_domain_memory_live(struct xc_sr_context
> *ctx)
> goto out;
> }
>
> -rc = update_progress_string(ctx, &progress_str,
> ctx->save.max_iterations);
> -if ( rc )
> -goto out;
> +if ( ct
On 15/05/15 11:17, Yang Hongyang wrote:
> With Remus, the save flow should be:
> live migration->{ periodically save(checkpointed save) }
>
> Signed-off-by: Yang Hongyang
> CC: Ian Campbell
> CC: Ian Jackson
> CC: Wei Liu
> CC: Andrew Cooper
This is even nicer given the previous refactoring.
On Fri, 2015-05-15 at 13:19 +0100, Julien Grall wrote:
> On 15/05/15 11:59, Ian Campbell wrote:
> AFAIU the process suggested, Xen will inject small batch as long as the
> physical command queue is not full.
> >>>
> Let's take a simple case, only a single domain is using vITS on the
On Fri, 2015-05-15 at 18:08 +0530, Vijay Kilari wrote:
> On Fri, May 15, 2015 at 4:58 PM, Ian Campbell wrote:
> > On Wed, 2015-05-13 at 21:57 +0530, Vijay Kilari wrote:
> >> > * On receipt of an interrupt notification arising from Xen's own use
> >> > of `INT`; (see discussion under Completion)
1 - 100 of 173 matches
Mail list logo
