I'm using virtualbox + vagrant to setup my dev environment. I've created a symlink at /vagrant/.ivy2 to resource (.jar) files stored on the guest (vm) at ~/.ivy2
While the symlink works and I'm able to traverse it in the vm, host applications like eclipse do NOT register the contents of the symlink. Is there a way for me to expose the resources with the guest os home directory via symlink or otherwise to the host?
Are you running the latest version of Vagrant? I don't think you should be having any issues with this...
Regardless if you want to try a different method of exposing the guest to the host there are several options that you could use, depending on your preference:
sshfs - http://fuse.sourceforge.net/sshfs.html
Samba - https://help.ubuntu.com/community/Samba
AFP - http://en.wikipedia.org/wiki/Apple_Filing_Protocol
Related
I am running Win 10 in a virtual machine under Fedora 30. I now need to do a clean install of Fedora 32. It is critical that the virtual machine survives this install.
The default location of virtual machines is under /var/lib/libvirt, which will will be run over by installation. Because of this, I now created a new pool onto a logical volume that will survive fresh OS install and used virt-clone to clone the virtual machine onto this logical volume. The cloned virtual machine is running just fine.
I can see that in the logical volume where the clone is the only file is the .qcow2-file containing the cloned virtual machine. I have two questions:
In order for the virtual machine to survive clean OS installation, is it sufficient that the .qcow2-file carries over? Or do I need to copy other information from some other directory?
After OS install, how do I tell virt-manager about the pool that already exists and the virtual machine that is located there?
You also need to at least copy the guest XML configuration files, which are stored under sub-dirs of /etc/libvirt.
If you've stored other things like snapshots, further dirs under /var/lib/libvirt may need to be preserved.
If you save the XML files somewhere, then in the new install "virsh define $XMLFILE" will load the guest into libvirt, such that virt-manager will see it again. You can use virt-manager's storage management UI to tell it about the pool.
I have a real host and an vm. they are both solaris system
sjcux-c7build01# uname -a
SunOS sjcux-c7build01 5.8 Generic_Virtual sun4v sparc sun4v
The real host has been used for years.The vm is new created.For maintenance，we want to use vm instead of real host in future.I need to install all the packages and let the vm can do gnu make like the old host.
How to list all the packages the real host has installed?
pkginfo just shows what's bundled with Solaris.
I noticed that directory /usr/local/lib in vm is empty,And In real host ,it has many .so file in it.
There must be many other difference. How to find out them? How to list the packages I need to install?
For example.on the vm ,I can't use git.
ldd git
libiconv.so.2 => /tools/sw/opt/SunOS/5.8/git/git-2.23.0/lib/libz.so/lib/libiconv.so.2 - Not a directory
libintl.so.8 => /tools/sw/opt/SunOS/5.8/git/git-2.23.0/lib/libz.so/lib/libintl.so.8 - Not a directory
So libiconv need to be installed.
I want to make the vm same as the real host, what need I to do? Who can give me some guide~
It is unrealistic to find one by one according to the .so files.
One possible way is to create flash archive of your old machine and install from this archive:
create repository where to store the archive
create flash archive of the system
check the archive
export via NFS the flash archive store
on new machine boot from CD, choose installation media select NFS
For more detailed instruction you can check this article in my blog
After creation of new machine you should take care of changing IP address or unconfigure and configure it from scratch (in sense of network and authentication services) it because two machines will have the same IP.
I want to install and set up TYPO3 on my local machine. What's the best practice and fastest way to do so?
For running TYPO3 on a local machine you need a web server running on your machine.
This can be done in different ways:
Native Web Server, PHP and database on a Linux based machine
Virtual Machine (VirtualBox, VMWare, Parallels, etc.)
Vagrant
Docker
Currently the fastest way to a "non power user" in my opinion is ddev.
ddev is a user-friendly possibility to run a perfect environment for TYPO3 on a docker base. It runs on Linux, Mac and Windows (minimum version 10, hyper-v recommended) and it brings all technologies you need for best experience.
Install Docker and ddev, see https://ddev.readthedocs.io/en/stable/
Create a folder for your installation, e.g. ~/Websites/my-website/ or C:\Websites\my-website\ and go into it.
Run ddev config and set these three options in the dialog:
Project name (default is your folder name): Whatever you like
Docroot location: public and say yes for creating
Project type: typo3
Run ddev start to start the Docker containers and add your root password to set the hosts entry (for accessing it via local domain)
Run ddev composer create typo3/cms-base-distribution ^9 and say yes for overwriting
Run ddev config again and just hit enter for every dialog to create a file which provides the DB credentials for your TYPO3 installation
Run ddev exec vendor/bin/typo3cms install:setup --no-interaction --admin-user-name=admin --admin-password=password --site-setup-type=site
That's all, you have a running TYPO3 instance on your local machine.
You can access it by using <project-name>.ddev.site in your browser, in our example it should be http://my-website.ddev.site. To get into the TYPO3 backend you only need to put the credentials admin:password on http://my-website.ddev.site/typo3.
For troubleshooting go to:
https://ddev.readthedocs.io/en/stable/users/troubleshooting/
https://docs.typo3.org/typo3cms/InstallationGuide/Troubleshooting/Index.html
https://docs.typo3.org/typo3cms/ContributionWorkflowGuide/Appendix/SettingUpTypo3Ddev.html
After a great deal work tinkering I have a mostly working copy of an ember-cli project running on a guest Ubuntu VirtualBox. One of my goals was to run the code inside a Shared Folder and I have it mostly working.
There are a number of hacks ahem, workarounds to get this far.
1. Enable symlinks on Virtualbox Shared Folders
2. Forward LiveReload port from Guest to Host
3. Replace the PROJECT/tmp folder with a symlink to the local Guest filesystem
What works...
When I edit a file in my ember project from the guest, the server sees the change and auto reloads.
What does not work....
When I edit a file in my ember project from the host, the server does NOT see the change and does nothing.
Why oh why does the ember-cli stack not detect changes made from the Host. I can't even point to the culprit. Is it Broccoli, livereload, node or my mother in law that is giving me trouble?
Is it possible to set the path where the berkshelf plugin puts the cookbooks it installs? (As in the .berkshelf folder)
I am running Windows 7.
I am currently trying to install a mysql server using an opscode cookbook to a vm and here at work they have the %HOMEDRIVE% system variable set to a network drive. So when .berkshelf starts at the beginning of the Vagrantfile, it pushes the cookbooks to the network drive and it causes it to be slow and well, its not where it should be. Is there a fix to this?
VirtualBox did this as well, but I fixed it by altering the settings. I tried looking for some sort of equivalent settings for berkshelf, but the closest I got was for the standard berkshelf (thats not a vagrant plugin), it appears you can set this environment variable:
ENV['BERKSHELF_PATH']
Found here:
http://www.rubydoc.info/github/RiotGames/berkshelf/Berkshelf#berkshelf_path-class_method
I need to be able to have the cookbooks it reads from the berksfile store to my laptops local drive instead, as in my scenario I cannot have the mobility of the VM limited to the building because of files that are stored on the network.
Any incite would be much appreciated.
Perhaps its better to use the actual berkshelf over the vagrant plugin?
Thanks.
If you want to have the portability - a full chef-repo ready for chef-solo runs, better off using standalone berkshelf instead of the vagrant-berkshelf plugin - which is NOT that flexibly.
For complex cookbooks, I prefer to use standalone berkshelf as it allows me to do berks install --path chef/cookbooks to copy all cookbooks required from ~/.berkshelf/cookbooks, then I can just tar the whole thing and transfer to other machines for the same chef-solo run. some people use capistrano automate the tar and scp/rsync over the network. I just use rysnc/scp;-)
HTH