similar to: pae hypervisor and kernel

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:

Hi, I have several machines using xen-hypervisor-3.2-1-i386 from etch-backports and they recently got upgraded to 20 or 24G RAM. I have seen talk of a limit of a 16G RAM with 32bit PAE Xen and indeed this is what I am seeing. I am guessing there is still no way to get the 32bit hypervisor to see more than 16G RAM, and I must go to 64bit. Can I boot a 64bit hypervisor and still keep the same

Hey there, Earlier today I went to rebuild a Xen0 kernel and my modules_image failed with an error based on the fact that my Xen0 image did not have the standard kernel-image-XXX/linux-image-XXX name format. The error output is at the bottom of this email. Previously it had worked fine, only recently the maintainer (Kel) of the module source added some restrictions to modules.control.in to look

hi, i''m having here the problem with bonding and crcchecksum. So as i read the mailing list the solution is to run ethtool -K eth0 tx off inside domU. So my domU is reachable. All is fine. But after i migrate (live) the domU to another machine the complete domU stopped. Und I also had one time this ugly Zombie thing in xm list and couldn''t reboot the machine (only power

Package: xen-hypervisor-4.0-i386 Version: 4.0.1-2 Severity: normal Hi, Take the following config file (standard lenny kernel and initrd, with some customization for iSCSI root): name = "lenny3" kernel = "vmlinuz-2.6.26-2-686-bigmem" ramdisk = "initrd.img-2.6.26-2-686-bigmem" memory = 100 vcpus = 1 vif = [ 'mac=00:16:3e:00:00:17, bridge=br695,

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

Hi, i''m prepering to upgrade my servers from xen 3.0.3 32-bit to 3.2.1 64-bit. The old system: Debian 4.0 i386 with included hypervisor 3.0.3 (pae) and dom0 kernel. The new systen: Debian lenny amd64 with the included hypervisor 3.2.1 and dom0 kernel from Debian 4.0 amd64. My domUs have a self compiled kernel out of the dom0 kernel of the old system (mainly the dom0 kernel but

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

Hello, I was also hit by this problem. Perhaps it is related to the xen-netback module in the dom0 kernel? Have a look at: http://www.gossamer-threads.com/lists/xen/devel/275548 -- greetings eMHa -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL:

Processing commands for control at bugs.debian.org: > reassign 463121 xen-unstable Bug#463121: xen-unstable non non-pae hypervisor package is not pae Bug reassigned from package `xen-unstable' to `xen-unstable'. > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)

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

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,

Package: xen-hypervisor-3.0-i386-pae Severity: wishlist The description of the package should give hints as to why it is different from xen-hypervisor-3.0-i386. Mike -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686 Locale:

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

Author: tha-guest Date: 2006-03-03 18:08:48 +0000 (Fri, 03 Mar 2006) New Revision: 70 Modified: trunk/xen-3.0/debian/changelog trunk/xen-3.0/debian/control trunk/xen-3.0/debian/xen-utils-3.0.postinst Log: The "Sorry for the step back, but I guess it''s more a 2 steps forwards" commit - Added the xen package again, because we believe there is a valid upgrade

Package: xen-hypervisor-4.0-i386 Version: 4.0.1~rc6-1 Severity: important --- Please enter the report below this line. --- Booting up the Xen Dom0 fails with an error in "i387.c:159" --- System information. --- Architecture: i386 Kernel: Linux 2.6.32-5-686-bigmem Kernel: Linux 2.6.32-5-xen-686 Debian Release: squeeze/sid 500 testing security.debian.org 500

Hello list, I cannot get make-kpkg to build a Xenlinux type kernel into a Debian kernel binary on my Debian Squeeze x86_64 system. I am using GNU/Linux kernel sources tree (2.6.34.4) with Xen patches for this custom kernel. I am trying to use the make-kpkg command to build a working linux-image-2.6.34.4-xen-amd64 package for my system. The sources are vanilla (available from kernel.org) with

Greetings Debian Xen team, I spent a weekend getting 3.0.2-testing building and thought i'd share the love. Manoj and I are already working to update make-kpkg for the new Xen architecture. My repo is at: http://debian.thoughtcrime.co.nz/debian/ I have posted a Breezy-centric howto for this build at: http://debian.thoughtcrime.co.nz/debian/README.txt Hope you enjoy it, and hope we can

Hello all, I downloaded the linux-2.6.16.16.tar.bz2 (www.kernel.org) and xen-3.0.2-src.tgz. I tried on Debian: # tar -xvzf xen-3.0.2-src.tgz # tar -xvjf linux-2.6.16.16.tar.bz2 # cd xen-3.0.2-2 # mkbuildtree ../../linux-2.6.16.16 # cd ../../linux-2.6.16.16 # make menuconfig (I made a basic configuration) # make-kpkg --append-to-version=-686-xen --revision=1.0 -us -uc kernel_image However

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