virtualbox.org

In the VBox-x86-Test-2022-06-16-19-34-07-final.log file, the statistics show that virtio-net#0 sent 1710 bytes in 5 packets, IntNet-0 sent 1710 bytes in 5 packets, IntNet-0 received 8692 bytes in 71 packets and virtio-net#0 received 8200 bytes in 67 packets. (I verified in my own working setup, that the received packet count can only be calculated from the raised interrupt count; there seems to be no counter for that.) Those summary statistics alone don't reveal what was in the packets, though.

FWIW, in your screenshot there are a lot of packets counted in /Drivers/IntNet-0/Packets/Lost, but in VBox-x86-Test-2022-06-16-19-34-07-final.log file the counter was 0.

With PCnet-FAST III, my QNX VM does not even recognize the network device. I have tried all different combinations of the network card in VBox & drivers on the QNX side. the virtio seems to be the closest match.

fth0 wrote:FWIW, in your screenshot there are a lot of packets counted in /Drivers/IntNet-0/Packets/Lost, but in VBox-x86-Test-2022-06-16-19-34-07-final.log file the counter was 0.

00:00:41.169363 /Devices/virtio-net#0/ReceiveBytes 8200 bytes
00:00:41.169366 /Devices/virtio-net#0/TransmitBytes 1710 bytes

00:00:41.169384 /Drivers/IntNet-0/Bytes/Received 8692 bytes
00:00:41.169388 /Drivers/IntNet-0/Bytes/Sent 1710 bytes

fth0 wrote: Those summary statistics alone don't reveal what was in the packets, though.

Its probably the dhclient in my VM that is trying to get an IP by sending requests regularly. I have nothing else at the moment trying to communicate with the host side.

@scottgus1, you mentioned you created a VM QNX7, Was it an actual QNX7 VM and its working?

amhblore wrote:Was it an actual QNX7 VM and its working?

No, I didn't install the OS, only made the VM according to the template to see what network card it would pick.

The OS installed in the VM must have built-in or user-provided (through an ISO) drivers for the network card presented. Does the QNX7 OS have drivers for virtio or the PCnet card?

amhblore wrote:Its probably the dhclient in my VM that is trying to get an IP by sending requests regularly.

The 5 sent packets could be DHCP DISCOVER packets, and the 67 received packets could contain 5 DHCP OFFER packets or not. A packet capture could tell.

scottgus1 wrote: The OS installed in the VM must have built-in or user-provided (through an ISO) drivers for the network card presented. Does the QNX7 OS have drivers for virtio or the PCnet card?

Yes, the OS has driver for the virtio. For PCnet, no. There is a driver devnp-e1000.so for the Intel network cards, but that gives no carrier detected error.

fth0 wrote: A packet capture could tell.

I need to create a new bootable image & write it to the hardisk. The tcpdump needs a library which is not in the current image

Just another idea: The nicinfo utility can provide low-level info according to Troubleshooting a driver, depending on a verbosity level. I have a rough understanding of network driver details, so perhaps I could make educated guesses ...

Unfortunately my driver does not support any verbose level. http://www.qnx.com/developers/docs/7.0. ... io.so.html

Attached output of tcpdump. There is no response to the DISCOVER message. And in the previous host logs we see the host OFFER message sent to the VM. But the VM never gets it!!! Where is it gone

The VirtualBox statistics also indicated that (virtual) hardware interrupts were raised for sent and received packets, so the next thing to look at would be the interrupt handling in QNX. Which interrupts are recognized, which are handled?

Additionally, capture the network traffic in QNX and in VirtualBox simultaneously (VBoxManage --nictrace option).

fth0 wrote:so the next thing to look at would be the interrupt handling in QNX. Which interrupts are recognized, which are handled?

I dont know how to check interrupts in QNX. This will need some effort & investigation