Differences

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

--- en:vm_server [2016/12/28 19:59] – [VirtualBox] Domperss
+++ en:vm_server [2021/12/03 18:19] (current) – external edit 127.0.0.1
@@ Line 31: / Line 31: @@
 What? Or perhaps? Does this VM still exist? Is it up-to-date with our current server?
- --- //[[wiki:user:zatalyz|zatalyz]] 2016/11/29 13:23//
+ --- //[[user:zatalyz|zatalyz]] 2016/11/29 13:23//
 </WRAP>
@@ Line 37: / Line 37: @@
 This requires a recent version of Virtualbox, this VM is based on 4.2.12, but what counts are the guest-additions on the vm that are 4.1.18(stable Debian), so it at least needs this version.
 ==== Interface vboxnet0 ====
-This is the Network interface that the VM will attempt to use. To create this interface, this is an theoretical solution that should work:
+This is the Network interface that the VM will attempt to use. To create this interface, this theoretical solution should work:
 <code>
 $ VBoxManage hostonlyif create
@@ Line 53: / Line 53: @@
 In case it creates a vboxnet1 interface at the first statement, it is then necessary to erase a remainder of another vboxnet(or at least to verify what it is). If the deletion is retained, it is enough to do:
 <code> $ VBoxManage hostonlyif remove vboxnet0 </code>
-then
+then:
 <code>$ VBoxManage hostonlyif remove vboxnet1</code>
-puis, de nouveau
+Then, again:
 <code>$ VBoxManage hostonlyif create</code>
 And then:
@@ Line 64: / Line 64: @@
 \\ ''VBoxManage:error:DHCP server already exists'' to command three, then it is the dpu that does a remainder of an already existing DHCP server. To check(in case) if an erasure is possible, do:
 \\ ''$ VBoxManage dhcpserver remove --ifname vboxnet0''
-Then type commands 3 and 4 again.
+Then retype commands "3 and 4" over again.
 To verify that everything works, type: