similar to: dom0 2.6.27 (or more) kernel package for Debian 64 bits

Hi, I just wanted to give a bit of feedback here. i have tried the Xen amd64 kernel from the kernel team and it just crashes with a stack dump on my laptop (thinkpad t500, that is a quite new stuff but will be a common thing very soon I beleive). Then I have tried the kernel 2.6.27 from the Xen repository that you can find here: http://xenbits.xensource.com/ext/linux-2.6.27-xen.hg It's

Hello, I can''t solve my problem. I want a 32 bits Lenny domU into a 64 bits Lenny dom0. I plan to use pygrub for that (xen 3.2.1). So, I tried to debootstrap a 32 bits domU into a 64 bits dom0. debootstrap --arch=i386 --include=libc6-xen,firmware-bnx2,linux-image-2.6.26-1-xen-686,linux-modules-xen-686,linux-image-xen-686,grub --components=main,contrib,non-free lenny /mnt/xen

Hello, More information and a patch for the bug. -- Pasi ----- Forwarded message from George Dunlap <George.Dunlap at eu.citrix.com> ----- From: George Dunlap <George.Dunlap at eu.citrix.com> To: Jan Beulich <JBeulich at novell.com> Cc: Sander Eikelenboom <linux at eikelenboom.it>, Jeremy Fitzhardinge <jeremy at goop.org>, Yunhong Jiang <yunhong.jiang at

Hi, We normally run Lenny dom0 with 384 MB of RAM in our production server. But as we did few trials with Squeeze, I had the very bad finding that a Squeeze dom0 requires at least 1024 MB of RAM. As soon as I do something like "xm mem-set Domain-0 800", my server crashes: OOM starts killing processes, starting with sshd, then mdadm and so on, then the server reboots by itself. This

Hi, We normally run Lenny dom0 with 384 MB of RAM in our production server. But as we did few trials with Squeeze, I had the very bad finding that a Squeeze dom0 requires at least 1024 MB of RAM. As soon as I do something like "xm mem-set Domain-0 800", my server crashes: OOM starts killing processes, starting with sshd, then mdadm and so on, then the server reboots by itself. This

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: important Hi, I set the severity to important as it seems that current xen tools does not allow to load amd64 Debian kernel in DomU. I also put the debian-kernel ML in CC as I'm not sure the problem comes from xen tools or the kernel itself. Here is my configuration: Hypervisor: xen-hypervisor-3.2-1-amd64 3.2.1-2

Package: xcp-xapi Version: 1.3.2-9 Severity: normal Hi guys, Just a couple of things I noticed running through /usr/share/doc/xcp-xapi/README.Debian.gz as referenced by http://wiki.debian.org/XCP In "4/ Configuring Xen and XCP": sed -i "s/TOOLSTACK=/TOOLSTACK=xapi/" /etc/default/xen should be sed -i "s/TOOLSTACK=.*/TOOLSTACK=xapi/" /etc/default/xen Otherwise

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-5.2 Severity: important Tags: patch I have a system based on a Supermicro X8DTH-i motherboard and a Xeon E5506 CPU. It was previously running Debian lenny with xen-hypervisor-3.2-1-amd64 / linux-image-2.6.26-2-xen-amd64 without incident. I upgraded it to Debian squeeze, with xen-hypervisor-4.0-amd64 / linux-image-2.6.32-5-xen-amd64 and now it does

Hello, The email (thread) below from xen-devel mailinglist indicates the changesets that should fix the bug that causes the lenny 2.6.26 xen kernel to crash on newer xen hypervisors. The workaround for this bug has been to use pci=nomsi on the dom0 kernel cmdline, but it would be better to apply the actual fix to the xen kernel in lenny. More information on xen-devel (archives). -- Pasi

I've just done a fresh lenny amd64 install, and taken the xm-debian.cfg example: http://people.debian.org/~joeyh/d-i/images/daily/netboot/xen/xm-debian.cfg and built a 32 bit lenny inside a 64 bit lenny dom0 # xm create -c xm-th2.cfg install=true install-installer=http://people.debian.org/~joeyh/d-i/images/daily/ When I try to boot the domU: # xm create -c xm-debian.cfg it

Hi, we''ll start virtualization with Xen in our company and we''re looking for the right distribution. The most important Servers in DomUs are working with a MS OS (Win2000/2003/2008). I''ve read something about to accelerate Windows with paravirtual drivers in some distributions. Other distributions have specific tools to install and support DomUs. And now I''m

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, I am trying to setup a DomU with linux-2.6.18-xen.hg in order to test Remus on a Debian Squeeze 6.0 / Xen 4.0.1 (2.6.32-5-xen-amd64) Dom0. After applying several patches to the Debian Squeeze Xen packages, I have built the linux-2.6.18-xen.hg, but when I start my DomU, I have got this error message : Error: (2, ''Invalid

Hello, Build: Xen 4.0 rc8 + 2.6.32.10 pv_ops kernel Following the post by Thiago http://lists.xensource.com/archives/html/xen-users/2010-03/msg00913.html and the follow-ups by Boris I succeeded with the build. This box is server only running with Intel C2Duo on a P45 chipset. Starting with Thiago''s kernel config, I removed all sound and MM drivers. My initrd was still 63+ MB. The

Package: xen-3 Version: 3.1.1-1 See the transcript below, where I * dpkg-source -x debian/xen-3_3.1.1-1.dsc * add an entry to debian/changelog at the top * run dpkg-buildpackage, which fails I installed the build-dependencies on sid and lenny and the path it's looking for doesn't exist there either. Thanks, Ian. mariner:d> dpkg-source -x ../debian/xen-3_3.1.1-1.dsc gpg:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I''ve been using xen for a number of years now without issues, but now have a problem. First, the problem: I have a Windows Server 2008 Standard 64bit DomU, I''ve installed a number of applications, and it works quite well and runs stable for weeks at a time so far (ie, has never crashed yet). I tried to install QuickBooks

I''m happy to announce that we have moved the xen-unstable.hg Solaris dom0 development out to the OpenSolaris community. For hard core developers, you can download, build, and run Solaris dom0 and xen-unstable bits following the instructions at the end of this post. We are currently sync''d up to changeset #17644 (~May 15th). Hopefully we will sync up with xen-unstable.hg every

Package: src:xen Severity: important Version: 4.1.3~rc1+hg-20120614.a9c0a89c08f2-2 I recently upgrade from Squeeze to Wheezy on a system which had the xen-linux-system-686-pae metapackage (one of two which Provides: xen-linux-system). After dist-upgrade I had the new xen-utils-common and xenstore-utils (and a few others) but not the xen-utils-4.1 or xen-hypervisor-4.1-i386 or xen-hypervisor-amd64

Hi list, I am starting a academic security related project and I was wondering if there is any documentation on compiling xen/dom0 with a recent kernel? I''ve seen a few good intentioned threads, but no real documentation so far. Any helpful pointers will be greatly appreciated! Thanks in advance, - SDG P.S: First mail, not sure if I should post it here...let me know if I am on the

Author: ultrotter Date: 2006-02-19 18:38:10 +0000 (Sun, 19 Feb 2006) New Revision: 26 Added: trunk/debian/patches/30xenchangeset.dpatch Modified: trunk/debian/patches/00list trunk/debian/patches/10sysconfig.dpatch trunk/debian/rules Log: Add 10sysconfig.dpatch description Add 30xenchangeset.dpatch to make the xen changeset configurable Force the xen changeset to be the correct one

Hello, please can someone on the list point me to the right direction how to build xen0 and xenU kernels for linux-2.6.27-xen.hg? A make world KERNELS="linux-2.6-xen0 linux-2.6-xenU" leads me to the error: select-linux-arch: x86 select-linux-image: cannot determine Linux image to use for x86 in build-linux-2.6.27-xen0_x86_32 cp: missing destination file operand after