search

shihjay2 / nosh-in-a-box

NOSH in a Box is a self-contained virtual machine that deploys NOSH ChartingSystem, an EHR coded by a physician for physicians
26 stars 13 forks source link

Running in Hyper-V? #6

Open JXPrime opened 6 years ago

JXPrime commented 6 years ago

It looks like the base box you're using only supports VirtualBox. Is it supported to change that to one that support hyper-v? "generic/ubuntu1604" as an example.

shihjay2 commented 6 years ago

You can certainly try either generic/ubuntu1604 or bento/ubuntu-16.04 and see if either of those 2 boxes will work; unfortunately, I only use a Linux machine for development and I have no way to test and confirm if Hyper-V works but I think that it should. If so, please report back to me and I can update the config.vm.box setting to one of these 2 boxes instead.

JXPrime commented 6 years ago

I tried with bento/ubuntu-16.04, and got to this after it asked for SMB share information: image

JXPrime commented 6 years ago

I'm wondering if I screwed up putting my credentials in, trying again.

shihjay2 commented 6 years ago

Did you do this command before vagrant up vagrant plugin install vagrant-vbguest

Based on the error message, I'm assuming you're using VirtualBox instead of Hyper-V right now. If you intend to use Hyper-V, change the vagrant up command to vagrant up --provider=hyperv

JXPrime commented 6 years ago

I did not, let me give that a shot. Thanks for the response!

JXPrime commented 6 years ago

I think that plugin is for the Virtual Box guest stuff (vbguest). When I look at the hyper-v manager, all of the integration services are enabled:

image

shihjay2 commented 6 years ago

See my previous comment above: you will need to designate the provider if both VirtualBox and Hyper-V is installed. Vagrant goes through a list of providers and it's possible that VirtualBox is higher in the list than Hyper-V. Either uninstall Virtualbox or set the provider before doing vagrant up.

JXPrime commented 6 years ago

Virtual box is currently uninstalled. I changed the sync folder line in the Vagrantfile to this and it seems to have worked (just commenting out the mount_options):

config.vm.synced_folder "", "/vagrant"

, :mount_options => ["dmode=777","fmode=666"]

shihjay2 commented 6 years ago

Thanks, I'll do some testing later to make sure commenting out the mount options does not affect VirtualBox boxes for NOSH. If your testing continues to work without problems, please let me know and I will consider updating to Vagrantfile to allow users to choose between VirtualBox and Hyper-V and potentially others. Thanks @JXPrime!

JXPrime commented 6 years ago

I appear to have success!

image

I'll let you know if I run into any other problems. Thanks!