On Thu, 10 Sep 2015, Wei Liu wrote:
> On Thu, Sep 10, 2015 at 03:19:35PM +0100, George Dunlap wrote:
> > On Wed, Jan 7, 2015 at 9:40 AM, Olaf Hering wrote:
> > > On Tue, Jan 06, Ian Campbell wrote:
> > >
> > >> On Fri, 2014-12-19 at 12:25 +0100, Olaf Hering wrote:
> > >> > The
CCing Lars (the community manager).
El 09/09/15 a les 14.11, Mike Belopuhov ha escrit:
> Hi,
>
> We're in the process of porting Xen PVHVM drivers to OpenBSD
> and have come across missing copyright lines on some of Xen
> interface header files, for instance:
>
>
On Thu, 2015-09-10 at 15:50 +0100, Wei Liu wrote:
> This is because the migration stream does not preserve node information.
>
> Note this is not a regression for migration v2 vs legacy migration
> because neither of them preserve node information.
>
> Signed-off-by: Wei Liu
Robert Ho writes ("[OSSTest Nested v12 03/21] Allow runvars to specify guest
disk and ram size (turning previous values into defaults)"):
> 1. The default disk size for guest is '1M' which is not sufficient
> for nested HVM guest, using larger disk size for nested guest
>
On Thu, Sep 10, 2015 at 05:53:35PM +0100, Ian Campbell wrote:
> On Thu, 2015-09-10 at 17:15 +0100, Wei Liu wrote:
> > On Thu, Sep 10, 2015 at 05:10:57PM +0100, Ian Campbell wrote:
> > > On Thu, 2015-09-10 at 15:50 +0100, Wei Liu wrote:
> > > > This is because the migration stream does not preserve
On Thu, 10 Sep 2015, Mark Rutland wrote:
> On Thu, Sep 10, 2015 at 02:52:25PM +0100, Stefano Stabellini wrote:
> > On Thu, 10 Sep 2015, Mark Rutland wrote:
> > > On Thu, Sep 10, 2015 at 12:37:57PM +0100, Stefano Stabellini wrote:
> > > > On Thu, 10 Sep 2015, Mark Rutland wrote:
> > > > > > > Does
Robert Ho writes ("[OSSTest Nested v12 06/21] Add new function of
'host_install_postboot_complete'"):
> This function is called to add 'osstest-confirm-booted' service
> in target's start up services.
> Previously, this was dircetly done by
> target_cmd_root($ho, "update-rc.d
On Thu, 2015-09-03 at 10:35 -0600, Jim Fehlig wrote:
> I wonder if this has anything to do with migration V2? I noticed a migration
> regression a few days back, but later realized that the sender was 4.5 and
> receiver was 4.6. I planned to see if migration worked through libvirt
> between
>
Robert Ho writes ("[OSSTest Nested v12 01/21] Optimize and re-format previous
code of 'submenu' parsing"):
> * space between ')' and '{'; and after '='
> * omit unnecessary 'define' and '!defined' usage
> * break long '{}' into several lines
These changes are all good.
But}
>
On 10/09/2015 17:26, "Roger Pau Monné" wrote:
>CCing Lars (the community manager).
>
>El 09/09/15 a les 14.11, Mike Belopuhov ha escrit:
>> Hi,
>>
>> We're in the process of porting Xen PVHVM drivers to OpenBSD
>> and have come across missing copyright lines on some of
commit 4b53d0d4ac9c "libxl: don't remove persistent domain on start
failure" cleans up the vm object and sets it to NULL if the vm is not
persistent, however at end job vm (now NULL) is dereferenced via the call to
libxlDomainObjEndJob. Avoid this by skipping "endjob" and going
straight to
> > C) When you could go:
> >
> >DT -> Discover Xen -> Xen-specific stuff -> Xen-specific EFI/ACPI
> > discovery
>
> I take you mean discovering Xen with the usual Xen hypervisor node on
> device tree. I think that C) is a good option actually. I like it. Not
> sure why we didn't think
Robert Ho writes ("[OSSTest Nested v12 04/21] Comment out CDROM entry in HVM
guest VM"):
> Comment out CDROM entry in sources.list to make HTTP URL entry
> available for L1 HVM guest VM.
This commit message should probably mention that the installation iso
is of course not generally
From: Wei Liu
Date: Thu, 10 Sep 2015 11:18:56 +0100
> Wei Liu (2):
> xen-netback: respect user provided max_queues
> xen-netfront: respect user provided max_queues
This looks better, series applied, thanks.
___
Xen-devel
Robert Ho writes ("[OSSTest Nested v12 15/21] Integrate Ian J. code and small
corrections."):
> Signed-off-by: Robert Ho
Thanks for fixing up my code.
But can you please squash these fixes into their corresponding
patches ? You should add your own S-o-b to each of them,
Robert Ho writes ("[OSSTest Nested v12 07/21] Replace 'start
osstest-confirm-booted' code by function"):
> Schedul start osstest-confirm-booted script via call
> `host_install_postboot_complete' fucntion; in order
> to avoid open code.
See my comments on the previous patch. The code
Ian Jackson:
> Robert Ho:
> > Ian Campbell:
> > > We should continue to use fixed IP addresses where we have them.
> >
> > Then I'm not confident to change selecthost(). Would you help give me
> > the patch addressing this?
>
> I will try to come up with something.
This is the kind of thing I
Robert Ho writes ("[OSSTest Nested v12 09/21] Wrapper and use core_dump_setup()
for nested host and normal host to setup coredump sysctl"):
> This patch does these 4 things:
> 1. wrapper coredump setup code from original ts-host-install into
> TestSupport.pm
> 2. replace ts-host-install original
Wei Liu writes ("Re: [Xen-devel] [PATCH 7/7] tools/hotplug: add wrapper to
start xenstored"):
> On Thu, Sep 10, 2015 at 03:19:35PM +0100, George Dunlap wrote:
> > ExecStart=/usr/bin/env $XENSTORED --no-fork $XENSTORED_ARGS
>
> And the difference between these two approaches is /usr/bin/env
>
On Fri, Sep 04, 2015 at 02:09:05PM +0200, Roger Pau Monne wrote:
> This structure contains the physical address of the command line, as well as
> the physical address of the list of loaded modules. The physical address of
> this structure is passed to the guest at boot time in the %ebx register.
>
On Thu, Sep 10, 2015 at 05:10:57PM +0100, Ian Campbell wrote:
> On Thu, 2015-09-10 at 15:50 +0100, Wei Liu wrote:
> > This is because the migration stream does not preserve node information.
> >
> > Note this is not a regression for migration v2 vs legacy migration
> > because neither of them
Robert Ho writes ("[OSSTest Nested v12 02/21] Correct a mistake in
setboot_grup2() of Xen entry parsing pattern"):
> In previous adding of 'submenu' parsing code, a mistake was made.
It would be conventional to mention the exact final commit message as
found in the mainline tree, which seems
On Thu, 10 Sep 2015, Julien Grall wrote:
> With 64KB page granularity support, the frame number will be different.
>
> It will be easier to modify the behavior in a single place rather than
> in each caller.
>
> Signed-off-by: Julien Grall
>
Reviewed-by: Stefano
Hi,
Riku reported me an error on their CI loop while run Xen on the Arndale:
Starting /usr/sbin/xenstored...
Setting domain 0 name, domid and JSON config...
libxl: error: libxl.c:675:libxl_domain_info: getting domain info list: Bad
address
libxl: error: libxl_dom.c:1869:libxl__userdata_path:
From: Tiejun Chen
Currently IGD drivers always need to access PCH by 1f.0. But we
don't want to poke that directly to get ID, and although in real
world different GPU should have different PCH. But actually the
different PCH DIDs likely map to different PCH SKUs. We do the
From: Tiejun Chen
basic gfx passthrough support:
- add a vga type for gfx passthrough
- register/unregister legacy VGA I/O ports and MMIOs for passthrough GFX
Signed-off-by: Tiejun Chen
Signed-off-by: Yang Zhang
Acked-by:
If we have been told that there should already be a bridge, but there
isn't one, we would previously rewrite the networking config just in
case (mainly to make it static). Instead, quit the /e/n/i editing in
this case.
Signed-off-by: Ian Jackson
---
ts-xen-install |
From: Tiejun Chen
Now we retrieve VGA bios like kvm stuff in qemu but we need to
fix Device Identification in case if its not matched with the
real IGD device since Seabios is always trying to compare this
ID to work out VGA BIOS.
Signed-off-by: Tiejun Chen
From: Tiejun Chen
We will try to reuse assign_dev_load_option_rom in xen side, and
especially its a good beginning to unify pci assign codes both on
kvm and xen in the future.
[Fix build for Windows]
Signed-off-by: Tiejun Chen
Signed-off-by:
From: Tiejun Chen
Pass types to configure pc_init1().
Signed-off-by: Tiejun Chen
Signed-off-by: Stefano Stabellini
Acked-by: Michael S. Tsirkin
---
hw/i386/pc_piix.c | 14 --
1
From: Tiejun Chen
Currently we just register this isa bridge when we use IGD
passthrough in Xen side.
Signed-off-by: Tiejun Chen
Acked-by: Stefano Stabellini
Signed-off-by: Stefano Stabellini
Instead, if we need to, simply change the physical interface in the
`iface' line to refer to xenbr0, and add the physical interface as a
`bridge_ports' along with the other bridge settings.
Signed-off-by: Ian Jackson
---
ts-xen-install | 33
From: Tiejun Chen
Just register that pci host bridge specific to passthrough.
Signed-off-by: Tiejun Chen
Acked-by: Stefano Stabellini
Signed-off-by: Stefano Stabellini
---
From: Tiejun Chen
Implement a pci host bridge specific to passthrough. Actually
this just inherits the standard one. And we also just expose
a minimal real host bridge pci configuration subset.
[Replace pread with lseek and read to fix Windows build]
Signed-off-by:
From: "Michael S. Tsirkin"
IGD passthrough wants to supply a different pci and
host devices, inheriting i440fx devices. Make types
configurable.
Signed-off-by: Michael S. Tsirkin
Signed-off-by: Tiejun Chen
Signed-off-by: Stefano
The main effect is that old Xend tests will no longer replace the
bridge network interface. If it was using dhcp then it will keep
using dhcp, rather than being switched to have the dhcp-obtained
address hardwired in a static configuration.
A side effect is that after this, `nodhcp' will do
The following changes since commit 8611280505119e296757a60711a881341603fa5a:
target-microblaze: Use setcond for pcmp* (2015-09-08 08:49:33 +0200)
are available in the git repository at:
git://xenbits.xen.org/people/sstabellini/qemu-dm.git tags/xen-2015-09-10-tag
for you to fetch changes up
From: Konrad Rzeszutek Wilk
We do not want to have two entries to cache the guest configuration
registers: XenPTReg->data and dev.config. Instead we want to use
only the dev.config.
To do without much complications we rip out the ->data field
and replace it with an
From: Tiejun Chen
The OpRegion shouldn't be mapped 1:1 because the address in the host
can't be used in the guest directly.
This patch traps read and write access to the opregion of the Intel
GPU config space (offset 0xfc).
The original patch is from Jean Guyader
From: Konrad Rzeszutek Wilk
It has changed but the comments still refer to the old names.
Reviewed-by: Stefano Stabellini
Signed-off-by: Konrad Rzeszutek Wilk
Signed-off-by: Stefano Stabellini
From: Konrad Rzeszutek Wilk
We seem to only use these functions when de-activating the
MSI - so just log errors.
Reviewed-by: Stefano Stabellini
Signed-off-by: Konrad Rzeszutek Wilk
Signed-off-by: Stefano
From: Konrad Rzeszutek Wilk
.errors - as it will most likely have the proper error value.
Signed-off-by: Konrad Rzeszutek Wilk
Acked-by: Stefano Stabellini
Signed-off-by: Stefano Stabellini
From: Jan Beulich
The number of slots per page being 511 (i.e. not a power of two) means
that the (32-bit) read and write indexes going beyond 2^32 will likely
disturb operation. The hypervisor side gets I/O req server creation
extended so we can indicate that we're using
flight 61666 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61666/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-libvirt-qcow2 3 host-install(3) broken REGR. vs. 61573
Ensure that every relevant bit is given an explicit value.
This has no effect on the generated code, but makes it
a little easier to follow.
Reported-by: Julien Grall
Signed-off-by: Chris Brand
---
v3 trims down the list of bits given explicit
Shuffle lines around so that the assignments in mfn_to_xen_entry()
occur in the same order as the bits are declared in lpae_pt_t.
This makes it easier to see which ones are never given a value.
No change in behaviour.
Also fix a minor comment typo.
Signed-off-by: Chris Brand
On Thu, Sep 10, 2015 at 02:59:17AM -0600, Jan Beulich wrote:
> >>> On 10.09.15 at 10:55, wrote:
> >> Sort of (the patch has the intended effect, but for its size very
> >> many rough edges).
> >>
> >
> > I guess we need to amend the original parameter, once_mapping_mfns,
flight 61675 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61675/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-libvirt 11 guest-start fail REGR. vs. 61593
Tests which did not
On 10 September 2015 at 18:15, Stefano Stabellini
wrote:
> The following changes since commit 8611280505119e296757a60711a881341603fa5a:
>
> target-microblaze: Use setcond for pcmp* (2015-09-08 08:49:33 +0200)
>
> are available in the git repository at:
>
>
From: Konrad Rzeszutek Wilk
We would like to know what the MSI register value is to help
in troubleshooting in the field. As such modify the logging
logic to include such details in xen_pt_msgctrl_reg_write.
Reviewed-by: Stefano Stabellini
From: Konrad Rzeszutek Wilk
As we do not use it outside our code.
Reviewed-by: Stefano Stabellini
Signed-off-by: Konrad Rzeszutek Wilk
Signed-off-by: Stefano Stabellini
---
From: Konrad Rzeszutek Wilk
However the init routines assume that on errors the return
code is -1 (as the libxc API is) - while those xen_host_* routines follow
another paradigm - negative errno on return, 0 on success.
Reviewed-by: Stefano Stabellini
From: Konrad Rzeszutek Wilk
During init time we treat the dev.config area as a cache
of the host view. However during execution time we treat it
as guest view (by the generic PCI API). We need to sync Xen's
code to the generic PCI API view. This is the first step
by
From: Konrad Rzeszutek Wilk
This way we can call it if we fail during init.
This code movement introduces no changes.
Acked-by: Stefano Stabellini
Signed-off-by: Konrad Rzeszutek Wilk
Signed-off-by: Stefano
From: Konrad Rzeszutek Wilk
In Xen 4.6 commit cd2f100f0f61b3f333d52d1737dd73f02daee592
"libxc: Fix do_memory_op to return negative value on errors"
made the libxc API less odd-ball: On errors, return value is
-1 and error code is in errno. On success the return value
is
From: Konrad Rzeszutek Wilk
Instead we have the emulation registers ->init functions which
consult the host values to see what the initial value should be
and they are responsible for populating the dev.config.
Reviewed-by: Stefano Stabellini
From: Konrad Rzeszutek Wilk
If XEN_PT_LOGGING_ENABLED is enabled the XEN_PT_LOG macros start
using the first argument. Which means if within the function there
is only one user of the argument ('d') and XEN_PT_LOGGING_ENABLED
is not set, we get compiler warnings. This is
This is more-or-less what Julien requested. He noted that pt.config
was never set to zero. When I looked further, I found other bits that
were also never given a value. Looking at the callsites, they almost
all seem to assume a value of zero, so that's what I went with.
Patch 1 re-orders the
flight 61663 linux-3.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61663/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-debianhvm-amd64 6 xen-boot fail REGR. vs. 30511
flight 61677 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61677/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 13 guest-localmigrate
fail REGR.
On Fri, Sep 11, 2015 at 08:44:50AM +0800, Chen, Tiejun wrote:
> >>Right, that's one of the things that would need taking care of.
> >>(Whether enforcing an upper limit is actually needed I'm not
> >>sure - we generally allow the admin to shoot himself in the foot
> >>if he wants to. And whether
Thanks Ian.
So strange, seems this mail was sent ' Tuesday, September 1, 2015 10:42 PM ',
but I
have just received it.
I'm fully occupied by some release test, so have to carefully read your
comments 1 ~2
weeks later. Sorry about this.
Best Regards,
Robert Ho
> -Original Message-
>
> From: Chen, Tiejun
> Sent: Friday, September 11, 2015 8:56 AM
>
> >> > > Need to have separate warning/error level for relax/strict.
> >> > >
> >> > > However I don't think this patch is a right fix. So far relax/strict
> >> > > policy
> >> > > is per-domain. what about one VM specifies relax
Thanks Ian.
So strange, seems this mail was sent ' Tuesday, September 1, 2015 10:42 PM ',
but I
have just received it.
I'm fully occupied by some release test, so have to carefully read your
comments 1 ~2
weeks later. Sorry about this.
Best Regards,
Robert Ho
> -Original Message-
>
Right, that's one of the things that would need taking care of.
(Whether enforcing an upper limit is actually needed I'm not
sure - we generally allow the admin to shoot himself in the foot
if he wants to. And whether the lower limit should be 64 instead
of just ensuring the limit is not zero is
> > Need to have separate warning/error level for relax/strict.
> >
> > However I don't think this patch is a right fix. So far relax/strict policy
> > is per-domain. what about one VM specifies relax while another VM
> > specifies strict when each is assigned with a device sharing rmrr
> > with
Jan Beulich writes:
> From: Kouya Shimura
>
> The ACPI PM timer is sometimes broken on live migration.
> Since vcpu->arch.hvm_vcpu.guest_time is always zero in other than
> "delay for missed ticks mode". Even in "delay for missed ticks mode",
> vcpu's
flight 61690 linux-next real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61690/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvh-intel 11 guest-start fail REGR. vs. 61295
> From: Wei Liu [mailto:wei.l...@citrix.com]
> Sent: Thursday, September 10, 2015 6:37 PM
>
> On Thu, Sep 10, 2015 at 02:09:39AM -0600, Jan Beulich wrote:
> > >>> On 10.09.15 at 07:23, wrote:
> > >> From: Jan Beulich [mailto:jbeul...@suse.com]
> > >> Sent: Wednesday,
Thanks! I'll fold it the offending patch
(http://marc.info/?l=qemu-devel=144174596628052=2) and resend.
Reviewed-by: Michael S. Tsirkin
Michale and Stefano,
Thanks a lot :)
Tiejun
___
Xen-devel mailing list
> From: Chen, Tiejun
> Sent: Friday, September 11, 2015 10:21 AM
>
> >> >> > > However I don't think this patch is a right fix. So far
> >> >> > > relax/strict policy
> >> >> > > is per-domain. what about one VM specifies relax while another VM
> >> >> > > specifies strict when each is assigned
On 09/10/2015 08:14 PM, Kevin Davis wrote:
>>
>>
>> On 10/09/2015 16:24, Kevin Davis wrote:
>>> Further leading me to guess that any actual use of those
>>> implementations could lead to you actually needing to hire a real
>>> attorney and not one that you find on YouTube.
>>
>> The good thing is
>> > > However I don't think this patch is a right fix. So far relax/strict
policy
>> > > is per-domain. what about one VM specifies relax while another VM
>> > > specifies strict when each is assigned with a device sharing rmrr
>> > > with the other? In that case it becomes a system-wide
>>> On 9/8/2015 at 10:17 PM, in message <1441721852.24450.120.ca...@citrix.com>,
Ian Campbell wrote:
> On Mon, 2015-08-10 at 18:35 +0800, Chunyan Liu wrote:
>
> Sorry for the delay, between 4.6 freeze crunch, conference and vacation
> I've been a bit swamped.
>
flight 61692 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61692/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-arndale 8 leak-check/basis(8) fail REGR. vs. 59254
> On Sep 10, 2015, at 8:44 PM, Kevin Davis wrote:
>
>>
>> On 09/10/2015 08:14 PM, Kevin Davis wrote:
>>> Ah. I wasn't in the room when they figured it out. And I've never seen
>> their written opinion. Is it documented somewhere?
>>
>> which in turn leads to
On Sat, May 30, 2015 at 06:56:25PM +0100, Andrew Cooper wrote:
> On 30/05/15 16:39, Mikko Rapeli wrote:
> > privcmd.h depends on xen/interface/xen.h which is now exported to userspace.
> > xen/interface/xen.h then depends on asm/xen/interface.h which is now
> > exported to userspace together with
> From: Chen, Tiejun
> Sent: Thursday, September 10, 2015 1:47 PM
>
> > Need to have separate warning/error level for relax/strict.
> >
> > However I don't think this patch is a right fix. So far relax/strict policy
> > is per-domain. what about one VM specifies relax while another VM
> >
> Am 10.09.2015 um 07:32 schrieb Jordan Justen :
>
> On 2015-09-09 20:26:54, Andrew Fish wrote:
>>> On Sep 9, 2015, at 5:41 PM, Jordan Justen wrote:
On 2015-09-09 16:05:20, Andrew Fish wrote:
So you have a legal degree and are
flight 61627 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/61627/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemut-debianhvm-amd64 19 guest-start/debianhvm.repeat fail
REGR. vs. 61059
> On Sep 9, 2015, at 11:19 PM, Alexander Graf wrote:
>
>
>
>> Am 10.09.2015 um 07:32 schrieb Jordan Justen :
>>
>> On 2015-09-09 20:26:54, Andrew Fish wrote:
On Sep 9, 2015, at 5:41 PM, Jordan Justen
wrote:
101 - 181 of 181 matches
Mail list logo