Well i think its cause i need a default route to the router
0.0.0.0 10.0.2.20.0.0.0 UG0 00 eth0
10.0.2.00.0.0.0 255.255.255.0 U 0 00 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 00 eth1
when
It is not a matter of a VM. The magnetic disks are just in the host. They
are not used by any VM nor VMware nor Vagrant. Right now, my MP3 collection
is on them. The whole Vagrant and VM stuff ist on SSD.
But wenn I run "vagrant ssh" (e.g.) in the Powershell, then it first spins
up the HDDs.
there is a nfs server on 192.168.121.1 ?
can you mount on the guest manually 192.168.121.1:/root/hlinux-
tools/netinst-iso
?
alvaro
On Tue, May 5, 2020 at 4:24 PM Ibrahim Vanak
wrote:
> The issue is, while running “vagrant up” I am trying to do NFS mount from
> host to Vagrant VM. It’s
if you share the script we can have a look
Xwindows
https://en.wikipedia.org/wiki/X_Window_System
On Tue, May 5, 2020 at 11:29 AM kathir wrote:
> yes that's correct
>
> I already did that individual commands are running in ssh, but not able
> run through vagrant external script provisioning
The issue is likely that NFS isn't installed inside the VM. You should read
the documentation at vagrantup.com regarding the options for NFS or Rsync
or "native" shared folders for Virtualbox or VMware (which require having
some additional packages installed in the VM as well).
On Tuesday, May
