Bug 1272483 - [RFE] chardev append support
[RFE] chardev append support
Product: Fedora
Classification: Fedora
Component: qemu (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Fedora Virtualization Maintainers
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-10-16 10:05 EDT by Attila Fazekas
Modified: 2015-10-19 17:35 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-10-19 17:35:58 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Attila Fazekas 2015-10-16 10:05:18 EDT
Description of problem:

qemu has multiple chardev options, but one of the simplest is not possible.

Basically, I have a libvirt domain where I would like to have all serial console output logged to a single big file, regardless to the number of domain start/stop cycles.

This configuration:

    <console type='file'>
      <source path='/opt/stack/new/ironic-bm-logs/baremetalbrbm_24_console.log'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>

leads to these qemu options:

 -device isa-serial,chardev=charserial0,id=serial0 -chardev file,id=charserial0,path=/opt/stack/new/ironic-bm-logs/baremetalbrbm_24_console.log

qemu at every restart recreates the file, because it was opened with

Version-Release number of selected component (if applicable):

Expected results:

-chardev file,id=charserial0,path=/opt/stack/new/ironic-bm-logs,append

qemu should be able to recognize an option like 'append' and open the file in appending mode, instead of truncating.

This option should be available via libvirt as well.
Comment 1 Cole Robinson 2015-10-19 17:35:58 EDT
FWIW the request seems reasonable to me, but I'm not much of a qemu developer.

Unfortunately RFEs in the Fedora tracker are unlikely to generate any movement, this is really for tracking bugs specific to fedora.

Since it looks like you are using openstack, is this something you want for openstack to use? If so, I'd suggest filing a RHEL qemu-kvm bug and make your case there, that's probably the best way to generate movement for an RFE.

Otherwise please file this in the upstream qemu tracker, and maybe one of the upstream devs will see it go by and jump on it... otherwise your best bet is implementing it yourself :)

Note You need to log in before you can comment on or make changes to this bug.