| commit | 7af4796d491cb19a15cf003a94b67868435830ef | |
| author | Michael Roth <mdroth@linux.vnet.ibm.com> | |
| Mon, 8 Nov 2010 14:45:27 +0000 (8 08:45 -0600) | ||
| committer | Michael Roth <mdroth@linux.vnet.ibm.com> | |
| Mon, 8 Nov 2010 14:45:27 +0000 (8 08:45 -0600) | ||
| tree | beba34dc5ca7ede4e21ccb26fd0a4bd4b370d2dd | treesnapshot (tar.gz zip) |
| parent | 13ec12921a6a055638adacbdefe171217ef5e18e | commitdiff |
virtproxy: integration, add a virtproxy chardev
This allows us to create a virtproxy instance via a chardev. It can now
be created with something like:
qemu -chardev virtproxy,id=vp1 \
-device virtio-serial \
-device virtserialport,chardev=vp1
In the future the ability to add oforwards/iforwards in the command-line
invocation and the monitor will be added. For now we leave it to users
of virtproxy (currently only virtagent) to set up the forwarding
sockets/ports they need via direct virtproxy API calls.
This allows us to create a virtproxy instance via a chardev. It can now
be created with something like:
qemu -chardev virtproxy,id=vp1 \
-device virtio-serial \
-device virtserialport,chardev=vp1
In the future the ability to add oforwards/iforwards in the command-line
invocation and the monitor will be added. For now we leave it to users
of virtproxy (currently only virtagent) to set up the forwarding
sockets/ports they need via direct virtproxy API calls.
| qemu-char.c | diffblobblamehistory |