[QUOTE=epretorious;12135]…I’ve migrated two PVM’s away from the host system but they persist in Xend even though they are not active on the host; they’re not in XenStore (/var/lib/xenstore/tdb), and; there are no configuration files for the VM’s (in /etc/xen/vm):
xen2:~ # xenstore-ls | grep "name = "
name = "Domain-0"
name = "Pool-0"
pool_name = "Pool-0"
name = "Domain-0"[/QUOTE]
[QUOTE=KBOYLE;12139]Your “xm list” reports oracle1 and oracle2. They are not running therefore they must exist in the XenStore.
To see the configuration of the DomU:
xm list -l oracle1
See here for more information:
Thanks for sharing your article “Managing your Xen DomU: Difference between “xm new” and "xm create”, Ken:
However, I’m more confused than before (because now I see that my understanding of Xend & XenStore is not necessarily correct)!
AFAICT, the xenstore-ls command (above) illustrates that the configuration settings of the PVM’s “oracle1” & “oracle2” do not exist in XenStore. However, as you suggested (above) the xm list command contradicts this:
[CODE]xen2:~ # xm list
Name ID Mem VCPUs State Time(s)
Domain-0 0 502 2 r----- 267.9
oracle1 786 1 211.9
oracle2 786 1 22.8
xen2:~ # xenstore-ls | grep oracle
xen2:~ # xm list -l oracle1
And so does this command:
[CODE]xen2:~ # file /var/lib/xenstored/tdb
/var/lib/xenstored/tdb: TDB database version 6, little-endian hash size 7919 bytes
xen2:~ # strings /var/lib/xenstored/tdb | grep oracle
So I guess that, without any authoritative instructions for the xenstore command, I’m back to Square #1.