Proxmox team, please can you add macvtap to the networking options for guests? it has been asked for across the years numerous times, but it has resulted in total silence. It can't even be implemented by manually tweaking the guest config file via the args.... really really unfortunate. It is...
Host nic is not being used, no IP assigned etc etc.
Would like to assign that nic to a guest where the guest retains the 'mac' address of the host nic, so that all traffic goes to the guest and back out of course. My problem is that MAC spoofing cannot be enabled on my environment due to hard...
On the proxmox host, do a:
# ethtool -k <interface-name>
(thats lower case 'k')
check the value of 'generic-receive-offload', if it is 'on', then try:
# ethtool -K <interface-name> gro off
(thats upper case 'k')
see if that helps....
This doesn't happen on another vm, but on this vm Proxmox keeps resetting the arg entry in the vm config to defaults, I do not desire this behaviour, any ideas how to disable this? Yes I am not making any changes via the UI, proxmox just seems to reset the args every vm shutdown.
"Added support for latest Distributions RHEL8.2/8.1/7.8, Ubuntu 20.04 and Kernel.org 5.4"
I shall be putting some hours aside to try this out!
Also Chelsio are supporting Debian based distros through their self-compile drivers, it's just they do not submit their drivers upstream as they work...
Just to update, the issue in the end was the hot-plug functionality in Debian, it works fine in RHEL, Debian throws a wobbly. To be frank I didn't like the RHEL+oVirt setup one bit, quite clunky in comparison to Proxmox and its ease of flexibility, plus RHEL doesn't support RDMA CIFS which is a...
Also, I'm unable to passthrough the bridge-card itself, unless that is not permitted as it is a PCI switch.
Update:
I've put in a new boot-drive and am in the process of installing RHE8 and oVirt, to see if the same issue manifests in that setup.
I see in the log that the hotplug button event is captured, but the kernel seems to have an issue assigning addresses, I will try this with a different brand drive too to see if the issue is not drive specific.
In the log we can see the button event being captured and triggering the assignment...
Proxmox VE 6.2
I slot a drive into the nvme backplane and heres dmesg output:
Jun 04 13:57:01 arcadia kernel: pci 0000:89:00.0: [1c58:0023] type 00 class 0x010802
Jun 04 13:57:01 arcadia kernel: pci 0000:89:00.0: reg 0x10: [mem 0x00000000-0x00003fff 64bit]
Jun 04 13:57:01 arcadia kernel: pci...
From what I have deduced through email exchanges with Chelsio support, they're not really big fans of supporting Debian as priority, they are hell bent on sticking with Red Hat, lo and behold RHV comes with all the offloading features enabled. The growth of Proxmox in enterprise is getting...
Understood.
I'm trying to build a modified version of the t4_tom and nvme-offload kernel modules (latest chelsio offloading drivers), as the inbox drivers are the standard nic drivers rather than offload enabled.
Definitely some fun as I try and get Chelsio driver code patched enough to...
I guess I can just create a merged folder with both but overriden by the backported tree? but if there is a cooler way to do it without copying files around I'm all ears.
Looking through the kernel makefile, it appears that's what it does too, so I guess I'd have to do the same thing, no...
@t.lamprecht - thank you for that info, is there a way for the make command to take both paths into consideration? as things are split out like this? at the moment if I use the submodules kernel source path I get "No utsrelease" failure.
Hi, just attempting to compile a driver, but its looking for the Documentation folder in the kernel source root path, this doesnt appear to be present in the PVE source I downloaded, any suggestions?
With GPUs the norm is to exclude the pcie card from being initialiased/drivers loaded in the host so that it can be passed through to VMs without issue.
Does the above also apply to SRIOV VFs?
Although currently I don't and passing them through to VMs even after being...
[ 18.028094] iw_cxgb4: Chelsio T4/T5 RDMA Driver - version 0.1
[ 20.944513] iw_cxgb4: 0000:88:00.4: Up
[ 20.944516] iw_cxgb4: 0000:88:00.4: On-Chip Queues not supported on this device
...that appears to be quite an old version?
From what I gather from QEMU discussions, there's been a lot of work going on in that department, although outside of the scope of Proxmox devs, but all in all there will be knock-on discoveries, new configuration requirements etc, and much of this information doesn't get out there until people...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.