Search results

My apologies. The way I read the above opening statement is that: - you confirmed that the VM name is specified and is being ignored by the resulting VM on start. - CloudInit user and password are configured in the VM resulting from the clone operation, but, again, ignored during the VM boot I...

Great! Now that we know that you have covered your basics, can you address my question from #2: Is the configuration of the clone same, similar or different from the template? Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

You can examine the code or watch the log (journalctl -f). Its just how this works. You've cut off the second, clarifying, part of my question in your quote. The question was - _before_ you converted your "golden" VM into template, did you start and manipulate it? This would not be related to...

Hello @zxy, welcome to the forum. Terraform integration is not developed or maintained by PVE personnel. Its 3rd party developed and your best bet to get support with it - on their forum/github. That said, Cloud-init ISO is regenerated on each VM cold start What is the base image that you...

There are other storage types (non-qcow based) that support snapshots, and where this functionality works for all disks, including TPM. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

yes, it is. At least for now. Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Great! We will get it into QA pipeline ASAP! Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Try to run that command manually (up to "zfs list" the rest you can drop). You may get a more verbose error. If it works, the SSH is working, keep adding portions of the command until you hit an error. Troubleshoot from there. If the ssh fails, then examine your password, ssh key etc. If you...

The error you are getting is directly from lvremove, i.e. on OS level. It implies that the OS/Kernel has a lock/hold on the disk. Possibly outside of Proxmox. First ensure that this disk is not used by any active VM, check other VM configurations. The search your favorite engine for tips on...

Please post current VM configuration: qm config VMID As well as list of disks: pvesm list STORAGE Good luck Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

ZFS+replication is not shared storage solution, it's a Disaster Recovery solution. You can't access source and target simultaneously. Good luck Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

if you don't need high availability than you can use anything really. If you need to be able to survive node failure (where storage is hosted on) then it's either Ceph or something centralized, ie outside your nodes. Good luck Blockbridge : Ultra low latency all-NVME shared storage for...

Any Linux variant will do. You can find a specialized QCOQW/ISO which is much more lightweight than TrueNas, or just install NFS server on Alpine. Good luck Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

Does the device exist? Have you examined the resulting VM config? May be your requests are not in correct order and the device does not exist at the time you are trying to set the order? Good luck Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...

Hi @logui. It seems that you have a misunderstanding of how shared iSCSI storage works. Unlike Ceph, which is a distributed storage meant to use local disks, iSCSI is centralized type of storage. Meaning that a single node (or specialized cluster) is presenting single or multiple LUNs to single...

Hi @JMarques , welcome to the forum. The symptoms you describe seem specific to your environment. Have you examined the logs on both the hypervisor (journalctl -n 500 // dmesg) and the VM? You may need to put performance monitoring in-place. Increasing CPU and Memory are easy steps. Increasing...

Hi @edymol , welcome to the forum. The terraform code is not maintained by PVE personnel, you would have to reach out to the creator of TF code for a definitive answer. In the meantime, you can dig into the code yourself to see what API call is being generated, that may tell you what is wrong...

Hi @Phips , welcome to the forum. Making a full clone of a VM with EFI and TPM works for me: Perhaps you can share your VM configuration, full output of the pveversion -v, storage configuration (cat /etc/pve/storage.cfg), exact output of the task result, repeat the command from CLI as its...

Keep in mind that you can only link-clone a template. All disks in the Template VM will be link-cloned (except CloudInit) Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

You can try adding debug: server:/export/path /mnt/point nfs defaults,_netdev,debug 0 0 "man mount": debug Turn on the debug flag. A version string and a list of filesystem parameters will be printed (these data are also printed if the parameters appear to be inconsistent). Check...