similar to: CentOS7, Xen 4.6.1, kernel 3.18.25-19 strange performance problem

On Sun, Apr 10, 2016 at 11:20 AM, T.Weyergraf <T.Weyergraf at virtfinity.de> wrote: > Hi all, > > i just stumbled over a strange performance issue with my Xen setup. > > I use centos-virt Xen since a long time on my workstation and usually never > check performance. However, yesterday I booted into the 3.18.25-19 Dom0 > kernel *without* Xen and found the system noticably

Hi I gave the new Xen-4.6rc2 a spin on a CentOS 7 virtualisation guest (nested-xen). I haven't yet started testing guests, but rather looked at the install itself. One issue, I found, was with xenstored.service and the corresponding unit-file: [root at xencen7ws ~]# systemctl status xenstored xenstored.service - The Xen xenstore Loaded: loaded

Greeting, We are about to update the centos-release-xen package to point to Xen 4.8 rather than 4.6. I'll push the update next week. As a reminder, you can "pin" your installation to Xen 4.6 by installing centos-release-xen-46 and then removing centos-release-xen. And for the more adventurous, that update will come with a new package centos-release-xen-410 to install Xen 4.10.

Hi I am attempting to setup Xen 4.10 with kernel 4.9.86-30 ( virt7-xen-410-testing, virt7-common-testing ) on CentOS7 After installing everything, the machine was unable to boot and hung in dracut stating it could not find its root device. The testsystem I use is a somewhat aged Dell M915 Blade (Quad opteron 61xx), using an MPT SAS controller for it's SAS boot drives. Stock CentOS 7

Hi folks, we (the company i am working for) are running several dozens of virtualisation servers using CentOS 6 + Xen4CentOS as the virtualisation infrastructure. With the latest versions of all packages installed [1], we see failures in live-migration of stock-CentOS6 HVM guests, leaving a "Domain-unnamed" on the source host, while the migrated guest runs fine on the target host.

At long last, I'd like to announce beta packages for CentOS 7, available from the community build system. Start by installing the centos-release-xen: rpm -ivh http://cbs.centos.org/repos/virt7-xen-44-testing/x86_64/os/Packages/centos-release-xen-7-3.el7.x86_64.rpm This will set up yum repositories for both the eventual release repositories (enabled by default), and the community build

On 09/04/2015 04:39 PM, T.Weyergraf wrote: > > > On 09/03/2015 09:50 PM, Chuck Meade wrote: >> Hi Thomas, > Hi Chuck >> >> This may be old news at this point, but I had 100% identical behavior >> to yours when I tried virtx7-44-testing. >> After looking around a bit I tried "virtx7-44-candidate", in a sibling >> directory to

On Mon, Sep 7, 2015 at 11:02 PM, T.Weyergraf <T.Weyergraf at virtfinity.de> wrote: > First of all, I fully agree, that forked repos are undesirable. However, to > the casual observer (like me), there are hardly any ressources for Xen on > CentOS 7. There are some beta packages, as announced in the start if this > thread, with the latest update being 4.4.2 on 4th of august. I

On Tue, Sep 8, 2015 at 11:25 PM, T.Weyergraf <T.Weyergraf at virtfinity.de> wrote: > Hi > > I gave the new Xen-4.6rc2 a spin on a CentOS 7 virtualisation guest > (nested-xen). I haven't yet started testing guests, but rather looked at the > install itself. > > One issue, I found, was with xenstored.service and the corresponding > unit-file: > > [root at

Hi, I'm instresting with the PVH mode, is there any wiki available to boot up a PVH guest? I used the following source code to compile the xen and dom0. I have tried adding pvh=1 in xl.cfg file as pv mode, but guest still uses qemu device model. This patch series can also be pulled from this git tree: git://xenbits.xen.org/people/gdunlap/xen.git out/pvh-v15 The kernel code for PVH guests

Hi Debian Grub maintainer, In december, Xen PVH support has been committed in grub master: https://www.mail-archive.com/grub-devel at gnu.org/msg28125.html The last pieces needed in the Linux kernel to boot PVH with grub2 landed in Linux 4.20. I asked our kernel team to carry those patches on top of the Linux 4.19 kernel that is going to ship in Buster, and that wish was granted:

Hey all, We've been on 4.9 for some time now, and while it's still supported, I think it's time to start thinking about upgrading, and I'd like input from the community about which version to move up to. 4.19 has been out for almost 5 months now. It will include PVH domU support, and PVH dom0 support in what _is believed_ to be the final form; so when the Virt SIG moves to a

Hi R-helpers, I'm trying to use this code > pvh_dnv<-pvh[sapply(pvh=="dnv"),] to make a new dataframe containing the rows from pvh that contain the value of "dnv" in ANY column. But, it's not working. I get this error Error in match.fun(FUN) : element 1 is empty; the part of the args list of 'is.function' being evaluated was: (FUN) which, to

Hello, I''ve had a look at PVH support, and I have a few questions: - events are still dispatched the PV way through the callback, right? - I guess FPU errors don''t trigger an INT13, so I don''t need to handle that? - How about the console and store MFNs from the boot info? Are they still MFNs, or actually PFNs? - How about PV network in non-copy mode? It used to be

This patch series is a reworking of a series developed by Mukesh Rathor at Oracle. The entirety of the design and development was done by him; I have only reworked, reorganized, and simplified things in a way that I think makes more sense. The vast majority of the credit for this effort therefore goes to him. This version is labelled v13 because it is based on his most recent series, v11.

On 3/7/19 10:30 AM, Akemi Yagi wrote: > On Thu, Mar 7, 2019 at 9:42 AM George Dunlap <dunlapg at umich.edu> wrote: >> >> Hey all, >> >> We've been on 4.9 for some time now, and while it's still supported, I >> think it's time to start thinking about upgrading, and I'd like input >> from the community about which version to move up to.

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

Hi Colin, Thanks for the quick reply. On 1/5/19 8:04 PM, Colin Watson wrote: > On Thu, Jan 03, 2019 at 01:02:47AM +0100, Hans van Kranenburg wrote: >> In december, Xen PVH support has been committed in grub master: >> https://www.mail-archive.com/grub-devel at gnu.org/msg28125.html >> >> The last pieces needed in the Linux kernel to boot PVH with grub2 landed >>

This information will be mirrored on the Xen 4.4 Roadmap wiki page: http://wiki.xen.org/wiki/Xen_Roadmap/4.4 Our timeline had us start the code freeze last Friday. However, we have not released an RC0 because we have been waiting for PVH dom0 support. Adding bug fixes during RCs makes sense, but RC0 should contain all of the functionality we expect to be in the final release. PVH dom0 support

Hello @ all, i wonder if there is any support for Xen PVH (https://wiki.xen.org/wiki/Xen_Project_Software_Overview) within libvirt. If i parse a xen native domU config file with 'virsh domxml-from-native' in which i set type='pvh' it changes it in the libvirt xml output to normal pv. Also the docs of libvirt do not state something like pvh. I am currently running Xen 4.10.0 with