1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
|
x86: 0.900
architecture: 0.858
virtual: 0.825
user-level: 0.792
hypervisor: 0.777
device: 0.776
network: 0.769
graphic: 0.761
socket: 0.736
permissions: 0.731
mistranslation: 0.728
PID: 0.715
performance: 0.704
ppc: 0.700
kernel: 0.686
register: 0.674
peripherals: 0.672
files: 0.662
KVM: 0.658
semantic: 0.639
arm: 0.636
VMM: 0.549
assembly: 0.533
TCG: 0.530
i386: 0.529
debug: 0.503
vnc: 0.487
risc-v: 0.444
boot: 0.439
--------------------
x86: 0.919
virtual: 0.893
user-level: 0.072
hypervisor: 0.065
debug: 0.051
network: 0.036
semantic: 0.013
TCG: 0.013
files: 0.013
socket: 0.010
PID: 0.010
device: 0.009
performance: 0.006
register: 0.005
boot: 0.005
permissions: 0.005
peripherals: 0.005
architecture: 0.003
assembly: 0.003
risc-v: 0.003
kernel: 0.003
VMM: 0.003
vnc: 0.003
graphic: 0.003
ppc: 0.002
mistranslation: 0.001
KVM: 0.001
arm: 0.001
i386: 0.000
virtio-serial blocks hostfwd ssh on windows 10 host
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
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.
[Expired for QEMU because there has been no activity for 60 days.]
|