similar to: No subject

On Fri, 2013-07-05 at 18:33 +0400, darkshvein l wrote: > http://pastebin.com/UFDUpW7r > >XEN) IVHD Error: Conflicting IO-APIC 0x8 entries This rings a bell, although I don't recall the specifics. I suggest you google for it. It's probably also worth ensuring you have the very latest firmware (BIOS) for your system, since ISTR it involves the BIOS provided tables being invalid.

We''ve been looking in to support of 32bit domains on machines with large amounts of RAM. Working from the ballooning and reservation support added a few years ago: http://lists.xen.org/archives/html/xen-devel/2009-11/msg01277.html 32 bit domains eventually fail to boot with the following Xen complaint: xm create: Error: (4, ''Out of memory'', "panic:

xm save lenny3 /tmp/lenny3.save The guest console says: Suspending xenbus... and detaches. Restore the guest (paused to attach its console before continuing): xm restore -p /tmp/lenny3.save xm console lenny3 xm unpause lenny3 The console starts spewing out "BUG: recent printk recursion" and the domain spins until destroyed. The same thing happens on (live or not) migration. The

Processing commands for control at bugs.debian.org: > unarchive 763102 Bug #763102 {Done: Ian Campbell <ijc at debian.org>} [xen-utils-common] xen-utils-common: xen-init-list fails to parse xm output -> cannot shutdown domains with service xendomains Unarchived Bug 763102 > reopen 763102 Bug #763102 {Done: Ian Campbell <ijc at debian.org>} [xen-utils-common] xen-utils-common:

Hi. Package: xen-hypervisor-4.1-amd64 Starting guest VM, after package upgrade: xm create winxp Using config file "./winxp". Error: failed to assign device: maybe the platform doesn't support VT-d, or VT-d isn't enabled properly? If I set up VM properly after few months, but I remember, I met same error only after package upgrade. Pastebin logs, for check my errors: xm info

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

UPDATE: This bug does not reproduce in version: 4.1.4-3 since the domU creation is shadowed by another new bug [1]. Below is my hypervisor log or "xm dmesg" output since the 706543 bug also affects my system: # xm dme (XEN) Xen version 4.1.4 (Debian 4.1.4-3) (waldi at debian.org) (gcc version 4.7.2 (Debian 4.7.2-5) ) Fri Apr 19 11:34:20 UTC 2013 (XEN) Bootloader: GRUB 1.99-27+deb7u1

On Thu, 2013-09-05 at 20:52 +0200, Alessandro Vesely wrote: > Package: xen-hypervisor-4.1-amd64 > Version: 4.1.4-3+deb7u1 > Severity: normal > > I tried GRUB_CMDLINE_XEN="dom0_mem=8192M": that delivers 6964868K total, then > crashes when used=2837436K free=4127432K. > By crash I mean the gnome screen was blown away, replaced by a black screen > with white log

On Fri 06/Sep/2013 10:12:29 +0200 Ian Campbell wrote: > On Thu, 2013-09-05 at 20:52 +0200, Alessandro Vesely wrote: >> >> I tried GRUB_CMDLINE_XEN="dom0_mem=8192M": that delivers 6964868K total, then >> crashes when used=2837436K free=4127432K. > > On a modern dom0 kernel you need to specify the maximum memory as well, > i.e. dom0_mem=8192M,max:8192M

Maybe it should be worth backporting some of what's bellow? Thomas -------- Original Message -------- Subject: [Xen-devel] Backport requests for 4.0 Date: Fri, 17 Dec 2010 17:41:56 +0000 From: Ian Jackson <Ian.Jackson at eu.citrix.com> To: Keir Fraser <keir at xen.org> CC: xen-devel at lists.xensource.com Having searched through the changelogs, these three changesets

Hi all, I''ve successfully installed xen3.3.0 on Linux ubuntu 2.6.27.5 #1 SMP i686 GNU/Linux. I built xen with the requisite XSM_ENABLE=y, ACM_SECURITY=y and believe I have the correct config parameters in the 2.6.27.5 kernel. Boot goes smoothly, set to automatically create 2 domUs. All appears okay with XSM/ACM... root@ubuntu:~# xm dmesg | grep -i xsm (XEN) XSM Framework v1.0.0

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

Hello friends! In this week, i had a problem with Xen version 3.0.2_09749-0.7 on SLES10 for x86, when the initrd-xen file was loaded. On console, various messages about "No space left on device" appears later that the "/dev" was monted on a tmpfs filesystem (for udev). The only sollution for this problem at that moment, was remove the "dom0_mem=192M" and the

Hi, I test pvgrub on xen-3.3.0. After starting pvgrub with "xm cr xmexample.pv-grub", I can see nothing but qemu window. With "xm li" , I can see this domain is running: Name ID Mem VCPUs State Time(s) Domain-0 0 1024 2 r-----

(This is a resend of my earlier message which may still be awaiting moderator approval for size reasons. Please Cc me on replies.) Hi, I'm not sure this is the right forum for messages like this, please redirect me if not. Please also Cc me in either case. Last week I upgraded my Xen HA setup (two hosts) to sqeeze. The upgrade itself was smooth, thanks for the nice work! Also the

Package: xen-hypervisor-4.1-amd64 Version: 4.1.1-3 Severity: important Whenever I try to start a domU, xm create failed for 'Boot loader didn't return any data!'. % sudo xm create -c squeeze.cfg Using config file "/etc/xen/squeeze.cfg". Error: Boot loader didn't return any data! It seems related to the following error in dmesg [1440.163935] pygrub[3654] trap invalid

hi, i red several mails, but didn''t found a real solution. I want to install hylafax in DomU and i need access to /dev/ttyS1. I hide com2 in grub: title Xen 2.0 / XenLinux 2.6.11 kernel /boot/xen.gz dom0_mem=64000 physdev_dom0_hide=''(00:2f.8)'' max_loop=32 module /boot/xen-linux-2.6.11.12-xen0.xen.kernel root=/dev/hda2 ro i used the entries from dmesg: Serial:

Hello, I have installed XCP in Debian following the steps depicted in http://wiki.xen.org/wiki/XCP_toolstack_on_a_Debian-based_distribution . Out of the box, dom0 takes hold of all the available memory, so I cannot start any domU (I''m using XenCenter). If I try to limit the dom0 memory using kernel parameter dom0_mem, it is apparently ignored. Info: # cat /proc/cmdline placeholder

Thank Zhigang Wang for your response. I have test pvgrub with this config file: #pv-config kernel = "/usr/lib/xen/boot/pv-grub-x86_32.gz" extra = "(hd0,5)/boot/grub/menu.lst" memory = 512 name = "ExampleDomain" disk = [ ''file:/var/lib/xen/images/opensuse11-1/disk0,xvda,w'' ] vif = [ "bridge=eth0" ] root = "/dev/sda5 ro" start