Your message dated Tue, 03 Jul 2012 18:14:05 +0400
with message-id <[email protected]>
and subject line Re: Bug#645336: -device XXX replacements for -serial &
-usbdevice not working (libvirt uses them)
has caused the Debian Bug report #645336,
regarding -device XXX replacements for -serial & -usbdevice not working
(libvirt uses them)
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.)
--
645336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645336
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qemu-kvm
Version: 1:0.14.1+dfsg-4
Severity: normal
Instead of the classic command line switches like -serial and
-usbdevice, libvirt invokes kvm with the more generic syntax, e.g.
-device serial,…
-device usb_host,…
Unfortunately, kvm does not seem to support those, and the device is
not made available to the guest. If I manually influence the command
line and use the classic command line switches, then it works,
however.
The reason why libvirt uses those generic -device lines is due to
hotplug support. Apparently -device … is hotpluggable, while
-usbdevice is not.
It would be good if kvm would support those generic device
specifications, not only because it advertises them in its manpage,
but mostly because libvirt makes use of them already.
Thanks,
-- 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
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
--- End Message ---
--- Begin Message ---
14.05.2012 13:28, martin f krafft пишет:
> also sprach Michael Tokarev <[email protected]> [2012.05.02.1940 +0200]:
>> Ping? Any information about this bug?
>
> I am afraid I have moved on and don't have the machine in front of me
> anymore. The situation was that a guest needed to provide a serial port to
> Windows, but the serial port was on another machine than the host (using
> ser2net).
>
> In the end, I was forced to add the following to the libvirt domain XML:
>
> <qemu:commandline> <qemu:arg value='-serial'/> <qemu:arg
> value='tcp:wall:2000'/> </qemu:commandline>
>
> because everything else didn't work.
>
> I just tried this all again with Sid's kvm/libvirt and adding a serial port
> with a TCP backend does seem to work, so we can close the bug report…
>
> <serial type='tcp'> <source mode='connect' host='wall' service='2000'/>
> <protocol type='raw'/> <target port='0'/> </serial> <console type='tcp'>
> <source mode='connect' host='wall' service='2000'/> <protocol type='raw'/>
> <target type='serial' port='0'/> </console>
>
> yields:
>
> -chardev socket,id=charserial0,host=wall,port=2000 -device
> isa-serial,chardev=charserial0,id=serial0
Okay, fine, closing this bugreport now.
Thank you!
/mjt
--- End Message ---
