[Bug 1912857] Re: virtio-serial blocks hostfwd ssh on windows 10 host
[Expired for QEMU because there has been no activity for 60 days.] ** Changed in: qemu Status: Incomplete => Expired -- 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: Expired Bug description: qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=n1,hostfwd=tcp::-:22 -device virtio-net-pci,netdev=n1 --> THIS WORKS - meaning I can ssh into the vm via port qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=n1,hostfwd=tcp::-: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 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::-: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 The same thing works just fine on a Mac OS X host (tested on Big Sur) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1912857/+subscriptions
[Bug 1912857] Re: virtio-serial blocks hostfwd ssh on windows 10 host
The QEMU project is currently moving its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting the bug state to "Incomplete" now. If the bug has already been fixed in the latest upstream version of QEMU, then please close this ticket as "Fix released". If it is not fixed yet and you think that this bug report here is still valid, then you have two options: 1) If you already have an account on gitlab.com, please open a new ticket for this problem in our new tracker here: https://gitlab.com/qemu-project/qemu/-/issues and then close this ticket here on Launchpad (or let it expire auto- matically after 60 days). Please mention the URL of this bug ticket on Launchpad in the new ticket on GitLab. 2) If you don't have an account on gitlab.com and don't intend to get one, but still would like to keep this ticket opened, then please switch the state back to "New" or "Confirmed" within the next 60 days (other- wise it will get closed as "Expired"). We will then eventually migrate the ticket automatically to the new system (but you won't be the reporter of the bug in the new system and thus you won't get notified on changes anymore). Thank you and sorry for the inconvenience. ** Changed in: qemu Status: New => Incomplete -- 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: Incomplete Bug description: qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=n1,hostfwd=tcp::-:22 -device virtio-net-pci,netdev=n1 --> THIS WORKS - meaning I can ssh into the vm via port qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=n1,hostfwd=tcp::-: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 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::-: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 The same thing works just fine on a Mac OS X host (tested on Big Sur) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1912857/+subscriptions
[Bug 1912857] Re: virtio-serial blocks hostfwd ssh on windows 10 host
** Description changed: qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=n1,hostfwd=tcp::-:22 -device virtio-net-pci,netdev=n1 --> THIS WORKS - meaning I can ssh into the vm via port qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=n1,hostfwd=tcp::-: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 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::-: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 + + The same thing works just fine on a Mac OS X host (tested on Big Sur) -- 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::-:22 -device virtio-net-pci,netdev=n1 --> THIS WORKS - meaning I can ssh into the vm via port qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=n1,hostfwd=tcp::-: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 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::-: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 The same thing works just fine on a Mac OS X host (tested on Big Sur) To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1912857/+subscriptions
[Bug 1912857] Re: virtio-serial blocks hostfwd ssh on windows 10 host
** Description changed: - qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev - user,id=n1,hostfwd=tcp::-:22 -device virtio-net-pci,netdev=n1 --> - WORKS - meaning I can ssh into the vm via port + qemu-system-x86_64 + -display none + -hda archlinux.qcow2 + -m 4G + -netdev user,id=n1,hostfwd=tcp::-:22 + -device virtio-net-pci,netdev=n1 - qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev - user,id=n1,hostfwd=tcp::-: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 + + qemu-system-x86_64 + -display none + -hda archlinux.qcow2 + -m 4G + -netdev user,id=n1,hostfwd=tcp::-: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 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::-: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::-: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::-:22 - -device virtio-net-pci,netdev=n1 + qemu-system-x86_64 + -display none + -hda archlinux.qcow2 + -m 4G + -netdev user,id=n1,hostfwd=tcp::-:22 + -device virtio-net-pci,netdev=n1 --> THIS WORKS - meaning I can ssh into the vm via port - qemu-system-x86_64 - -display none - -hda archlinux.qcow2 - -m 4G - -netdev user,id=n1,hostfwd=tcp::-: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::-: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 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::-: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::-: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::-:22 -device virtio-net-pci,netdev=n1 --> THIS WORKS - meaning I can ssh into the vm via port qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=n1,hostfwd=tcp::-: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 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::-:22 -device virtio-net-pci,netdev=n1 - -device virtio-serial -device virtserialport,chardev=cid0 + -device virtio-serial + -device virtseria
[Bug 1912857] Re: virtio-serial blocks hostfwd ssh on windows 10 host
** Description changed: qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=n1,hostfwd=tcp::-:22 -device virtio-net-pci,netdev=n1 --> WORKS - meaning I can ssh into the vm via port qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=n1,hostfwd=tcp::-: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 + socket,id=cid0,host:localhost,port:55298,server,nowait --> DOES NOT WORK + - meaning I cannot ssh into the vm Not only does the port 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::-: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 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=n1,hostfwd=tcp::-:22 -device virtio-net-pci,netdev=n1 --> WORKS - meaning I can ssh into the vm via port qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=n1,hostfwd=tcp::-: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 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::-: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 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 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=n1,hostfwd=tcp::-:22 -device virtio-net-pci,netdev=n1 --> THIS WORKS - meaning I can ssh into the vm via port qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=n1,hostfwd=tcp::-: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 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::-: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 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1912857/+subscriptions
[Bug 1912857] Re: virtio-serial blocks hostfwd ssh on windows 10 host
** Description changed: qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=n1,hostfwd=tcp::-:22 -device virtio-net-pci,netdev=n1 --> WORKS - meaning I can ssh into the vm via port qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=n1,hostfwd=tcp::-: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 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::-:22 -device virtio-net-pci,netdev=n1 --> WORKS - meaning I can ssh into the vm via port qemu-system-x86_64 -display none -hda archlinux.qcow2 -m 4G -netdev user,id=n1,hostfwd=tcp::-: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 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