similar to: Bug#520641: Cannot create HVM domain

-----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

Hello List, when i try to create a domU i get: xm create www1.cfg Using config file "/etc/xen/www1.cfg". Error: Creating domain failed: name=www1 Error Log: ---------------- [2009-05-27 15:00:31 5237] DEBUG (XendDomainInfo:92) XendDomainInfo.create([''vm'', [''name'', ''www1''], [''memory'', ''1024''],

Hi, I am able to get Xend running on Fedora 8 but when I try to create any VM it fails. The xm create osc.cfg throws following error - [root@asds174 vm_images]# xm create osc.cfg Modified arg=osc.cfg stop3 Using config file "./osc.cfg". group_id=None [''create'', ''osc.cfg''] Stop 1 None [''vm'', [''name'',

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

Package: xen-utils-4.0 Version: 4.0.1-1 Severity: important I'm running a 32-bit Ubuntu 10.04 domU on a 32-bit Debian squeeze dom0. xm create works fine, but whenever I try to reboot this domU it fails with the following traceback in xend.log: [2010-10-23 17:48:58 1679] INFO (XendDomainInfo:2088) Domain has shutdown: name= onini id=2 reason=reboot. [2010-10-23 17:48:58 1679] DEBUG

Hi, I have some trouble to create hvm machines. Xen just tell me that the domain creation failed: # xm create /etc/xen/xenwin2008 Using config file "/etc/xen/xenwin2008". Error: Creating domain failed: name=xenwin2008 The last time i had this error there was some trouble with ne vif line, but the configuration worked perfectly until I had to restart my system (and change the netmask

On Wed, Jun 22, 2016 at 05:45:05PM +0000, Shaun Reitan wrote: > 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

On Wed, Jun 22, 2016 at 6:45 PM, Shaun Reitan <shaun.reitan at ndchost.com> wrote: > 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'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

I am trying to get a vm running on a different host. It fails to start with the error below. Both hosts are running the same software CentOS 5.4 and Xen 3.3.1 any clues as to why it fails would be appreciated. [2009-05-04 15:31:59 3933] DEBUG (XendDomainInfo:89) XendDomainInfo.create([''vm'', [''name'', ''agree-37''],

Xen Version: 4.2.0 Linux Kernel Version: 3.2.30 OS: Debian 6.0 Sometimes when trying to reboot a VM, the reboot fails with the following message in xend.log: Has anyone experienced this issue before, know the cause and/or fix? This is an HVM VM. Device model is set in the configuration file device_model = ''/usr/lib/xen/bin/qemu-dm'' We use the same configuration file with

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

Hello Xen refuses to create domU VM. I have posted some info about my system. Please suggest a solution. gate xen # xm info host : gate release : 2.6.25.5-1.1dom0 version : #24 SMP Sun Aug 31 16:55:27 EEST 2008 machine : x86_64 nr_cpus : 2 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 1 cpu_mhz : 1999 hw_caps : 178bf3ff:e3d3fbff:00000000:00000010:00000001:00000000:00000003:00000000

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 I am trying to install Windows using HVM but I get an error message that is totally useless and I am unable to figure out what the problem is. I just pulled xen-unstable.hg because nothing else supports my CPU yet. So here is what I get when I simply try to create the domain: [2008-05-28 13:55:26 16515] DEBUG (__init_s:1072) XendDomainInfo.create([''vm'',

Package: xen-utils-4.0 Version: 4.0.1-2 If you reboot with the DomU disk DRBD domain destroy. pygrub error when trying to run a image on DRBD device My config DomU ------------------------------------------------------ bootloader = '/usr/lib/xen-default/bin/pygrub' vcpus = '1' memory = '256' cpus="8-15" root = '/dev/xvda2 ro' #disk

Something I''m experiencing here using graphics/vga pass-through with Xen 4....rebooting the domU does not seem to work. I''m running Windows XP, and, when I reboot, the domain appears to just shut down. A look at the xend.log file, however, shows the following entries: [2010-04-15 15:24:15 17820] DEBUG (XendDomainInfo:2543) XendDomainInfo.constructDomain [2010-04-15 15:24:15

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:

Hi all, after upgrading from xen 3.0 to xen 3.2 I cannot start my domUs: I get: VmError: Boot loader didn''t return any data! Suggestions? This is the log [2008-06-25 11:24:53 2755] DEBUG (XendDomainInfo:84) XendDomainInfo.create([''vm'', [''name'', ''engtest3.infolan''], [''memory'', ''2048''],

Package: xen-utils-4.0 Version: 4.0.1-2 Severity: normal File: pygrub pygrub error when trying to run a image created by xen-create-image with partitions option. ---------------------------------------------------------------------------------------------------------------------------------------- [2011-10-02 21:36:08 1512] DEBUG (XendDomainInfo:101) XendDomainInfo.create(['vm',