similar to: Xen+drbd VmError: Block device must have "phy", "file" or "tap" specified to type

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

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

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-hypervisor-4.1-amd64 Version: 4.1.4-3 Severity: grave Justification: causes non-serious data loss -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash

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 =

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

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

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

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

Hardware: 2x Intel Xeon Quad-Core 2.33GHz 24GB FBDIMM RAM 2x 2TB HDD in RAID-1 Intel Server Board S5400SF Setup: Arch Linux x86_64 Xen 4.1.2 Grub2 Multiboot Synopsis: I set up a new VM for Debian Squeeze following instructions here: http://www.howtoforge.com/installing-debian-squeeze-6.0-domu-on-centos-5.5-x86_64-dom0. Partitioning & installation completed correctly. When I tried to run the

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

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

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

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

Hi all, I am trying the pci-passthrough on xen 3.3.0. I binded the pci slot to pciback using late binding. But xend fails to allocate this slot to domU. linux-242:/home/xen-3.3.0 # xm create -c pci=08:01.0 /etc/xen/xen3.3_guest1 Using config file "/etc/xen/xen3.3_guest1". Error: [Errno 2] No such file or directory: ''/sys/bus/pci/devices/0000:06:00.0/config''

Hi All: I have run Xen 4.0.1 on my PC ( Intel(R) Core(TM) i7 CPU ) , when I run HVM domain, I found an error: sudo xm create winxp.cfg [2010-11-23 17:00:24 4993] DEBUG (XendDomainInfo:3053) XendDomainInfo.destroy: domid=1 [2010-11-23 17:00:24 4993] DEBUG (XendDomainInfo:2416) No device model [2010-11-23 17:00:24 4993] DEBUG (XendDomainInfo:2418) Releasing devices [2010-11-23 17:00:24 4993]

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

Dear Users, Debian Etch 2.6.18.8-xen from xensource.com with Xen 3.3.0 on AMD64: After i want to start the HVM i get: VmError: fail to assign device(1:0.0): maybe it has already been assigned to other domain, or maybe it doesn''t exist. [2008-10-25 19:59:30 2460] DEBUG (__init__:1072) XendDomainInfo.destroy: domid=5 [2008-10-25 19:59:30 2460] DEBUG (__init__:1072)

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''],

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