I am newbie in Big Data space. I downloaded cloudera-quickstart-vm-5.7.0-0-virtualbox from Cloudera and got Oracle virtual box where i have to setup remote space. But i am not able to run .vmdk file using VM. I am able to get it using .ovf file. I am not sure what is the issue here. Do i need to change some configuration for running this on machine (network or something else).
Adding error print in my post.
enter image description here
Other users have reported similar problems using the .vmdk file. The workaround, which you have already done, is to import the .ovf file instead. The user experience should be the same, either way.
Related
I want to build an image in Azure on Windows 2019 with a large file. The file contains the artifacts I need to create my image. All was going well getting the VM going until I tried to copy a 200MB file to the host. That was slated to take 11 hours. That's when I found out about WinRM and its file copy limitations.
I then found out about the http_directory parameter to copy a file to the host over http, but that is not available with the azure-arm builder.
I then saw that I can use SSH. The issue is I cannot start with the ssh provisioner and switch to the WinRM provisioner to run my ps1 configuration script. I read I can start with ssh, take an image and then start it up with WinRM. Not ideal.
I came across this software: "https://github.com/winfsp/sshfs-win" - but I am unaware of a way for a provisioned host to directly access the packer host it was provisioned by.
I came across winrmcp but that seems old and not likely to work if I could ever figure out how to get it going.
I am leaning towards blob storage, but that seems like a cop-out.
What is the best way to start a Windows 2019 Server, copy a 200MB file to it and run a ps1 script?
I've created custom Windows_10_PRO_1909_x64 image with hashicorp packer (with QEMU).
To build it I used unattend.xml file. Steps to prepare were:
Absolutely unattended installation of Windows
Installation of big amount of software
Converting VM (it was build with QEMU) to raw .img file
Now I want to deploy this image to new PC. I'm using bootable USB stick with embedded Linux (also custom) which can grab this .img file from local storage and write to /dev/sda
Everything works fine in this process.
Main problem is - after writing .img to /dev/sda I'm changing ComputerName in unatted.xml file (on mounted /dev/sda), but after first time boot, Windows ignores this file, and PC name is the same as it was before changing. When I checked unattend file, it has correct PC name, which I changed while was on bootable linux, before Windows first run.
Maybe somebody have an idea - how I can change PC name, each time I deploy new PC? But it should be without user interaction. It could be any file modification on bootable linux, or maybe there is a way to do it automatically on first Windows boot?
Found solution.
Need to run sysprep afer Windows install with sysprep-unattend.xml file to clean system.
After it Windows will catch this file on first boot. So it's possible to change PC name in this file before boot.
I am writing a program for Microsoft refurbishers, and I would like to include a feature for creating a system recovery partition once all the necessary drivers are installed. The problem that I am running into is that it won't let me create the .wim file while the disk is mounted. When I try it gives me the error "The process cannot access the file because it is being used by another process". I have seen guides that say to boot to a windows installer, but that seems inefficient. Is it possible to create a backup of a running machine without booting to another drive? Any help is appreciated.
This can be done by creating a shadow copy of the drive. A free project using this approach was presented by the german c't magazine as a command script.
The project can be found and the scripts downloaded here:
c't WIMage.
Unfortunately this page is in german, but the script files may show you how it works.
I have a Vagrant set up with 3 virtual machines. Each machine has its own shell script for provisioning.
Now I would like to share the exact same status of my set up with somebody else. Since the provisioning procedure takes really (!!) long for each machine, I hope there is another solution.
Ideally I would be able to save each machine as it is in one file, which the other person then could import into Virtualbox. Is there a way to do that?
If I understand you correctly you would like to make a Vagrant base box from provisioned by Vagrant VMs. This is not recommended way to go. How you can approach this is:
Create new VM manually with required OS in the VBox.
Adjust it so Vagrant can connect to it as described here and here.
Provision it using your shell scripts.
Install all the things you would find useful to have on this VM.
Use Vagrant to package it as a base box as described here.
After packaging it with Vagrant you will get a Vagrant base box file with .box extension. You can then pass this to your team mates (usb, network share, ftp etc.) and they can add it to their Vagrant installation and use it. Whenever they will do Vagrant up they will get fully provisioned VM in VBox with all the stuff you have packaged to it. Vagrant also gives you versioning capabilities. If properly configured whenever you will create new version of base box everybody who is using it will be notified and would be able to download and use new version of your box.
Hope I understood your problem correctly and this will help to solve it.
I mounted a vagrant machine several time ago.I have modified some configurations to the VM since the installation and now my co-workers need to use exactly the same VM.
How can I do it ? I would like keep the database i used for my co-workers too if it's possible.
Look into VagrantCloud: https://vagrantcloud.com/
I'm using that service to host a customized box for my team. Started from a vanilla box, customized it to match our environment, then used the "vagrant package" command to create a new *.box file. You just need to host that file somewhere online, register it with the VagrantCloud service, and you can manage box releases and deployments for your co-workers. It even notifies them if you update the box. Pretty nifty.
As far as the DB, if it is in the VM it will get packaged up too. Might wat to look into providing updated DB files for later since they will get out of date fast, I would imagine.