similar to: HEADS UP: PAE patch to be committed

Hi, everyone, I've ported Jake Burkholder's PAE support from -current to the 4.x branch. This has been scheduled to go into the coming 4.9 release. You can get the most recent set of patch files from http://people.freebsd.org/~luoqi/pae-4. If you are interested and have a machine with over 4GB memory, please give it a try. You may also try it just for fun, even if you don't have 4GB

In addition to the network drivers Luoqi provided PAE patches for, I have also backported -current's if_xl driver; it is available at: http://www.silby.com/pae/ Even if you're not running Luoqi's PAE patch, I'd be interested in hearing how it works for you. Thanks, Mike "Silby" Silbersack

Hi, On Sun, Aug 24, 2003 at 07:14:29AM -0400, Brandon S. Allbery KF8NH wrote: > >Synopsis: vmware2 broken on -STABLE, presumably by PAE import >> (..) Your patch makes VmWare2 build, but it doesn't make it work: - VmWare fails to allocate memory (see http://anders.fix.no/test/vmware/1.png and http://anders.fix.no/test/vmware/2.png). - There seems to be something wrong with

If you start to experience problems with ata devices, please direct your report this way. Thanks -lq

Hi all, I got a machine with 8GB of RAM and plenty of disk space. I need gvinum to manage big number of file systems but PAE enabled kernel does not compile modules. I couldn't figure out how to get vinum statically compiled in the kernel if that is the way to go. I am running 6-STABLE. Please advise on how to get PAE kernel and gvinum working together! TIA, Stoyan

Package: xen-hypervisor-3.0-i386-pae Severity: normal Forwarding a problem reported by Nathan Hawkins. > I ran into a problem with the PAE version of the hypervisor. I'm looking at > xen-hypervisor-3.0-i386-pae_3.0.2+hg9611-1_i386.deb from alioth, and I > ran into a problem with PAE being disabled in the binary: > > $ zcat xen-3.0-i386-pae.gz | strings | grep PAE

I thought this might be of interest to the list. I am only running Xen on amd64, so I am not sure how intelligently I can help out. Probably best to CC urs, since I don't imagine he is subscribed to the list. Regards, -Roberto On Wed, Mar 21, 2007 at 07:26:26PM +0100, Urs Thuermann wrote: > I have two separate questions, actually, concerning Xen and PAE: > > Today, I installed

Hi Is there a doc/wiki page which explains, the kind of domu images/appliances/kernels can be run with what type of dom0 kernels(xen_caps). For example : -- Can a 32 bit, non-PAE domU run on 64 bit, PAE dom 0 in PV mode ? (or HVM mode ?) Are there any checks that can be done before doing the migration ? Is there any programmatic way (from python) to find out if the kernel in a domU disk

I ran into a problem with the PAE version of the hypervisor. I'm looking at xen-hypervisor-3.0-i386-pae_3.0.2+hg9611-1_i386.deb from alioth, and I ran into a problem with PAE being disabled in the binary: $ zcat xen-3.0-i386-pae.gz | strings | grep PAE PAE=yes PAE disabled. PAE mode mismatch between Xen and DOM0 (xen=%s, dom0=%s) It should look like: PAE=yes PAE enabled, limit: %d GB PAE

Hello, I am compiling xen 3.3.1 with linux 2.6.18.8 as domain 0. I am able to compile this successfully on a PAE enabled TOSHIBA machine (However having problems with loading graphics drivers but able to boot with runlevel 3). But since the graphics problem could be because of non standard hardware that comes with Toshiba laptop, I tried compiling the same on an IBM laptop . This system does not

Hi, I have just looked at the xen source, because I want to finish my work from yesterday and have the hypervisor-pae really build & packaged. It seems so that we have two possibilities to do this: 1) create another dpatch that would patch xen/Makefile in order to have other filenames for the hypervisor when the pae-flag is set. the advanced would be, that if we use diffrent filenames

On Wed, Mar 6, 2019 at 7:23 AM Mike McTernan (wavemobile) <mike.mcternan at wavemobile.com> wrote: > > On 3/6/19 1:28 PM, Johnny Hughes wrote: > > On 3/6/19 6:26 AM, Mike McTernan (wavemobile) wrote: > > > On 3/5/19 5:48 PM, Johnny Hughes wrote: > > <snip> > > > > Last question, if I may - Is there any specific reason why an i686 PAE > >

hi, first of all, you guys make great work to use xen under debian. I use etch to set up a xen server for later production use and so i try to use as much debian packages without manual adaptations to later use security updates when etch is released. As i have a machine with 16G of ram i need the pae versions of the hypervisor and the linux kernel. But there is only the pae version of the

On 3/6/19 9:49 AM, Akemi Yagi wrote: > On Wed, Mar 6, 2019 at 7:23 AM Mike McTernan (wavemobile) > <mike.mcternan at wavemobile.com> wrote: >> >> On 3/6/19 1:28 PM, Johnny Hughes wrote: >>> On 3/6/19 6:26 AM, Mike McTernan (wavemobile) wrote: >>>> On 3/5/19 5:48 PM, Johnny Hughes wrote: >> >> <snip> >> >>>> Last

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

On 3/6/19 6:26 AM, Mike McTernan (wavemobile) wrote: > On 3/5/19 5:48 PM, Johnny Hughes wrote: >> On 3/4/19 3:39 PM, Mike McTernan (wavemobile) wrote: <snip> > Last question, if I may - Is there any specific reason why an i686 PAE kernel > built from the main RHEL sources isn't in the AltArch i386 os- repo? > > Notably CentOS 6 provided both non-PAE and PAE

On 3/4/19 3:39 PM, Mike McTernan (wavemobile) wrote: > Hi Gurus, > > I've been playing with CentOS 7's AltArch i386 builds with some good results on one machine, but can't get it to boot properly on another with a newer Bay Trail CPU. Previously CentOS 6 i386 worked on both, and that set a legacy I'd like to recreate... > > I *think* the problem is that the 7

I am trying to install dahdi-linux from packages onto an OEL5u3 server which has an old kernel (5.2.6.18_128) and is a PAE variant. As there are no kmod packages now available for this kernel I am having to build them from source packages. I have installed the dahdi-firmware-2.0.0-1_centos5 RPM directly. I have downloaded the following SRPMS dahdi-linux-2.4.1.2-1_centos5.src.rpm

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-2 Severity: minor The package description reads: This version of the hypervisor is built with PAE enabled, in order to support systems with more than 4GB of memory. If you have less than that you should probably choose the non -pae version. That's not entirely true. I tried installing the non-pae version on my ProLiant

I'm not sure if this is a bug, known issue, feature, etc. On my CentOS systems with the PAE kernel installed, package-cleanup behaves as follows: # rpm -q kernel package kernel is not installed # rpm -q kernel-PAE kernel-PAE-2.6.18-92.1.13.el5 kernel-PAE-2.6.18-92.1.18.el5 kernel-PAE-2.6.18-92.1.22.el5 # uname -r 2.6.18-92.1.22.el5PAE # package-cleanup