- got the idea. And noticed the following:
It really removes domain from file system, but why does it throw that error message?
- if i simply destroy domain via vzctl (without undefining it via virsh):
[root alt-03 ~]# vzctl destroy 3005
Destroying container private area: /var/lib/vz/private/3005
Container private area was destroyed
- and then try to create another one (this time via virsh)
virsh # create ovz.xml
libvir: OpenVZ error : operation failed: Already an OPENVZ VM defined with the id '3005'
error: Failed to create domain from ovz.xml
It seems domain is still defined from LibVirt's point of view but actually it doesn't exist any more. It was removed via native OpenVZ tool. In case I try to undefine it:
virsh # undefine 3005
libvir: OpenVZ error : Domain not found
libvir: error : vzctl exited with non-zero status 14 and signal 0
libvir: OpenVZ error : internal error Could not exec vzctl
error: Failed to undefine domain 3005
And from this moment it is imposible to create domain with ID 3005. So how can I obtain a list of already defined domains? And how can it be purged?
7) Is there any way to publish domain's console on a host system so that I can connect via telnet to HW node on some TCP/4567 and get into domain's console?
- yeah, that for sure is true wheh you are on HW node itself. But I need to organize access into domain's consoles from remote mashines. In my case there is no network connectivity between real lan and domains. I believed, this XML definition could help me:
- "The character device acts as a TCP client connecting to a remote server, or
as a server waiting for a client connection
", so when you connect to HW node on some TCP port you get into domain's console. But it seems I got it in a wrong way because is didn't work in case of OpenVZ.
P.S. You can ask ALT-specific questions to me directly.
- thanks, will keep that in mind.