search for: apxeng

I have a 12GB 64-bit Linux HVM guest (CentOS 5.5). When I look at the e820 map in the guest, I see the following: BIOS-provided physical RAM map: BIOS-e820: 0000000000010000 - 000000000009e000 (usable) BIOS-e820: 000000000009e000 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 00000000f0000000 (usable) BIOS-e820:

I wanted to run without 2MB and 1GB EPT pages, so I added "hap_2mb=0 hap_1gb=0" to the Xen grub command line. However I see the following on Xen boot: (XEN) EPT supports 2MB super page. When I bring up a guest I see a non-zero number of 2MB pages in the "xl create" output: xc: info: VIRTUAL MEMORY ARRANGEMENT: Loader: 0000000000100000->000000000017af10 TOTAL:

> > After using 'python sdist', can't you use the tarball (in python/dist) > > in order to create a venv directly? > > I think I will be able to install the python library in the venv using > the tarball. However, won't my liguestfs application require some of > the binaries installed as part of 'make install' for running? I am > trying to not

I am building xen-unstable (23860:a422e2a4451e) on Ubuntu 11.10. I noticed that the "make install" does not create lib entries in /usr/lib/. I see them only in /usr/lib64/. This is causing program like xenpaging to not find the xenctrl library (error while loading shared libraries: libxenctrl.so.4.2: cannot open shared object file: No such file or directory) Is this expected behavior or

Following discussion, and a bit of slip to allow better contributions from those who''ve been away for the Chinese New Year, the plan for 4.1 now looks like this. We intend to go into code freeze at the end of the week, after which patches even for bugfixes will be much harder to get into the tree. We are here: | Feature code freeze | | Bugfixes are allowed provided they are

When booting a recently compiled Xen 4.2 on Ubuntu 12.04, dom0 crashes. I''ve included a serial console log below. I''ve used: Xen 4.2 unstable rev. 25483, compiled on the same machine. I had to apply the AT_EMPTY_PATH patch from http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to get it to compile. Linux 3.2.0-25, which is the default kernel in Ubuntu''s

I am trying to install the libguestfs python bindings in my virtualenv. Since this cannot be done through PIP, I was trying to do the following: https://github.com/libguestfs/libguestfs/commit/fcbfc4775fa2a44020974073594a745ca420d614 To get to building the python dist, I did the following: git clone https://github.com/libguestfs/libguestfs.git git checkout 1.28.5 ./autogen.sh --disable-php

>> I am trying to install the libguestfs python bindings in my >> virtualenv. Since this cannot be done through PIP, > > The PIP problem is https://bugzilla.redhat.com/show_bug.cgi?id=1075594 > Unfortunately we are stuck here because the pypi website still has a > license that we cannot live with (it would have the effect of > assigning all work we upload to them). They

I am running xen-unstable (change log 23842) and linux 3.0 (ubuntu 10.10) on a Lenovo x220. I am having trouble installing ubuntu 11.04 64-bit with the following config file: builder=''hvm'' memory = 1024 name = ''ubuntu'' vcpus = 2 pae = 1 acpi = 1 apic = 1 vif = [ '''' ] disk =

I am running Xen 4.0.1 with a 2.6.18-194.32.1.el5xen CentOS Dom0. I built and installed the Xen binaries from source. The systems boot successfully however I am having issues bring up DomUs. Here is config: name = ''xyz'' memory = 256 vcpus = 1 pae = 1 vnc = 1 vncunused = 1 disk = [ ''phy:/dev/vg1/xyz,hda,w'' ] vif = [

James, I am running Windows 2008 R2 on Xen that is packaged with CentOS 5.4. I installed gplpv_Vista2008x64_0.11.0.238.msi using the falling steps: 1. Turn on testsigning 2. Reboot 3. Install gplpv_Vista2008x64_0.11.0.238.msi 4. Install process requests a reboot at the end. 5. At the end of the subsequent boot, there is a prompt for a reboot again. I

I am running Xen 4.0.1 with a 2.6.18-194.32.1.el5xen CentOS Dom0. I built and installed the Xen binaries from source. The systems boot successfully however I am having issues bring up DomUs. Here is config: name = ''xyz'' memory = 256 vcpus = 1 pae = 1 vnc = 1 vncunused = 1 disk = [ ''phy:/dev/vg1/xyz,hda,w'' ] vif = [