QEMU

  1. Bug #1912857
  2. Activity log

Activity log for bug #1912857

Date Who What changed Old value New value Message
2021-01-22 21:42:35 Ven Karri bug added bug
2021-01-22 21:47:33 Ven Karri 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 -serial tcp:localhost:55298,server,nowait --> DOES NOT WORK - meaning I cannot ssh into the vm Not only does the port 2222 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 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 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
2021-01-22 22:48:05 Ven Karri 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 -serial tcp:localhost: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. Host: Windows 10 Guest: archlinux QEMU version 5.2 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
2021-01-22 23:09:47 Ven Karri 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 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,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 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
2021-01-22 23:10:27 Ven Karri 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,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 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 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,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 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
2021-01-22 23:18:24 Ven Karri 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,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 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 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 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
2021-01-22 23:19:44 Ven Karri 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=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 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 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
2021-01-22 23:20:06 Ven Karri 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=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 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 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
2021-01-22 23:22:13 Ven Karri 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=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 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 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
2021-01-22 23:25:04 Ven Karri 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=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 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 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
2021-01-22 23:25:38 Ven Karri 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=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 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
2021-01-22 23:45:53 Ven Karri 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 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 The same thing works just fine on a Mac OS X host (tested on Big Sur)
2021-05-12 18:00:08 Thomas Huth qemu: status New Incomplete
2021-07-12 04:17:55 Launchpad Janitor qemu: status Incomplete Expired