similar to: Bug#586729: Xen boot error: ERROR: Unable to locate IOAPIC for GSI

Package: xen-hypervisor-4.0-i386 Version: 4.0.0-2

(I accidently (cross) posted this also in the xen-bugs mailing list. This wasn''t my intention. Sorry for that) Hi, I have two kernels vmlinuz-2.6.32-5-amd64 vmlinuz-2.6.32-5-xen-amd64 As you can see, distributions are the same, the latter differs by loading xen stuff. When booting the xen kernel (vmlinuz-2.6.32-5-xen-amd64) I noticed a problem which does not occur in the non

Is it expected that running btrfsck more than once will keep reporting errors? Below is the end of a btrfsck output when run the second time. backpointer mismatch on [111942471680 32768] owner ref check failed [111942471680 32768] ref mismatch on [111942504448 40960] extent item 1, found 0 Incorrect local backref count on 111942504448 root 5 owner 160739 offset 3440640 found 0 wanted 1 back

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 >

>>> 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 > interrupts. I wonder if these messages from Xen's dmesg are relevant. > (XEN) Not enabling x2APIC: depends on iommu_supports_eim. > (XEN) I/O virtualisation disabled > (XEN) Enabled directed EOI with ioapic_ack_old on! The last one

Processing commands for control at bugs.debian.org: > close 587090 4.1.0~rc6-1 Bug #587090 [xen-utils-4.0] xen-utils-4.0: Exception starting xend ('NoneType' object has no attribute 'rfind') There is no source info for the package 'xen-utils-4.0' at version '4.1.0~rc6-1' with architecture '' Unable to make a source version for version

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

Whoops, wrong recipient. On Thu, Jun 10, 2010 at 05:54:28PM +0200, Bastian Blank wrote: > I'm currently thinking about which version of Xen supporting in Squeeze. > There are two possibilities: 3.4 and 4.0. 3.4 is currently in testing > and unstable, 4.0 is in experimental. > > Xen 3.4 > ======= > Pros > - Proofed to be stable > Cons > - NUMA-mode only opt-in,

On 05/16/2014 06:08 AM, Jan Beulich wrote: >>>> 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 >> interrupts. I wonder if these messages from Xen's dmesg are relevant. >> (XEN) Not enabling x2APIC: depends on iommu_supports_eim. >> (XEN) I/O virtualisation disabled >>

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

From: Ian Campbell <ian.campbell@citrix.com> The zImage compatible binary is the useful one on real hardware. The relocated ELF thing is only really useful when booting directly on Fast Models. The customary suffix for that case is .axf so provide that as a target. Signed-off-by: Ian Campbell <ian.campbell@citrix.com> Cc: Wookey <wookey@linaro.org> --- xen/arch/arm/Makefile |

Package: xen-utils-common Version: 4.4.1-9+deb8u1 Severity: normal With SE Linux it's desirable to give utilities and daemons the minimum privileges. That includes not permitting general utilities to create directories under /var/run. I think it would be best if /var/run/xen-hotplug was created by an init script such as /etc/init.d/xen (or by systemd-tmpfiles when using systemd units).

Ian Campbell <ijc at hellion.org.uk> writes: #Was that with the Jessie or Wheezy dom0 kernel? Actually tried both kernels. 3.13 on Jessie and 3.2 on Wheezy. The keyboard failed on any xen 4.3 boot. If it was nonxen, or xen 4.1 on any kernel the keyboard worked normal. Thanks for your help troubleshooting. Cheers, Mike -------------- next part -------------- An HTML attachment was

# HG changeset patch # User Ian Campbell <ijc@hellion.org.uk> # Date 1354011148 0 # Node ID 3174dc24e3efb0c5b964c244dbfb0218a03a38cf # Parent 541b0e1a36c86db5df04988dd4ade5430776a7f2 xl: xl.conf(5): correct advice re autoballooning vs. dom0_mem. The advice was backwards, you should really disable autoballoon if you use dom0_mem. Also add a reference to the command-line docs.

Hello list, I have performed a fresh install (fully updated) of squeeze amd64 and installed the xen-linux-system-2.6.32-5-xen-amd64 package with all its dependencies. When I restart and tried to boot the linux-image-2.6.32-5-xen-amd64 (pvops style) kernel on bare-metal my laptop boots fine. When I use the hyper-visor on the system with the same linux-image-2.6.32-5-xen-amd64 kernel, it hangs

Hello list, I have performed a fresh install (fully updated) of squeeze amd64 and installed the xen-linux-system-2.6.32-5-xen-amd64 package with all its dependencies. When I restart and tried to boot the linux-image-2.6.32-5-xen-amd64 (pvops style) kernel on bare-metal my laptop boots fine. When I use the hyper-visor on the system with the same linux-image-2.6.32-5-xen-amd64 kernel, it hangs

Hi, "Ian Campbell" <ijc at hellion.org.uk> ?rta 2013-10-22 11:17-kor: > On Tue, 2013-10-22 at 11:52 +0200, PASZTOR Gyorgy wrote: > > When you use xl toolstack, you can't reboot domUs. > > When you switch back to xm toolstack, than reboot works again. > > I think the problem with the debian packaged version is the same as in > > this thread: > >

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.

Source: xen Version: 4.4.1-1 Severity: serious Justification: FTBFS Hello, Your package fails to build from source on Debian autobuilder network. Please check your package build logs at: <https://buildd.debian.org/status/package.php?p=xen&suite=sid> install: cannot stat 'debian/xen-utils-4.4.lintian-overrides': No such file or directory debian/rules.real:201: recipe

On Thu, 2014-05-15 at 12:44 -0700, Mike Egglestone wrote: > FWIW, > I also tried a fresh wheezy install. > Dist-upgraded to Jessie, and installed the xen-hypervisor package. > Then rebooted into the XEN 3.2 kernel that comes with wheezy. > Keyboard still doesn't work. Was that with the Jessie or Wheezy dom0 kernel? Ian.