http://bugzilla.suse.com/show_bug.cgi?id=1166419 http://bugzilla.suse.com/show_bug.cgi?id=1166419#c4 Michal Suchanek <msuchanek@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(msuchanek@suse.co | |m) | --- Comment #4 from Michal Suchanek <msuchanek@suse.com> --- shell is bash. not sure if timeout is builtin. The thing is that qemu tries to do something 'clever' here. If you do qemu-system-x86_64 -cpu core2duo -smp cores=2,threads=2,sockets=2 -m 1024 -nographic -no-reboot -kernel /srv/build/x86_64_ref/arch/x86/boot/bzImage -append console=ttyS0\ panic=-1 it fucks up your terminal if you do qemu-system-x86_64 -cpu core2duo -smp cores=2,threads=2,sockets=2 -m 1024 -nographic -no-reboot -kernel /srv/build/x86_64_ref/arch/x86/boot/bzImage -append console=ttyS0\ panic=-1 >boot.log 2>&1 < /dev/null & you know the PID of qemu and can kill it but it fucks up your terminal if you do res="$(qemu-system-x86_64 -cpu core2duo -smp cores=2,threads=2,sockets=2 -m 1024 -nographic -no-reboot -kernel /srv/build/x86_64_ref/arch/x86/boot/bzImage -append console=ttyS0\ panic=-1 | tail -n 1)" ; echo "$res" your terminal is not fucked up but you don't know the PID of qemu and if it locks up it never ends if you do res="$(timeout 30 qemu-system-x86_64 -cpu core2duo -smp cores=2,threads=2,sockets=2 -m 1024 -nographic -no-reboot -kernel /srv/build/x86_64_ref/arch/x86/boot/bzImage -append console=ttyS0\ panic=-1 | tail -n 1)" ; echo "$res" you get no output -- You are receiving this mail because: You are on the CC list for the bug.