| 41 |   |    * 猜測掛載 NFS 時只會使用正常名稱的網路設備 eth (而非 br0) | 
                      
                        | 42 |   |  * '''drbl_PXE_KVM-VM_deploy''':再 deploy KVM VM 時網路會有一小段時間中斷,dmesg 時會出現 bridge 設備的相關訊息(浸入混亂模式...等等)。 | 
                      
                        | 43 |   |    * 但有趣的是同樣是用 bridge 方式的 Xen VM,卻不會有其狀況,可能狀況是 KVM 額外用的 tap 機制會先 down 原來的網路設備再 bridge 過去,導致短暫時間的網路中斷,或許可以朝 KVM 的 tap 運作這方向研究一下。 | 
                      
                        | 44 |   | {{{ | 
                      
                        | 45 |   | #!sh | 
                      
                        | 46 |   | [ 3094.923757] device tap1 entered promiscuous mode | 
                      
                        | 47 |   | [ 3094.923757] eth0: port 3(tap1) entering learning state | 
                      
                        | 48 |   | [ 3094.923759] eth0: topology change detected, propagating | 
                      
                        | 49 |   | [ 3094.923812] eth0: port 3(tap1) entering forwarding state | 
                      
                        | 50 |   | [ 3111.080606] tap1: no IPv6 routers present | 
                      
                        | 51 |   | [ 3177.729006] eth0: port 3(tap1) entering disabled state | 
                      
                        | 52 |   | [ 3177.741005] device tap1 left promiscuous mode | 
                      
                        | 53 |   | [ 3177.741055] eth0: port 3(tap1) entering disabled state | 
                      
                        | 54 |   | [ 3247.704954] nfs: server 192.168.0.254 not responding, still trying | 
                      
                        | 55 |   | [ 3247.716962] nfs: server 192.168.0.254 not responding, still trying | 
                      
                        | 56 |   | [ 3265.098977] nfs: server 192.168.0.254 OK | 
                      
                        | 57 |   | [ 3265.098977] nfs: server 192.168.0.254 OK | 
                      
                        | 58 |   | [ 3374.350940] device tap1 entered promiscuous mode | 
                      
                        | 59 |   | [ 3374.350999] eth0: port 3(tap1) entering learning state | 
                      
                        | 60 |   | [ 3374.354588] eth0: topology change detected, propagating | 
                      
                        | 61 |   | [ 3374.354641] eth0: port 3(tap1) entering forwarding state | 
                      
                        | 62 |   | [ 3390.236338] tap1: no IPv6 routers present | 
                      
                        | 63 |   | [ 3459.817440] eth0: port 3(tap1) entering disabled state | 
                      
                        | 64 |   | [ 3459.833495] device tap1 left promiscuous mode | 
                      
                        | 65 |   | [ 3459.833544] eth0: port 3(tap1) entering disabled state | 
                      
                        | 66 |   | [ 3516.902404] nfs: server 192.168.0.254 not responding, still trying | 
                      
                        | 67 |   | [ 3531.835094] nfs: server 192.168.0.254 OK | 
                      
                        | 68 |   | [ 3864.515775] device tap1 entered promiscuous mode | 
                      
                        | 69 |   | [ 3864.515775] eth0: port 3(tap1) entering learning state | 
                      
                        | 70 |   | [ 3864.516286] eth0: topology change detected, propagating | 
                      
                        | 71 |   | [ 3864.516340] eth0: port 3(tap1) entering forwarding state | 
                      
                        | 72 |   | [ 3880.818880] tap1: no IPv6 routers present | 
                      
                        | 73 |   | [ 4188.100115] eth0: port 3(tap1) entering disabled state | 
                      
                        | 74 |   | [ 4188.111312] device tap1 left promiscuous mode | 
                      
                        | 75 |   | [ 4188.111361] eth0: port 3(tap1) entering disabled state | 
                      
                        | 76 |   | [ 4259.250465] nfs: server 192.168.0.254 not responding, still trying | 
                      
                        | 77 |   | [ 4259.262465] nfs: server 192.168.0.254 not responding, still trying | 
                      
                        | 78 |   | [ 4278.774055] nfs: server 192.168.0.254 OK | 
                      
                        | 79 |   | [ 4278.774055] nfs: server 192.168.0.254 OK | 
                      
                        | 80 |   | }}} | 
                      
                        | 81 |   |  | 
                      
                      
                        |   | 41 |    * 猜測掛載 NFS 時只會使用正常名稱的網路設備 eth (而非 br0),或許需要再追一下開機時的掛載步驟。 |