Hi,
suppose I have several snapshots of a VM:
Snap1
└── Snap2
└── Snap3
└── Snap4
└── Snap5
Is there a way to determine the size of each snapshot?
Regards,
Uwe
___
pve-user mailing list
pve-user@pve.proxmox.com
On 09/18/2017 11:12 PM, lemonni...@ulrar.net wrote:
Unfortunatly proxmox doesn't really use that for everything, it uses the
machines hostnames and you can't do anything about it.
If you do something like pvecm add pve01 -ring0addr 10.1.1.XX you can
force corosync to use your local network, but
But that's my point!
I always do what I told before, 'cause I suppose that all cluster/migrate
traffic run over my private network... Is this no certain, so?
2017-09-18 18:23 GMT-03:00 :
> Well if it works, sure. I know my nodes can't have corosync use eth0, so
> I have
Well if it works, sure. I know my nodes can't have corosync use eth0, so
I have to add the ring0 paramter to force that to use the local network,
but that's might not be a problem for you.
Just saying don't be surprised when you see your VM migration use your
public interface instead of the local
Oh I see
But that's ok if I continue use the /etc/hosts.conf as I pointed before.
right?
2017-09-18 18:12 GMT-03:00 :
> Unfortunatly proxmox doesn't really use that for everything, it uses the
> machines hostnames and you can't do anything about it.
>
> If you do
Unfortunatly proxmox doesn't really use that for everything, it uses the
machines hostnames and you can't do anything about it.
If you do something like pvecm add pve01 -ring0addr 10.1.1.XX you can
force corosync to use your local network, but if your hostnames resolve
to public IPs, VM migration
Hi guys...
I always do, as good practices, adjust the /etc/hosts.conf, in order to
resolve the internal IP to the machine name, when creating a cluster.
So, I puted this in /etc/hosts.conf in each node:
127.0.0.1 localhost
10.1.1.10 pve01 pvelocalhost
10.1.1.20 pve02
10.1.1.30 pve03
just
Thanks for your help,
Le 18/09/2017 à 12:37, Alwin Antreich a écrit :
On Sun, Sep 17, 2017 at 11:18:51AM +0200, Phil Schwarz wrote:
Hi,
going on on the same problem (links [1] & [2] )
[1] : https://pve.proxmox.com/pipermail/pve-user/2017-July/168578.html
[2] :
(I'm speaking of PVE 4.4, i don't know if in 5.0 things are better...)
I know that, if the underlying storage is a 'thin' storage, i can use
in VM 'VirtIO SCSI' and enable trim to reclaim space:
https://pve.proxmox.com/wiki/Qemu_trim/discard_and_virtio_scsi
But on Containers?! I've
On Sun, Sep 17, 2017 at 11:18:51AM +0200, Phil Schwarz wrote:
> Hi,
> going on on the same problem (links [1] & [2] )
>
> [1] : https://pve.proxmox.com/pipermail/pve-user/2017-July/168578.html
> [2] : https://pve.proxmox.com/pipermail/pve-user/2017-September/168775.html
>
> -Added a brand new
10 matches
Mail list logo