Hi @Adasvejas , welcome to the forum.
Start by reducing your DHCP range so that the PVE IP is not within it. That usually helps with access to non-standard ports.
you should use the same one that you have on your windows workstation. You can...
You should not have all devices on the same subnet. Your cluster network should be on a different subnet.
Note that none of this is PVE specific, but rather basic Linux Networking.
Cheers
PS I initially misread and thought you have more than 2...
What networks/subnets are being used here?
Can you expand on this? Are all your connections on the same subnet? What does /etc/pve/storage.cfg say? What about "ip a" from PVE? IPs of the TrueNAS?
Blockbridge : Ultra low latency all-NVME...
Hi @Jacx , welcome to the forum.
Looks like you exposed your PVE to the Internet and as such you are subject to immediate automated attacks. I would highly recommend rethinking your deployment, or, at the very least, implementing very strict...
Looking at the man page of the QM:
qm import <vmid> <source> --storage <string> [OPTIONS]
Import a foreign virtual guest from a supported import source, such as an ESXi storage.
<vmid>: <integer> (100 - 999999999)
The...
Hi @Xavier Droniou , can you provide exact commands with subsequent output that you executed? As well as your storage configuration:
cat /etc/pve/storage.cfg
To answer your question: Yes, you can can import file from locally mounted path...
Although you have not provided the requested information, the additional details you did provide point to a not-ideally configured network infrastructure.
Are you working with your network team specialist?
If not, you should definitely review...
Hi @dazmac ,
Perhaps you can clarify your inquiry:
- Are both sides (Netapp and PVE) using LACP?
- Are the 9500 MLAG connected?
- I am not overly familiar with variations of the ISSU, why have you highlighted 5 seconds? Are there other options...
Hi @Wodel , you should provide the following information:
- what does "imported" mean in your particular situation?
- what is the resulting VM configuration that does not work?
- what is the exact storage configuration?
Outputs from the...
Does this conversation match your concern and assist with resolving it?
https://forum.proxmox.com/threads/proxmox-pve9-upgrade-apparmor-denied-messages.169553/#post-824122
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
no worries. If your question is answered, feel free to mark this thread as solved by editing the first post and select solved from the dropdown near the subject.
Cheers
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
You are missing leading slash (/) in the path.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Outside of maintaining your own map, probably not.
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
Nothing stands out. The system should not be using Internal Snapshots with RBD. I'd recommend making sure that you are running the latest available software (apt update), and if the issue continues - utilize the support channel to open a ticket...
Based on the information provided we know that the VM configuration does not have a reference to any snapshots. However, the snapshots exits on the backend. They had to be created by an operator via PVE at some point. How the reference got lost...
Can you provide additional information:
pveversion
qm config [vmid]
cat /etc/pve/storage.cfg
cat /etc/pve/qemu-server/[vmid].conf
pvesm status
Are other VMs running on the same node? Are they located on the same storage (qm config [vmid])
Has...
The action you took is specific to snapshot, the error message is specific to snapshot, so we can be reasonably certain that the problem is related to snapshot management. However, it is likely not related to the origin of the VM. The fact that a...
The migration path is not relevant. You should examine the current state of the LVM as suggested previously. Post the results here as text output encoded with CODE tags.
The two primary outcomes are: the snapshot exists on disk and does not exist...
You should start by checking your LVM structure:
lvs
lvdisplay
etc
I am not sure how you got into this state, backtracking your steps may be a good idea. If there is an edge case of snapshots being orphaned, I am sure developers would like to...