similar to: [PATCH]xend: fix dual destroy

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

If list is searched and item not found, then don''t attempt to delete the item. I''ve seen this bug manifest as xen81:~/bin # xm li Name ID Mem VCPUs State Time(s) Domain-0 0 3151 16 r----- 1240.8 pxe 3 256 1 -b---- 26.4 xen81:~/bin

Hi all, Here is our weekly test report for Xen-unstable tree: 3 new issues were exposed, and 6 old issues got fixed. Due to bug #1304 (qcow issue of ioemu-remote), our testing is based on ioemu. New issues: ============================================== 1. With ioemu-remote, guest cannot be created with qcow image. http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1304. 2. Domain0 will

Hi, I have a 3 columns data and need to generate a vector of counts. These counts are the number of rows that are contiguous. It looks easy for manual counting, but to turn it algorithmic really split my head. For example, 11 (i.e. 18004 to 180014), 1 (i.e., 18017), 7 (i.e., 18060 to 18064) 18004 10314568 0.5205757 18005 10333837 0.5135572 18006 10566333 0.5111271 18007 10566624 0.8196611

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

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

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

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

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:

I have an installation of 32bit SLES 10.1 on 2 servers in my lab that I just rebuilt. I applied the files from xen-3.1.0-install-x86_32.tgz and broke all the virtman functions. The errors I got indicate some missing python classes, specifically xen.install. I''m not sure why. This is what I get when I try to run virtman from the command line. If I try to run it from yast i get nothing.

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

I''m looking for a suggestion on a good way to hunt down the source of high context switching and mutex contentions... Is dtrace the way to go now, or should I stick with something like lockstat? Russ This is a 5 second interval for mpstat: CPU minf mjf xcal intr ithr csw icsw migr smtx srw syscl usr sys wt idl 16 0 0 1115 1241 206 9095 912 2420 7393 0 12105 68 25

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

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

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

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

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

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