similar to: Problems creating hvm guest after dom0 reboot

Any of you guys ever seen an issue with Xen 4.4 were xm cannot create a guest because of what looks like an issue allocating memory even though xm info shows like 5x the amount of free memory needed? We are still unfortunately still using xm... it's on my list, i know.. We've had this happen on a couple hosts now. Only way to resolve seams to be rebooting the host. I'm going to

Hi everyone, i have a problem on a running xen installation. The server on which the following problem occurs manages 7 VMs at the moment. Now I wanted to create a new one. After sending the xm create command I get the following error: Using config file "/etc/xen/de-smartnet-asterisk". Error: Creating domain failed: name=de-smartnet-asterisk In my xend.log I can find the following

We're using the stock configuration, the dom0 is limited to 1024MB via grub. ------ Original Message ------ From: "Pasi K?rkk?inen" <pasik at iki.fi> To: "Shaun Reitan" <shaun.reitan at ndchost.com>; "Discussion about the virtualization on CentOS" <centos-virt at centos.org> Sent: 6/26/2016 9:30:57 AM Subject: Re: [CentOS-virt] Cannot

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello. I''m having a quite big problem with xen and I''m pretty much stuck with it by myself, so hopefully someone can help me out with this. Symptoms look like this: tvsrv1:~# xm create ns1 Using config file "/etc/xen/ns1". Error: Creating domain failed: name=ns1 And relevant parts from the xend.log: [2010-02-02 11:35:18

Hi, Since a week or two I can''t create two of my three WinXP DomU''s anymore, the third one starts just fine. This is the basic error message I get: # xm create WinXPViaLilaGeert Using config file "./WinXPViaLilaGeert". Error: Creating domain failed: name=WinXPViaLilaGeert There is little information in this error message. /var/log/xen/xend.log has a little more:

Hello, I''m using Xen (installed from source - "hg clone http://xenbits.xen.org/xen-4.0-testing.hg") on Debian Lenny. Dom0 kernel is 2.6.32-bpo.5-xen-686. Until now I have successfully ran the Lucid Ubuntu as domU guest, defining disks as (and also as file:): disk = [''tap2:aio:/home/xen/domains/lucid/disk.img,xvda1,w'',

Hi everyone, I generated my own DomU guest using opensuse''s yast dirinstall and stored it on a seperate iscsi target. I created it as a DomU on my Domain0 (2.6.25.16-0.1-xen kernel) successfully, using the following configuration: name = "vm01-opensuse11-base-LAMP" memory = 256 kernel = "/boot/vmlinuz-xen" ramdisk = "/boot/initrd-xen" root =

I''m newbie Xen-4.1.1 I''m trying to boot DomU with the following configuration. Sometime DomU boot, but sometime boot failed I''m not sure what is the problem. I can attach that image with tap-ctl on Dom0. Does anybody advice me about this problem?? Sincerely * Environment OS : Scientific Linux 6.1 x86_64 Kernel : 2.6.32.43

# HG changeset patch # User Lutz.Dube # Node ID ca2c8c262dbaa6b2521cec60af7cd688dabdf850 # Parent 8992134dcfd0b9e1e86f4111e68a8aa48bd33c3c Values of cpu_weight and cpu_cap are lost after xend restart For managed domains in state ''halted'' I always get default values for cpu_cap / cpu_weight after xend restart. This is because the names of parameters differ between a SXP file to

Hello everyone... I get the following error when i try to creat a virtual machine Error: (4, ''Out of memory'', "xc_dom_boot_mem_init: can''t allocate low memory for domain\n") I''m using Xen under Gentoo, kernel 2.6.32-r1 in a i686 Dual Core AMD Opteron(tm) Processor 290 AuthenticAMD with 16Gb of memory and 4Tb of hard disk. It was a pain to install

Hello, I''ve done an update from xen 3.2 to 3.3. Since 3.3 I can not use my TV-Card anymore. The error message is "Error: pci: 0000:10:0a.0: non-page-aligned MMIO BAR found." lspci shows the card as 10:0a.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Any hints ? Thanks in advance Christoph xm dmesg: (XEN) Xen version 3.3.1-rc1-pre (root@artus.own) (gcc

Hello, we have a strange problem on a fresh install of CentOS 6.5. On the server we want to use Xen to host paravirtualised guests (the system has no hardware virtualization support). To manage the domain we would like to use libvirt. Xen and libvirt are set up as described here: http://wiki.centos.org/HowTos/Xen/Xen4QuickStart http://wiki.centos.org/HowTos/Xen/Xen4QuickStart/Xen4Libvirt When

Hi Keir, Attached patch gets rid of the global attr variable and adds support for NetBSD. Signed-off-by: Christoph Egger <Christoph.Egger@amd.com> -- AMD Saxony, Dresden, Germany Operating System Research Center Legal Information: AMD Saxony Limited Liability Company & Co. KG Sitz (Geschäftsanschrift): Wilschdorfer Landstr. 101, 01109 Dresden, Deutschland Registergericht

Hi,    I''ve been using xVM with no problems since 2009.06 release (centos4/5, rhel4/5, sol10 as guests). This was using the 111a version. Just installed a new server with the 111b version and .... virt-install --nographics -p -r 8192 -n CentOS_48_64_92 -f /dev/zvol/dsk/zm0/vm/CentOS_48_64_92 -l ftp://192.168.101.120/pub/CentOS-48 -w bridge=aggr0 --os-type=linux --os-variant=rhel4

Hi all, I got this error starting a domU Started domain <servername> xen_start_info @ffffffff80837000 shared @m00befea000 @ffffffff80107000=@ffffffffff5fd000 [0x802] xen_start_info: @ffffffff80837000 cr3 0000000000101000 pml4p ffffffff80101ff8 pml4e 0000000000103067 (real 00000004ea4f4067) pgdp ffffff8000103ff0 pgde 0000000000105067 (real

Hi, I''m trying to install a FC 16 PV guest. After installation the guest doesn''t load with: Error: Boot loader didn''t return any data! xend.log: [2011-11-14 18:57:32 32321] ERROR (XendBootloader:214) Boot loader didn''t return any data! [2011-11-14 18:57:32 32321] ERROR (XendDomainInfo:483) VM start failed Traceback (most recent call last): File

Hi all, Today I got problem below and my domU become unresponsive and I should restart the pc to make it running properly again. [ 240.172092] INFO: task kworker/u:0:5 blocked for more than 120 seconds. [ 240.172110] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 240.172376] INFO: task jbd2/xvda1-8:153 blocked for more than 120 seconds. [ 240.172388]

Note: I could simply direct boot the appropriate kernel/initrd to get the alpha1 installation going as always done in the past, but I think this should work. The Debian alpha 1 installer page says it should. Details $ sudo xm create -c wheezytest.cfg Using config file "./wheezytest.cfg". Error: Boot loader didn''t return any data! direct pygrub test run: # pygrub

Hello , everyone I am a newcomer to xen , which i study in recent months . I have deploy the xen-4.1.2 on dell server , centos as dom0 , now , i use the vhd format to be the virtual hard disk , after i execute " xm new ***.cfg" , this vm generate the vm in "xm list" , but when i execute " xm start *** ", "Error: Boot loader didn''t return any data

Hi, I''ve prepared a Ubuntu 10.04 LTS server on a Xen 3.2-1 host running Debian Lenny on kernel 2.6.26-2-xen-amd64. The Ubuntu 10.04 domU is running a 2.6.32-24-server kernel from the Ubuntu repositories, which is (must be :-) ) xen-aware. The domU uses pygrub to boot and it works like a charm. Now I''m trying to deploy this domU on a Xen 3.2-1 host running Debian Etch on kernel