Tag Info

Hot answers tagged

2

The basic math stems from that Visual Studio on the host requiring 1GB includes 0.5GB for Windows and 0.5GB for Visual Studio. In a VM you have 0.5GB for host Windows 0.5GB for virtual Windows and 0.5GB for Visual Studio. Those are minimums. I personally would not recommend running either Windows or Visual Studio without at least double those numbers in ...


2

This message has nothing to do with your VM's HDD, and is showing because your host machine doesn't have enough disk space remaining. ...the disk on which the virtual machine is stored is almost full. (Emphasis mine). You need to free up some space on your Mac's drive in order for the VM to continue.


2

Instead of loading the isos into a virtual drive and trying to boot from that, have you tried just pointing the VirtualBox boot device to the iso file? AskUbuntu has the steps for that


1

All shares are protected by the host shares them let that be real or virtual, and nothing happens to them as long as the host protects them. You cannot remove a shared resource just by removing a client by disconnecting it or by destroying it, so yes, rm away.


1

I've created a Ubuntu 14.04 VM and found exactly your observations, though in my case I was using Ubuntu as host. It appeared that installing vmtools made no difference to the VM, unlike in Windows, where a new graphics driver was installed. It seems that the link you cite refers to much earlier versions of Ubuntu. I then found this link, which confirms ...


1

If you haven't already, install Guest Additions. You can download the version-specific one on the VirtualBox website. Which non-USB devices you want to mount?


1

I'm assuming that by a non-USB device you mean PCI or PCIExpress device. VirtualBox has experimental support for PCI passthrough via an extension. However, support is only available on Linux hosts and only with certain hardware.


1

The initrd.img files contain all the drivers required to boot your VM. That means it probably can't boot to the point where the network is up, let alone sshd. You'll need to get console access and (virtual) CD access, and boot from an ISO file. Or else roll back to a snapshot before you deleted the files from /boot. You shouldn't delete files from /boot ...



Only top voted, non community-wiki answers of a minimum length are eligible