vagrant boot error #9008
Comments
|
Hello @snfnwgi - You are attempting to use NFS on windows, which is not supported.
I recommend using a different method for synced folders. Thanks! |
|
@briancain Thank you. Isn't it possible to run WINDOWS on MAC? The official website said, "WINDOWS" can not refer to "active" or "virtual machine"? This is the way I support it, SMB doesn't seem to be able to do so |
|
@snfnwgi When you are in the Windows-on-Mac, you are using the Windows operating system, and its filesystem, as Brian @briancain mentions. These are not conducive to NFS. The Mac is only providing hardware in this situation -- display, cpu, disk but not Mac filesystem: rather Windows on that partition. I don't name it as NTFS to avoid confusing you as sounding like NFS -- not related. I see you are eager, but imagining is not going to fix this situation. |
|
Thank you. Which way should I synchronize?Thank you very much for your kind reply @narration-sd |
|
Well, it depends on what you want to do with your Vagrant vm. If you want to get reasonable performance 'transparently', the best way I know is to run your vm with the commercial VMware Workstation provider. If you are not commercial, this is available free, but to get the better performance you'll still need to purchase the VMware Vagrant Provider, which costs about USD 100. What I actually do is use the free Virtualbox provider, but with rsync to initiallly copy only the software I'm developing up to the Vagrant box. This is extremely rapid. You can look up how to use rsync online. As I edit and change the code, I have my developing environment automatically SFTP the changes, which occurs 'instantly'. The original is always on the workstation, so I don't need to copy back. Rsync is in trouble with 2.0.0, but should shortly be working again in a fresh release. It has worked for years with earlier versions, so a current 1.9.6 should be fine if you want to practice ahead on rsync, given my way of working would be appropriate for you. Otherwise, I would just get the VMware software packagess, and expect those to work usefully well. Good fortune, Yang ZhiJian, p.s. if a database is involved, you'd back that up or reload it using a remote database tool such as Navicat. No matter how you run Vagrant, you wouldn't want to copy it up and down directly, as this could make corruption in the data, as is well understood. |
|
@narration-sd I'm so moved. Thank you for your patience.I've just tried two synchronization methods: SMB and RSYNC. 1.、smbBringing machine 'default' up with 'virtualbox' provider... 2.rsyncBringing machine 'default' up with 'virtualbox' provider... ==> default: Machine booted and ready! |
|
Well, again, you will have to be patient.
|
|
Thank you. Isn't SMB also not in sync with WINDOWS?I have just tried a new version of vagrant. I have found the answers online, but I haven't found them. boot errorBringing machine 'default' up with 'virtualbox' provider... Host path: /vagrant/win7/modernie-winrm/ExtraFolder/ |
|
To use rsync, you have to install it. To use the kind of development software Vagrant is, you're expected to look up how to do things like this. The information is there; and against further questions, sometimes you have to look for the most recent instructions or experiences which modify from these, to be successful. |
|
Hello, I have installed rsync. rsync -v rsync comes with ABSOLUTELY NO WARRANTY. This is free software, and you |
|
@snfnwgi I have to go. It isn't enough often to just install things -- this is not phone apps land. You have to work out how to make their connections. I checked, and the version of rsync that works for me is MinGW msys. I would uninstall and get this if you aren't using it, as versions differ. I think this version is recommended in the Vagrant documentation for rsync. Then you need to assure that your path contains the directory under MinGW where rsync is. The Windows command 'where rsync' should show if you have this set up correctly, as the MinGW installer should do. Then Vagrant booting will find rsync. |
|
@narration-sd I'm using MAC OS, haha, thank you, I'm looking for other answers, cheers |
|
Well, my young friend, you opened this long conversation saying you were using Windows on Mac hardware. I think you will now work this out yourself. |
|
Haha, what do you mean? I am a little dizzy. My question is clear at the beginning. vagrant 1.8.1 Host operating system mac Guest operating system windows7 Vagrantfile |
|
Well, then, the same needs hold -- in this case rsync must be findable on the PATH of the guest machine. And also on the host, the Mac. Both ends must have rsync installed and executable from a shell -- in understanding of how it works. The advice will change then for what arrangements are possible and work, besides rsync. I suggest again that you use google and learn what the most recent advice is. Which seems it would include not using High Sierra yet. It and 2.0 Vagrant appear to be released before ready, and for each other.. |
|
Thank you for your valuable advice. My last question, if it's MACOS running WINDOWS, can you use NFS? |
|
Well, here we are back to @briancain 's first reply, I believe.
|
|
You know, it must occur to ask -- if you want Windows on a Mac, why not run Parallels, or whatever the latest good flavor of co-working is? No Vagrant then. Maybe you want Windows versions which don't work with those however? The other thought is what I mentioned above about running the VMware provider. There is a question whether the online doc is out of date as far as which VMware Fusion versions can run the Homestead/Vagrant boxes, which you would have to work out. This I suspect is the limit of what I usefully am aware of for your case. |
|
It's just synchronous, the default vagrant synchronization mode, the access is a little bit slow, so I want to change it a different way.Because of my work, my environment must run under WINDOWS, so WINDOWS7 is installed.I just try once, I also installed the RSYNC inside the virtual machine, but the same error when I sync or a newspaper, good helpless, is there any better way, I'm sorry my English is not good, I said is through the translation software and you said.. |
|
Ok, I understand about languages, have lived in Asia (Korea) and Europe many years. Good to take advantage of the translation tools. That error you show seems simple: that the rsync executable can't be found; I am not sure on which end, but it seems the Windows end. In either case, setting and verifying the PATHs on both host and guest rsyncs should clear this problem. Yes, the virtualbox implementation is slow. |
|
Ha ha ha, thank you, you are full of awe. |
|
So, at the Mac command line terminal, you can verify Using then If not, you can look into setting Windows PATH -- it's in the System interface, Advanced tab I think, but look this up with pictures via google. |
|
I need to go for a walk now, and then will sleep. I will check once more in between, if I think you have enough informtion to work with now -- cheers... |
|
It's hard for you to go to bed after the walk. Cheers |
|
yes, but I have to do it :) |
|
Ha ha ha, have a good rest, thank you big brother |
|
Most welcome, and for that memory of speaking... |
|
Ha ha ha, I am also glad to have your guidance today |
|
I installed rsync on the virtual machine windows in this way
I feel the problem will soon be resolved, but do not know where the problem
|
|
@narration-sd @briancain God for help |
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Please note that the Vagrant issue tracker is reserved for bug reports and
enhancements. For general usage questions, please use the Vagrant mailing list:
https://groups.google.com/forum/#!forum/vagrant-up. Thank you!
Vagrant version
vagrant 1.8.1
Host operating system
mac
Guest operating system
windows7
Vagrantfile
Debug output
boot error! Sorry, my English is not good！
==> default: Forwarding ports...
default: 5985 (guest) => 55985 (host) (adapter 1)
default: 5986 (guest) => 55986 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: WinRM address: 127.0.0.1:55985
default: WinRM username: IEUser
default: WinRM execution_time_limit: PT2H
default: WinRM transport: plaintext
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Configuring and enabling network interfaces...
==> default: Exporting NFS shared folders...
==> default: Preparing to edit /etc/exports. Administrator privileges will be required...
==> default: Mounting NFS shared folders...
Vagrant attempted to execute the capability 'mount_nfs_folder'
on the detect guest OS 'windows', but the guest doesn't
support that capability. This capability is required for your
configuration of Vagrant. Please either reconfigure Vagrant to
avoid this capability or fix the issue by creating the capability.
Expected behavior
What should have happened?
The text was updated successfully, but these errors were encountered: