Differences

This shows you the differences between two versions of the page.

--- fuss:libvirt [2018/02/04 02:13] – [Speed-Up Virtualization using Virtio Drivers] office
+++ fuss:libvirt [2019/03/11 17:34] – [Passing Plan 9 Permissions] office
@@ Line 11: / Line 11: @@
 Next, to start the install, run:
 <code bash>
-virt-install --name live --network bridge:br0 --ram 1024 --boot cdrom --cdrom live.iso --graphics vnc,listen=192.168.1.1,port=5901 --disk /var/lib/libvirt/images/live.img
+virt-install --name live \
+    --network bridge:br0 --ram 1024 \
+    --boot cdrom --cdrom live.iso \
+    --graphics vnc,listen=192.168.1.1,port=5901 \
+    --disk /var/lib/libvirt/images/live.img
 </code>
@@ Line 644: / Line 648: @@
   * ''posixacl'' turns on passing POSIX ACLs (very convenient for using ''getfacl'' and ''setfacl'' to fine tune permissions).
+====== Setting Custom Interface Name for Bridge Networking Mode ======
+libvirt allows using:
+<code>
+<target dev='...'/>
+</code>
+to set the custom name for bridge interfaces such as ''vnet0'', ''vnet1'', etc...
+However, if the name of the interface contains the substring ''vnet'', libvirt will ignore the entry and will not save it, for instance, setting the interface name with:
+<code>
+<target dev='vnet888'/>
+</code>
+will just be ignored by libvirt.
+To resolve this issue, use a more custom-tailored interface name, for instance:
+<code>
+<target dev='mynet0'/>
+</code>
+without containing the ''vnet'' substring.