blob: dcede9df819107a7842150039ce2ce73edf21340 (
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
|
operating system: 0.980
network: 0.966
graphic: 0.907
device: 0.818
virtual: 0.784
performance: 0.636
socket: 0.608
register: 0.601
boot: 0.567
files: 0.565
ppc: 0.562
user-level: 0.542
mistranslation: 0.533
PID: 0.504
vnc: 0.498
hypervisor: 0.492
peripherals: 0.470
architecture: 0.459
semantic: 0.454
alpha: 0.419
permissions: 0.403
debug: 0.400
arm: 0.379
risc-v: 0.345
assembly: 0.275
VMM: 0.258
TCG: 0.217
i386: 0.187
x86: 0.164
KVM: 0.153
kernel: 0.063
[Qemu-devel] [BUG] network : windows os lost ip address of the network card in some cases
we found this problem for a long time ãFor example, if we has three network
card in virtual xml file ï¼such as "network connection 1" / "network connection
2"/"network connection 3" ã
Echo network card has own ip address ï¼such as 192.168.1.1 / 2.1 /3.1 , when
delete the first card ï¼reboot the windows virtual os, then this problem
happened !
we found that the sencond network card will replace the first one , then the
ip address of "network connection 2 " become 192.168.1.1 ã
Our third party users began to complain about this bug ãAll the business of the
second ip lost !!!
I mean both of windows and linux has this bug , we solve this bug in linux
throught bonding netcrad pci and mac address ã
There is no good solution on windows os . thera are ? we implemented a plan to
resumption of IP by QGA. Is there a better way ?
|