similar to: Re: Xen and PAE

I have recently discovered when trying to configure a new domU that pygrub is completely broken. That is, the missing Build-Depend on e2fslibs-dev in xen-3.0 causes the ext2/3 python module to not be build. Consequently, using pygrub fails miserably since the filesystem cannot be read at all by pygrub. Additionally, it is apparently not possible for pygrub to find its library directory without

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

Processing commands for control at bugs.debian.org: > reassign 469811 linux-2.6 Bug#469811: xen-hypervisor-3.0.3-1-i386-pae: kernel BUG at drivers/xen/core/evtchn.c:481 Bug reassigned from package `xen-hypervisor-3.0.3-1-i386-pae' to `linux-2.6'. > forcemerge 410807 469811 Bug#410807: linux-2.6/etch xen support - kernel BUG at drivers/xen/core/evtchn.c:481 Bug#469811:

> > ---------- Mensaje reenviado ---------- > From: Roberto C. Sánchez <roberto@connexer.com> > To: shorewall-users@lists.sourceforge.net > Date: Fri, 4 Jul 2008 18:52:36 -0400 > Subject: Re: [Shorewall-users] Shaper > On Fri, Jul 04, 2008 at 04:47:31PM -0500, RokeFeler wrote: > > Saludos, Tengo 3 inferfaces eth0, eth1, eth2 > > eth0 - Net > > eth1 -

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-4 Severity: critical Justification: breaks the whole system Hi! the error suddenly appeared when creating a domU using xm create <name> on our etch server The server freezes and isn't accessible via console/ssh anymore. The server is a Dell PowerEdge 2900 with 2 Quad-Core Xeon E5335 and 8Gb memory. pc307005:~# xm create -c

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-2 Followup-For: Bug #423006 FYI, I experience the very same problem here. The machine reboots immediately after the error... I had to reboot outside xen to standard Linux kernel, and then it works... Hope this helps -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500,

Greetings, There is a very old bug report [0] still floating around asking for a configuration check before restarting on upgrade. While this may not have been possible in the past, would it be possible now with Shorewall-perl? Regards, -Roberto [0] http://bugs.debian.org/200573 -- Roberto C. Sánchez http://people.connexer.com/~roberto http://www.connexer.com

------------------------------------------------------------------------ Shoreline Firewall http://www.shorewall.net/ January 9, 2009 press@shorewall.net ------------------------------------------------------------------------ Subject: Public unveiling of logo design competition submissions The Shorewall developers are pleased to

------------------------------------------------------------------------ Shoreline Firewall http://www.shorewall.net/ January 9, 2009 press@shorewall.net ------------------------------------------------------------------------ Subject: Public unveiling of logo design competition submissions The Shorewall developers are pleased to

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-2 Severity: critical Justification: breaks the whole system I use Debian Sid and Xen 3.0.3-1, and recently after an apt-dist upgrade, i reboot my server and now when i restart the server, i receive these error : /bin/sh : error while loading shared library libcrypt.so.1 cannot open shared object file :no such file ... I reboot the

Package: xen-hypervisor-3.0.3-1-i386-pae Version: 3.0.3-0-2 Severity: normal If quagga is running, and I start & stop a domain, the VIF interface doesn't go down properly (in addition to other problems). Here's what I do: 1. Boot the computer. By default, quagga is running (zebra + ospfd). 2. xm create test7.cfg, wait until the domU starts. 3. xm shutdown test7, wait until the domU

Shorewall 4.0.15 is now available from shorewall.net, SourceForge and Debian Sid. Additionally, I have updated my Debian Etch repository with 4.0.15 packages. Problems Corrected in Shorewall 4.0.15. 1) Beginning with iptables version 1.4.1, the syntax for commands using the conntrack module has changed. Shorewall now detects if the installed version of iptables requires the new

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

Hi, Did I get it right or is it a confusion in my mirrors, that the change from linux-image-2.6.18-3-xen-686 to linux-image-2.6.18-4-xen-686 also changed the PAE mode of the Kernel? After installing this new version and and changeing the kernel in a domU config, I get: Error: (2, 'Invalid kernel', 'xc_dom_compat_check: guest type xen-3.0-x86_32p not supported by xen kernel,

> Hello, > > I'm booting linux-3.16-686-pae kernel (32-bit) via syslinux.efi 64-bit version. > After boot linux sees only 2.5G of RAM while system has 32G installed. > > If I boot the same kernel with GRUB64 efi instead of syslinux > then amount of RAM available to linux is 32G. > > Is this a bug or I'm missing something? > > syslinux.cfg: > >

On Sat, Nov 21, 2015 at 1:04 AM, Andrey Plankin via Syslinux <syslinux at zytor.com> wrote: > Hello, > > I'm booting linux-3.16-686-pae kernel (32-bit) via syslinux.efi 64-bit version. > After boot linux sees only 2.5G of RAM while system has 32G installed. Why not use a 64-bit kernel with such a large machine? Do you have the config used to build that kernel? I'm

2015-11-26 16:39 UTC+01:00, Ady via Syslinux <syslinux at zytor.com>: > >> On Sat, Nov 21, 2015 at 1:04 AM, Andrey Plankin via Syslinux >> <syslinux at zytor.com> wrote: >> > Hello, >> > >> > I'm booting linux-3.16-686-pae kernel (32-bit) via syslinux.efi 64-bit >> > version. >> > After boot linux sees only 2.5G of RAM

Hi Konrad, Does this look at all familiar? There is some more info in the full bug log at http://bugs.debian.org/637234 . In particular, contrary to the message below, the user subsequently confirmed that the issue appears to be Xen specific (doesn''t happen on native or vmware) and that it arose between 2.6.39-2-686-pae and 3.0.0-1-686-pae. Could it be related to edf6ef59ec7e

> On Sat, Nov 21, 2015 at 1:04 AM, Andrey Plankin via Syslinux > <syslinux at zytor.com> wrote: > > Hello, > > > > I'm booting linux-3.16-686-pae kernel (32-bit) via syslinux.efi 64-bit version. > > After boot linux sees only 2.5G of RAM while system has 32G installed. > > Why not use a 64-bit kernel with such a large machine? > > Do you have

Hi all, Would it be possible to include support for a non-pae capable machines on the demo cd. The 3.0 version worked but the 3.0.3 version fails with Cannot execute PAE-enabled kernel on a PAE-less CPU! (Please CC me since I am not subscribed to the list) Thanks, -- Adriaan Peeters _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com