Ubuntu KVM 橋接 DHCP 不起作用

Ubuntu KVM 橋接 DHCP 不起作用

我已經查看了這裡的問題以及我可以在谷歌上找到的每個教程,但似乎沒有什麼可以解決我的問題。我有一台 Ubuntu 16.04 伺服器,上面有很多軟體(Unifi、Unifi Video、UNMS、Bluecherry、Apache2)。我需要一個僅支援 14.04 (mFi) 的軟體。所以我的軟體只能在 16.04 上更新,而軟體則不能在 16.04 上運行,但出於電費原因需要安裝在 1 台 PC 上。我運行的是 16.04 KVM,可以很好地安裝 VM。我還創建了一個 br0,用於從路由器接收 DHCP。我還需要 14.04 虛擬機器才能從路由器取得 DHCP。在主機上 ifconfig 看起來像這樣:

br0       Link encap:Ethernet  HWaddr 00:1c:c0:38:c5:42
      inet addr:10.11.11.254  Bcast:10.11.11.255  Mask:255.255.255.0
      inet6 addr: fe80::21c:c0ff:fe38:c542/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:77330 errors:0 dropped:0 overruns:0 frame:0
      TX packets:48141 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:97552697 (97.5 MB)  TX bytes:31018242 (31.0 MB)

br-441049093d8f Link encap:Ethernet  HWaddr 02:42:29:9b:ba:1c
      inet addr:172.18.0.1  Bcast:172.18.255.255  Mask:255.255.0.0
      inet6 addr: fe80::42:29ff:fe9b:ba1c/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:3 errors:0 dropped:0 overruns:0 frame:0
      TX packets:180 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:84 (84.0 B)  TX bytes:8560 (8.5 KB)

br-f26207b68430 Link encap:Ethernet  HWaddr 02:42:62:fb:8a:5e
      inet addr:172.19.0.1  Bcast:172.19.255.255  Mask:255.255.0.0
      inet6 addr: fe80::42:62ff:fefb:8a5e/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:55749 errors:0 dropped:0 overruns:0 frame:0
      TX packets:47179 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:7779523 (7.7 MB)  TX bytes:26110547 (26.1 MB)

docker0   Link encap:Ethernet  HWaddr 02:42:1e:8a:a7:a3
      inet addr:172.17.0.1  Bcast:172.17.255.255  Mask:255.255.0.0
      UP BROADCAST MULTICAST  MTU:1500  Metric:1
      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
      TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

eth0      Link encap:Ethernet  HWaddr 00:1c:c0:38:c5:42
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:14320804 errors:0 dropped:88 overruns:0 frame:0
      TX packets:9161214 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:18267999423 (18.2 GB)  TX bytes:4224704433 (4.2 GB)
      Interrupt:20 Memory:e8200000-e8220000

lo        Link encap:Local Loopback
      inet addr:127.0.0.1  Mask:255.0.0.0
      inet6 addr: ::1/128 Scope:Host
      UP LOOPBACK RUNNING  MTU:65536  Metric:1
      RX packets:455114 errors:0 dropped:0 overruns:0 frame:0
      TX packets:455114 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1
      RX bytes:323006260 (323.0 MB)  TX bytes:323006260 (323.0 MB)

veth6087736 Link encap:Ethernet  HWaddr 92:6b:9e:30:3f:3f
      inet6 addr: fe80::906b:9eff:fe30:3f3f/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:2323 errors:0 dropped:0 overruns:0 frame:0
      TX packets:4719 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:631966 (631.9 KB)  TX bytes:451342 (451.3 KB)

veth0be9933 Link encap:Ethernet  HWaddr f6:4b:44:26:95:31
      inet6 addr: fe80::f44b:44ff:fe26:9531/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:22962 errors:0 dropped:0 overruns:0 frame:0
      TX packets:23170 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:1511612 (1.5 MB)  TX bytes:6634025 (6.6 MB)

veth4721a38 Link encap:Ethernet  HWaddr a6:30:ad:6b:99:c9
      inet6 addr: fe80::a430:adff:fe6b:99c9/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:51401 errors:0 dropped:0 overruns:0 frame:0
      TX packets:48796 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:23393519 (23.3 MB)  TX bytes:22044039 (22.0 MB)

veth4bfc810 Link encap:Ethernet  HWaddr 96:a8:06:b1:01:21
      inet6 addr: fe80::94a8:6ff:feb1:121/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:35421 errors:0 dropped:0 overruns:0 frame:0
      TX packets:38362 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:38357384 (38.3 MB)  TX bytes:27451189 (27.4 MB)

veth670940c Link encap:Ethernet  HWaddr ba:ee:fa:d6:a2:3f
      inet6 addr: fe80::b8ee:faff:fed6:a23f/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:53627 errors:0 dropped:0 overruns:0 frame:0
      TX packets:44489 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:38465696 (38.4 MB)  TX bytes:49446336 (49.4 MB)

vethd484c2b Link encap:Ethernet  HWaddr 36:53:04:68:c2:d1
      inet6 addr: fe80::3453:4ff:fe68:c2d1/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:26617 errors:0 dropped:0 overruns:0 frame:0
      TX packets:20841 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:4291112 (4.2 MB)  TX bytes:18090223 (18.0 MB)

vethda042e9 Link encap:Ethernet  HWaddr 36:6b:69:35:34:34
      inet6 addr: fe80::346b:69ff:fe35:3434/64 Scope:Link
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:6563 errors:0 dropped:0 overruns:0 frame:0
      TX packets:11108 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:0
      RX bytes:10448286 (10.4 MB)  TX bytes:10590365 (10.5 MB)

vnet0     Link encap:Ethernet  HWaddr fe:54:00:88:62:21
      UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
      RX packets:71 errors:0 dropped:0 overruns:0 frame:0
      TX packets:586 errors:0 dropped:0 overruns:0 carrier:0
      collisions:0 txqueuelen:1000
      RX bytes:11162 (11.1 KB)  TX bytes:53777 (53.7 KB)

其中一個程式還安裝了一個 docker 軟體,但我很確定其他東西是來自無盡的嘗試。

我的主機等/網路/介面目前看起來像這樣(再次在我無盡的嘗試中):

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet manual

# bridge interface for kvm
auto br0
iface br0 inet dhcp
    bridge_ports eth0 vnet1 vnet0 vethda042e9 vethd484c2b veth670940c veth4bfc810 veth4721a38 veth0be9933 veth6087736
    bridge_stp off
    bridge_fd 0
    bridge_maxwait 0

這真的有效嗎? VMware就是這樣做的。 Virtualbox 就是這麼做的。為什麼無法在乙太網路和虛擬機器之間建立 L2 橋接?很確定我甚至可以使用 Windows Hypervisor 來做到這一點。

防火牆已停用。不要從虛擬機器取得任何內容,因為一段時間後,如果在安裝所有內容之前 DHCP 失敗,那完全是浪費時間。嘗試透過終端安裝。設定另一個桌面 Ubuntu 以安裝虛擬網路管理員並從中安裝約 9 次

是的,我正在使用 libvirt。最初加入 br0 的唯一介面是 eth0,但仍然沒有 DHCP。我開始添加其他的希望可能有用但沒有。

這是 XML:

<domain type='kvm' id='11'>
  <name>mFi</name>
  <uuid>096832a0-76bf-488c-88dd-f0bcae02046c</uuid>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <vcpu placement='static'>1</vcpu>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-i440fx-xenial'>hvm</type>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='custom' match='exact'>
    <model fallback='allow'>core2duo</model>
  </cpu>
  <clock offset='utc'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <pm>
    <suspend-to-mem enabled='no'/>
    <suspend-to-disk enabled='no'/>
  </pm>
  <devices>
    <emulator>/usr/bin/kvm-spice</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='qcow2'/>
      <source file='/var/lib/libvirt/images/mFi.img'/>
      <backingStore/>
      <target dev='vda' bus='virtio'/>
      <boot order='1'/>
      <alias name='virtio-disk0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' 
function='0x0'/>
    </disk>
    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/var/lib/libvirt/boot/ubuntu-14.04.5-server-amd64.iso'/>
      <backingStore/>
      <target dev='hda' bus='ide'/>
      <readonly/>
      <boot order='2'/>
      <alias name='ide0-0-0'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' 
function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <alias name='usb'/>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' 
function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <alias name='usb'/>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' 
function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <alias name='usb'/>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' 
function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'>
      <alias name='pci.0'/>
    </controller>
    <controller type='ide' index='0'>
      <alias name='ide'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' 
function='0x1'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' 
function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:88:62:21'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='rtl8139'/>
      <boot order='3'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 
function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/0'/>
      <target port='0'/>
      <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/0'>
      <source path='/dev/pts/0'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <channel type='spicevmc'>
      <target type='virtio' name='com.redhat.spice.0' state='disconnected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='5900' autoport='yes' listen='127.0.0.1'>
      <listen type='address' address='127.0.0.1'/>
    </graphics>
    <sound model='ich6'>
      <alias name='sound0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' 
function='0x0'/>
    </sound>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' 
function='0x0'/>
    </video>
    <redirdev bus='usb' type='spicevmc'>
      <alias name='redir0'/>
    </redirdev>
    <redirdev bus='usb' type='spicevmc'>
      <alias name='redir1'/>
    </redirdev>
    <memballoon model='virtio'>
      <alias name='balloon0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' 
function='0x0'/>
    </memballoon>
  </devices>
  <seclabel type='dynamic' model='apparmor' relabel='yes'>
    <label>libvirt-096832a0-76bf-488c-88dd-f0bcae02046c</label>
    <imagelabel>libvirt-096832a0-76bf-488c-88dd-f0bcae02046c</imagelabel>
  </seclabel>
</domain>

當我嘗試編輯配置時,它顯示:

  <interface type='bridge'>
      <mac address='52:54:00:88:62:21'/>
      <source bridge='br0'/>
      <model type='rtl8139'/>
      <boot order='3'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 
function='0x0'/>
    </interface>

甚至認為轉儲顯示了 alis 和 target。他們不是來拿走的。不允許我在評論中這樣做。

樓主不是這個:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
iface eth0 inet manual

# bridge interface for kvm
auto br0
iface br0 inet dhcp
    bridge_ports eth0
    bridge_stp off
    bridge_fd 0
    bridge_maxwait 0

不知道您所說的訪客網路配置是什麼意思,這不是我們剛剛檢查過的嗎?

答案1

讓我們看看您的虛擬機器的網路介面配置。

    <interface type='bridge'>
      <mac address='52:54:00:88:62:21'/>
      <source bridge='br0'/>
      <target dev='vnet0'/>
      <model type='rtl8139'/>
      <boot order='3'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' 
function='0x0'/>
    </interface>

首先,<target>在橋接到現有橋樑時是可選的;通常你根本不應該指定它。我會刪除這一行。

其次,您定義了 an <alias>,但該name屬性是錯誤的。所有別名必須以文字字串開頭ua-。此選項在 libvirt 3.9.0 之前不存在。它也是可選的,因此您可以將其刪除。

使用 編輯虛擬機器virsh edit vmname。如果編輯時 VM 正在執行,則必須停止並再次啟動 VM 才能使設定生效。

除此之外,如果虛擬機無法連接到網絡,則問題很可能出在來賓配置或本地實體網路(例如上游交換器)。

相關內容