have you been able to solve this already? Usually posting
from both Proxmox VE host and within the VM is really helpful.
In addition, you can debug really many networking problems using tcpdump, for example:
tcpdump -envi vmbr0
Hi, if you absolutely want TrueNAS then this sounds OK. You can also think about
letting Proxmox VE handle the physical disks and create a (maybe ZFS) storage on it
install some (other) data storage solution in a VM
assign the VM virtual disks residing on the storage from step 1
I would not recommend two-node Ceph cluster. Instead you could look into ZFS & storage replication.
In addition, I would avoid the partitioning. You can give PVE one of the slower drives (or an additional 128GB SSD) and use the NVME as cache for ZFS. Note that for both Ceph & ZFS you should use...
Which storage controller do you have in your server? In general ZFS is a good choice, but it does use 50% of the host memory for caching by default. Depending on how much memory you need for your computations and the controller, other storage technologies might be interesting as well.
Yes, as explained by the preconditions in the upgrade guide.
A temporary combination of 6.4 and 7 should work. There are some hints in the forum.
Octopus is OK before the upgrade. You can upgrade later. See also in the upgrade guide.
Great to hear that you got so far! Unfortunately, that process often requires experiment with a couple of VM configuration options.
Did you get the glitches with the noVNC shell? Maybe you can use some remote desktop solution (Chrome Remote Desktop) instead?
importing VMs into Proxmox VE has become much easier. For the CloudReady image
Move the .ova archive to the server (or some accessible shared storage)
qm importovf 137 CloudReady\ Home\ 83.4.ovf tank
where you replace tank by your storage name and 137 by your...
Can you start VMs? It seems the container problem can be expected with the old kernel https://forum.proxmox.com/threads/container-status-unknown-after-pve5-pve6-blkio-throttle-io_service_bytes_recursive-no-such-file-or-directory-500.72252/
Can you verify that your backups work with another...