From: Thomas Huth <1819108@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1819108] Re: qemu-bridge-helper failure but qemu not exit
Date: Wed, 05 May 2021 11:18:04 -0000 [thread overview]
Message-ID: <162021348439.6519.12420713318335442974.malone@wampee.canonical.com> (raw)
In-Reply-To: 155202794501.28960.14152482675587823273.malonedeb@wampee.canonical.com
This is an automated cleanup. This bug report has been moved to QEMU's
new bug tracker on gitlab.com and thus gets marked as 'expired' now.
Please continue with the discussion here:
https://gitlab.com/qemu-project/qemu/-/issues/166
** Changed in: qemu
Status: New => Expired
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #166
https://gitlab.com/qemu-project/qemu/-/issues/166
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1819108
Title:
qemu-bridge-helper failure but qemu not exit
Status in QEMU:
Expired
Bug description:
When qemu-bridge-helper run failed, its parent process qemu is still alive.
This is my command line:
qemu-system-x86_64 -curses -enable-kvm -cpu host -smp 4 -m 4096 \
-vnc :1 \
-kernel /data/xugang_vms/boot/vmlinuz \
-initrd /data/xugang_vms/boot/initram \
-append 'module_blacklist=drm,evbug net.ifnames=0 biosdevname=0 ROOTDEV=rootfs' \
-drive file=/data/xugang_vms/instances/vn7/rootfs.img,format=qcow2,if=virtio \
-monitor unix:/data/xugang_vms/var/monitor/vn7.sock,server,nowait \
-netdev bridge,br=vmbr99,helper="/root/bridgehelper --ns=kvm_1 ",id=n1 -device virtio-net,netdev=n1,mac=92:99:98:76:01:07
"/root/bridgehelper" is self defined helper binary by me. But after
bridge-helper exited with failure(not send fd to qemu process yet),
the linux vm's console will be messed up. I checked the qemu source
code(at net/tap.c) and found following snip:
===>
do {
fd = recv_fd(sv[0]);
} while (fd == -1 && errno == EINTR);
saved_errno = errno;
close(sv[0]);
while (waitpid(pid, &status, 0) != pid) {
/* loop */
}
<=========
why recv_fd will infinitely wait for recv? Maybe it shall waitpid and
then recv_fd ?
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1819108/+subscriptions
prev parent reply other threads:[~2021-05-05 11:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 6:52 [Qemu-devel] [Bug 1819108] [NEW] qemu-bridge-helper failure but qemu not exit cavanxg
2021-05-05 11:18 ` Thomas Huth [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=162021348439.6519.12420713318335442974.malone@wampee.canonical.com \
--to=1819108@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.