From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 91F9DC433DB for ; Fri, 22 Jan 2021 23:21:26 +0000 (UTC) Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 16DAA23B51 for ; Fri, 22 Jan 2021 23:21:25 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 16DAA23B51 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=bugs.launchpad.net Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Received: from localhost ([::1]:55124 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l35k5-0001HA-3t for qemu-devel@archiver.kernel.org; Fri, 22 Jan 2021 18:21:25 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:57540) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l35jM-0000jk-64 for qemu-devel@nongnu.org; Fri, 22 Jan 2021 18:20:40 -0500 Received: from indium.canonical.com ([91.189.90.7]:50670) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1l35jJ-0003Jo-US for qemu-devel@nongnu.org; Fri, 22 Jan 2021 18:20:39 -0500 Received: from loganberry.canonical.com ([91.189.90.37]) by indium.canonical.com with esmtp (Exim 4.86_2 #2 (Debian)) id 1l35jH-0006Hw-Sa for ; Fri, 22 Jan 2021 23:20:35 +0000 Received: from loganberry.canonical.com (localhost [127.0.0.1]) by loganberry.canonical.com (Postfix) with ESMTP id CBD632E8137 for ; Fri, 22 Jan 2021 23:20:35 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Date: Fri, 22 Jan 2021 23:09:47 -0000 From: Ven Karri <1912857@bugs.launchpad.net> To: qemu-devel@nongnu.org X-Launchpad-Notification-Type: bug X-Launchpad-Bug: product=qemu; status=New; importance=Undecided; assignee=None; X-Launchpad-Bug-Information-Type: Public X-Launchpad-Bug-Private: no X-Launchpad-Bug-Security-Vulnerability: no X-Launchpad-Bug-Commenters: imperialguy X-Launchpad-Bug-Reporter: Ven Karri (imperialguy) X-Launchpad-Bug-Modifier: Ven Karri (imperialguy) References: <161135175608.19792.5002633896122919993.malonedeb@wampee.canonical.com> Message-Id: <161135698798.20013.1879270459630073174.launchpad@wampee.canonical.com> Subject: [Bug 1912857] Re: virtio-serial blocks hostfwd ssh on windows 10 host X-Launchpad-Message-Rationale: Subscriber (QEMU) @qemu-devel-ml X-Launchpad-Message-For: qemu-devel-ml Precedence: bulk X-Generated-By: Launchpad (canonical.com); Revision="2d1d5e352f0d063d660df2300e31f66bed027fa5"; Instance="production" X-Launchpad-Hash: 4927d6f6ec48f5a560c5c05db63c690570dd9537 Received-SPF: none client-ip=91.189.90.7; envelope-from=bounces@canonical.com; helo=indium.canonical.com X-Spam_score_int: -65 X-Spam_score: -6.6 X-Spam_bar: ------ X-Spam_report: (-6.6 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.23 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Bug 1912857 <1912857@bugs.launchpad.net> Errors-To: qemu-devel-bounces+qemu-devel=archiver.kernel.org@nongnu.org Sender: "Qemu-devel" ** Description changed: qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=3Dn1,hostfwd=3Dtcp::2222-:22 -device virtio-net-pci,netdev=3Dn1 -= -> 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=3Dn1,hostfwd=3Dtcp::2222-:22 -device virtio-net-pci,netdev=3Dn1 -device virtio-serial -device virtserialport,chardev=3Dcid0 -chardev - socket,id=3Dcid0,{socket_addr_serial},server,nowait --> DOES NOT WORK - - meaning I cannot ssh into the vm + socket,id=3Dcid0,host:localhost,port:55298,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. = + The following doesn't work either: + = + qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev + user,id=3Dn1,hostfwd=3Dtcp::2222-:22 -device virtio-net-pci,netdev=3Dn1 + -device virtio-serial -device virtserialport,chardev=3Dcid0 -chardev + file,id=3Dcid0,path=3Dtemp,server,nowait + = + No matter which character device I use for my virtio-serial-port + communication (socket or udp or file or pipe), the hostfwd doesn't work. + = Host: Windows 10 Guest: archlinux QEMU version 5.2 ** Description changed: qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=3Dn1,hostfwd=3Dtcp::2222-:22 -device virtio-net-pci,netdev=3Dn1 -= -> 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=3Dn1,hostfwd=3Dtcp::2222-:22 -device virtio-net-pci,netdev=3Dn1 -device virtio-serial -device virtserialport,chardev=3Dcid0 -chardev socket,id=3Dcid0,host:localhost,port:55298,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. = The following doesn't work either: = qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=3Dn1,hostfwd=3Dtcp::2222-:22 -device virtio-net-pci,netdev=3Dn1 -device virtio-serial -device virtserialport,chardev=3Dcid0 -chardev file,id=3Dcid0,path=3Dtemp,server,nowait = - No matter which character device I use for my virtio-serial-port + No matter which character device I use for my virtserialport communication (socket or udp or file or pipe), the hostfwd doesn't work. = 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 =C2=A0=C2=A0-display none =C2=A0=C2=A0-hda archlinux.qcow2 =C2=A0=C2=A0-m 4G =C2=A0=C2=A0-netdev user,id=3Dn1,hostfwd=3Dtcp::2222-:22 =C2=A0=C2=A0-device virtio-net-pci,netdev=3Dn1 --> THIS WORKS - meaning I can ssh into the vm via port 2222 qemu-system-x86_64 =C2=A0=C2=A0-display none =C2=A0=C2=A0-hda archlinux.qcow2 =C2=A0=C2=A0-m 4G =C2=A0=C2=A0-netdev user,id=3Dn1,hostfwd=3Dtcp::2222-:22 =C2=A0=C2=A0-device virtio-net-pci,netdev=3Dn1 =C2=A0=C2=A0-device virtio-serial =C2=A0=C2=A0-device virtserialport,chardev=3Dcid0 =C2=A0=C2=A0-chardev socket,id=3Dcid0,host=3Dlocalhost,port=3D55298,serve= r,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. The following doesn't work either: qemu-system-x86_64 =C2=A0=C2=A0-display none =C2=A0=C2=A0-hda archlinux.qcow2 =C2=A0=C2=A0-m 4G =C2=A0=C2=A0-netdev user,id=3Dn1,hostfwd=3Dtcp::2222-:22 =C2=A0=C2=A0-device virtio-net-pci,netdev=3Dn1 =C2=A0=C2=A0-device virtio-serial = -device virtserialport,chardev=3Dcid0 =C2=A0=C2=A0-chardev file,id=3Dcid0,path=3Dtemp,server,nowait No matter which character device I use for my virtserialport communication (socket or udp or file or pipe), the hostfwd doesn't work. 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