similar to: Re: FreeBSD PVHVM call for testing

On 19 Jun 2013, at 13:34, Roger Pau Monné <roger.pau@citrix.com> wrote: > > Could you provide the boot log of the DomU, backtrace, Xen version and > Dom0 kernel version? I did not have a console attached when it rebooted, so I did not have a log of the initial boot. Now that I did, I see that it fails to mount its root volume. It had been running previously on pvhvm_v10 for about

Hi, After some more testing I thought it would be good to put this into production for my personal server. I''ve used pvhvm_v19 and built it without debugging options and installed it on a FreeBSD 9.1 system. I''ve run into some hiccups with 9.1 user land and a 10-CURRENT kernel, but that''s all solvable[0]. My VPS has some very limited memory (256M), but I''ve

Call update_domain_wallclock_time on hvm_latch_shinfo_size even if the bitness of the guest has already been set, this fixes the problem with the wallclock not being set for PVHVM guests on resume from migration. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Cc: Jan Beulich <JBeulich@suse.com> Cc: Keir Fraser <keir@xen.org> Cc: George Dunlap

The initial values of the wallclock time in the shared info page are set for PVHVM guests when the hypercall page is initialized, since the hypercall page is not reinitialized on resume, the hypervisor wallclock time is not properly set on resume. Fix it by forcing an update of the wallclock values when the shared info page is mapped. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>

Add a note to the public headers regarding how to get the VCPU ID for HVM guests (on x86). Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Cc: Jan Beulich <jbeulich@suse.com> Cc: Keir Fraser <keir@xen.org> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Cc: Matt Wilson <msw@amazon.com> --- This is what Linux PVHVM does AFAIK, and also what I've been

Add a note to the public headers regarding how to get the VCPU ID for HVM guests (on x86). Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Acked-by: Matt Wilson <msw@amazon.com> Cc: Jan Beulich <jbeulich@suse.com> Cc: Keir Fraser <keir@xen.org> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Cc: Matt Wilson <msw@amazon.com> --- This is what Linux PVHVM

Hi, On 19 Jun 2013, at 18:52, Justin T. Gibbs <gibbs@FreeBSD.org> wrote: >> I guess the kernel-toolchain takes a long time to build…and from what I can see it does a clean before rebuilding also. >> >> I''m doing the kernel-toolchain step only now and will report how long it took. This seems to be it, that took roughly 2 hours to build. The actual kernel is

flight 22107 xen-4.3-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/22107/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pv 9 guest-start fail REGR. vs. 22042 build-armhf 2 host-install(2) broken REGR. vs. 22042 build-armhf-pvops 2

On Mon, 27 Feb 2012, Ian Campbell wrote: > On Thu, 2012-02-23 at 13:34 +0000, Roger Pau Monné wrote: > > 2012/2/22 Anthony Liguori <anthony@codemonkey.ws>: > > > On 02/20/2012 06:11 AM, Roger Pau Monne wrote: > > >> > > >> Replace clock_gettime with timer_gettime, since at least under > > >> uclibc 0.9.33 the clock_getttime function can

With the introduction of indirect segments we can receive requests with a number of segments bigger than the maximum number of allowed iovecs in a bios, so make sure that blkback doesn't try to allocate a bios with more iovecs than BIO_MAX_PAGES Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> ---

flight 22144 xen-4.3-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/22144/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf 2 host-install(2) broken in 22138 REGR. vs. 22042 build-i386 3 host-build-prep fail in 22138 REGR. vs. 22042 Tests which are failing intermittently

Moving grant ref handles from blkbk to pending_req will allow us to get rid of the shared blkbk structure. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Cc: xen-devel@lists.xen.org --- drivers/block/xen-blkback/blkback.c | 16 ++++------------ 1 files changed, 4 insertions(+), 12 deletions(-) diff --git

We already have the frame (pfn of the grant page) stored inside struct grant, so there's no need to keep an aditional list of mapped frames for a specific request. This reduces memory usage in blkfront. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Cc: xen-devel@lists.xen.org --- drivers/block/xen-blkfront.c | 6 +-----

MTRR is not available for PVH Dom0, so prevent cpuid from reporting it as an available feature. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Cc: George Dunlap <george.dunlap@eu.citrix.com> Cc: Mukesh Rathor <mukesh.rathor@oracle.com> Cc: Jan Beulich <JBeulich@suse.com> Cc: Keir Fraser <keir@xen.org> --- This should go in after Mukesh Dom0 series, or merged

flight 14682 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/14682/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-winxpsp3 8 guest-saverestore fail REGR. vs. 14678 test-amd64-amd64-xl-qemut-winxpsp3 12 guest-localmigrate/x10 fail REGR. vs. 14678 test-amd64-amd64-xl-qemuu-win7-amd64

This hotplug script has been tested with IET and NetBSD iSCSI targets, without authentication. This hotplug script will only work with PV guests not using pygrub. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Cc: Ian Campbell <ian.campbell@citrix.com> Cc: Ian Jackson <ian.jackson@citrix.com> --- Changes due to 4.3 release freeze: * We can no longer provide a

When using a vtsc, hvm_set_guest_time changes hvm_vcpu.stime_offset, which is used in the vcpu time structure to calculate the tsc_timestamp, so after updating stime_offset we need to propagate the change to vcpu_time in order for the guest to get the right time if using the PV clock. This was not done correctly, since in context_switch update_vcpu_system_time was called before vmx_do_resume,

Hi, Commit 63753b3e0dc56efb1acf94fa46f3fee7bc59281c x86: allow VCPUOP_register_vcpu_info to work again on PVHVM guests Leaves HVM guests dangling after shutdown or destroy: xl list gives: (null) 16 0 4 --p--d 11.5 (null) 17 0 1 --ps-d 12.0 (first was destroyed, second shutdown) The

The aim of this patch is to define a stable way in which PVH is going to do AP bringup. Since we are running inside of a HVM container, PVH should only need to set flags, cr3 and user_regs in order to bring up a vCPU, the rest can be set once the vCPU is started using the bare metal methods. Additionally, the guest can also set cr0 and cr4, and those values will be appended to the default values

On Wed, Oct 25, 2017 at 09:13:54AM -0700, Xinliang David Li wrote: > On Wed, Oct 25, 2017 at 12:26 AM, Roger Pau Monné via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > Hello, > > > > I've been working on implementing some basic functionality in order to > > use the llvm profiling functionality inside of a kernel (the Xen > > hypervisor).