similar to: Xen 3.1.2 on CentOS 5.5 doesn't see all 4 CPUs

Trying to get Xen going on Fedora 9. Xen was installed from the distro RPMs. Xen version is 3.2.0 and the linux-xen version is 2.6.25.3. Xen seems to come up fine, but the system just hangs at the point where booting of Dom0 should start. There is absolutely no output from Dom0. I configured Xen to log to a serial port and captured the output below. Any suggestions on how to continue

Hi all I keep on getting this error when I try and install a Xen guest on a CentOS 5.1 x64 server with Xen installed from the repositories: [root at gimbli ~]# virt-install sdl=0 vnc=0 nographic=0 -v --location=http://intranet/kickstart/cPanel/centos/5.1/32/os/i386/ --ram=256 --file-size=10 --file=/home/vm/vps07.img --name=vps07 libvir: error : configuration file syntax error: expecting an

Hey, It looks like one of the patches that went in Xen 4.1 blows up. This used to work over the weekend, so I can only surmise it is one the three patches. This is with a debug=y build (which has been working nicely for the last month or more). It looks like one of the patches that went in Xen 4.1 blows up. This used to work a day ago - that is c/s 23551 worked nicely. ----- Forwarded message

Hi I''m putting together a Dom0 and three DomU (all Gentoo) with kernel 3.5.7 and Xen 4.1.1. Each Dom has it''s own md (md0 for Dom0, md1 for Dom1 etc). Dom0 works fine so far, however, I''m stuck trying to create DomUs. It appears the xvda1 device on DomU is not created or accessible: Parsing config file dom1 domainbuilder: detail: xc_dom_allocate:

Hi, I try to start a DomU with xm create endian -c and got the following error message Xend has probably crashed! Invalid or missing HTTP status code. I''ve tested the DomU with nearly the same system at VMWare (Windows) and it works normaly, but on my server I get this error message. I useing gentoo as Dom0. I tried also a gentoo DomU with the same result. Thanks.

Hi, I have a problematic CentOS XEN server and hope someone could point me in the right direction to optimize it a bit. The server runs on a Core2Quad 9300, with 8GB RAM (max motherboard can take, 1U chassis) on an Intel motherboard with a 1TB SATA HDD. dom0 is set to 512MB limit with a few small XEM VM's running: root at zaxen01:[~]$ xm list Name ID

Hi, I''m trying to boot a PV VM I just installed (following http://wiki.xen.org/wiki/Debian_Guest_Installation_Using_Debian_Installer) without success. My XEN installation is xen-unstable 54c8c9eaee92+ on a Debian unstable machine (x86_64), kernel 3.3.4+. The VM I installed is, again, a Debian unstable x86_64. The installation went smoothly; I used an 8GB file as a disk back-end. I went

Hi, I have a problematic CentOS XEN server and hope someone could point me in the right direction to optimize it a bit. The server runs on a Core2Quad 9300, with 8GB RAM (max motherboard can take, 1U chassis) on an Intel motherboard with a 1TB SATA HDD. dom0 is set to 512MB limit with a few small XEM VM''s running: root@zaxen01:[~]$ xm list Name ID

Hi, I'm geting this message from virt-manager. Server: SuperMicro X8SIL with INTEL X3440 Here is my logs /var/log/dmesg: Bootdata ok (command line is ro root=/dev/md2) Linux version 2.6.18-194.3.1.el5xen (mockbuild at builder10.centos.org) (gcc version 4.1.2 20080704 (Red Hat 4.1.2-48)) #1 SMP Thu May 13 13:49:53 EDT 2010 BIOS-provided physical RAM map: Xen: 0000000000000000 -

When booting a recently compiled Xen 4.2 on Ubuntu 12.04, dom0 crashes. I''ve included a serial console log below. I''ve used: Xen 4.2 unstable rev. 25483, compiled on the same machine. I had to apply the AT_EMPTY_PATH patch from http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to get it to compile. Linux 3.2.0-25, which is the default kernel in Ubuntu''s

In hvm enviroment, acpi failed. why? centos5.1 =================================================== [root@hvm001 ~]# xm dmesg __ __ _____ _ ____ ___ ____ _ ____ \ \/ /___ _ __ |___ / / | |___ \ / _ \___ \ ___| | ___| \ // _ \ \047_ \ |_ \ | | __) |_| (_) |__) | / _ \ |___ \ / \ __/ | | | ___) || |_ / __/|__\__, / __/ | __/ |___) | /_/\_\___|_| |_| |____(_)_(_)_____| /_/_____(_)___|_|____/

Hi, I did a git pull on pv_ops tree this morning and now get a crash when eth0 is started, here is the full boot log: Booting ''Xen 3.4 / Linux 2.6.29-rc6-tip'' root (hd0,0) Filesystem type is ext2fs, partition type 0x83 kernel /xen.gz com1=115200,8n1 console=com1,vga iommu=1 [Multiboot-elf, <0x100000:0x131748:0x8e8b8>, shtab=0x2c0078, entry=0x100000] module

Hi, I''ve not tried pv_ops for a long time but just got a new system (Supermicro X9DRL-iF) so decided to try 3.5.0 with the latest Xen 4.2-unstable, unfortunately the system crashes immediately after loading dom0: traps.c:486:d0 Unhandled invalid opcode fault/trap [#6] on VCPU 0 [ec=0000] I''ve tried loading both bzImage and vmlinuz (gzip compressed vmlinuz) with the same

Today is my day! This is with Xen 4.4 (pulled today) when I build a kernel in dom0 and have two guests launching at the same time. This is what I get: (XEN) Assertion ''l1e_get_pfn(MAPCACHE_L1ENT(hashent->idx)) == hashent->mfn'' failed at domain_page.c:203 and it blows up. Here is the full log: \ \/ /___ _ __ | || | | || | _ _ _ __ ___| |_ __ _| |__ | | ___

Hi all, I have a following problem: - Remus network buffering doesn''t work. It seems to be because of no vif is reported by the function server.xend.domain on line 29 of /usr/local/lib/python2.7/dist-packages/xen/remus/vm.py (seen using pdb) : 27 if domid: 28 try: 29 self.dominfo = server.xend.domain(domid, ''all'') >

If you compiled your kernel and booted under Xen and got: (XEN) *** LOADING DOMAIN 0 *** (XEN) elf_parse_binary: phdr: paddr=0x1000000 memsz=0x9db000 (XEN) elf_parse_binary: phdr: paddr=0x1a00000 memsz=0xa30f0 (XEN) elf_parse_binary: phdr: paddr=0x1aa4000 memsz=0x13c00 (XEN) elf_parse_binary: phdr: paddr=0x1ab8000 memsz=0x206000 (XEN) elf_parse_binary: memory: 0x1000000 -> 0x1cbe000 (XEN)

Hey I wanted to try my hand at doing some GPU passthrough so on my ASUS M5A97 which in the pass worked with an older BIOS (but said BIOS had issues after S3 suspend) - but with a BIOS the PCI passthrough does not work. That is due to:: (XEN) IVHD Error: Invalid IO-APIC 0xff (XEN) AMD-Vi: Error initialization

This issue I am encountering seems to only happen on multi-socket machines. It also does not help that the only multi-socket box I have is an Romley-EP (so two socket SandyBridge CPUs). The other SandyBridge boxes I''ve (one socket) are not showing this. Granted they are also a different model (42). The problem is that when I run ''perf top'' within an SMP PVHVM guest,

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

Hi all, All of a sudden my xend is crashing, when i do "xm create domu" due to which the domains are created in paused state. Iam using minios as domU kernel, but the problem occurs even for linux-2.6.18.1 pv kernel as domu kernel. xend.log shows [2008-07-31 03:00:54 14821] CRITICAL (SrvDaemon:231) Xend died due to signal 11! Restarting it.... after doing some preliminary