[PVE-User] libguestfs-tools

Is there any chance of proxmox doing a libguestfs-tools package? the Debian one won't install due to package dependencies. I'd really like it for the "virt-sparsify" command: http://libguestfs.org/virt-sparsify.1.html really useful for guest images where the "sparseness" has become

Re: [PVE-User] Proxmox API catch response

On 02/05/2016 04:46 PM, Mohamed Sadok Ben Jazia wrote: I think those last lines are good for my work do { sleep (1) task = APICALL(get nodes/nina/tasks/UPID:nina:7F77:0029667A:56B36272:vncproxy:104:tom@pam:/status) } while (task->{status} != 'stopped') Do you think proxmox

Re: [PVE-User] Message from PVE-HA-CRM

On 02/05/2016 04:26 PM, Gilberto Nunes wrote: > Also if you have no more VM under HA you can remove the HA resource config > > # rm /etc/pve/ha/resources.cfg But if do this, in the future, when I realize that I need insert the previously node removed, it will work? Yes, if you add the

Re: [PVE-User] Message from PVE-HA-CRM

So I use journalctl --since "2016-02-04 19:00" --until "2016-02-05 07:30", in order to get useful information... Since I do not have enought skill I send to the list some outputs, in hope that somebody can help... Thanks a lot 2016-02-05 14:19 GMT-02:00 Thomas Lamprecht

Re: [PVE-User] Message from PVE-HA-CRM

It is proxmox 4.1 with lasts updates ? I think I have had something like that with proxmox 4.0. - Mail original - De: "Gilberto Nunes" À: "proxmoxve" Envoyé: Vendredi 5 Février 2016 13:04:21 Objet: [PVE-User] Message from PVE-HA-CRM

[PVE-User] Message from PVE-HA-CRM

Hello list In the past, I had a cluster with two nodes plus storage with HA enabled... About 3 month, I note that the VM just stop, from nothing at all The PVE remain alive and storage too... I get this message in syslog: Feb 4 19:15:42 proxmox01 pve-ha-crm[1894]: got unexpected error -

Re: [PVE-User] Message from PVE-HA-CRM

Hi, the obvious questions: what did you do before the error came to light? With this error the HA CRM cannot do any action (start, stop, migrate, ...) whats the output from # systemctl status pve-ha-lrm # ha-manager status on this node (or both nodes), be sure that pve-ha-lrm is started!

Re: [PVE-User] Message from PVE-HA-CRM

Sorry... I don'e mention it, but now, I have just one node and had disable the HA for that VM... There's no other VM Just one, with HA disable... BTW, here the outputs... # systemctl status pve-ha-lrm systemctl status pve-ha-lrm ● pve-ha-lrm.service - PVE Local HA Ressource Manager Daemon

Re: [PVE-User] Message from PVE-HA-CRM

On 02/05/2016 01:39 PM, Gilberto Nunes wrote: Sorry... I don'e mention it, but now, I have just one node and had disable the HA for that VM... There's no other VM Just one, with HA disable... Ah okay, now i understand. Can you try: # systemctl restart pve-ha-lrm Also if you have no

[PVE-User] Proxmox API catch response

Hello list, i'm using proxmox api to create Containers and managing ressources. proxmox commands don't have a fixed duration so you need to refresh calls to see that an action is correctly done.. Are there a method to catch the end of an action when using API calls?

Re: [PVE-User] Message from PVE-HA-CRM

did you stop the VM before you disabled HA? On 2/5/2016 7:56 AM, Gilberto Nunes wrote: And the stop from time to time... Last time was about two weeks ago... 2016-02-05 10:39 GMT-02:00 Gilberto Nunes >: Sorry... I don'e

Re: [PVE-User] Message from PVE-HA-CRM

Sure! Many month ago I did it... Thanks 2016-02-05 11:41 GMT-02:00 David Lawley : > did you stop the VM before you disabled HA? > > On 2/5/2016 7:56 AM, Gilberto Nunes wrote: > >> And the stop from time to time... Last time was about two weeks ago... >> >> 2016-02-05 10:39

Re: [PVE-User] Message from PVE-HA-CRM

And the stop from time to time... Last time was about two weeks ago... 2016-02-05 10:39 GMT-02:00 Gilberto Nunes : > Sorry... I don'e mention it, but now, I have just one node and had disable > the HA for that VM... There's no other VM Just one, with HA disable...

Re: [PVE-User] Proxmox API catch response

If it's a call where a worker gets forked we have an UPID which represents this action and we have a UPID wait function where you can wait for this task to finish. If you're making perl scripts on a PVE host it'd be really easy: use PVE::API2::Qemu; use PVE::ProcFSTools; my