On 2012-06-03 09:45, Alexander Graf wrote:
> When using guestfwd=, Qemu only connects the virtual server's TCP port
> to a single chardev. This is useless in most cases, as we usually want
> to have more than a single connection from the guest to the outside world.
>
> This patch adds a new cmd: t
When using guestfwd=, Qemu only connects the virtual server's TCP port
to a single chardev. This is useless in most cases, as we usually want
to have more than a single connection from the guest to the outside world.
This patch adds a new cmd: target to guestfwd= that allows for execution
of a com
On 2012-05-31 01:08, Alexander Graf wrote:
>
> On 04.06.2011, at 08:12, Alexander Graf wrote:
>
>> When using guestfwd=, Qemu only connects the virtual server's TCP port
>> to a single chardev. This is useless in most cases, as we usually want
>> to have more than a single connection from the gue
On 05/31/2012 07:08 AM, Alexander Graf wrote:
On 04.06.2011, at 08:12, Alexander Graf wrote:
When using guestfwd=, Qemu only connects the virtual server's TCP port
to a single chardev. This is useless in most cases, as we usually want
to have more than a single connection from the guest to the
On 04.06.2011, at 08:12, Alexander Graf wrote:
> When using guestfwd=, Qemu only connects the virtual server's TCP port
> to a single chardev. This is useless in most cases, as we usually want
> to have more than a single connection from the guest to the outside world.
>
> This patch adds a new
When using guestfwd=, Qemu only connects the virtual server's TCP port
to a single chardev. This is useless in most cases, as we usually want
to have more than a single connection from the guest to the outside world.
This patch adds a new cmd: target to guestfwd= that allows for execution
of a com
