Displaying 20 results from an estimated 1000 matches similar to: "Starting win2k3 hvm on another host."
2010 Apr 13
0
raise VmError(''Creating domain failed: name=%s'' %
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
2016 Jun 26
0
Cannot allocate Memory
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
2016 Jun 24
0
Cannot allocate Memory
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..
>
>
2016 Jun 30
1
Cannot allocate Memory
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
2008 Jun 25
0
domUs doesn''t boot after upgrade to xen 3.2
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''],
2014 Jan 28
1
Can't create new Xen domains using libvirt on CentOS 6.5
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
2009 Mar 12
0
Successfully running VM, subsequently startup gives this error -- VmError: Boot loader didn''t return any data!
Hi
I have configured few VMs with RHEL5,32 bit, but some VMs
after successful stop/restart few times, suddenly they start giving
following error from "xm create vm1.cfg" startup.
----
Error: (''c618d493-a696-7637-333d-bd891fa41ac2'', ''VM_metrics'')
----
If i replace system.img, they starts working again. This is what i see in xend.log file.
This happens
2009 May 27
0
VM start failed - How to debug?
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''],
2010 Feb 02
1
DomU won''t start on 3.4.2
-----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
2016 Jun 22
4
Cannot allocate Memory
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
2009 Mar 21
0
Bug#520641: Cannot create HVM domain
Package: xen-utils-3.2-1
Version: 3.2.1-2
If I try to create an HVM domain I get the following error message:
araminta:~# xm create -c heceptor.cfg
Using config file "/etc/xen/heceptor.cfg".
Error: Creating domain failed: name=heceptor
xend-log has a Python backtrace in it:
[2009-03-21 14:14:46 25927] DEBUG (XendDomainInfo:84)
XendDomainInfo.create(['vm', ['name',
2009 Jun 13
4
Unable to create WinXP DomU
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:
2008 May 28
0
xen-unstable hvm problem
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'',
2010 May 19
0
Hi - Regarding xend - xm create Error
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'',
2009 Sep 30
5
Cant create new VM: Error -> ERROR (XendDomainInfo:445) VM start failed
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
2009 Jan 26
1
Xen+drbd VmError: Block device must have "phy", "file" or "tap" specified to type
Hello List,
i am trying to get xen 3.3.1+ linux kernel 2.6.18 +drbd 8.3.0 working.
Here is my config:
----------------------------------------------
kernel = ''/boot/vmlinuz-2.6.18.8-xenU''
memory = ''128''
root = ''/dev/sda2 ro''
disk = [
''drbd:pgone-disk,sda2,w''
]
name
2009 Apr 17
2
Problems creating hvm guest after dom0 reboot
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
2011 Oct 02
0
Bug#644100: pygrub error if the root disk value is not the first in the list.
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',
2011 Jan 23
1
SETVCPUCONTEXT failed
Hi guys,
I cannot get my domU''s to boot. My current setup is as follows:
Xen: 4.0.1
Dom0: Debian with custom linux 2.6.32.27 Xen kernel
DomU: Same kernel as Dom0
When I try to start the VM, I just get:
Error: (1, ''Internal error'', ''launch_vm: SETVCPUCONTEXT failed (rc=-1)\n'')
And /var/log/xend.log says:
[2011-01-23 15:36:01 3201] DEBUG
2011 Jan 23
1
SETVCPUCONTEXT failed
Hi guys,
I cannot get my domU''s to boot. My current setup is as follows:
Xen: 4.0.1
Dom0: Debian with custom linux 2.6.32.27 Xen kernel
DomU: Same kernel as Dom0
When I try to start the VM, I just get:
Error: (1, ''Internal error'', ''launch_vm: SETVCPUCONTEXT failed (rc=-1)\n'')
And /var/log/xend.log says:
[2011-01-23 15:36:01 3201] DEBUG