Search results

A solution would be to make an entry for USB adapter in cat /etc/udev/rules.d/90-persistent-net.rules and define a "pretty name" for it, e.g. "enu0" - then you will see it after the next reboot as a NIC. But the question is whether it's necessary in the current case - see below. In case of...

The LVM form you posted is the one which creates new volume groups. In case you configure a storage in an already existing volume group you have to select "Existing Volume Groups" even it is hosted by an iscsi device. From the date you posted I conclude connection ti iscsi drive is visible. If...

Proxmox created LXC containers my run in other environment (as e.g. ubuntu) too, but you cannot rely on this. Moreover it is the question which kind of backup you make; directly compatible they will be only if you failover environment is also Proxmox VE. That means the solution installing...

All in one pve and Ceph cluster hyperconverged offers more flexibility. Moreover, when Ceph storage is hosted by pve nodes it is supported (i.e. e.g. repository always fully compatible to current pve version) by Proxmox.

Does "passed through" mean PCi pass-through using IOMMU? Since this is an experimental feature it's not reliable and may cause the problems you have.

I/O delay is not necessarily caused by "doing anything", but just slow (or defect) access to periphery. I don't know since I don't know about these bugs either - do you have more information about them?

Simply assign the number of cores to each VM and let OS decide how to share cores. If you want to assign certain cores explicitly to VMs you can use the command `taskset` assigning cores to the respective qemu-kvm processes.

"Freezing" (precisely rather "very slow") may be caused by huge amount of I/O delay. Statistic figures of it are shown when selecting in WEB GUI "Summary" of a node. High I/O delay can be caused by access problems to a media or simply intense write/read operations to it.

Sieht für mich eher wie ein BIOS Problem aus. Darin mal die boot Einstellungen überprüfen, ggf. nachjustieren (die erste boot Oprion sollte die Disk sein, auf der sich GRUB und OS befinden) und - da "wenn der PC einige Minuten ausgeschaltet ist" ein Problem auftritt - prüfen ob die EInstellung...

Not possible, ZFS RAID and hardware RAID are different technologies.

According to the above enp3,4,5s0 are not configured at all - therefore it is not possible to use them for traffic to a VM too. If you want to use them of the mentioned openwrt VM you have to assign them to bridges and also assign the virtual NICs in the VMs to this bridges too.

Yes, assign simply an IP address to the bridge where the physical NIC is assigned to. The diagram does not present the Prox Host configuration precisely, clearer woud be the content of /etc/network/interfaces or simply the output of pvereport

Use hardware RAID or (not "and"!) ZFS, mdadm is not supported from Proxmox.

I would create a container having virtual NICs assigned to both Linux vmbr0 and another new bridge (vmbr1 as member of an additional LAN, without physical NIC ), container will be the openvpn endpoint and routes incoming connections dedicated for Proxmox Host via the mentioned additional LAN to...

There is no "right way", both is possible. However, in case of having more or less two firewalls understanding and maintaining configuration would be more complex and IMO, whenever possible use OPNsense or Proxmox Firewall, just in cases when some needs are not well supported by one of them use...

Well known issue with USB drives. Since booting from USB is neither usual nor recommended in productive environments there is no need of adding the "rootdelay" (btw. usually vale "2" is sufficient) as default. Those who make experiments can find a hint (maybe you used the same source) regarding...

In principle yes (I would say "faster" not "more stable"), but comparision shows also that is an issue of the physical NIC(s ?) not of virtualization. Since between external machines and Proxmox host there are probably 1 or more switches it is not necessarily caused by the NIC in Proxmox host or...

No, nat tables cannot be set via Proxmox WEB GUI, but would be an interesting new feature, feel free to open en "enhancement" entry in https://bugzilla.proxmox.com/ in order to stress such a request; however: no problem to set them by `iptables -t nat` command, it will not have any impact on...

What exactly did you check: VM(Container) to host, host to external or VM(container) to external? What is the result when you compare the figures of these 3 scenarios?

Probably a hardware (mainboard, controller) issue. Check whether it works with a different OS (e.g. booting ubunto live media or server from USB stick).