> It seems the storage plugin function "deactivate_volume" will be not executed,
> when the VM stops by issuing a "poweroff" command.
> Hint: It is executed, when you klick the Shutdown button from the GUI.
That is by design ...
> I have seen
> pvedaemon[21622]: client closed connection
> in
> OK, so no GUI for now :(
>
> Is there a possibility / concept to dynamically rewrite parts of the GUI which
> may be reused here ?
Currently not. But I guess an experienced extjs programmer can write
such thing in a few days ...
___
pve-devel mailing
Hi!
It seems the storage plugin function "deactivate_volume" will be not executed,
when the VM stops by issuing a "poweroff" command.
Hint: It is executed, when you klick the Shutdown button from the GUI.
I have seen
pvedaemon[21622]: client closed connection
in the log, but no further storag
Hi!
I am just analysing the Storage class and plugins and discovered that
activate_storage in Storage.pm and also activate_storage in the plugins is
executed cyclically.
The reason is, that "cache" is always a new hash and therefore
"if $cache->{activated}->{$storeid};" in activate_storage(Sto
Hi!
> Is there anything else I need activate to get it displayed in the Add dialog?
I just found this in the README of the plugin:
PVE currently doesn't offers interface to add custom plugins via GUI,
so storage needs to be configured manually.
OK, so no GUI for now :(
Is there a possibilit
Hi!
I started today playing with storage plugins.
I installed this plugin on my machine to see how it works, but I couldn't see
it in the Add dialog on the WEB interface.
I restarted only "pveproxy", which should enough, I guess.
I even tried to execute it directly from Storage.pm, without luc
>>Something like direct import from a Xen dump (xva) ?
we have talked about importing disk (vmdk, qcow2, or other) to proxmox.
It's easy with file as target, but for vm with rbd,lvm,zfs , it's difficult
for users to create the vm, mount the volume, use qemu-img convert...
for xva, ova, or othe
