Search results

I just installed a Windows 2022 a couple of hours ago and then use 0.1.248 and works fine.

Think again https://pbs.proxmox.com/wiki/index.php/Roadmap#Roadmap

Hi there. Any idea when we would perform a Proxmox VE bare-metal backup? It's coming about? When??

Ooops... Ok folks. My bad! This topic was alread discused here: https://forum.proxmox.com/threads/solved-looks-like-a-qm-movedisk-bug-reclaim-disk-space-when-move-virtual-disk-from-lvm-to-directory.76706/ The vm needs to be offline before move disk. Sorry guys. My bad.

I don't know, either. Nop. No snapshot at all.

So how to explain that I can create a virtual image with 1TB using qcow2 and directory based storage?? qemu-img info vm-104-disk-1.qcow2 image: vm-104-disk-1.qcow2 file format: qcow2 virtual size: 1 TiB (1099511627776 bytes) disk size: 208 KiB cluster_size: 65536 Format specific information...

As i said, new disk image works fine. I was able to create a 1TB of size in the /vms mounted point, which has just about 900GB! Already tried preallocation off, default, metadata and nothing changes when migra virtual disk from local-lvm to directory based storage.

But new virtual disk are created like thin provision. Look: https://www.youtube.com/watch?v=nW_XZoNDlAg

dir: local path /var/lib/vz content backup,vztmpl,iso lvmthin: local-lvm thinpool data vgname pve content images,rootdir pbs: BKP datastore BKP server 10.10.100.20 content backup fingerprint blah prune-backups...

Any toughts?

Hi there I have a couple of vm using the local-lvm storage. I attached a directory storage and when move the disk of the vm from local-lvm to the directory storage, using qcow2, the disk image fill all the qcow2 image. Is that right? For instance, I have a VM with has the disk image about 100G...

Ok. Turns out I needs to do it in two process: 1 - in order to create the separate DB and add it to the OSD, I used the script provided by @mitcHELLspawn . Thanks a lot So I did this: vgcreate cephdb /dev/sdc add-db-to-osd.sh -b 280G -d /dev/sdc -o 0 Works as charm. 2 - in order to create the...

Actually I found a better way https://docs.clyso.com/blog/ceph-volume-create-wal-db-on-separate-device-for-existing-osd/

So based in this docs from Ceph, I had used this: - First set the osd to noout ceph osd set-group noout osd - Followed to stop it systemctl stop ceph-osd@0 - Create lvm ceph-volume lvm create --data /dev/sdc - Check the lvm created ceph-volume lvm list - Create the new-db ceph-volume lvm new-db...

Done https://bugzilla.proxmox.com/show_bug.cgi?id=5604

I will do that. Thanks for the tip.

Either make sense or not, the behavior is weird, to say the least. But would be good to do both things at same time.

Now that is weird. When the VM lies in local-lvm, so now I am able to select the target storage??? And the local-lvm it's even shared storage!!! Why is that?

Well. I don't know. This image bellow shows up a VM running in PVE 8.2.4 with the vm disk hosted in directory storage, shared between nodes. The VM is running and, still, no target storage appears. The apolo server has zfs pool called apolozfs and the zeus has zeuzfs pool, or something like that.

Hi there I am facing a strange behavior here. Have some servers, with different versions, some is pve7 and some is pve8. But the issue is when try to migrate a VM, sometimes I can choose the target storage but other times the choise even appears at all. I just want to know what is the right...