Your message dated Tue, 03 Jul 2012 22:49:56 +0400
with message-id <[email protected]>
and subject line Re: Bug#645337: serial chardev backend not supported
has caused the Debian Bug report #645337,
regarding serial chardev backend not supported
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
645337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645337
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-kvm
Version: 1:0.14.1+dfsg-4
Severity: normal
Tags: upstream

The manpage speaks of a serial -chardev:

   -chardev backend ,id=id [,mux=on|off] [,options]
       Backend is one of: null, socket, udp, msmouse, vc, file,
       pipe, console, serial, pty, …

However, if one wants to use the serial backend (which presumably
gives raw access to the serial port), kvm says

  chardev: backend "serial" not found

For most applications, tty or console will be a viable backend, but
if one needs raw serial port access, then the serial backend would
be needed.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-rc4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages kvm depends on:
ii  qemu-kvm  0.14.1+dfsg-4

kvm recommends no packages.

kvm suggests no packages.

Versions of packages qemu-kvm depends on:
ii  adduser          3.113               
ii  ipxe             1.0.0+git-2.149b50-1
ii  libaio1          0.3.109-2           
ii  libasound2       1.0.24.1-4          
ii  libattr1         1:2.4.46-3          
ii  libbluetooth3    4.96-3              
ii  libbrlapi0.5     4.2-8+b1            
ii  libc6            2.13-21             
ii  libcurl3-gnutls  7.21.7-3            
ii  libgnutls26      2.12.11-1           
ii  libjpeg8         8c-2                
ii  libncurses5      5.9-2               
ii  libpng12-0       1.2.46-3            
ii  libpulse0        1.0-4               
ii  libsasl2-2       2.1.25.dfsg1-2      
ii  libsdl1.2debian  1.2.14-6.4          
ii  libuuid1         2.19.1-5            
ii  libvdeplug2      2.2.3-3+b1          
ii  libx11-6         2:1.4.4-2           
ii  python           2.6.7-3             
ii  qemu-keymaps     0.15.0+dfsg-1       
ii  qemu-utils       0.15.0+dfsg-1       
ii  seabios          0.6.1.2-3           
ii  vgabios          0.6c-3              
ii  zlib1g           1:1.2.3.4.dfsg-3    

Versions of packages qemu-kvm recommends:
ii  bridge-utils  1.5-2     
ii  iproute       20110629-1

Versions of packages qemu-kvm suggests:
ii  debootstrap  <none>    
ii  samba        <none>    
ii  vde2         2.2.3-3+b1

-- no debconf information


-- 
 .''`.   martin f. krafft <[email protected]>      Related projects:
: :'  :  proud Debian developer               http://debiansystem.info
`. `'`   http://people.debian.org/~madduck    http://vcs-pkg.org
  `-  Debian - when you have better things to do than fixing systems

Attachment: digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)


--- End Message ---
--- Begin Message ---
On 29.01.2012 19:40, Michael Tokarev wrote:
> [Acting on old bugs...]
[Again]

> On 14.10.2011 19:30, martin f krafft wrote:
>> Package: qemu-kvm
>> Version: 1:0.14.1+dfsg-4
>> Severity: normal
>> Tags: upstream
>>
>> The manpage speaks of a serial -chardev:
>>
>>    -chardev backend ,id=id [,mux=on|off] [,options]
>>        Backend is one of: null, socket, udp, msmouse, vc, file,
>>        pipe, console, serial, pty, …
>>
>> However, if one wants to use the serial backend (which presumably
>> gives raw access to the serial port), kvm says
>>
>>   chardev: backend "serial" not found
>>
>> For most applications, tty or console will be a viable backend, but
>> if one needs raw serial port access, then the serial backend would
>> be needed.
> 
> What is "raw serial port access"?
> 
> The -chardev serial is only available on windows platform, since
> their COMx: devices needs special attention, regulare reads/writes
> does not quite work on these like in unix.
> 
> If you really want "raw serial port access", whatever does it mean,
> shouldn't this be a wishlist bug?
> 
> In any way, the manpage is a bit wrong here: it correctly omits
> the 'serial backend' description on non-windows platform, but still
> mentions 'serial' in the -chardev brief description.

I'm closing this bugreport now, since apparently there's no bug per
se, just like with the cousin bug about the same issue I closed today.
If it is still important or if I'm wrong, let's reopen it.

Thank you for your patience!

/mjt


--- End Message ---

Reply via email to