All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ven Karri <1912857@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1912857] Re: virtio-serial blocks hostfwd ssh on windows 10 host
Date: Fri, 22 Jan 2021 22:48:05 -0000	[thread overview]
Message-ID: <161135568608.10605.8266017330272740569.launchpad@gac.canonical.com> (raw)
In-Reply-To: 161135175608.19792.5002633896122919993.malonedeb@wampee.canonical.com

** Description changed:

  qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev
  user,id=n1,hostfwd=tcp::2222-:22 -device virtio-net-pci,netdev=n1 -->
  WORKS - meaning I can ssh into the vm via port 2222
  
  qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev
  user,id=n1,hostfwd=tcp::2222-:22 -device virtio-net-pci,netdev=n1
- -device virtio-serial -serial tcp:localhost:55298,server,nowait --> DOES
- NOT WORK - meaning I cannot ssh into the vm
+ -device virtio-serial -device virtserialport,chardev=cid0 -chardev
+ socket,id=cid0,{socket_addr_serial},server,nowait --> DOES NOT WORK -
+ meaning I cannot ssh into the vm
  
  Not only does the port 2222 not work, but I am not able to perform any
  serial transfer on port 55298 as well.
  
  Host: Windows 10
  Guest: archlinux
  QEMU version 5.2

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1912857

Title:
  virtio-serial blocks hostfwd ssh on windows 10 host

Status in QEMU:
  New

Bug description:
  qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev
  user,id=n1,hostfwd=tcp::2222-:22 -device virtio-net-pci,netdev=n1 -->
  WORKS - meaning I can ssh into the vm via port 2222

  qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev
  user,id=n1,hostfwd=tcp::2222-:22 -device virtio-net-pci,netdev=n1
  -device virtio-serial -device virtserialport,chardev=cid0 -chardev
  socket,id=cid0,{socket_addr_serial},server,nowait --> DOES NOT WORK -
  meaning I cannot ssh into the vm

  Not only does the port 2222 not work, but I am not able to perform any
  serial transfer on port 55298 as well.

  Host: Windows 10
  Guest: archlinux
  QEMU version 5.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1912857/+subscriptions


  reply	other threads:[~2021-01-22 22:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22 21:42 [Bug 1912857] [NEW] virtio-serial blocks hostfwd ssh on windows 10 host Ven Karri
2021-01-22 22:48 ` Ven Karri [this message]
2021-01-22 23:09 ` [Bug 1912857] " Ven Karri
2021-01-22 23:18 ` Ven Karri
2021-01-22 23:45 ` Ven Karri
2021-05-12 18:00 ` Thomas Huth
2021-07-12  4:17 ` Launchpad Bug Tracker

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=161135568608.10605.8266017330272740569.launchpad@gac.canonical.com \
    --to=1912857@bugs.launchpad.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.