Bug 1005677

Created attachment 795667 [details]
Guest script which repeatedly writes some data into vs1 serial port.

Hi guys, I was asked in another similar bug https://bugzilla.redhat.com/show_bug.cgi?id=1005150 to retest this.

Host (F19):
upstream qemu-1.6.50 (2d1fe1873a984d1c2c89ffa3d12949cafc718551)
Guest (F19):
kernel-3.11.1-200.fc19.x86_64

Following the same steps results in the same results. Only now I saw a kernel message:
[  209.822469] virtio_console virtio0: output:id 102 is not a head!

in the serial console log. After this message there were few plug/unplug iterations and than exit with ret = 1.

The output of serial console (-serial stdio), where I executed the simple_reproducer.py:

[root@localhost tmp]# python repr.py 


[Errno 19] No such device
[Errno 19] No such device
[Errno 19] No such device
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'

# CUT

[Errno 19] No such device
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 19] No such device
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 19] No such device
[Errno 19] No such device
[Errno 19] No such device
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[  209.822469] virtio_console virtio0: output:id 102 is not a head!
[Errno 19] No such device
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 19] No such device
[Errno 19] No such device
[Errno 19] No such device
[Errno 19] No such device
[Errno 6] No such device or address: '/dev/virtio-ports/vs1'
[Errno 6] No such device or address: '/dev/virtio-ports/vs1'
[Errno 19] No such device
[Errno 19] No such device

# CUT

[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'
[Errno 2] No such file or directory: '/dev/virtio-ports/vs1'[medic@localhost ~ 1]$

So now qemu doesn't quit?

That means this the bug you were seeing was related to the guest kernel failing.  With the new kernel, you don't see anything similar?

Hi Amit, unfortunately not. Qemu is the process, which dies with ret = 1. No messages in the qemu log, serial, nor in ssh.

This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Retested on:

host: kernel-3.17.2-200.fc20.x86_64
qemu: upstream tag v2.2.0-rc5
guest: kernel-3.17.8-200.fc20

with the same results. It dies in less then 1 second.

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

OK I give up. I had been retesting this every couple of months for 2 years now without any response. Feel free to test it yourself, the simple reproducer is in the report.

Sorry this has lagged for so long, but the fedora qemu tracker only gets so much attention. The best way to get this realistically fixed IMO is to reproduce it against a RHEL version and file the bug + reproducer there, and QE will probably run with it

One way of ensuring someone's looking at it is to assign it to the relevant person.  In this case, that's me, and I could (should!) have assigned this bug to myself when I saw it.  Fixing that now.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.