> -Original Message-
> From: qemu-devel-bounces+xudong.hao=intel@nongnu.org [mailto:qemu-
> devel-bounces+xudong.hao=intel@nongnu.org] On Behalf Of Gerd
> Hoffmann
> Sent: Tuesday, January 12, 2016 6:25 PM
> To: Hao, Xudong
> Cc: Lars Kurth ; xen-de...@lists.xensource.com; Stefano
flight 77918 seabios real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77918/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 77427
Tests which did not succeed, but a
This simplifies a number of pointless conditionals: Bits 0 and 1 of
xcomp_bv don't matter anyway, and as long as none of bits 2..62 are
set, setting bit 63 is pointless too unless XSAVES is in use.
Signed-off-by: Jan Beulich
---
v2: Retain setting of bit 63 on XSAVES-capable systems.
--- a/xen/a
> From: Xu, Quan
> Sent: Thursday, January 07, 2016 9:47 PM
>
> > On January 07, 2016 9:28 PM, wrote:
> > >>> On 07.01.16 at 02:39, wrote:
> > > On January 06, 2016 7:26 PM, wrote:
> > >> > I didn't think about the full logic thoroughly now. But it would
> > >> > always be good to not hide devi
On 12/01/16 18:23, Stefano Stabellini wrote:
> On Tue, 12 Jan 2016, Juergen Gross wrote:
>> On 12/01/16 18:05, Stefano Stabellini wrote:
>>> On Tue, 12 Jan 2016, Jan Beulich wrote:
>>> On 12.01.16 at 13:07, wrote:
> On Mon, 11 Jan 2016, David Vrabel wrote:
>> On 11/01/16 17:17, Andrew
This run is configured for baseline tests only.
flight 38625 qemu-upstream-4.4-testing real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38625/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-chec
flight 77892 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77892/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail
REGR. vs. 66879
Reg
On 1/12/16 7:14 AM, Roger Pau Monne wrote:
> According to the FreeBSD sysconf man page [0] if the variable is associated
> with functionality that is not supported, -1 is returned and errno is not
> modified. Modify libxl__dm_runas_helper so it's able to correctly
> deal with this situation by sett
commit 5d3dc8671521ea4a4f753e77d3e7fb3a3a6f5f80
"tools: Refactor "xentoollog" into its own library"
with older python versions (2.6.4) will fail to
the build if attempted to be done twice (which
happens due to pygrub dependencies).
make -C python DESTDIR=/tmp
make -C python DESTDIR=/tmp
The secon
"can't boot up" means guest doesn't boot at all, guest will stop to booting
after adding vga device, detail log in attachment.
Thanks,
-Xudong
> -Original Message-
> From: qemu-devel-bounces+xudong.hao=intel@nongnu.org [mailto:qemu-
> devel-bounces+xudong.hao=intel@nongnu.org] O
flight 77910 qemu-upstream-4.2-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77910/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3865 xen-build fail REGR. vs. 62044
build-a
On 01/12/2016 01:40 PM, Peter Zijlstra wrote:
It is selectable only for MIPS R2 but not MIPS R6. The reason is - most of
MIPS R2 CPUs have short pipeline and that SYNC is just waste of CPU
resource, especially taking into account that "lightweight syncs" are
converted to a heavy "SYNC 0" in man
flight 38624 distros-debian-snapshot real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38624/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-i386-weekly-netinst-pygrub 9 debian-di-install fail REGR. vs.
38592
flight 77871 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77871/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-libvirt-vhd 9 debian-di-installfail like 77684
Tests which did not succeed, but a
flight 77867 linux-mingo-tip-master real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77867/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail
REGR. vs.
flight 77886 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77886/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail
REGR. vs. 65543
test-amd64-i386-
flight 77858 qemu-upstream-4.5-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77858/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail in 77752 pass in
77858
test-amd64-amd
This run is configured for baseline tests only.
flight 38623 linux-3.16 real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/38623/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-multivcpu 6 xen-boot
flight 77853 qemu-upstream-4.3-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77853/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-winxpsp3 15 guest-localmigrate/x10 fail REGR. vs.
62112
Reg
On Tue, Jan 12, 2016 at 12:45:14PM -0800, Leonid Yegoshin wrote:
> (I try to answer on multiple mails in one)
>
> First of all, it seems like some generic notes should be given here:
>
> 1. Generic MIPS "SYNC" (aka "SYNC 0") instruction is a very heavy in some
> CPUs. On that CPUs it basically ki
(I try to answer on multiple mails in one)
First of all, it seems like some generic notes should be given here:
1. Generic MIPS "SYNC" (aka "SYNC 0") instruction is a very heavy in
some CPUs. On that CPUs it basically kills pipelines in each CPU, can do
a special memory/IO bus transaction (sim
Chunyan Liu writes ("[PATCH V12 4/5] xl: add pvusb commands"):
> Add pvusb commands: usbctrl-attach, usbctrl-detach, usb-list,
> usbdev-attach and usbdev-detach.
The way you have documented usbctrl-attach and the config file syntax
in this patch and the next one means that each usb config setting
flight 77846 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77846/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-armhf-armhf-xl-rtds 9 debian-install fail like 77743
Tests which did not succeed,
On Tue, Jan 12, 2016 at 08:28:44AM -0800, Paul E. McKenney wrote:
> On Sun, Jan 10, 2016 at 04:16:32PM +0200, Michael S. Tsirkin wrote:
> > From: Davidlohr Bueso
> >
> > With commit b92b8b35a2e ("locking/arch: Rename set_mb() to smp_store_mb()")
> > it was made clear that the context of this call
Chunyan Liu writes ("[PATCH V12 3/5] libxl: add pvusb API"):
> Add pvusb APIs, including:
> - attach/detach (create/destroy) virtual usb controller.
> - attach/detach usb device
> - list usb controller and usb devices
> - some other helper functions
>
> Signed-off-by: Chunyan Liu
> Signed-off
Chunyan Liu writes ("[PATCH V12 1/5] libxl: export some functions for pvusb
use"):
> Signed-off-by: Chunyan Liu
> Signed-off-by: Simon Cao
> Reviewed-by: Wei Liu
Acked-by: Ian Jackson
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.
Chunyan Liu writes ("[PATCH V12 2/5] libxl_utils: add internal function to read
sysfs file contents"):
> Add a new function libxl_read_sysfs_file_contents to handle sysfs file
> specially. It would be used in later pvusb work.
Acked-by: Ian Jackson
__
El 12/01/16 a les 17.31, Jan Beulich ha escrit:
On 12.01.16 at 17:12, wrote:
>> @@ -2087,19 +2100,21 @@ static int hvm_load_cpu_ctxt(struct domain *d,
>> hvm_domain_context_t *h)
>> seg.attr.bytes = ctxt.ldtr_arbytes;
>> hvm_set_segment_register(v, x86_seg_ldtr, &seg);
>>
>> -
On 12/01/16 16:56, Vitaly Kuznetsov wrote:
> Add support for the newly added kernel memory auto onlining policy to Xen
> ballon driver.
[...]
> --- a/drivers/xen/Kconfig
> +++ b/drivers/xen/Kconfig
> @@ -37,23 +37,29 @@ config XEN_BALLOON_MEMORY_HOTPLUG
>
> Memory could be hotplugged in f
On Tue, 12 Jan 2016, Juergen Gross wrote:
> On 12/01/16 18:05, Stefano Stabellini wrote:
> > On Tue, 12 Jan 2016, Jan Beulich wrote:
> > On 12.01.16 at 13:07, wrote:
> >>> On Mon, 11 Jan 2016, David Vrabel wrote:
> On 11/01/16 17:17, Andrew Cooper wrote:
> > So from one point of view,
On 12/01/16 18:05, Stefano Stabellini wrote:
> On Tue, 12 Jan 2016, Jan Beulich wrote:
> On 12.01.16 at 13:07, wrote:
>>> On Mon, 11 Jan 2016, David Vrabel wrote:
On 11/01/16 17:17, Andrew Cooper wrote:
> So from one point of view, sufficient justification for this change is
> "be
On Tue, 12 Jan 2016, Jan Beulich wrote:
> >>> On 12.01.16 at 13:07, wrote:
> > On Mon, 11 Jan 2016, David Vrabel wrote:
> >> On 11/01/16 17:17, Andrew Cooper wrote:
> >> > So from one point of view, sufficient justification for this change is
> >> > "because the Linux way isn't the only valid way
>>> On 12.01.16 at 17:43, wrote:
> On Tue, Jan 12, 2016 at 09:25:27AM -0700, Jan Beulich wrote:
>> >>> On 08.01.16 at 03:25, wrote:
>> > The mechanism to get this is via the XENVER hypercall and
>> > we add a new sub-command to retrieve the binary build-id
>> > called XENVER_build_id. The sub-hyp
Currently, all newly added memory blocks remain in 'offline' state unless
someone onlines them, some linux distributions carry special udev rules
like:
SUBSYSTEM=="memory", ACTION=="add", ATTR{state}=="offline", ATTR{state}="online"
to make this happen automatically. This is not a great solution
Add support for the newly added kernel memory auto onlining policy to Xen
ballon driver.
Suggested-by: Daniel Kiper
Signed-off-by: Vitaly Kuznetsov
---
drivers/xen/Kconfig | 20 +---
drivers/xen/balloon.c | 30 +++---
2 files changed, 32 insertions(+),
Changes since v3:
- Add support for the policy to Xen balloon driver [Daniel Kiper, David Vrabel]
- I found an issue with PATCH v3: when memory auto onlining was requested we
do nothing to memblocks states so in sysfs they stay 'offline' (while in
reality they're online). Modify register_new_me
PCI passthrough cannot work if QEMU is run as a non-root process today,
as QEMU needs to open /dev/mem to mmap the MSI-X table of the device and
read/write relevant nodes on sysfs.
Update the docs to reflect that.
Run QEMU as root and print a warning if at least one PCI device has been
assigned t
On Tue, Jan 12, 2016 at 09:25:27AM -0700, Jan Beulich wrote:
> >>> On 08.01.16 at 03:25, wrote:
> > The mechanism to get this is via the XENVER hypercall and
> > we add a new sub-command to retrieve the binary build-id
> > called XENVER_build_id. The sub-hypercall parameter
> > allows an arbitrary
>>> On 31.12.15 at 04:03, wrote:
> This patch implements a common function hvm_scale_tsc() to scale TSC by
> using TSC scaling information collected by architecture code.
>
> Signed-off-by: Haozhong Zhang
> Reviewed-by: Kevin Tian (except the mul64 part)
The tail of this should have been dropp
osstest service owner writes ("[xen-unstable test] 77827: regressions - FAIL"):
> flight 77827 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/77827/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test
>>> On 31.12.15 at 04:03, wrote:
> @@ -2003,6 +2011,10 @@ static struct hvm_function_table __initdata
> vmx_function_table = {
> .altp2m_vcpu_update_vmfunc_ve = vmx_vcpu_update_vmfunc_ve,
> .altp2m_vcpu_emulate_ve = vmx_vcpu_emulate_ve,
> .altp2m_vcpu_emulate_vmfunc = vmx_vcpu_emul
>>> On 12.01.16 at 17:37, wrote:
> On Mon, Jan 11, 2016 at 09:17:57AM -0700, Jan Beulich wrote:
>> >>> On 11.01.16 at 17:01, wrote:
>> > On Mon, Jan 11, 2016 at 02:02:54AM -0700, Jan Beulich wrote:
>> >> >>> On 08.01.16 at 18:31, wrote:
>> >> >> >> > The rest: XENVER_[version|capabilities|
>> >>
On Mon, Jan 11, 2016 at 09:17:57AM -0700, Jan Beulich wrote:
> >>> On 11.01.16 at 17:01, wrote:
> > On Mon, Jan 11, 2016 at 02:02:54AM -0700, Jan Beulich wrote:
> >> >>> On 08.01.16 at 18:31, wrote:
> >> >> >> > The rest: XENVER_[version|capabilities|
> >> >> >> > parameters|get_features|page_siz
On Sun, Jan 10, 2016 at 04:17:09PM +0200, Michael S. Tsirkin wrote:
> On powerpc read_barrier_depends, smp_read_barrier_depends
> smp_store_mb(), smp_mb__before_atomic and smp_mb__after_atomic match the
> asm-generic variants exactly. Drop the local definitions and pull in
> asm-generic/barrier.h i
>>> On 12.01.16 at 17:12, wrote:
> @@ -2087,19 +2100,21 @@ static int hvm_load_cpu_ctxt(struct domain *d,
> hvm_domain_context_t *h)
> seg.attr.bytes = ctxt.ldtr_arbytes;
> hvm_set_segment_register(v, x86_seg_ldtr, &seg);
>
> -/* In case xsave-absent save file is restored on a xsa
On 12/01/16 16:00, Jan Beulich wrote:
> I've got repeatedly annoyed by the bad naming: Make them slightly
> better recognizable (and less likely to get mixed up), except in cases
> where they can be eliminated altogether.
>
> Signed-off-by: Jan Beulich
Reviewed-by: Andrew Cooper
___
On Sun, Jan 10, 2016 at 04:16:32PM +0200, Michael S. Tsirkin wrote:
> From: Davidlohr Bueso
>
> With commit b92b8b35a2e ("locking/arch: Rename set_mb() to smp_store_mb()")
> it was made clear that the context of this call (and thus set_mb)
> is strictly for CPU ordering, as opposed to IO. As such
flight 77852 qemu-upstream-4.2-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77852/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-i3865 xen-build fail REGR. vs. 62044
build-a
>>> On 08.01.16 at 03:25, wrote:
> The mechanism to get this is via the XENVER hypercall and
> we add a new sub-command to retrieve the binary build-id
> called XENVER_build_id. The sub-hypercall parameter
> allows an arbitrary size (the buffer and len is provided
> to the hypervisor). A NULL para
>>> On 08.01.16 at 03:25, wrote:
> @@ -226,9 +227,10 @@ void __init do_initcalls(void)
> /*
> * Simple hypercalls.
> */
> -
> DO(xen_version)(int cmd, XEN_GUEST_HANDLE_PARAM(void) arg)
> {
> +bool_t deny = !!xsm_version_op(XSM_OTHER, cmd);
> +
> switch ( cmd )
> {
> case
Introduce a new flags field and use bit 0 to signal if the FPU has been
initialised or not. Previously Xen always wrongly assumed the FPU was
initialised on restore.
Signed-off-by: Roger Pau Monné
---
Cc: Jan Beulich
Cc: Andrew Cooper
---
Changes since v5:
- Adapt the code due to the changes i
Hello,
This patch series tries to properly solve the problem seen with the HVMlite
series, that Xen always assumes the FPU is initialised on CPU context
restore.
Roger.
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
This reverts commit d64dbbcc7c9934a46126c59d78536235908377ad:
Xen always set the FPU as initialized when loading a HVM context, so libxc
has to provide a valid FPU context when setting the CPU registers.
This was a stop-gap measure in order to unblock OSSTest Windows 7 failures
while a proper fix
On Mon, Jan 11, 2016 at 11:10:35AM -0600, Doug Goldstein wrote:
> On 1/11/16 9:19 AM, Wei Liu wrote:
> > On Fri, Jan 08, 2016 at 12:49:07PM -0600, Doug Goldstein wrote:
> > [...]
> >> Ok so I'm at a loss what steps I need to take. I've submitted patches to
> >> put the config in /boot so that this
flight 77834 qemu-upstream-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77834/
Failures :-/ but no regressions.
Regressions which are regarded as allowable (not blocking):
test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 62580
test-amd64-i386-
I've got repeatedly annoyed by the bad naming: Make them slightly
better recognizable (and less likely to get mixed up), except in cases
where they can be eliminated altogether.
Signed-off-by: Jan Beulich
--- a/xen/arch/x86/hvm/hvm.c
+++ b/xen/arch/x86/hvm/hvm.c
@@ -6523,29 +6523,29 @@ long do_h
On 12/01/16 16:19, George Dunlap wrote:
> On 07/01/16 10:21, Wei Liu wrote:
>> CC George (who does the packaging for CentOS)
>>
>> BTW this problem is better directed to appropriate mailing list of
>> CentOS (centos-virt? I can't remember the exact name).
>
> It would be centos-virt, but as it loo
Hello,
I would like to request the backport of the following SeaBIOS commit to
the master branch of the SeaBIOS repository used by Xen unstable (this
is AFAICT the only one that requires this build fix).
commit 3b8c5378dfe24ca8dfeabbcc435c7eb9e2d8d769
Author: Roger Pau Monne
Date: Mon Dec 28 1
Ian Campbell writes ("Re: [OSSTEST PATCH 3/7] Database locking: Tcl: Use
db-execute"):
> On Thu, 2016-01-07 at 19:38 +, Ian Jackson wrote:
> > Replace open-coded uses of pg_execute dbh STMT with
> > jobdb::db-execute-array STMT.
>
> ITYM jobdb::db-execute?
Yes, fixed, thanks.
Ian.
Ian Campbell writes ("Re: [PATCH 4.4 1/2] libxl: Rerun bison and flex"):
> On Mon, 2016-01-04 at 14:50 +, Ian Jackson wrote:
> > We are going to want to cherry pick a change to the bison input, which
> > will involve rerunning bison.
> >
> > So firstly, update the bison and flex output to that
Ian Campbell writes ("Re: [OSSTEST PATCH 5/7] Database locking: Tcl: for
errorCode, use pg_exec, not pg_execute"):
> On Thu, 2016-01-07 at 19:38 +, Ian Jackson wrote:
> > A wrinkle is that as a result it is no longer possible to use
> > db-execute on a SELECT statement nor db-execute-array on
Ian Campbell writes ("[PATCH RFC OSSTEST v1 12/12] make-flight: Use older
Debian for host and guest OS with older Xen"):
> Sometimes when updating osstest to use a newer version of Debian as a
> baseline we find that the new compiler or other tools pickup latent
> errors in older code bases for wh
Ian Campbell writes ("[PATCH RFC OSSTEST v1 11/12] mfi-common:
usual_debianhvm_image: derive version from $guestsuite"):
> This more likely matches the callers intention.
>
> Move the setting into production-config* alongside the Suite and
> TftpDiVersion settings. Continue to support $DEBIAN_IMA
On 1/12/16 2:41 AM, Jan Beulich wrote:
On 11.01.16 at 23:02, wrote:
>> --- a/xen/include/xen/config.h
>> +++ b/xen/include/xen/config.h
>> @@ -92,4 +92,7 @@
>> #define FLASK_AVC_STATS 1
>> #endif
>>
>> +/* allow existing code to work with Kconfig variable */
>> +#define NR_CPUS CONFIG_NR_
On 07/01/16 10:21, Wei Liu wrote:
> CC George (who does the packaging for CentOS)
>
> BTW this problem is better directed to appropriate mailing list of
> CentOS (centos-virt? I can't remember the exact name).
It would be centos-virt, but as it looks like an upstream bug, if Janis
had reported th
Ian Campbell writes ("[PATCH RFC OSSTEST v1 10/12] Qualify TftpDiVersion with
the suite."):
> This allows the version to differ e.g. between Wheezy and Jessie.
>
> Update production-config* to set TftpDiVersion_jessie instead of just
> TftpDiVersion, also add TftpDiVersion_wheezy using the versio
>>> On 12.01.16 at 12:55, wrote:
> On 12/01/16 10:08, Jan Beulich wrote:
>> This went unnoticed until a backport of this to an older Xen got used,
>> causing migration of guests enabling this VM assist to fail, because
>> page table pinning there preceeds vCPU context loading, and hence L4
>> tabl
>>> On 12.01.16 at 13:07, wrote:
> On Mon, 11 Jan 2016, David Vrabel wrote:
>> On 11/01/16 17:17, Andrew Cooper wrote:
>> > So from one point of view, sufficient justification for this change is
>> > "because the Linux way isn't the only valid way to do this".
>>
>> "Because we can" isn't a good
On 11/01/16 23:01, Stephen Rothwell wrote:
> Hi David,
>
> On Mon, 11 Jan 2016 11:32:01 + David Vrabel wrote:
>>
>> Please git pull the following tag:
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
>> for-linus-4.5-rc0-tag
>>
>> xen: features and fixes for 4.5-rc0
>>
>> - -
El 12/01/16 a les 14.14, Roger Pau Monne ha escrit:
> Hello,
>
> This series contains a couple of small fixes for FreeBSD. The first one is
> regarding the newly introduced libxl__dm_runas_helper function and it's
> usage of sysconf, while the second one fixes a long-stading bug that impacts
>
flight 77830 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77830/
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. 59254
test-armhf-armhf-xl
Ian Campbell writes ("[PATCH RFC OSSTEST v1 08/12] make-flight: Set diversion
runvar on d-i based test jobs."):
> Note that make-distros-flight does not want this, since it uses d-i
> fetched from the web not the version in our config.
Acked-by: Ian Jackson
Subject to anticipated change to the
Ian Campbell writes ("[PATCH RFC OSSTEST v1 07/12] ts-debian-di-install: Allow
Di Version to come from runvars"):
> and following the lead of the suite arrange for a version selected
> from the defaults to be written back to the runvars.
...
> - debian_guest_suite
> +
Ian Campbell writes ("[PATCH RFC OSSTEST v1 09/12] mfi-common: Set diversion
for build & test host install"):
> This means that bisections will use the same version, even if
> production-config changed in the mean time.
Acked-by: Ian Jackson
Subject to anticipated change to the runvar name.
Ia
Ian Campbell writes ("[PATCH RFC OSSTEST v1 05/12] make-*flight: Abolish
$defsuite and $guestdefsuite"):
> Instead have mfi-common set $suite or $guestsuite if it is unset. When
> doing so move the use of local to this point, using local at the top
> of the function would shadow any attempt to set
Ian Campbell writes ("[PATCH RFC OSSTEST v1 06/12] ts-host-install: Support
DiVersion coming from runvars"):
> To do so initialise $ho->{DiVersion} in select host and use it in
> ts-host-install.
Acked-by: Ian Jackson
___
Xen-devel mailing list
Xen-de
Insure that memory and maxmem are set to the same value.
On 01/11/2016 10:38 PM, Konrad Rzeszutek Wilk wrote:
Hey,
The machine is an X5-2 which is a Haswell based E5-2699 v3.
We are trying to launch to use the nested virtualization. The
guest is a simple VMware vSphere 6.0 with 32GB, 8 CPUs.
On Sun, 10 Jan 2016, Michael S. Tsirkin wrote:
> This defines __smp_xxx barriers for x86,
> for use by virtualization.
>
> smp_xxx barriers are removed as they are
> defined correctly by asm-generic/barriers.h
>
> Signed-off-by: Michael S. Tsirkin
> Acked-by: Arnd Bergmann
Reviewed-by: Thomas
On Sun, 10 Jan 2016, Michael S. Tsirkin wrote:
> As on most architectures, on x86 read_barrier_depends and
> smp_read_barrier_depends are empty. Drop the local definitions and pull
> the generic ones from asm-generic/barrier.h instead: they are identical.
>
> This is in preparation to refactorin
On 01/04/2016 08:08 PM, Jim Fehlig wrote:
> The xen sexpr config format has long supported specifying vif rate
> limiting, e.g.
>
> (device
> (vif
> (mac '00:16:3e:1b:b1:47')
> (rate '10240KB/s')
> ...
> )
> )
>
> Add support for mapping rate to and from in the xe
flight 77890 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77890/
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
libxl makes the assumtion that libxl_uuid == uuid_t, and that uuid_t can be
freely used as a byte array. This is not true on FreeBSD (and NetBSD
too, not sure about other BSD UUID implementations), where the internals of
uuid don't match what libxl expects as a byte array because of endianness
issu
According to the FreeBSD sysconf man page [0] if the variable is associated
with functionality that is not supported, -1 is returned and errno is not
modified. Modify libxl__dm_runas_helper so it's able to correctly
deal with this situation by setting the initial buffer value to 2048.
[0] https://
Hello,
This series contains a couple of small fixes for FreeBSD. The first one is
regarding the newly introduced libxl__dm_runas_helper function and it's
usage of sysconf, while the second one fixes a long-stading bug that impacts
UUID usage on FreeBSD (and NetBSD AFAICT).
Thanks, Roger.
___
On 1/12/16 2:37 AM, Jan Beulich wrote:
On 11.01.16 at 23:02, wrote:
>> --- /dev/null
>> +++ b/xen/arch/Kconfig
>> @@ -0,0 +1,8 @@
>> +
>> +config NR_CPUS
>> +int "Maximum number of physical CPUs"
>> +range 1 65536
>
> Why did you change this to 64k, when we settled on 4k-1 being
> co
Hello,
El 12/01/16 a les 13.05, Wei Liu ha escrit:
> Drop xen-users@, CC xen-devel@ and blk maintainers, change title.
>
> On Mon, Jan 11, 2016 at 03:08:24PM +0100, Kojedzinszky Richárd wrote:
>> Dear all,
>>
>> We are facing a regular lockup with our xen setup. We have an nfs share
>> mounted on
On Sun, Jan 10, 2016 at 04:16:22PM +0200, Michael S. Tsirkin wrote:
> I parked this in vhost tree for now, though the inclusion of patch 1 from tip
> creates a merge conflict - but one that is trivial to resolve.
>
> So I intend to just merge it all through my tree, including the
> duplicate patch
On Tue, Jan 12, 2016 at 08:36:42AM +, osstest service owner wrote:
> flight 77825 ovmf real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/77825/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking,
> including tests which could not be run:
> test-amd64-amd64-xl-q
On Mon, 11 Jan 2016, Andrew Cooper wrote:
> Currently, hypercalls issued from HVM userspace will unconditionally fail with
> -EPERM.
>
> This is inflexible, and a guest may wish to allow userspace to make
> hypercalls.
>
> Introduce HVMOP_set_hypercall_dpl which allows the guest to alter the
> pe
On Jan 12, 2016 3:21 AM, "Jan Beulich" wrote:
>
> >>> On 06.01.16 at 12:50, wrote:
> > On Wed, Jan 6, 2016 at 12:48 PM, Andrew Cooper <
andrew.coop...@citrix.com>
> > wrote:
> >
> >> On 06/01/16 11:42, Tamas K Lengyel wrote:
> >>
> >>
> >>
> >> On Wed, Jan 6, 2016 at 12:32 PM, Jan Beulich wrote:
On Mon, 11 Jan 2016, David Vrabel wrote:
> On 11/01/16 17:17, Andrew Cooper wrote:
> > So from one point of view, sufficient justification for this change is
> > "because the Linux way isn't the only valid way to do this".
>
> "Because we can" isn't a good justification for adding something new.
>
Drop xen-users@, CC xen-devel@ and blk maintainers, change title.
On Mon, Jan 11, 2016 at 03:08:24PM +0100, Kojedzinszky Richárd wrote:
> Dear all,
>
> We are facing a regular lockup with our xen setup. We have an nfs share
> mounted on the xen dom0, where the vm images are served, and those file
On 12/01/16 10:08, Jan Beulich wrote:
> This went unnoticed until a backport of this to an older Xen got used,
> causing migration of guests enabling this VM assist to fail, because
> page table pinning there preceeds vCPU context loading, and hence L4
> tables get initialized for the wrong mode. F
Hi all,
I attached a cleaned-up version for 2015. Thanks to those which provided input
Lars
On Mon, Jan 11, 2016 at 11:53 AM, Lars Kurth wrote:
> Hi folks,
>
> please find attached 2014 and 2015 contribution stats, including some of the
> tags. To compare like with like, the 2015 figures do cont
On Tue, Jan 12, 2016 at 11:40:12AM +0100, Peter Zijlstra wrote:
> On Tue, Jan 12, 2016 at 11:25:55AM +0100, Peter Zijlstra wrote:
> > On Tue, Jan 12, 2016 at 10:27:11AM +0100, Peter Zijlstra wrote:
> > > 2) the changelog _completely_ fails to explain the sync 0x11 and sync
> > > 0x12 semantics nor
Ian Campbell writes ("[PATCH RFC OSSTEST v1 04/12] mfi-common: always add host
suite to hostos_runvars"):
> This avoids situations where production-config* has changed
> DebianSuite but the bisector is still picking up baselines etc from
> before the change and reusing their runvars (without suite
flight 77827 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/77827/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail
REGR. vs. 66879
Reg
On Tue, Jan 12, 2016 at 10:57 AM, Andrew Cooper
wrote:
> Writing a PV guest from scratch has been very enlightening to
> demonstrate how much of a trainwreck the ABI is. Almost nothing is
> documented. Some bits which are documented are misleading. Several
> areas needlessly deviate from x86 ar
On 12/01/16 07:33, Jan Beulich wrote:
On 11.01.16 at 18:17, wrote:
>> On 11/01/16 14:44, Jan Beulich wrote:
>> On 11.01.16 at 14:59, wrote:
Currently, hypercalls issued from HVM userspace will unconditionally fail
with -EPERM.
This is inflexible, and a guest may wish
On Tue, Jan 12, 2016 at 11:25:55AM +0100, Peter Zijlstra wrote:
> On Tue, Jan 12, 2016 at 10:27:11AM +0100, Peter Zijlstra wrote:
> > 2) the changelog _completely_ fails to explain the sync 0x11 and sync
> > 0x12 semantics nor does it provide a publicly accessible link to
> > documentation that doe
1 - 100 of 122 matches
Mail list logo
