Hello Andreas,
I can't seem to find anything wrong with your setup. I have a question,
though, once you do onevm saveas does it show in onevm show vm_id like
this?
$ onevm show vm_id
[...]
DISK = [
[...]
SAVE=YES,
SAVE_AS=4,
Andreas,
actually, I think Shankhadeep is right. Does the VM go back to running
after a few minutes in shutdown? If the VM doesn't have the acpid package
installed, it won't shutdown on the shutdown event, thus never going into
the epilog state.
Can you make sure that you have acpid installed?
Sure!
/var/lib/one/config:
AUTH_MAD=ARGUMENTS=--authn
ssh,x509,ldap,server_cipher,server_x509,EXECUTABLE=one_auth_mad
DATASTORE_LOCATION=/var/lib/one//datastores
DATASTORE_MAD=ARGUMENTS=-t 15 -d
fs,vmware,iscsi,EXECUTABLE=one_datastore
DB=BACKEND=sqlite
DEBUG_LEVEL=3
DEFAULT_DEVICE_PREFIX=hd
I does not get to the EPILOG state, so it's is not saving changes.
Do I have to enable the qcow driver in the datastore drivers?
--
Andreas Calvo Gómez
Systems Engineer
Scytl Secure Electronic Voting
Plaça Gal·la Placidia, 1-3, 1st floor · 08006 Barcelona
Phone: + 34 934 230 324
Fax: + 34 933
The qcow2 tm driver takes advantage of qcow2 images. If you are not getting
epilog state it means your vm isn't shutting down properly. Do you have
acpi packages on your vm?
On May 7, 2012 4:48 AM, Andreas Calvo andreas.ca...@scytl.com wrote:
I does not get to the EPILOG state, so it's is not
What I see when I run the SHUTDOWN command is:
Fri May 4 11:03:11 2012 [LCM][I]: New VM state is SHUTDOWN
Is there something else I should do?
Image is not marked as persistent, should it be changed?
On Thu, 2012-05-03 at 23:51 -0400, Shankhadeep Shome wrote:
If you use a qcow backing store
No you don't have to change image to persistent, it wouldn't change the
running vm anyways. After the shutdown there are two more states, EPILOG
and DONE. EPILOG is reached after the VM is completely shutdown and
reported back, DONE is after the VM files are deleted from the system
datastore, you
Hi all,
What is the procedure to save a running VM as an image if it's running
with QCOW2?
As per the documentation, I've used shutdown after issuing save as, but
the image gets in a LOCKED stated and do not progress.
If the VM gets deleted, the image changes to READY but I think it's just
a link
If you use a qcow backing store this is what happens in the background
qemu-img create -backing_store (your original image) -f qcow2 (running
image)
when you save as its
qemu-img convert (running image + backing store) -O qcow2 (new base image)
The vm log should look like this... check to see
