The script does return information about 6 and 7. any way to tell the
hypervisor to clear them out?
alpha # ./domstate 6
[{'paused': 1, 'cpu_time': 0L, 'ssidref': 0, 'hvm': 0,
'shutdown_reason': 0, 'dying': 1, 'mem_kb': 4096L, 'domid': 6,
'max_vcpu_id': 1, 'crashed': 0, 'running': 0, 'maxmem_kb': 4096L,
'shutdown': 0, 'online_vcpus': 0, 'handle': [216, 238, 227, 14, 148, 51,
177, 178, 249, 66, 188, 4, 149, 144, 142, 147], 'blocked': 1},
{'paused': 1, 'cpu_time': 0L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason':
0, 'dying': 1, 'mem_kb': 4096L, 'domid': 7, 'max_vcpu_id': 1, 'crashed':
0, 'running': 0, 'maxmem_kb': 4194304L, 'shutdown': 0, 'online_vcpus':
0, 'handle': [216, 238, 227, 14, 148, 51, 177, 178, 249, 66, 188, 4,
149, 144, 142, 147], 'blocked': 1}, {'paused': 0, 'cpu_time':
222810037566L, 'ssidref': 0, 'hvm': 0, 'shutdown_reason': 0, 'dying': 0,
'mem_kb': 4194304L, 'domid': 8, 'max_vcpu_id': 1, 'crashed': 0,
'running': 0, 'maxmem_kb': 4194304L, 'shutdown': 0, 'online_vcpus': 2,
'handle': [216, 238, 227, 14, 148, 51, 177, 178, 249, 66, 188, 4, 149,
144, 142, 147], 'blocked': 1}]
alpha # ./domstate 7
[{'paused': 1, 'cpu_time': 0L, 'ssidref': 0, 'hvm': 0,
'shutdown_reason': 0, 'dying': 1, 'mem_kb': 4096L, 'domid': 7,
'max_vcpu_id': 1, 'crashed': 0, 'running': 0, 'maxmem_kb': 4194304L,
'shutdown': 0, 'online_vcpus': 0, 'handle': [216, 238, 227, 14, 148, 51,
177, 178, 249, 66, 188, 4, 149, 144, 142, 147], 'blocked': 1},
{'paused': 0, 'cpu_time': 223547284066L, 'ssidref': 0, 'hvm': 0,
'shutdown_reason': 0, 'dying': 0, 'mem_kb': 4194304L, 'domid': 8,
'max_vcpu_id': 1, 'crashed': 0, 'running': 0, 'maxmem_kb': 4194304L,
'shutdown': 0, 'online_vcpus': 2, 'handle': [216, 238, 227, 14, 148, 51,
177, 178, 249, 66, 188, 4, 149, 144, 142, 147], 'blocked': 1}]
John Levon wrote:
On Mon, Feb 23, 2009 at 04:12:07PM -0800, Joseph Mocker wrote:
We have encountered a strange problem where "virsh list" is attempting
to look up some non-existent domains.
alpha # virsh list
This can happen occassionally when the hypervisor still thinks a domain
exists. Try running this script (passing 6 and 7):
$ cat ~johnlev/bin/domstate
#!/usr/bin/amd64/python
import sys
import xen.lowlevel.xc
xc = xen.lowlevel.xc.xc()
print "%s" % xc.domain_getinfo(int(sys.argv[1]))
This is always a bug, but I don't know which one it might be. I've not
had a reproducible case of this for quite some time.
regards
john
_______________________________________________
xen-discuss mailing list
[email protected]
