[SOLVED] VBox Can't select which image file to use
Linux - Virtualization and CloudThis forum is for the discussion of all topics relating to Linux Virtualization and Linux Cloud platforms. Xen, KVM, OpenVZ, VirtualBox, VMware, Linux-VServer and all other Linux Virtualization platforms are welcome. OpenStack, CloudStack, ownCloud, Cloud Foundry, Eucalyptus, Nimbus, OpenNebula and all other Linux Cloud platforms are welcome. Note that questions relating solely to non-Linux OS's should be asked in the General forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I downloaded Arch Linux and I haven't be able to select the Arch .iso image file for some reason.
When I attempt to choose a virtual hard disk file and click on my Downloads directory (which is where the Arch .iso is) the directory opens but appears empty.
Attached; are screenshots of what I have going on.
I always drop in on the ide. (add to that is) Put the iso above the empty one or delete the empty one.
The gui has a goofy way where it lets you add two different things in the same place. One is new controller and other is device/drive.
Generally you don't select an existing .vdi unless you got a pre-made appliance.
Most time I create a (virtual) hard drive that will fill up local space as needed.(grow vesus pre-allocate) For example. A 150G virtual hard drive at start is almost no size on host. As you need space in the client the virtual drive will expand.
You can pre-allocate the space in some cases to help odd behavior. Some OS's won't easily install on a growing drive. Rare.
Not sure what to do here at the root prompt in VBox; as I am not familiar with Arch Linux.
I read a good portion of the Arch Linux Documentation but I'm going to have to find complete
documentation on "How To Install Arch Linux in Virtual Box" to get it installed.
In an odd twist, this iso image is a hybrid image. It could have actually been mounted as a virtual hard drive. It would have been easier to use it in a normal install however.
In an odd twist, this iso image is a hybrid image. It could have actually been mounted as a virtual hard drive. It would have been easier to use it in a normal install however.
What makes it a hybrid image?
I agree, it would have been easier to perform a regular install to a HDD rather than VBox.
No, I meant that using the iso as a hard drive versus using it as a cd image.
I use vm's all the time. They are fantastic, easy, almost impossible to mess up host, fast, fun, easy to move. blaa blaa blaa and so forth and so on.
A hybrid image came out a few years ago. The image offered by many distro's is some cd/dvd image or so it seems. In fact most of them have been converted, edited and some tweaks added to allow one to copy it to a usb flash/hard drive or other media as it is without any changes. It would then allow the user to boot to this media. Common way is to use dd command. You can use rawrite and other image tools usually and dd for windows.
virtual machines also some times have special video so you may need to match virtualbox to client's driver as opposed to matching your hosts driver to client.
virtual machines also some times have special video so you may need to match virtualbox to client's driver as opposed to matching your hosts driver to client.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.