Search results

I still cannot mark my thread as solved. I do not see any option to edit threads i have already made. Is there still an issue with the permissions?

ok i finally found the issue. Turns that it was the actual NIC. For what ever reason the specific NIC would only work bridged and not using pass through. When i switched to the other pci NIC the passthrough worked. No module blacklist needed either. So i will just passthrough the working NIC on...

Its looks the same but it would fail when i tried it in other machines...but as i said i will try it again ans see on this one.

I could try but on other similar machines when i did that, the passthrough would fail as it would try to passthrough the same NIC twice. Only passing once with all functionality worked in passing both interfaces. I am really not sure what is up here. any ideas @dcsapak maybe?

That is what i want. To pass both interfaces and team them up in the VM.

Same result with the driver blacklisted: dmesg output: https://pastebin.com/6ve8bdLH blacklist contents: The vfio-cpi driver seems to be loaded

I do but the performance is really subpar even with Vrtio. On other machines this was only solved with a passthrough. The good thing is that the only other bridge to be used if the passthrough works is a 1g one that uses a different module thus not really an issue to blacklist the driver.

SRIOV is already enabled globally. I will try to blacklist the module. @dcsapak The module to blacklist would be bnxt_en correct?

I did do an upgrade and the error message now is more specific. Dmesg output: https://pastebin.com/6zNvSKrV Configuration of the passthrough: Sorry for the mix up before. There are more than one NICs on the machine. The VM configuration is the same as in the previous post but without...

VM config: I am adding the passthrough from the web interface like so: The full dmesg:https://pastebin.com/s0q9YUe5

I have been trying implement a PCI passthrough for a 25g NIC to a Windows Server 2016 guest but it does not seem to work. The Host server is a Dell Poweredge with a 1st gen Epyc CPU. I have tried the same passthrough with CentOS 8 guests on a different server with the same hardware (same CPU...

Thank you that was a great idea (i feel bad for not thinking it earlier). I ended up actually disabling virtulization from the BIOS and indeed the host booted normally so i could remove the incorrect passthrough.

So the issues i have are similar to this: https://forum.proxmox.com/threads/i-o-errors-pve-not-booting.75120/post-343494 The reason i think things go read only is that there is no quorum with the networking disabled. The problem is that if i disable networking the errors stop - i can boot. If...

yeah i did. btw this in a node with a cluster of two if this matters for this case.

thank you for the reply. I actually managed to boot up by disabling all the networking card. But /etc/pve/qemu-server/VMID.conf seems read only and cannot change this even using root.

I have made a mistake trying to passthrough a NIC that was already used by another VM through a bridge. At restart the host is trying to start both VMs and crashes and i have no access to it either from the web interface or the console. Is there a way to disable the automatic start of the VMs...

Great will try it out. Thank you very much!

Typically by adding a mount point on the container resources.

So my question is this: If i have a LXC with a disk raw image mounted. Is it possible for that disk image to unmount it from that container and move/remount it on a different LXC container and retain the data inside? Thanks!

Have the same bug. Also followed the same to remove directories. Btw if you do not want to reboot to reuse the disk after you removed the directory (the disk still seen as used for partitions) you can remove the partitions using fdisk.