I installed Fedora Core 7 as a domU via "virt-install". In playing around with adding ZFS devices via iSCSI, we managed to bork the config file. We want to destroy the guest and try again. However, we can''t. "virsh destroy" and "xm destroy" both left it present according to "virsh list", and it survived across dom0 reboots as well. I would suppose that the framework used by "virt-install", which puts things off in /var/lib/xend, is used to restart guests if and when the dom0 reboots. Very handy, but not in this case! Is this framework documented anywhere, and how can I manually disassemble a "stuck" domU? We finally moved the /var/lib/xend/domains/UID directory out of the way and that did the trick, but I suspect there''s still an entry in some DB somewhere that I''d like to zap. Where is it, please? Mike O''Brien
Mike O''Brien wrote:> We want to destroy the guest and try > again. However, we can''t. "virsh destroy" and "xm destroy" both > left it present according to "virsh list", and it survived > across dom0 reboots as well.''virsh undefine'' permanently removes a guest. Evan
Mike O''Brien wrote:> I installed Fedora Core 7 as a domU via "virt-install". > In playing around with adding ZFS devices via iSCSI, we managed > to bork the config file. We want to destroy the guest and try > again. However, we can''t. "virsh destroy" and "xm destroy" both > left it present according to "virsh list", and it survived > across dom0 reboots as well. I would suppose that the framework > used by "virt-install", which puts things off in /var/lib/xend, > is used to restart guests if and when the dom0 reboots. Very > handy, but not in this case! > > Is this framework documented anywhere, and how can I manually > disassemble a "stuck" domU?did you try xm delete? Can you reproduce the problem?> We finally moved the /var/lib/xend/domains/UID directory > out of the way and that did the trick, but I suspect there''s still > an entry in some DB somewhere that I''d like to zap. Where is it, > please?That should do it. That''s the only state kept across reboots of dom0. MRJ> Mike O''Brien > _______________________________________________ > xen-discuss mailing list > xen-discuss@opensolaris.org
On Wed, Apr 16, 2008 at 02:07:07PM -0700, Mike O''Brien wrote:> Is this framework documented anywhere, and how can I manually > disassemble a "stuck" domU?virsh undefine regards john
On 16 Apr 2008, at 10:07 pm, Mike O''Brien wrote:> I installed Fedora Core 7 as a domU via "virt-install". > In playing around with adding ZFS devices via iSCSI, we managed > to bork the config file. We want to destroy the guest and try > again. However, we can''t. "virsh destroy" and "xm destroy" both > left it present according to "virsh list", and it survived > across dom0 reboots as well. I would suppose that the framework > used by "virt-install", which puts things off in /var/lib/xend, > is used to restart guests if and when the dom0 reboots. Very > handy, but not in this case!"virsh undefine".