I believe this error ^^ comes from the remote host where your ZFS pool is located. Once you allocated the disk/image/volume - do a list on the storage box, does it show up under /dev/poolname, or in a different location?
Blockbridge : Ultra low...
Hi @marco.caserio , welcome to the forum.
PVE uses Debian kernel with Ubuntu userland. Proxmox does not certify any specific hardware combinations, usually neither does Linux Kernel organization. It is up to the vendors to ensure that their...
This is the key ! ^
https://kb.blockbridge.com/technote/proxmox-lvm-shared-storage/
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
I just want to reiterate, absent some new severe bug, nothing in the VM (including virtio drivers) should be able to cause the hypervisor host to crash to a point that a user has to manually reboot the server. Except, may be, if a misbehaving or...
There are three primary ways to provide LOCAL storage to the VM: as virtual images/disks (qcow), via LVM/ZFS flexible volumes, physical passthrough.
By formatting your disk (EXT4, XFS, ZFS, etc) you are selecting virtual image/disk path. You can...
I have not looked at the referenced blogs so I don't know whether they are incorrect or you may have skipped a step. The error most likely means you have wrong path/pool information, or the system you are using utilizes different organization...
I wish I could!
We're teaching cyber security and they have to learn how to lock down a PVE system and the VMs that run on them. We don't give 'em root or a PVE admin account, but they do have a sudo-like account for some of the Terraform stuff...
Hi @netguynick , welcome to the forum.
As @tomservo suggested, you need to show us what actual repos you have and their state. Run the command below and provide back the output (using CODE tags):
for f in /etc/apt/sources.list...
Hi @skins4ever86 , the exit error is generic - anything not 0 is conventionally an error. 1 is a catch all. Some developers use other integers to describe specific problems.
Your particular error is related to the PCI passthrough, and is more...
Its not part of our installation here that went through 7>8>9 upgrades. I don't know off hand whether it is part of any standard PVE install, I suspect not.
Somehow you, or someone on your team brought it in. I'd examine the journal and dpkg logs...
There was a typo in the journal command - extra p at the end, did you fix it by chance in your run?
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
You can try to run the pveproxy manualy to see the error you are getting:
pveproxy start
or
pveproxy start --debug 1
Looking at the log, as @fabian suggested, should, of course, be the first step.
Blockbridge : Ultra low latency all-NVME shared...
Your /etc/resolv.conf is a symlink to systemd-resolved's generated file (as evident by the text at the start), and resolved has no DNS servers, hence "No DNS servers known." Removing the package leaves the symlink behind, pointing at a stale...
Hi @Nemesiz, it's just a little console tool we wrote for this project. One Python script on top of the Rich library: https://github.com/Textualize/rich.
Strictly read-only: it pulls from /sys/class/net, /proc/stat, /proc/interrupts, the CPPC...
LVM is not my area of expertise, but here are a few things to try and report back:
1. An open count of 1 on -tpool is normal while the pool is active. It's the internal pool device, held open by the thin LVs and by dmeventd monitoring. lvchange...
My mistake, my reading of your initial post was you are using Proxmoxer to create a PVE template VM. It appears that these are two independent flows that you are trying.
The wrapper is only as good as the API request it creates. If it omits the...
Hi @Tacioandrade ,
I believe most if not all of your questions about coding are covered here: https://pve.proxmox.com/wiki/Developer_Documentation
As for the goal alignment, that is a more appropriate discussion for PDM list here...
@Francois Baillargeon , the VirtIO version is mentioned in the opening post, and it appears to be the latest version.
That said, a VM should not normally be able to hard-crash the hypervisor host. Even in the case of memory exhaustion, I would...