blob: 01635ce85129e2abf750ba13b785591893818f8e (
plain) (
blame)
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
|
VMM: 0.753
device: 0.725
socket: 0.721
graphic: 0.699
virtual: 0.671
network: 0.669
performance: 0.653
mistranslation: 0.558
hypervisor: 0.557
peripherals: 0.552
KVM: 0.550
PID: 0.521
risc-v: 0.520
i386: 0.512
debug: 0.509
kernel: 0.501
register: 0.488
ppc: 0.485
vnc: 0.477
semantic: 0.477
permissions: 0.465
architecture: 0.461
files: 0.455
x86: 0.443
boot: 0.435
user-level: 0.433
assembly: 0.374
TCG: 0.367
arm: 0.300
Serial communication between VMs problematic
Hello,
I want to setup serial communication between VM hosts but I have found it quite difficult...:
...because when trying unix sockets:
- host A has serial device as unix socket (bind)
- host B has serial device as client of unix socket
- host A is down thus not unix socket does exist
- host B can't be started because cannot read the socket:
error: Failed to start domain opd1s02
error: internal error Process exited while reading console log output: char device redirected to /dev/pts/0
connect(unix:/tmp/test.sock): Connection refused
chardev: opening backend "socket" failed
Can that work like the cable is not plugged in? So host B can start and when the socket would exist it would connect to it?
...and when using pty and host device combination one cannot predict pty device under /dev/pts, it would be nice if would be possible to define exact device name.
Tested on Fedora 14.
The QEMU project is currently considering to move 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 older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.
[Expired for QEMU because there has been no activity for 60 days.]
|
