DELL SERVER IS REBOOTING WHEN I AM ADDING PCI CARD

Vineet Sharma

New Member
Jun 14, 2023
5
0
1
Hi,

I am facing a problem when I am adding PCI Device form "Harware" option. My Dell server is getting reboot when I select PCI device. Below are the logs :

Jun 13 20:53:21 www systemd[1]: Created slice qemu.slice.
Jun 13 20:53:21 www systemd[1]: Started 100.scope.
Jun 13 20:53:21 www systemd-udevd[2162]: Using default interface naming scheme 'v247'.
Jun 13 20:53:21 www systemd-udevd[2162]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 13 20:53:21 www kernel: device tap100i0 entered promiscuous mode
Jun 13 20:53:21 www systemd-udevd[2162]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 13 20:53:21 www systemd-udevd[2162]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 13 20:53:21 www systemd-udevd[2161]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 13 20:53:21 www systemd-udevd[2161]: Using default interface naming scheme 'v247'.
Jun 13 20:53:22 www kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Jun 13 20:53:22 www kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Jun 13 20:53:22 www kernel: device fwpr100p0 entered promiscuous mode
Jun 13 20:53:22 www kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Jun 13 20:53:22 www kernel: vmbr0: port 2(fwpr100p0) entered forwarding state
Jun 13 20:53:22 www kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Jun 13 20:53:22 www kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Jun 13 20:53:22 www kernel: device fwln100i0 entered promiscuous mode
Jun 13 20:53:22 www kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Jun 13 20:53:22 www kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
Jun 13 20:53:22 www kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Jun 13 20:53:22 www kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Jun 13 20:53:22 www kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Jun 13 20:53:22 www kernel: fwbr100i0: port 2(tap100i0) entered forwarding state
Jun 13 20:53:32 www kernel: vfio-pci 0000:3b:00.0: vfio_ecap_init: hiding ecap 0x19@0x1c0
Jun 13 20:53:33 www pvedaemon[1808]: <root@pam> end task UPID:www:0000086A:00003714:648889E7:qmstart:100:root@pam: OK
Jun 13 20:53:33 www pvedaemon[2438]: starting vnc proxy UPID:www:00000986:00003C97:648889F5:vncproxy:100:root@pam:
Jun 13 20:53:33 www pvedaemon[1808]: <root@pam> starting task UPID:www:00000986:00003C97:648889F5:vncproxy:100:root@pam:
Jun 13 20:53:34 www pvestatd[1779]: status update time (6.966 seconds)
Jun 13 20:53:37 www pvedaemon[1808]: <root@pam> end task UPID:www:00000986:00003C97:648889F5:vncproxy:100:root@pam: OK

Please help me to resolve this problem.
 
Last edited:
1686745474006.png
I have above configuration, 0000:3b:00.0 is my PCI device. And When I am starting VM then, whole server is getting reboot.
 
Jun 14 18:18:52 www systemd[1]: Started 100.scope.
Jun 14 18:18:52 www systemd-udevd[3454]: Using default interface naming scheme 'v247'.
Jun 14 18:18:52 www systemd-udevd[3454]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 14 18:18:53 www kernel: device tap100i0 entered promiscuous mode
Jun 14 18:18:53 www systemd-udevd[3457]: Using default interface naming scheme 'v247'.
Jun 14 18:18:53 www systemd-udevd[3457]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 14 18:18:53 www systemd-udevd[3457]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 14 18:18:53 www systemd-udevd[3454]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun 14 18:18:53 www kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Jun 14 18:18:53 www kernel: vmbr0: port 2(fwpr100p0) entered disabled state
Jun 14 18:18:53 www kernel: device fwpr100p0 entered promiscuous mode
Jun 14 18:18:53 www kernel: vmbr0: port 2(fwpr100p0) entered blocking state
Jun 14 18:18:53 www kernel: vmbr0: port 2(fwpr100p0) entered forwarding state
Jun 14 18:18:53 www kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Jun 14 18:18:53 www kernel: fwbr100i0: port 1(fwln100i0) entered disabled state
Jun 14 18:18:53 www kernel: device fwln100i0 entered promiscuous mode
Jun 14 18:18:53 www kernel: fwbr100i0: port 1(fwln100i0) entered blocking state
Jun 14 18:18:53 www kernel: fwbr100i0: port 1(fwln100i0) entered forwarding state
Jun 14 18:18:53 www kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Jun 14 18:18:53 www kernel: fwbr100i0: port 2(tap100i0) entered disabled state
Jun 14 18:18:53 www kernel: fwbr100i0: port 2(tap100i0) entered blocking state
Jun 14 18:18:53 www kernel: fwbr100i0: port 2(tap100i0) entered forwarding state
Jun 14 18:19:01 www pvedaemon[1780]: VM 100 qmp command failed - VM 100 qmp command 'query-proxmox-support' failed - unable to connect to VM 100 qmp socket - timeout after 51 retries
Jun 14 18:19:01 www pveproxy[1789]: proxy detected vanished client connection
Jun 14 18:19:01 www pvedaemon[1778]: VM 100 qmp command failed - VM 100 qmp command 'query-proxmox-support' failed - unable to connect to VM 100 qmp socket - timeout after 51 retries
Jun 14 18:19:08 www pvestatd[1750]: VM 100 qmp command failed - VM 100 qmp command 'query-proxmox-support' failed - unable to connect to VM 100 qmp socket - timeout after 51 retries
Jun 14 18:19:08 www pvestatd[1750]: status update time (8.188 seconds)
Jun 14 18:19:09 www kernel: vfio-pci 0000:3b:00.0: vfio_ecap_init: hiding ecap 0x19@0x1c0
Jun 14 18:19:10 www pvedaemon[1778]: <root@pam> end task UPID:www:00000D6E:00006122:6489B733:qmstart:100:root@pam: OK
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!