similar to: Boot time wrong on VM (PV on xen 4.1 debian)

I''ve been trying to compare memory access speed between bare-metal, xen-pv and xen-pvhvm (hvm with pv drivers). In all 3 setups I''m running the same kernel (3.6.6), built with support for xen, on a 64 core AMD Opteron 6378. The output of xm info (relevant parts): machine : x86_64 nr_cpus : 64 nr_nodes : 8 cores_per_socket : 16

If you are running CentOS Linux 7 inside a Xen DomU (VM) in PV mode, you can not upgrade to the standard 7.4.1708 kernel that is currently in the CR repo and that will be soon released in our file 7.4.1708 tree (3.10.0-693.*el7) The CentOS Plus kernel will be available when we release the 7.4.1708 tree and it does boot inside a Xen DomU PV, so you can either upgrade to the CentOS Plus kernel in

Hi Jeremy, I backported the branch I have in linux-next plus some older PV on HVM fixes to stable-2.6.32.x. Please pull: git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git stable-2.6.32-pvhvm Ian Campbell (11): xen: do not respond to unknown xenstore control requests xen: use new schedop interface for suspend xen: switch to new schedop hypercall by default. xen:

On 08-09-2017 6:17, Kevin Stange wrote: > On 09/06/2017 05:21 PM, Kevin Stange wrote: >> On 09/06/2017 08:40 AM, Johnny Hughes wrote: >>> On 09/05/2017 02:26 PM, Kevin Stange wrote: >>>> On 09/04/2017 05:27 PM, Johnny Hughes wrote: >>>>> On 09/04/2017 03:59 PM, Kevin Stange wrote: >>>>>> On 09/02/2017 08:11 AM, Johnny Hughes wrote:

On 14-09-2017 20:57, Adi Pircalabu wrote: > On 08-09-2017 6:17, Kevin Stange wrote: >> On 09/06/2017 05:21 PM, Kevin Stange wrote: >>> On 09/06/2017 08:40 AM, Johnny Hughes wrote: >>>> On 09/05/2017 02:26 PM, Kevin Stange wrote: >>>>> On 09/04/2017 05:27 PM, Johnny Hughes wrote: >>>>>> On 09/04/2017 03:59 PM, Kevin Stange wrote:

On 09/06/2017 08:40 AM, Johnny Hughes wrote: > On 09/05/2017 02:26 PM, Kevin Stange wrote: >> On 09/04/2017 05:27 PM, Johnny Hughes wrote: >>> On 09/04/2017 03:59 PM, Kevin Stange wrote: >>>> On 09/02/2017 08:11 AM, Johnny Hughes wrote: >>>>> On 09/01/2017 02:41 PM, Kevin Stange wrote: >>>>>> On 08/31/2017 07:50 AM, PJ Welsh wrote:

Hi, I''ve been working on getting a working blktap driver allowing to access ceph RBD block devices without relying on the RBD kernel driver and it finally got to a point where, it works and is testable. Some of the advantages are: - Easier to update to newer RBD version - Allows functionality only available in the userspace RBD library (write cache, layering, ...) - Less issue when

On 09/06/2017 05:21 PM, Kevin Stange wrote: > On 09/06/2017 08:40 AM, Johnny Hughes wrote: >> On 09/05/2017 02:26 PM, Kevin Stange wrote: >>> On 09/04/2017 05:27 PM, Johnny Hughes wrote: >>>> On 09/04/2017 03:59 PM, Kevin Stange wrote: >>>>> On 09/02/2017 08:11 AM, Johnny Hughes wrote: >>>>>> On 09/01/2017 02:41 PM, Kevin Stange wrote:

hello, I know this not quite a xen problem but im sure a fair number of people are using debian for their dom0 and maybe have some insight into this. I have a large number of dom0''s running squeeze and for a long time i was hoping for pvhvm to make into the official debian xen packages and recently during some periodic updates I noticed pvhvm working after a kernel package update. Now

On 09/05/2017 02:26 PM, Kevin Stange wrote: > On 09/04/2017 05:27 PM, Johnny Hughes wrote: >> On 09/04/2017 03:59 PM, Kevin Stange wrote: >>> On 09/02/2017 08:11 AM, Johnny Hughes wrote: >>>> On 09/01/2017 02:41 PM, Kevin Stange wrote: >>>>> On 08/31/2017 07:50 AM, PJ Welsh wrote: >>>>>> A recently created and fully functional CentOS

Hey Roger, I am seeing this weird behavior when using #linux-next + stable/for-jens-3.8 tree. Basically I can do ''pvscan'' on xvd* disk and quite often I get checksum errors: # pvscan /dev/xvdf PV /dev/xvdf2 VG VolGroup00 lvm2 [18.88 GiB / 0 free] PV /dev/dm-14 VG vg_x86_64-pvhvm lvm2 [4.00 GiB / 68.00 MiB free] PV /dev/dm-12 VG vg_i386-pvhvm lvm2

How exactly would the existing packages be re-used ? The resulting binary of PV Grub will not be run on the Dom0, it is cross compiled to run as a stub domain under the hypervisor directly and it will not have access to the dom0 at that point so I don't see how you'd re-use the packages installed on the dom0. Cheers, Sylvain

Hi, A bit of explanation of what I''m trying to achieve : We have a bunch of homogeneous nodes that have CPU + RAM + Storage and we want to use that as some generic cluster. The idea is to have Xen on all of these and run Ceph OSD in a domU on each to "export" the local storage space to the entire cluster. And then use RBD to store / access VM images from any of the machines.

Hi, I''m using a custom block script in my xen setup and when started, it creates a new device node pointing to some network resources. Now I noticed that the script is called twice for the root block, the first time for pygrub most likely, but is only stopped once ... I don''t mind creating two devices node, but then I need to destroy both ... Is this a known issue ? Cheers,

Hi Stefano, [just casting the net a bit wider ...] On Tue, 19 Oct 2010 18:51:47 +0100 Stefano Stabellini <stefano.stabellini at eu.citrix.com> wrote: > > I forgot to CC the LKML and linux-next... > > On Tue, 19 Oct 2010, Stefano Stabellini wrote: > > Stephen, > > I have two patch series to merge in linux-next: > > > > PV on HVM: receive interrupts as

Hi Stefano, [just casting the net a bit wider ...] On Tue, 19 Oct 2010 18:51:47 +0100 Stefano Stabellini <stefano.stabellini at eu.citrix.com> wrote: > > I forgot to CC the LKML and linux-next... > > On Tue, 19 Oct 2010, Stefano Stabellini wrote: > > Stephen, > > I have two patch series to merge in linux-next: > > > > PV on HVM: receive interrupts as

Hi Stefano, [just casting the net a bit wider ...] On Tue, 19 Oct 2010 18:51:47 +0100 Stefano Stabellini <stefano.stabellini at eu.citrix.com> wrote: > > I forgot to CC the LKML and linux-next... > > On Tue, 19 Oct 2010, Stefano Stabellini wrote: > > Stephen, > > I have two patch series to merge in linux-next: > > > > PV on HVM: receive interrupts as

Hello, I know, often asked, often discussed .. No recommendation from Citrix. What is the better solution? 1) use ntp in the XEN host and synchronize the guests with the clock running on the control domain (independent_wallclock=0, what the default is) 2) or use ntp in host and guest (and independent_wallclock=1) I ask, because the XEN host (bare metal) has a more stable clock and if the ntp

Hi, So, the issue is a fairly common one: Network doesn''t work for like a minute or so after a live migration. The setup is a debian wheezy dom0 with xen 4.1.2 running 3.6.11 kernel. The domU is a Ubuntu 12.04 with a 3.2 kernel. The networking setup uses bridges on the dom0. I also made sure that the bridge forwarding delay is set to 0. The VM doesn''t initiate any network

On Mar 20, 2014 11:40 PM, Waiman Long <waiman.long at hp.com> wrote: > > On 03/19/2014 04:28 PM, Konrad Rzeszutek Wilk wrote: > > On Wed, Mar 19, 2014 at 04:14:05PM -0400, Waiman Long wrote: > >> This patch adds a XEN init function to activate the unfair queue > >> spinlock in a XEN guest when the PARAVIRT_UNFAIR_LOCKS kernel config > >> option is