Recent content by EugenMayer

Thanks for the effort and information Stefan! I will try to replicate that in an office our and post the kernel exception here. there are no open kernel updates Running FreeBSD:12 on Opnsense 21.1.5 (latest) so I suppose it is the latest FreeBSD 12 kernel Why would I need nested virtualization...

Updated CPU in the original post (its an AMD) This is the non-bootable configuration due to cpu: host boot: dcn bootdisk: scsi0 cores: 2 ide2: none,media=cdrom memory: 6000 name: gateway net0: virtio=<redacted>,bridge=vmbr30 net1: virtio=<redacted>,bridge=vmbr0 net2...

Due to fixing nested virtualization issues I switch to the 5.11 kernel line using apt-get install pve-kernel-5.11 after that my freebsd/opnsense (21.1.5-amd64) box (FreeBSD 12), which is using cpu:host will no longer boot due to a kernel panic. Are there any hints or known issues on how to fix...

TLTR: When you have an AMD Ryzen CPU and want to use any nested virtualization (nonfancy, just packer builds with Virtualbox) it will freeze about 5-10 seconds after starting the VM. To fix this issue, you need to upgrade your PVE kernel to 5.11. My setup: - Proxmox 6 latest patch version...

i was writing FUD - removed it. In the end, the debian installer created a FQDN entry in hostname 127.0.0.1 with a vagrant domain, while the chef hostname recipe created one with <LANIP> real FQDN, the point is, since the hostname was the same in both cases, but not the FQDN, pve-cluster picks...

Ich versuche auf einem HP Gen8 (Xeon E3-1225) mit VTd aktiviert, natürlich auch mit vi /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet intel_iommu=on" cat /etc/modules vfio vfio_iommu_type1 vfio_pci vfio_virqfd lspci -nn | grep Eth 03:00.0 Ethernet controller [0200]: Broadcom...

C) will be gone ( shorewall ) when PCIpassthrough is done - since it will obv make 0 sense as you mention

b) yes, thought / focussing on this already, so virtual IP in opnsense + 1:1 nat, right o n that c) not dnsmasq, but http://shorewall.org/manpages/shorewall-snat.html - so source natting Currently working on PCI nic passthrough to ease things up / having a better performance. If that fails i...

There are a lot of ressources online, old legacy, handling performance issues, partial multi-NIC setups and all this, but nothing is comprehensive, rather a lot of unfinished ones. I try to not repeat the whole story i posted here...

Thank you Fabian, so yet no "build in" way i guess, right

Hallo Flavio - hast du das mittlerweile hinbekommen? - ich habe hier was ganz ähnliches aufgebaut https://stackoverflow.com/questions/44118442/proxmox-with-opnsense-as-firewall-gw-routing-issue komme aber auch nicht so recht weiter

I am using chef to configure my host network and bridges, but as to due best practices it happens to interfaces.d/eth0 .. interfaces.d/vmbr0 and so on, while /e/n/interfaces is just an include like source /etc/network/interfaces.d/* doing that leads to issues with proxmox, which will not offer...

We solved the problem using mount-parameters (fstab) ,cache=none,forcedirectio,rsize=32768,wsize=32768,llock,rw,vers=3,prot=tcp,hard Best

Well thats a pitty, i cant change to NFS but i could try to backup localy - if the error does not occur, it must be SMB - maybe some mount options ( locking) are responsible for this? Thanks for the reply

How is that a solution to the problem :) ? SMB is supposed to work and i cannot use NFS, since it is not available from my storage hoster.