virtual: 0.953
network: 0.903
x86: 0.886
graphic: 0.869
performance: 0.862
VMM: 0.844
device: 0.841
vnc: 0.807
mistranslation: 0.791
files: 0.727
PID: 0.699
hypervisor: 0.665
socket: 0.648
semantic: 0.607
register: 0.597
architecture: 0.584
risc-v: 0.575
kernel: 0.538
boot: 0.527
peripherals: 0.523
arm: 0.473
debug: 0.459
ppc: 0.455
permissions: 0.451
i386: 0.436
KVM: 0.430
user-level: 0.364
TCG: 0.347
assembly: 0.272

vhost_user:When configure queues of vhost-user NIC exceeds max_queues, the virtual machine is always paused
Description of problem:
When the virtual machine uses the vhost-user network card and sets the queue number of the network card to exceed the maximum number of supported queues, the virtual machine fails to start and stays in the paused state.
And the virtual machine log file kept print "qemu - system - x86_64: -netdev host-user,chardev=charnet0,queues=5,id=hostnet0:you are asking more queues than supported:4”
Steps to reproduce:
1.Configure vhost-user network cards for VMS and use multiple queues.
2.The number of NIC queues configured in the VM xml file is greater than the maximum number of queues supported by the VM, that is, the number of Vcpus on the VM.
3.Execute "virsh create VM_xml_file" cmd to start VM.
Additional information:
According to normal logic, if the number of configured vhost-user NIC queues exceeds max-queues, the qemu process should be stopped, rather than paused the virtual machine.
I am confused about this patch:https://github.com/qemu/qemu/commit/c89804d674e4e3804bd3ac1fe79650896044b4e8
The process will remain in the do...while loop, when vhost_user_start is called in net_vhost_user_event, if queues > max_queues in vhost_user_start.
/label ~"kind::Bug"
```