similar to: Dependency to the xen kernel

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

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: serious Tags: squeeze Hi there! Upgrading from Lenny to Squeeze left my box with xen-hypervisor-3.2-1-amd64 installed, and I had to "apt-get install xen-hypervisor-4.0-amd64" manually to have it installed after a dist-upgrade. This for sure, isn't the expected behavior. Also, after the dist-upgrade, I did: apt-get

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

Hello, I've been asked to test this, can anyone help me? The platform I would like to test on: - Lenny/amd64 - Intel VT-i (Xen HVM support) I've looked over the various threads and wiki pages on the issue and I thought I would try to summarise it more concisely: dom0 (32 bit): - regular install using Lenny CD, Debian Installer, i386 - install the kernel package from etch,

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Severity: normal Tags: upstream When creating Xen DomU's, at some point xend invokes the oom-killer and the entire machine restarts: Sep 5 12:04:59 arbiter kernel: [259697.101212] __ratelimit: 136 callbacks suppressed Sep 5 12:04:59 arbiter kernel: [259697.101218] xend invoked oom-killer: gfp_mask=0x200da, order=0, oom_adj=0 Sep 5

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: serious After noting that this version supposedly loads bzImage kernels: | xen-3 (3.2.1-2) unstable; urgency=low | | * Use e2fslibs based ext2 support for pygrub. (closes: #476366) | * Fix missing checks in pvfb code. | See CVE-2008-1952. (closes: #487095) | * Add support for loading bzImage files. (closes: #474509) | *

Package: xen-hypervisor-4.0-amd64 Fresh install of squeeze beta amd64 System is a Thinkpad X61s with L7500 CPU Windows 7 is on the box, the Thinkpad tools on Windows 7 say VMX is present Followed the squeeze dom0 instructions at: http://wiki.debian.org/Xen aptitude -P install xen-hypervisor-4.0-amd64 linux-image-xen-amd64 xen-tools mv -i /etc/grub.d/10_linux /etc/grub.d/50_linux update-grub2

Package: xen-3 Severity: important After testing with waldi, he found out that the kernel arch cant be different as the xen-utils. So when using xen-amd64 with xen-utils-i386 the dom'Us wont work. xm create /etc/xen/test2.cfg gets: VmError: (22, 'Invalid argument') Debug: [2008-10-23 18:01:48 4211] DEBUG (XendDomainInfo:84) XendDomainInfo.create(['vm', ['name',

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1~rc3-1 Severity: normal Hi, I upgrade one server from lenny to squeeze, to start testing xen-hypervisor-3.4 and xen-hypervisor-4.0, but it seems to don't work. The error : xm create -c /etc/xen/slhoka.cfg Using config file "/etc/xen/slhoka.cfg". Error: Device 0 (vif) could not be connected. Hotplug scripts not working. The error

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.0-5 Severity: important The hypervisor loads OK but then fails to load my dom0 kernel. I get an erorr message "not an ELF binary" followed after 5s by a hypervisor reboot. /boot/grub/grub.cfg contains: menuentry "Debian GNU/Linux, Xen 3.2-1-amd64, Linux 2.6.22-3-vserver-amd64 (single-user mode)" { set root=(hd0,1)

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: normal *** Please type your report below this line *** Hi, Recently I've experienced some crashes of Xen domU (also debian Lenny, running same kernel as dom0 (linux-image-2.6.26-xen-amd64)). At xm top that domain appears as running, but hogs all CPUs, because this problem has appeared on two identic servers (Supermicro X7SBi,

Processing commands for control at bugs.debian.org: > # reassigning all open bugs reported against versioned xen packages that are no longer in the archive to src:xen > reassign 399073 src:xen 3.0.3-0-2 Bug #399073 [xen-hypervisor-3.0.3-1-i386] xen-hypervisor-3.0.3-1-i386: dom0 crashes with a domU that define more than 6 vdb Warning: Unknown package 'xen-hypervisor-3.0.3-1-i386' Bug

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

Package: xen-utils-3.4 Version: 3.4.0-1 Severity: critical Justification: breaks unrelated software After installing xen-utils-3.4 besides my existing xen-3.2 system, I could not start xend-3.2 anymore. The message I was getting is this: "Failed to initialize dom0 state." As far as I know, xen 3.2 and 3.4 are supposed to be able to live peacefully on the same system. (The

Hello. Which kernel could be used for dom0 together with just-uploaded xen hypervisor 3.2 ? -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part. Url : http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20080123/64b16f1f/attachment.pgp

Package: xen-utils-3.2-1 Version: 3.2.1-2 Severity: grave I tried to start an HVM guest to setup Windows 2003 64 bits entreprise R2, and I spent a long time figuring out that there is no /usr/lib/xen folder by default, and this is where Xen is searching for it's file when using HVM, VNC and all. Doing a simple symlink with ln -s /usr/lib/xen-3.2.1 /usr/lib/xen made it working, if it's not

Subject: xen-hypervisor-unstable-amd64: Post update from 3.2 -> 3.3, initrd which previously worked failes Package: xen-hypervisor-unstable-amd64 Version: 3.3-unstable+hg17961-1 Severity: normal *** Please type your report below this line *** System was running hypervisor 3.2, and domUs were working correctly. System was updated to -unstable (3.3) hypervisor and utils. Unchanged kernel and

Hi, I have three squeeze servers running: ii linux-image-2.6.32-5-xen-amd64 2.6.32-38 Linux 2.6.32 for 64-bit PCs, Xen dom0 support ii xen-hypervisor-4.0-amd64 4.0.1-4 The Xen Hypervisor on AMD64 All three servers have Intel gigabit NICs, but one server uses the e1000e driver and the other two use the igb driver. They've been in production for around 6 months now

package grub-pc tag 505517 patch upstream thanks Le jeudi 13 novembre 2008 09:36:03, vous avez ?crit?: > Hi, > > Willing to try Xen, I installed "xen-linux-system-2.6.26-1-xen-amd64", > which came with a bunch of packages? > > When I tried to boot the corresponding image, I got an error in Grub. > > AFAIK and from what I gathered on the web, the entry

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: grave Tags: squeeze upstream Some newer hardware components (it is unclear what exactly causes the issue) render xen-hyervisor unusable as it crashes immediately after boot for the Debian out-of-box configuration. This results in a system rebooting all over again if the hypervisor is choosen as default stanza to be booted by grub