** 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 - 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,host:localhost,port:55298,server,nowait --> DOES NOT WORK - - meaning I cannot ssh into the vm + --> THIS 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,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=n1,hostfwd=tcp::2222-:22 -device virtio-net-pci,netdev=n1 - -device virtio-serial -device virtserialport,chardev=cid0 -chardev - file,id=cid0,path=temp,server,nowait + 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 file,id=cid0,path=temp,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
** 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 + 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 --> THIS 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,host:localhost,port:55298,server,nowait + 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,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=n1,hostfwd=tcp::2222-:22 - -device virtio-net-pci,netdev=n1 - -device virtio-serial -device virtserialport,chardev=cid0 - -chardev file,id=cid0,path=temp,server,nowait + 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 file,id=cid0,path=temp,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 ** 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 --> THIS 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,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=n1,hostfwd=tcp::2222-:22 -device virtio-net-pci,netdev=n1 - -device virtio-serial -device virtserialport,chardev=cid0 + -device virtio-serial + -device virtserialport,chardev=cid0 -chardev file,id=cid0,path=temp,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 ** 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 --> THIS 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,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=n1,hostfwd=tcp::2222-:22 -device virtio-net-pci,netdev=n1 - -device virtio-serial - -device virtserialport,chardev=cid0 + -device virtio-serial + -device virtserialport,chardev=cid0 -chardev file,id=cid0,path=temp,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. + Also, if I enable the display, I am unable to type anything in the + emulator window when I use virtserialport. + 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=n1,hostfwd=tcp::2222-:22 -device virtio-net-pci,netdev=n1 --> THIS 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,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=n1,hostfwd=tcp::2222-:22 -device virtio-net-pci,netdev=n1 -device virtio-serial -device virtserialport,chardev=cid0 - -chardev file,id=cid0,path=temp,server,nowait + -chardev file,id=cid0,path=temp No matter which character device I use for my virtserialport communication (socket or udp or file or pipe), the hostfwd doesn't work. Also, if I enable the display, I am unable to type anything in the emulator window when I use virtserialport. 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=n1,hostfwd=tcp::2222-:22 -device virtio-net-pci,netdev=n1 --> THIS 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,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=n1,hostfwd=tcp::2222-:22 -device virtio-net-pci,netdev=n1 -device virtio-serial -device virtserialport,chardev=cid0 - -chardev file,id=cid0,path=temp + -chardev file,id=cid0,path=mypath No matter which character device I use for my virtserialport communication (socket or udp or file or pipe), the hostfwd doesn't work. Also, if I enable the display, I am unable to type anything in the emulator window when I use virtserialport. 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 --> THIS 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,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=n1,hostfwd=tcp::2222-:22 -device virtio-net-pci,netdev=n1 -device virtio-serial -device virtserialport,chardev=cid0 -chardev file,id=cid0,path=mypath No matter which character device I use for my virtserialport communication (socket or udp or file or pipe), the hostfwd doesn't work. Also, if I enable the display, I am unable to type anything in the emulator window when I use virtserialport. 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
