Someone virtio driver doesn't switch off debug messages by default.
When Windows guest used for kernel debugging - a lot of debug messages (non stopping flood)
Windbg shows an infinite sequence of messages:
```
virtio: vp_notify vq->index = 0
```
or
```
virtio: vp_notify vq->index = 1
```
The performance is worse - the debugger slows down both VMs.
The debugging is practically impossible.
The temporal solution is filtering inside Windbg itself, but this does not solve the slowdown.

*To Reproduce*
Connect to a Windows guest from another Windows guest via network using Windbg as a kernel debugger.

*Expected behavior*
Windbg should show minimal number of messages when all is ok inside virtio.

host: No matter, but: Debian 13 stable, kernel 6.12.43,
host QEMU - seems also no matter.

both VMs: Windows 10
virtio: https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso
(seems 0.1.271)

*Additional context*
As I understood, VirtIO lib is used by several drivers, so I can't say exactly who doesn't hide debug messages completely.

the source of messages:
/VirtIO/VirtIOPCICommon.c

```
/* The notify function used when creating a virt queue, common to both modern

• and legacy (the difference is in how vq->notification_addr is set up).
  */
  bool vp_notify(struct virtqueue *vq)
  {
  /* we write the queue's selector into the notification register to
• signal the other end */
  iowrite16(vq->vdev, (unsigned short)vq->index, vq->notification_addr);
  DPrintf(6, "virtio: vp_notify vq->index = %x\n", vq->index);
  return true;
  }
  ```
  Someone driver sets debug level >= 6