Recent content by Replicant

  1. R

    I would like to have my custom /var/lib/vz. Would like guidance on content storage paths - I don't know where to store CT images.

    I have multiple standalone PVE hosts that all have their own ZFS pools. Inside each pool I would like to have my custom "var-lib-vz" ZFS dataset (this filesystem will be synced using syncthing running in LXC on each host). The main reasoning for this setup is: One centralized location for iso...
  2. R

    How do I manually move VM disks (zvols) from one pool to another and update them in Proxmox?

    I have two pools, pool1 and pool2 and proxmox sees them as ZFS storages. I have previously used the GUI to transfer vm disks between these pools. Currently vm disks are on pool2. I need to destroy pool2 and recreate it because it was made with incorrect properties. Therefore I need to transfer...
  3. R

    I would like to physically migrate the storage backing a VM. Aside from their "storage", what constitutes a VM?

    I will travel to and setup a PVE host in another country. In the meantime, I have setup its storage (ZFS pool) in PVE the current country. So, there are two ZFS "storages" on my PVE host defined in storage.cfg, one [current-host-data] and one [future-host-data]. Both contain a mix of VM disks...
  4. R

    LXC fail to start due to "newuidmap failed to write mapping" but they worked before

    Terrible news, for those of you unfortunate enough to have wasted your valuable time/attention on my thread: one of my /etc/subgid files had: root 1000:1 rather than root:1000:1 I highly suspect this is the issue, I really have no energy today to test anymore, and I am seriously rethinking...
  5. R

    LXC fail to start due to "newuidmap failed to write mapping" but they worked before

    I migrated my containers from an old host to a new one and they wouldn't even restore, complaining about uid errors: lxc 20240303081721.668 ERROR conf - ../src/lxc/conf.c:lxc_map_ids:3701 - newuidmap failed to write mapping "newuidmap: uid range [1000-1001) -> [1000-1001) not allowed"...
  6. R

    Moved PVE host to new network, where else is networking info stored aside from /etc/network/interfaces, /etc/hosts, and /etc/resolv.conf?

    I temporarily set up a PVE host on my home network and physically moved it to a different target network afterwards. Both networks are A.B.C.D/24 format but different IP addresses. In the new network, I changed the static IP in /etc/hosts and the static IP and gateway in...
  7. R

    Move of TPM State disk fails

    That is great... What is the appropriate place to monitor the status of this particular issue if I am interested in it being merged? Also, could you provide any advisory regarding when the tpm disk is stored on storage not supporting snapshots like nfs? (nfs requires qcow2 for snapshots, tpm...
  8. R

    Move of TPM State disk fails

    Hi, the person you replied to referred to moving vm's with tpm disk. Does the fixed issue fix things for cloning vm's as well? I cloned vm1 which converted the raw tpm file to qcow2. I ran your command on the target tpm disk and it was in qcow2 format. I didn't try to start it, I just replaced...
  9. R

    EFI/TPM disk order changed after clone - is this a bug and where should I report it?

    I'm not sure but I think the clone operation goes down the vm's .conf file (whose options are alphabetical) line by line and "efidisk0" is followed by "scsi0" then "tpmstate0", so that's why efidisk0 is cloned first. I tested this by moving scsi0 to the top of the .conf file and cloning, which...
  10. R

    EFI/TPM disk order changed after clone - is this a bug and where should I report it?

    I set up a Windows VM with EFI disk and TPM. After setup, the disk order was 1. Boot HDD (vm-XXX-disk-0) 2. EFI Disk (vm-XXX-disk-1) 3. TPM Disk (vm-XXX-disk-2) During cloning, the EFI disk is always cloned first in the task viewer, the order then becomes: 1. EFI Disk (vm-XXX-disk-0) 2. Boot...
  11. R

    Manual setup for zfs RAIDZ-1 root filesystem on different size disks (proxmox-boot-tool not grub)

    I wanted to have a redundant zfs rpool so if either drive fails the system will still boot. However my boot volumes are not identically sized. Apparently the installer does not allow this. There exists an older thread where a user describes installing proxmox's zfs rpool on differently sized...