No one replied to my mail. Someone might think I was talking nonsense. When the
DVS service stopped, all our QEMU processes exited. DVS users complain that
even if their DVS services are stopped, vhost-user networks should not be
blocked, but virtual machines should not be allowed to exit. I fo
From: "yin.zuowei"
Signed-off-by: yin.zuowei
---
chardev/char-fe.c | 8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/chardev/char-fe.c b/chardev/char-fe.c
index 3f90f05..82f7e2b 100644
--- a/chardev/char-fe.c
+++ b/chardev/char-fe.c
@@ -353,7 +353,13 @@ guint qemu_chr_f
That's true. Let me confirm to you whether this problem exists or whether there
are any solutions already available. If so, I would like you to tell me the
existing solution. My patch comes from the company code, and the code is
long.The notes are written in Chinese. We work too much and don't h
From: "yin.zuowei"
Signed-off-by: yin.zuowei
bug description: In the windows virtual machine, if there are multiple network
cards, the hypothesis is that A/B/C is equipped with a different IP address.
Once you delete a B card in the middle and restart the virtual machine, you
will find that
From: "yin.zuowei"
Signed-off-by: yin.zuowei
when ovdk socket is not ok, this vhost_dev is null ,then qemu will be quit.
We think ovdk is just a network devices, should not cause an exit .
---
hw/virtio/vhost-user.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/hw/virtio/vhost-user.c
