Search results

FWIW, all windows needs to do is look at the BIOS to know it is running in a VM :-)

Dear, For all proxmox VM i simply configure the hostname and the DHCP service maps it to an FQDN so i can ping myhost.sub.sub.mydom.tld Except for the one container i'm running, that does not work at all, whatever i try. The only difference i notice is the dhcp client here is udhcpc but i've...

yes, separate the network into functionality like (internet/mgmt/office) it will offer realistic segmentation and avoid mishaps

checking the output of dmesg for iommu and vfio keywords should tell you more

you may need to search /var/log/* instead, dmesg may be overflowing and not showing anything if you setiommu=pt then you should get: iommu: Default domain type: Passthrough (set via kernel command line) typically i also check on iommu in dmesg or /var/log/* there should be quite a bit of...

check for pvx kernel: iommu: Default domain type: Passthrough in the dmesg output with: dmesg | grep Passthrough

Did you update the 6.2 to the most recent version ? Did you consider supplementing the bios as a rom-option file to the VM ? personally is use both iommu= and intel_iommmu= to assure the mode is set correctly. For your setup: iommu=pt intel_iommu=on also try by including the nomodeset...

Don't take my word for it, here are a few considerations. be aware, very aware, if this proxmox cluster is running at home you are extending the office network to home and vice versa, you may be held accountable if anything goes wrong such as your home network is compromised. Unless you own the...

to my knowledge, if a device is performing outbound NAT only then the inbound will fail per default if no NAT is configured to do so. Same result.

Hey, thanks for sharing. While the string worked for my set-up the pass-through worked much simpler only after a kernel update. This is the string i append and use today, note the sequence is of some importance. the part in italic is optional and part of tests being performed. iommu=pt...

dear, for this setup i use a pf based firewall appliance also running unbound as dns and assuring dhcp leases are distributed and the local domain is resolved. For all VM the DNS works fine. Except for the one CT i'm using, there the hostname does not resolve for the domain. DNS lookups work...

the problem is most definitely with the disk for OPNSense i'm yet to figure out what exactly, for now i choose IDE with SSD emulation because it appears the only stable option.

After the prior post on FreeBSD (OPNSense and FreeNAS) failing to boot due to hotplug being enabled there remain issues. Both install just fine and boot just fine. It is only after a while they become unresponsive. I have yet to find an indication or metric to watch to understand what is going...

update: somehow i assumed enabling hotplug had little effect, disabling at least appears to solve all boot issues. I leave this dumb post here for future references and testimony it had been a long day already.

initially my experience with Proxmox 6 was rather disturbing, eventually i resolved what caused these issues and proxmox works well for me now. Recently (yeah) though i took on myself to install FreeNAS and OPNSense which are FreeBSD based and both behave "weird". The vm config i use can be...

My guess is it is really not suitable or interesting for production. It requires maintaining an entire kernel. If someone out there rebuilds the kernel with this patch, offers its as an APT repository, it's fixed.

Not sure what the big difference between 6.1 and 6.2 could be but kernel version and related modules. What is important is you understand your system. The many reported configuration parameters do not work or are required for all systems. I doubt gpu passtrhough would have worked out of the box...

Dear, Having found https://app.element.io/#/room/#proxmox:matrix.org which does use the official proxmox logo i wonder if it is in any way a viable and reliable alternate support channel ? Best Regards, Joris

I see the relevant packages, what does not makes sense is why they keep on being logged by the host and containers despite being disabled for logging everywhere

Despite both the host and lxc having all sysctl keys for martians set to =0 the dmesg output for both host and lxc show repeat martian notifications followed by ll header ... I do not understand where these keep on comming from or how to investigate more in depth. Br, Joris