Hi Carlos.
A shutdown doesn't work for me. Even with 'acpi=yes' and a *graceful*
shutdown inside the vm (via vnc) the VM state always remains RUNNING
(ACTIVE) although it was already successfully removed by libvirt.
If I then manually execute onevm shutdown 345 (see [1]) the state
changed to
Hi,
If I'm understanding right, you first log into your VM, shutdown it
yourself, and then issue the onevm shutdown id.
Is this right?
onevm shutdown command assumes the VM is still running, and sends the ACPI
signal to the machine. Your virtualized OS is supposed to shutdown itself
with this
Hi Carlos.
You have saved my day. I had a look at the acpi deamon inside my vm: it
wasn't running. As soon as I have repaired the configuration the acpi
signals were successfully passed into the machine and the onevm
shutdown works again.
Thank you!
Just for clarification: As soon as the vm
2011/2/11 Marco Strutz marco.str...@desy.de
Hi Carlos.
You have saved my day. I had a look at the acpi deamon inside my vm: it
wasn't running. As soon as I have repaired the configuration the acpi
signals were successfully passed into the machine and the onevm shutdown
works again.
Thank
Hi Carlos.
Very strange: After running ttylinux and enabling the saveas-feature
('onevm saveas 318 0 318_archived') I get the following error message
(vm.log) after deleting this instance:
Thu Feb 10 12:24:31 2011 [VMM][W]: Ignored: CANCEL SUCCESS 318
Domain one-318 destroyed
Thu Feb 10
Hi Marco,
After a *graceful* shutdown, the disk images marked to be saved
are transferred back from var/vm_id/images/XX to var/vm_id/disk.XX
Try using 'onevm shutdown' instead of delete, that will probably solve your
problem.
Regards.
--
Carlos Martín, Engineer, MSc
Project Major Contributor
