search for: xen_target_x86_pa

...HOSTCC=$(CC) + $(MAKE) dist DESTDIR=$(CURDIR)/debian/install KERNELS= XEN_PYTHON_NATIVE_INSTALL=1 CC=$(CC) GCC=$(CC) HOSTCC=$(CC) XEN_CHANGESET=$(XEN_CHANGESET) ifeq ($(DEB_BUILD_ARCH),i386) $(MAKE) mrproper - $(MAKE) xen DESTDIR=$(CURDIR)/debian/install KERNELS= GCC=$(CC) CC=$(CC) HOSTCC=$(CC) XEN_TARGET_X86_PAE=y TARGET=$(CURDIR)/xen/xen_pae + $(MAKE) xen DESTDIR=$(CURDIR)/debian/install KERNELS= GCC=$(CC) CC=$(CC) HOSTCC=$(CC) XEN_TARGET_X86_PAE=y TARGET=$(CURDIR)/xen/xen_pae XEN_CHANGESET=$(XEN_CHANGESET) endif $(MAKE) -C tools/examples install-udev DESTDIR=$(CURDIR)/debian/install find $(CURDIR)/...

.../install $(MAKE) dist DESTDIR=$(CURDIR)/debian/install KERNELS= XEN_PYTHON_NATIVE_INSTALL=1 CC=$(CC) GCC=$(CC) HOSTCC=$(CC) XEN_CHANGESET=8743 ifeq ($(DEB_BUILD_ARCH),i386) $(MAKE) mrproper $(MAKE) xen DESTDIR=$(CURDIR)/debian/install KERNELS= GCC=$(CC) CC=$(CC) HOSTCC=$(CC) XEN_TARGET_X86_PAE=y TARGET=$(CURDIR)/xen/xen_pae XEN_CHANGESET=8743 endif $(MAKE) -C tools/examples install-udev DESTDIR=$(CURDIR)/debian/install ... Doesn't then install make three times (one in its debian/stamps/build dependency and the other two in install?) Aren't two of them sufficient (one f...

Hi All, I''ve tried upgrading from 3.0.1 to 3.0.2 on a couple of test servers and had the same strange results on both... In both cases I had a running 3.0.1server, then downloaded the 3.0.2 source. Next, I extracted the files and executed "make XEN_TARGET_X86_PAE=y world". Upon completion I executed "dist/install.sh", changed the grub.conf and rebooted. Once the machines rebooted both began complaining that files in "/etc/rc.d/*" were missing. Various services failed to start because of this as well as networking. Does anyone know...

...adapters and make the bonding inside domU. Or would this cause more trouble (beside the performance loss)? I''m using xen-3.0.1 (stable!?) with two dell poweredge 1850 with two 3.2 GHz Xeons, 8 GB RAM (pae version of xen) and four Intel(R) PRO/1000 as xen hosts. I build xen with make XEN_TARGET_X86_PAE=y world make XEN_TARGET_X86_PAE=y install only modified the kernel config before for my needs (md inside domU) linux-2.6-xen-sparse/arch/xen/configs/xenU_defconfig_x86_32 232c232,242 < # CONFIG_MD is not set --- > CONFIG_MD=y > CONFIG_BLK_DEV_MD=y > CONFIG_MD_LINEAR=m > CONFIG_M...

...ile making mdadm --grow inside domU only the size og the raid goes up but no rebuild. Any help would be appreciated. I''m using xen-3.0.1 with two dell poweredge 1850 with two 3.2 GHz Xeons, 8 GB RAM (pae version of xen) and four Intel(R) PRO/1000 as xen hosts. I build xen with make XEN_TARGET_X86_PAE=y world make XEN_TARGET_X86_PAE=y install only modified the kernel config before for my needs (md inside domU) linux-2.6-xen-sparse/arch/xen/configs/xenU_defconfig_x86_32 232c232,242 < # CONFIG_MD is not set --- > CONFIG_MD=y > CONFIG_BLK_DEV_MD=y > CONFIG_MD_LINEAR=m > CONFIG_M...

I''m currently using the xen-3.0-testing.hg version with the XEN_TARGET_X86_PAE=y complied dom0/hypervisor. I have an HP dl585 with 28GB but the hypervisor boots and says "(XEN) WARNING: Only the first 16 GB of the physical memory map can be accessed...". Xentop shows 16GB. When I boot a RHEL4 2.6.9 hugemem kernel, I can see all 28GB. Any suggestions...

...Are your two computers all SLES9? Thanks, Yongkang You(Kangkang) > >All. > >I am running Xen on an ES7000 system with 4 procs and 4 GB memory. >I am running Suse Sles-9 (32-bit) on the machine. > >I have compiled Xen (the tip on the unstable tree : 6552) with PAE >enabled (XEN_TARGET_X86_PAE=y). >The system boots fine. > >I started xend and when I tried to bring up a virtual machine, the >system gave me the following error on the command line. >On the serial port, I saw an error message (Error pfn) which I have >attached here. > >I was not able to repeat this p...

...xen-3.0-testing.hg/xen/Makefile ---- xen-3.0-testing.hg.old/xen/Makefile 2006-02-16 23:44:09.000000000 +0100 -+++ xen-3.0-testing.hg/xen/Makefile 2006-02-18 17:05:59.803870888 +0100 -@@ -27,6 +27,13 @@ - - install: $(TARGET).gz - [ -d $(DESTDIR)/boot ] || $(INSTALL_DIR) $(DESTDIR)/boot -+ifeq ($(XEN_TARGET_X86_PAE),y) -+ $(INSTALL_DATA) $(TARGET).gz $(DESTDIR)/boot/$(notdir $(TARGET))_pae-$(XEN_FULLVERSION).gz -+ ln -f -s $(notdir $(TARGET))_pae-$(XEN_FULLVERSION).gz $(DESTDIR)/boot/$(notdir $(TARGET))_pae-$(XEN_VERSION).$(XEN_SUBVERSION).gz -+ ln -f -s $(notdir $(TARGET))_pae-$(XEN_FULLVERSION).gz $(DESTDI...

Hello xen-users, I have two days (or rather nights) ago start to play with xen. I have quite old laptop without PAE support, so when I try to install xen 3.1.0 there was error saying, that I cannot run PAE-enabled kernel on PAE-less processor. So I build and install PAE-disabled kernel (for dom0), but I can''t find the way to turn off PAE i XEN micro-kernel. Is there any manner to change

I edited the line as "kernel /xen-3.0.gz hvm_debug=1" I did not *see* any HVM_DBG_LOG messages .I was of course looking for the ones in "vmx_do_msr_read" function in vmx.c I issued "dmesg" and "xm dmesg" in both guest and host OS. Any ideas why this is not working? Regards Shobha Ranganathan "The significant challenges we face cannot be

I wanted to install Xen on 32bit processor with 8GB RAM. I am running Debian on it. The general Kernel can only address ~4GB of RAM. So, Is it necessary to install BigMEM kernel so that all the memory get addressed? And then install xen kernel. Or ?? Suggestions welcome. Thanks, gorkhe _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

...debian/stamps/build rm -rf debian/install $(MAKE) dist DESTDIR=$(CURDIR)/debian/install KERNELS= XEN_PYTHON_NATIVE_INSTALL=1 CC=$(CC) GCC=$(CC) HOSTCC=$(CC) +ifeq ($(DEB_BUILD_ARCH),i386) + $(MAKE) mrproper + $(MAKE) xen DESTDIR=$(CURDIR)/debian/install KERNELS= GCC=$(CC) CC=$(CC) HOSTCC=$(CC) XEN_TARGET_X86_PAE=y +endif $(MAKE) -C tools/examples install-udev DESTDIR=$(CURDIR)/debian/install find $(CURDIR)/debian/install -name ''*.pyc'' | xargs rm mkdir -p debian/install/etc/xen/sv debian/install/etc/xen/xend/server Modified: trunk/debian/xen-hypervisor-pae.install =================...

Dom0 = centos 5 (32bit), 4GB Ram DomU = centos 5 (PV) (32bit) xen 3.1.2 rc1, compiled using XEN_TARGET_X86_PAE=Y kernel 2.6.18, modified to load areca card drivers initrd image created using the following command mkinitrd -v -f --with=aacraid --with=arcmsr --with=sd_mod --with=scsi_mod initrd-2.6.18-xen.img 2.6.18-xen When i issue xm create for a domU which was working earlier i get the following error...

...his using a single drive on the target), and runs a default config of IET, i.e. ''yum -y install scsi-target-utils ; /etc/init.d/tgtd start''. The config on the initiator needed to reproduce this is default to the best of my recollection. Xen was compiled with ''make world XEN_TARGET_X86_PAE=y vmxassist=n''. /etc/multipath.conf is as follows: defaults { udev_dir /dev polling_interval 2 selector "round-robin 0" path_grouping_policy multibus # getuid_callout "/sbin/scsi_id -g...

Attempting to boot xVM dom0 for the first time on a Toshiba Tecra M2 running 75a. Getting a panic immediately after selecting xVM from the grub menu: panic[cpu0]/thread=f502c020: Processor does not support PAE This is a 2000 MHz Pentium-M, which I thought was PAE-capable.

This patch adds SMP support to the previous version. Since that has not been merged I have included it in this patch. This should apply cleanly to the tip. Below is the text of the original submittal, slightly updated. Attached is a preliminary patch that adds Intel(R) LaGrande Technology (LT) (Safer Mode Extensions - SMX) support to Xen. While there are still several enhancements needed for

...Xen/Linux ================ needs: modify kmap to use update_va_mapping is an important optimization for domains with more than 890MB (CONFIG_HIGHMEM4G). bug: nasty networking issue reported in domU SLES9 guests. x86_32p (PAE for >4GB) Xen/Linux ================================ [ compile with XEN_TARGET_X86_PAE=y ] Nightly snapshot x86_32p install tarballs are now available from the downloads page. Seems stable running dom0 and domU''s, though not widely tested. Needs particular testing on systems with >4GB RAM. Machines with dumb SATA controllers with >4GB may be a particular problem....

All. I am running Xen on an ES7000 system with 4 procs and 4 GB memory. I am running Suse Sles-9 (32-bit) on the machine. I have compiled Xen (the tip on the unstable tree : 6552) with PAE enabled (XEN_TARGET_X86_PAE=y). The system boots fine. I started xend and when I tried to bring up a virtual machine, the system gave me the following error on the command line. On the serial port, I saw an error message (Error pfn) which I have attached here. I was not able to repeat this problem on my Dell Precision 470...