similar to: PVHVM example for xen 4.3.1

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, after an debian-update (jessie) the hvm do not start: >xl create mywin7.xm Parsing config from mywin7.xm xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->00000000001a0164 Modules: 0000000000000000->0000000000000000 TOTAL: 0000000000000000->000000003e000000 ENTRY ADDRESS: 0000000000100608 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB

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

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:

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:

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:

Hi Linus, These patches make it possible to inhibit the Xen emulated device unplug on the kernel command line (mostly "Just In Case") and renames xen_emul_unplug=ignore to the clearer xen_emul_unplug=unnecessary. Since it changes the name of a command line option we''d like to get it in before 2.6.36 proper. The third changeset is a pure cleanup which you could ignore for

Hello users, I have a problem when I save/restore a PVHVM guest. I installed xen-4.1.2 on my server. And I run a PVHVM guest on LVM. And my PVHVM guest is ubuntu-12.04.2-desktop. Actually when I save a machine, it acts fine. (Of course, when I saved it, There were some processes like movie player) But, When I restore it, It seems more slow. Additionally, machine finally die after a while. I

Dear Xen-Team, after an debian-update (jessie) the hvm do not start: I'm not sure it's a bug or a support-question? If it's a bug I don't know which packet is affected. <http://www.dict.cc/englisch-deutsch/affected.html> I get now response on mailing lists so it look looks like bug fore me. The hvm works fine until I did 'apt-get upgrade' ( I think on Aug 9).

kernel use callback linked in panic_notifier_list to notice others when panic happens. NORET_TYPE void panic(const char * fmt, ...){ ... atomic_notifier_call_chain(&panic_notifier_list, 0, buf); } When xen aware this, it will call xen_reboot(SHUTDOWN_crash) to send out an event with reason code - SHUTDOWN_crash. xen_panic_handler_init() is defined to register on panic_notifier_list but

kernel use callback linked in panic_notifier_list to notice others when panic happens. NORET_TYPE void panic(const char * fmt, ...){ ... atomic_notifier_call_chain(&panic_notifier_list, 0, buf); } When xen aware this, it will call xen_reboot(SHUTDOWN_crash) to send out an event with reason code - SHUTDOWN_crash. xen_panic_handler_init() is defined to register on panic_notifier_list but

kernel use callback linked in panic_notifier_list to notice others when panic happens. NORET_TYPE void panic(const char * fmt, ...){ ... atomic_notifier_call_chain(&panic_notifier_list, 0, buf); } When xen aware this, it will call xen_reboot(SHUTDOWN_crash) to send out an event with reason code - SHUTDOWN_crash. xen_panic_handler_init() is defined to register on panic_notifier_list but

Checked out the latest unstable version of Xen 4.4 but failed to create a PVHVM domU Configured Xen with ./configure --prefix=/usr DomU config file: name = "pvhvm" builder=''hvm'' device_model = ''qemu-xen'' memory = ''512'' vcpus = ''4'' pae=1 acpi=1 apic=1 vif = [ ''mac=00:16:3E:51:20:8C, bridge=xenbr0,

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

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

On 19/06/13 14:33, Jeroen van der Ham wrote: > > On 19 Jun 2013, at 14:20, Roger Pau Monné <roger.pau@citrix.com> wrote: >> That''s because Justin recently pushed a commit that changed the ad >> translation to ada, you should change your /etc/fstab to ada0p2. It''s >> commit 526f3ad11acb296481215d7c2915b3f30f1844f6. > > > Ah, you may want

Hello, While testing Fedora 16 Xen PVHVM guests I noticed the following problem: When starting F16 PVHVM guest I can see the vifX.0 and tapX.0 interfaces appear on dom0, but after the guest kernel (Linux 3.1.0) starts and loads PVHVM drivers the vif/tap interfaces disappear from dom0.. so the bridge in dom0 doesn''t have any vifs/taps connected to it anymore. Has anyone seen that

Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> diff --git a/arch/x86/pci/xen.c b/arch/x86/pci/xen.c index 492ade8..d99346e 100644 --- a/arch/x86/pci/xen.c +++ b/arch/x86/pci/xen.c @@ -374,7 +374,7 @@ int __init pci_xen_init(void) int __init pci_xen_hvm_init(void) { - if (!xen_feature(XENFEAT_hvm_pirqs)) + if (!xen_have_vector_callback ||

Hi List, I'm trying to work out the balloon driver on CentOS6 HVM but it seems to be not working with default 2.6.32 or newer 3.4 kernel. Does balloon driver work on HVM linux guests with Linux Kernel 3.4 from centos repo ? PV is fine and is able to balloon. My host is Xen 4.1.2 with dom0 as 3.4.46-8.el6.centos.alt.x86_64 My guest is CentOS6.4 with kernel 3.4.46-8.el6.centos.alt.x86_64

On Wed, 2013-05-01 at 04:42 +0100, Jim Fehlig wrote: > David Scott wrote: > > Hi, > > > > [added xen-devel: FYI this is about how to properly set the libxl > > device_model_version when the user has provided a manual device_model > > override (aka a path to a qemu) in the libvirt domain XML.] > > > > On 30/04/13 16:10, Jim Fehlig wrote: > >>