similar to: Bug#601869: Sorry, but binary only nvidia driver is not supportable under Xen.

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: normal Hello, I've this message in dmesg that I can't understand: [ 4.032472] ------------[ cut here ]------------ [ 4.032521] WARNING: at /build/buildd-linux-2.6_2.6.32-26-amd64-KkHF2p/linux-2.6-2.6.32/debian/build/source_amd64_xen/mm/page_alloc.c:1833 __alloc_pages_nodemask+0x177/0x5f5() [ 4.032590] Hardware name:

This should have gone here and not to #706233. Patch will obviously need rebasing by now... ----- Forwarded message from Ian Campbell <ijc at hellion.org.uk> ----- Date: Fri, 16 Aug 2013 14:56:49 +0100 From: Ian Campbell <ijc at hellion.org.uk> To: 706233 at bugs.debian.org Cc: control at bugs.debian.org Subject: move core dumps to /var/lib/xen/dump X-Spam-Status: No, score=-4.9

Processing commands for control at bugs.debian.org: > unarchive 753358 Bug #753358 {Done: Ian Campbell <ijc at hellion.org.uk>} [xen] pygrub not working when a disk script is in use Unarchived Bug 753358 > reopen 753358 Bug #753358 {Done: Ian Campbell <ijc at hellion.org.uk>} [xen] pygrub not working when a disk script is in use 'reopen' may be inappropriate when a bug

Il 27/04/2011 14:37, Ian Campbell ha scritto: > Which specific revision of qemu-xen-4.1 are you using? I'm using a tarball from http://bits.xensource.com/oss-xen/release/4.1.0/xen-4.1.0.tar.gz It seems Thomas used the tools/ioemu-qemu-xen subdirectory as source for xen-qemu-dm. At a first glance I didn't notice debian/mypatches/add-rules.patch: it adds Rules.mk from the tools

Hi, First of all, thanks for your help. I have made some test with this results debian testing with xen 4.4 can run if we add mmcfg=0 as boot options to kernel boot parameters !!! Remember that with xen kernel <=4.0 works perfect without to add mmcfg=0 I have tried to install citrix xenserver 5.6 and works perfect (remember that this is xen 3 branch) Also we have tried to install xenserver

Control: tag -1 +patch (experimenting with http://www.donarmstrong.com/posts/control_at_submit/ ...) Hi Thomas, I think it is as simple as the following, which works for me with xl and xm. Does it work as you expect/want with xe? Ian. >From 88f10bc8dbf96dd2c32f12259249f8be70fd01a4 Mon Sep 17 00:00:00 2001 From: Ian Campbell <ijc at hellion.org.uk> Date: Thu, 19 Jul 2012 16:19:09

tags 706233 +patch thanks This is somewhat more FHS compliant IMHO. commit 7d171826bc97bf5f3f2019fc32c1ca85b49de7c9 Author: Ian Campbell <ijc at hellion.org.uk> Date: Fri Aug 16 14:54:42 2013 +0100 * debian/patches/tools-core-dump-dir.patch: Switch tools to dumping to /var/log/xen/dump by default. * debian/xen-utils-common.dirs: Ensure /var/lib/xen/dump is created *

Hi Bastian, I had a couple of build failures trying to build the current pkg-xen SVN tree. The following made it work for me... Cheers, Ian. commit e9a08d8d5afa92da73ab09b3ed53dc9f1f084381 Author: Ian Campbell <ijc at hellion.org.uk> Date: Thu Aug 15 17:14:56 2013 +0100 * debian/patches/series: Add new patch * debian/patches/qemu-without-blktap1.patch: Backport upstream patch

Your message dated Fri, 06 Sep 2013 09:09:48 +0100 with message-id <1378454988.3057.2.camel at dagon.hellion.org.uk> and subject line Re: [Pkg-xen-devel] Bug#710522: Problem found has caused the Debian Bug report #710522, regarding xen-hypervisor-4.1-amd64: Boot hang with Linux 3.2+Xen, works with linux 2.6.32+Xen or 3.2 raw to be marked as done. This means that you claim that the problem

Processing commands for control at bugs.debian.org: > forcemerge 587090 588888 Bug #587090 {Done: Ian Campbell <ijc at hellion.org.uk>} [xen-utils-4.0] xen-utils-4.0: Exception starting xend ('NoneType' object has no attribute 'rfind') Unable to merge bugs because: package of #588888 is 'xen-utils-common' not 'xen-utils-4.0' Failed to forcibly merge

On Sun, 2014-06-15 at 13:35 +0200, lee wrote: > Ian Campbell <ijc at hellion.org.uk> writes: > > > On Sun, 2014-06-15 at 11:03 +0200, lee wrote: > >> Hi, > >> > >> how could I get better debugging output from the dom0 kernel? > > > > Either configure a serial console [0] or add "noreboot" to your > > *hypervisor* command

Hello, my latest try : X11 starts up and freeze with a black screen. I've updated the nvidia package to 195.36.31-5. ii nvidia-glx 195.36.31-5 ii nvidia-kernel-2.6-xen-amd64 195.36.31+1 ii nvidia-kernel-2.6.32-5-amd64 195.36.31+2+4+2.6.32-24 ii nvidia-kernel-2.6.32-5-xen-am 195.36.31+1+2+2.6.32-21 ii nvidia-kernel-common 20100522+1 ii nvidia-kernel-dkms

Ian Campbell <ijc at hellion.org.uk> writes: > On Sun, 2014-06-15 at 11:03 +0200, lee wrote: >> Hi, >> >> how could I get better debugging output from the dom0 kernel? > > Either configure a serial console [0] or add "noreboot" to your > *hypervisor* command line, so you can see (and perhaps > transcribe/photograph) the crash before manually

On 18 February 2013 16:32, Ian Campbell <ijc at hellion.org.uk> wrote: > On Mon, 2013-02-18 at 13:51 +0000, Gavin wrote: > > > <stumped! /> > > If the kernel hasn't changed and you are 100% sure the network > configuration before and after the reboot is the same then so am I. > > All I can suggest is to reinstall the previous version of Xen. > Thanks

On Wed, 10 Sep 2014 20:22:54 +0100 Ian Campbell <ijc at hellion.org.uk> wrote: > On Sun, 2014-09-07 at 13:42 +0200, John Keates wrote: > > 1. Rebuild the debian package with a small change > > > > Do your usual apt-sourcing and build-depping, but add the pep target to debian/rules: > > > > (I put it right underneath include debian/rules.defs) > >

On Fri, 2014-05-16 at 11:08 +0100, Jan Beulich wrote: Thanks for taking a look. FYI Mike has since mentioned on the bug report that 4.1 worked. I've asked for logs of Xen 4.1 + Linux 3.13 and Xen 4.3 + Linux 3.13 for comparison. > >>> On 16.05.14 at 10:58, <ijc at hellion.org.uk> wrote: > > So it seems like dom0 is unable to (correctly) bind to some hardware >

Package: xen-utils-common Severity: normal When setting (network-script network-bridge) in the xen config, restarting xen will result in error messages like: /etc/xen/scripts/network-bridge: line 219: brctl: command not found /etc/xen/scripts/network-bridge is part of xen-utils-common which doesnt depend or recommend the bridge-utils package which contains brctl.

On Fri, 2014-09-05 at 13:39 +0200, trenta wrote: > Additional information: > http://lists.xen.org/archives/html/xen-devel/2013-09/msg00584.html This thread suggests that mmconfig might be the issue, in which case does adding "mmcfg=0" to your hypervisor command line help? I'd recommend continuing to pursue this upstream, there are far more experts on the low level aspect of

Package: xen-utils-4.4 Version: 4.4.0-1 Tags: patch grub-xen-host implements the dom0 side of the x86 pv bootloader protocol[0] and is now in unstable. This enables the use of pvgrub2 in preference to the less secure pygrub. The following patch makes the (trivial) change. Once I have a bug number I will add the Closes: and push to a feature/bugNNNN branch. Ian. [0]

Hi Russell, Was there an underlying issue here (e.g. failure to boot or crash?) or were you just concerned by the messages? Are you able to test if this still happens with the 4.1 based hypervisor in Wheezy? Ian.