Search results

It depends on your needs. You can pvcreate /dev/vda or create partitions on it. Or you can even directly format /dev/vda (that's what I do for data disks as it makes it easier to resize it later)

Disk images are what you attach to a VM to represent a disk. Yo use them, just create a VM (or a new disk attached to an existing VM)

Quorum needs more than half the nodes alive. That's why you need 3 nodes for HA as it's the minimum to be able to have strictly more than half the nodes (2). In your case, you need 4 nodes alive to keep the quorum

Yes, still the same. Changes might be needed inside the guest (like rebuilding the initrd), but this depends on the guest (and for centos, it shouldn't be needed)

Exactly Reducing a volume is always tricky, and risky. You first need to reduce all the layers inside the guest. And there's no simple how-to because it can be very different. First, you need to reduce the FS (if it's possible. Some can't be shrunked at all, like XFS or ZFS). Then the...

On RAIDZ, depending on the volblocksize, you can have more used disk space than logical space, du to padding. See https://www.mail-archive.com/freebsd-virtualization@freebsd.org/msg05685.html for example Check with zfs list -o name,used,lused,refer,ratio to have a better picture of the space...

NFS, ZFS over iSCSI, GlusterFS ans Ceph are alternatives which are shareable, with snapshots support and thin provisionned.

This thread is old. But I do have the same issue. Using a CentOS 7.6 + ZoL 0.8.1 storage box (with the LIO backend)

Great, will try it ASAP. Thanks :)

If you use file based images, it doesn't really matters what's under the filesystem (could be a standard lvm, thin lvm, raw partition, nfs etc...). You just rely on the qcow2 format to provide snapshots features. But proxmox can also use raw lvm volume as images (in which case there's no...

If you can use snapshot, you either use lvm thin, or file based images with qcow2, on a filesystem, on an lvm volume. But you can't use snapshot with non thin lvm directly

Hi there. I'm having a problem with SPICE display when the VM is migrated from one node to another. I'm using remote-viewer on Fedora (from the virt-viewer package) and connect to Windows 10 VM. SPICE itself is working very well (display, including multi monitors, USB, sound etc.). But, if I...

Here are the result (changed the second bench from read to seq as read is not valid): Total time run: 600.668960 Total writes made: 15200 Write size: 4194304 Object size: 4194304 Bandwidth (MB/sec): 101.22 Stddev Bandwidth: 40.9338 Max bandwidth...

I've reproduced it once again (after several successful live disk moves back and forth between Ceph and NFS). The task starts and then just hangs indefinitely at 3.17% without any further progress : create full clone of drive scsi0 (nfs-fws:103/vm-103-disk-0.qcow2) drive mirror is starting for...

Yes, I'm testing their "Ceph-as-a-service" offer to evaluate it's perf The two nodes setup is just for prototyping. If tests and stability are good enough, the plan is to scale to at least 5 or 6 nodes, so ZFS replication is not really an option for me.

Nothing fancy. PVE6 with latest updates. root@pvo2:~# pveversion -v proxmox-ve: 6.0-2 (running kernel: 5.0.15-1-pve) pve-manager: 6.0-4 (running version: 6.0-4/2a719255) pve-kernel-5.0: 6.0-5 pve-kernel-helper: 6.0-5 pve-kernel-5.0.15-1-pve: 5.0.15-1 ceph-fuse: 12.2.11+dfsg1-2.1 corosync...

Hi. I'm playing with PVE 6 and have 2 storages : one NFS and another Ceph (external, not managed on PVE). Both are working fine, and I can move disk from Ceph to NFS without any issue. But not the other way arround : from NFS to Ceph, the transfert starts, and then hangs arround 3% indefinitely...

As the VMA format is not linear, I think this is also not possible. You have to restore it as is

No, I don't thinks it's possible. vma are low level backups, and know nothing about files and directories inside

This is not something Proxmox can (or should) provide. It can be done with management tools like ansible