diff options
Diffstat (limited to 'results/classifier/105/graphic/1916343')
| -rw-r--r-- | results/classifier/105/graphic/1916343 | 75 |
1 files changed, 75 insertions, 0 deletions
diff --git a/results/classifier/105/graphic/1916343 b/results/classifier/105/graphic/1916343 new file mode 100644 index 00000000..1e7f0aac --- /dev/null +++ b/results/classifier/105/graphic/1916343 @@ -0,0 +1,75 @@ +graphic: 0.922 +semantic: 0.918 +other: 0.908 +mistranslation: 0.871 +instruction: 0.851 +device: 0.847 +vnc: 0.822 +assembly: 0.817 +socket: 0.782 +network: 0.725 +boot: 0.693 +KVM: 0.663 + +-daemonize not working on macOS + +Basically e.g, if I try with below command on macOS: + +qemu-system-x86_64 \ + -m 4G \ + -vga virtio \ + -display default,show-cursor=on \ + -usb \ + -device usb-tablet \ + -machine type=q35,accel=hvf \ + -smp 2 \ + -drive file=ubuntu.qcow2,if=virtio -cpu max \ + -net nic -net user,hostfwd=tcp::50022-:22,hostfwd=tcp::8000-:80 \ + -daemonize + +With this command, the QEMU processes hang there forever. I guess there is a bug when forking a child and kill the parent? Because when this issue occurs, there are actually 2 QEMU processes running + +``` + 501 14952 14951 0 7:08PM ?? 0:00.00 (qemu-system-x86_) + 501 14953 1 0 7:08PM ?? 0:00.03 qemu-system-x86_64 -m 4G -vga virtio -display default,show-cursor=on -usb -device usb-tablet -machine type=q35,accel=hvf -smp 2 -drive file=ubuntu.qcow2,if=virtio -cpu max -net nic -net user,hostfwd=tcp::50022-:22,hostfwd=tcp::8000-:80 -daemonize + 501 14951 14626 0 7:08PM ttys000 0:00.03 qemu-system-x86_64 -m 4G -vga virtio -display default,show-cursor=on -usb -device usb-tablet -machine type=q35,accel=hvf -smp 2 -drive file=ubuntu.qcow2,if=virtio -cpu max -net nic -net user,hostfwd=tcp::50022-:22,hostfwd=tcp::8000-:80 -daemonize +``` + +The QEMU project is currently moving its bug tracking to another system. +For this we need to know which bugs are still valid and which could be +closed already. Thus we are setting the bug state to "Incomplete" now. + +If the bug has already been fixed in the latest upstream version of QEMU, +then please close this ticket as "Fix released". + +If it is not fixed yet and you think that this bug report here is still +valid, then you have two options: + +1) If you already have an account on gitlab.com, please open a new ticket +for this problem in our new tracker here: + + https://gitlab.com/qemu-project/qemu/-/issues + +and then close this ticket here on Launchpad (or let it expire auto- +matically after 60 days). Please mention the URL of this bug ticket on +Launchpad in the new ticket on GitLab. + +2) If you don't have an account on gitlab.com and don't intend to get +one, but still would like to keep this ticket opened, then please switch +the state back to "New" or "Confirmed" within the next 60 days (other- +wise it will get closed as "Expired"). We will then eventually migrate +the ticket automatically to the new system (but you won't be the reporter +of the bug in the new system and thus you won't get notified on changes +anymore). + +Thank you and sorry for the inconvenience. + + + +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/313 + + |