similar to: Unable to create WinXP DomU

Displaying 20 results from an estimated 1300 matches similar to: "Unable to create WinXP DomU"

2009 Aug 13
10
HVM or PV
Hi All, Sorry if this is a stupid question. I am walking into someone else''s xen install, and don''t have access to the host os at the moment. How do I tell just from a domU (with Ubuntu) if it is PV or HVM. I have looked through the forums and documentation and it seems to be very easy to figure this out from dom0, but unfortunately that isn''t possible at the
2013 Mar 05
2
make_dev_physpath_alias
Hello all. I have a supermicro 16 bay box with a LSI 9211-8i card. We use it for temp data storage, and we wanted to try the l4z compression. After updating the source tree to r247839: and doing a make buildworld cycle all works fine. But at boot time we get some warnings. make_dev_physpath_alias: WARNING - Unable to alias gptid/281951f4-a996-11e1-83eb-00259061b51a to enc at
2014 Sep 07
0
Bug#703586: Bug#703586: Xen fails to boot Linux dom0 under UEFI
As an addition to anyone having issues with booting but only getting 1 CPU and a ton of devices that misbehave, check to see if you have an RSDP in Xen and Linux. You should have both (I use xl and not xm): sudo xl dmesg | grep RSDP (XEN) ACPI: RSDP DDA4A000, 0024 (r2 SUPERM) and sudo dmesg | grep RSDP [ 0.000000] ACPI: RSDP 00000000000f0010 000024 (v02 SUPERM) I?m running this on a
2012 Aug 02
1
Problem detecting Sil3124 SATA controllers off of Sandy Bridge northbridge-connected PCIe slots
Hi, We're having some trouble with detection of a couple of Sil3124 SATA controller cards on newer motherboard and processor combos. Specifically, we're running a Supermicro X9SCM-F motherboard (latest BIOS) and Intel E3-1220v2 CPU. What we're seeing: - Syba Sil3124 PCIe cards are only being detected when installed in PCIe Slot 4 -- The motherboard documentation shows that this
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
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 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
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
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
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
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
2010 Oct 24
1
Bug#601271: xen-utils-4.0: domain fails to reboot (AttributeError: 'NoneType' object has no attribute 'getBitSize')
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
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.. > >
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''],
2012 Nov 08
0
Sometimes unable to reboot VM
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
2009 May 04
0
Starting win2k3 hvm on another host.
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''],
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',
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'',
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
2008 Jul 25
1
[PATCH]xend: fix dual destroy
After changeset 18030 and 18064 were checked in, I found some issues when creating HVM domains with devices assigned: In XendDomainInfo.py, we have the call trace: the global function create() => vm.start() => _constructDomain(). In _constructDomain(), we invoke xc.test_assign_device() and when the function fails (maybe because iommu=1 is not specified in grub entry since iommu is 0 by