Displaying 4 results from an estimated 4 matches for "domains_lock".
Did you mean:
domain_lock
2010 Nov 07
0
Problem about RLock when starting VMs in parallel
...subsequent VMs.
In the function of "start" from the class of XendDomain which is in the module of xen.xend.XendDomain, there's a pair of operations acquiring and releasing threading.RLock, which is like following:
def domain_start(self, domid, start_paused = True):
self.domains_lock.acquire()
....
self.domains_lock.release()
The confine of the locked area is quite large, in fact it covers nearly all the function, which would cause most time in the serial scene when I actually call the start interface subsequently in hope that VMs would be parallel started....
2006 May 02
0
Mini-OS and Xend issue
...ns() -> xc.domain_getinfo()
This ends up in
lowlevel/xc/xc.c: pyxc_domain_getinfo()
Strange thing is that can see the last debug print in getDomains before
it called xen_domains() and the last print in xen_domains(). But I
cannot see the next print in getDomains(). Is a locking issue with
"domains_lock" happening somewhere?
Could someone shed some light on this as to how I can move forward in
debugging this issue?
Thanks,
Aravindh Puthiyaparambil
Xen Development Team
Unisys
[2006-05-01 15:25:00 xend.XendDomainInfo] DEBUG (XendDomainInfo:182)
XendDomainInfo.create([\047vm\047, [\047name\0...
2011 Jan 30
0
Stub domains broken in Xen 4.0?
...urn func(*params)
File "/usr/lib64/python2.6/site-packages/xen/xend/server/XMLRPCServer.py",
line 80, in domain_create
info = XendDomain.instance().domain_create(config)
File "/usr/lib64/python2.6/site-packages/xen/xend/XendDomain.py", line
998, in domain_create
self.domains_lock.release()
File "/usr/lib64/python2.6/threading.py", line 138, in release
raise RuntimeError("cannot release un-acquired lock")
RuntimeError: cannot release un-acquired lock
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.c...
2006 Aug 01
18
[Patch] Enable "sysrq c" handler for domU coredump
Hi,
In the case of linux, crash_kexec() is occured by "sysrq c".
In the case of DomainU on xen, Help is occured by "sysrq c" now.
So The way of dumping DomainU''s memory manualy is nothing.
I fix this issue by the following way.
1. Panic is occured by "sysrq c" on both Domain0 and DomainU.
2. On DomainU, coredump is generated in /var/xen/dump (on Domain0).