summary refs log tree commit diff stats
path: root/classification_output/02/semantic/05479587
blob: 8df3bc6ef524fc61e689c360135edc0d200103f4 (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
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
semantic: 0.866
mistranslation: 0.759
instruction: 0.597
boot: 0.474
other: 0.200

[Qemu-devel]  [BUG] network qga : windows os lost ip address of the network card  in some cases

We think this problem coulde be solevd in qga modules。can anybody give some 
advice ?


[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 ?








原始邮件



发件人:尹作为10144574
收件人: address@hidden
日 期 :2017年04月14日 16:46
主 题 :[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 ?