Search results

yes of course. pressing it a 2nd time gave a log entry for it - curiously the 2nd attempt had the fail msg come up first while the first attempt was still spinning. eventually they both went to 'fail' (though the first one might have only failed once I killed it from the cmd line actually..)...

how can this be extended to subusers of the VM in the web interface who are given group control over a collection of VMs? this would be fine if hardware could be removed after it gets stuck in BIOS, but it seems to not be possible, even after CTRL-ALT-DEL (hmm, maybe more hardware can be added...

And how do you shutdown a VM that's stuck waiting for a TFTPboot/failed boot? doesnt the virt bios accept ACPI signals? TASK ERROR: VM quit/powerdown failed - got timeout

aha. I suppose the ultimate issue is rsync cant copy deleted files, even if we can get at the content via /proc/*/fd - no way to drop it in the right place in the filesystem for the migrated container to find without some kinda hacky support in the OpenVZ kernel. Actually Im quite suprised that...

few comments down in that thread I posted on the bug: https://bugzilla.openvz.org/show_bug.cgi?id=2242#c33 more specifically: https://bugzilla.openvz.org/attachment.cgi?id=1886&action=diff

maria has even more links to deleted files in /tmp for some reason (not that it matters, any more than zero is an issue). it's still better than mysql :) however, im not always aware and can't vette every piece of software my customers will run, so migratability could be an issue without this...

in an ideal world of cooperative under-one-person/design's control yes, that'd be great, but I support multiple different customers with various versions of mysql and debian etc etc. It's a big mixed bag. Any proper virtualization/containerization environment can support these disparate servers...