similar to: [PATCH] XendAPIStore - do not remove non-existent item

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

hi all, why we implement VM_metrics.VCPUs_utilisation as the proportion of all cpu time? Then XenAPI client (xm) can not get the accumulated cpu_time of each vcpu. I recommend we make VM_metrics.VCPUs_utilisation just the cpu_time which is maintained by hypervisor. Then XenAPI client (xm) not only can get the accumulated cpu_time of each vcpu, but also can calculate the proportion by getting

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

I have pulled a recent (today''s) clone of staging/xen-unstable.hg and I get a failure when trying to create a domain with xend/xm. The failure I get is: Error: (''<domain GUID>'', ''VM_metrics'') I have traced the problem down to where the pci = [ ''02:00.0'' ] parameter (which is the value in my case) from my configuration

I tried to start a domain that I knew would fail, as the vbd it would use was already in use. However, Xend entered a state that made xm unusable and I had to restart it: # xm create -c hal2.xm Using config file "./hal2.xm". /usr/lib/xen/bin/xenconsole: invalid option -- 1 Invalid number of arguments Try `/usr/lib/xen/bin/xenconsole --help'' for more information. # xm list

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.

I am trying to upload into R 143 Affymetrix chips onto using R on the NIH Nimbus server. I can load 10 chips without a problem, however, when I try to load 143 I receive a error message: cannot create a vector of 523263 KB. I have expanded the memory of R as follows: R --min-vsize=10M --max-vsize=2500M --min-nsize=10M -max-nsize=50M (as specified in help in R). After running this command the

On 26.09.2014 09:46, ustermann78@web.de wrote: > hello, > > if i start a transient guest doamin via "virsh create abcd.xml" i see an additional libvirt thread and also some open files: > > pstree -h `pgrep libvirtd` > libvirtd───11*[{libvirtd}] > > libvirtd 3016 root 21w REG 253,0 6044 1052094 /var/log/libvirt/libxl/abcd.log > libvirtd

On 02/18/2014 10:45 PM, Jim Fehlig wrote: > Cole Robinson wrote: >> On 02/18/2014 05:12 AM, Kim Larry wrote: >> >>> The thing I found today is that if libvirt uses xend driver, shutdown events >>> are delivered, but if libvirt uses libxl drvier, doesn't show up anything. It >>> seems there are bugs on shutdown event, so I did dig into the libvirt

Hi All I have downloaded the opensource xapi source code. I am not sure what the functins of the follow modules: 1 block_device_io 2 datamodel 3 xiu (I am puzzled by the name "xiu") 4 stats 5 rpc-light 6 rss 7 xb (I think the xapi needs not to talk to xenbus directly) 8 xsrpc (why it writes some "rpc" keys to path of "domain/<domid>" in the

On 10/29/18 11:58 PM, Minjun Hong wrote: > On Tue, Oct 30, 2018 at 4:57 AM Jim Fehlig <jfehlig@suse.com > <mailto:jfehlig@suse.com>> wrote: > > On 10/29/18 12:26 PM, Minjun Hong wrote: > > Hello. > > I want to use libvirt for toolstack of Xen (not XenServer) to set up > Openstack > > system but, > > I'm new to

Cole Robinson wrote: > On 02/18/2014 10:45 PM, Jim Fehlig wrote: > >> Cole Robinson wrote: >> >>> On 02/18/2014 05:12 AM, Kim Larry wrote: >>> >>> >>>> The thing I found today is that if libvirt uses xend driver, shutdown events >>>> are delivered, but if libvirt uses libxl drvier, doesn't show up anything.

flight 16260 xen-4.2-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/16260/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-i386-i386-xl 5 xen-boot fail REGR. vs. 16228 test-i386-i386-xl-qemuu-winxpsp3 5 xen-boot fail REGR. vs. 16228 test-i386-i386-win 5

Libvirt version as per virsh --version 1.2.2 Xen version as per xl info 4.4.2 I am working with xl toolstack On Mar 30, 2016 11:09 PM, "Jim Fehlig" <jfehlig@suse.com> wrote: > nidhi d wrote: > > When i tried > > > > virsh migrate <vm> xen+ssh://user@remote/system > > > > I get the error > > > > This function is not supported by

----- Am 6. Okt 2020 um 22:52 schrieb Jim Fehlig jfehlig@suse.com: > On 10/6/20 7:55 AM, Lentes, Bernd wrote: >> Hi, >> >> i have a domain (SLES 10 SP4) running with KVM. > > Wow, that's old! I'm surprised time keeping is your only problem :-). It is indeed the only problem. > >> Time is very wrong when booting unless ntp synchronizes. >>

Le lundi 28 septembre 2020 19:04, Jim Fehlig <jfehlig@suse.com> a écrit : > On 9/28/20 5:21 AM, Mathieu Tarral wrote: > > > Hi, > > I'm facing an issue with libvirt and the LIBXL driver, failing when searching for DMI data in /sys. > > info : libvirt version: 5.0.0, package: 4+deb10u1 (Guido Günther agx@sigxcpu.org Thu, 05 Dec 2019 00:22:14 +0100) > > error

Jim, Thanks a lot for your confirmation. Could you also please explain if the issue can be ever fixed, if it's possible to make some patch to fix it? Is it libvirt-specific bug or Libvirt development team rely on some other developers of libxl code...etc? I'm asking because XL tools works fine and I wonder if XL uses the same libxl libraries , doesn't it? Lastly is the issue is going

Hi Michal, thank you for your answer. so if i understand that correctly, no matter if i shutdown or destroy the domain and no matter if it is a transient or an persistent vm, the thread should disappear, right? in my case they still exist, also an hour after i destroy the domain (and don´t start any new one). i use libvirt-1.1.35 on fedora core 20, for information. all the best max    

# HG changeset patch # User Jim Fehlig <jfehlig@novell.com> # Date 1288301229 21600 # Branch xend-pci # Node ID 461b9d3a643a2c67c961d9fc468a804891f3770d # Parent 28a16074681582f1209c9077f870ccf44927133e Fix pci passthru in xend interface used by libvirt Attempting to define or create a domain whose XML config contains a passthru PCI device fails with libvirt xen84: # cat win2k8r2.xml ...

# HG changeset patch # User Jim Fehlig <jfehlig@suse.com> # Date 1360861948 -3600 # Node ID 0f9c7503650fa1b1103b769e1129d66ff614b2ad # Parent cffb489a6df37d8d114e7d2d53a7a85d14e8f968 tools/xend: Only add cpuid and cpuid_check to sexpr once When converting a XendConfig object to sexpr, cpuid and cpuid_check were being emitted twice in the resulting sexpr. The first conversion writes