Differences

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

--- fuss:libvirt [2018/07/27 13:27] – [Create a New Virtual Machine] office
+++ fuss:libvirt [2019/06/10 20:27] – [Passing Plan 9 Permissions] office
@@ Line 618: / Line 618: @@
 ====== Passing Plan 9 Permissions ======
-Given a passed-through folder defined in the domain configuration file:
+===== Access Mode Mapped =====
+The following configuration changes for the domain have to be made:
+<code xml>
+    <filesystem type='mount' accessmode='mapped'>
+      <source dir='/mnt/cdrom'/>
+      <target dir='cd'/>
+    </filesystem>
+</code>
+===== Access Mode Passthrough =====
+For passthrough access mode, the following configuration change has to be made for the domain:
 <code xml>
     <filesystem type='mount' accessmode='passthrough'>
@@ Line 626: / Line 639: @@
 </code>
-virtual machines running under ''qemu'' / ''kvm'' have to be started as root. To accomplish that, edit ''/etc/default/libvirt/qemu.conf'' and set:
+Virtual machines running under ''qemu'' / ''kvm'' have to be started as root. To accomplish that, edit ''/etc/default/libvirt/qemu.conf'' and set:
 <code>
 user = "root"
@@ Line 637: / Line 650: @@
 </code>
 has to be added to ''/etc/default/libvirt/qemu.conf''.
+===== Mounting the Share =====
 Once the virtual machine boots, the share can then be automatically mounted by adding the following line:
@@ Line 648: / Line 663: @@
   * ''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.