Tag Info

New answers tagged

0

I had found the way to implement the automatic guest installation of default archiso image, controlling only host machine, however it's somewhat cumbersome. You need to combine VBox native functionality with exposed serial port over ssh. Enable virtual serial port support for VBox: VBoxManage modifyvm "$VNM" --uart1 0x3F8 4 --uartmode1 server "$SERIAL" ...


1

Is my guess right? Was VirtualBox indeed the culprit? All the clues do point in its direction. Probably so. If it was VBox, then how come it went on to hijack/reserve all USB devices in case of failure. I had only shared one USB device with it i.e. my USB wireless device. Is this a bug? Did my virtual machine have some virus, and it did something ...


0

Have you tried to install NTP in your VM and let it take care of that? If you were using VMware the best thing to do would be to install vmware-tools which provides automatic sync of time. However, I don't know whether a similar package exists for VirtualBox.


0

apt-get install docker.io It's simple like that.


1

Since elementary OS doesn't provide a traditional desktop, where you can place files (or shortcuts), the default desktop directory is linked to the home directory of your user (you can check it with the command /usr/bin/xdg-user-dir desktop). So, your created shortcut should be in this directory. Once you have found it, just drag&drop it into Plank. ...


0

On my Deepin Linux (a variant of Ubuntu), I know two ways to start the Virtualbox services. In the terminal type service --status-all -- It will list the services registered in system with the status mentioned in output. You can see VirtualBox related services with the name vbox*. This step is now trivial. To start a service type service service_name start ...


0

The guest did have 4 Cores selected from 4 marked as green with 90% processing power on a dual core chip. Changed it to 2 cores and now it works. Thank you Marc for your hint with the RAM.


0

The problem was that I followed tutorials on the web and youtube videos, instead of reading manjaro wiki. The correct way of doing it is not to install virtualbox virtualbox-host-modules, instead of that, first I should check kernel version uname -r in my case I'm using 3.16.7.10-1-MANJARO so I have to do sudo pacman -S linux316-virtualbox-host-modules As ...


1

The address 10.0.2.15 is a internal address for your VM which can not be reached from the Host OS because of the NAT mode. You need to change your network adapter to use bridged mode or host-only-adapter. In bridged mode the guest will try to get an address in the host network and using host-only-adapter you will create an interface on the host OS, ...


1

If the program runs on PlayOnLinux well and you are satisfied with that, it will most probably be faster than in a VM. This would be my first preference. You can check applications' combatibility at WineHQ. Running windows programs in a Virtual Machine (like with VirtualBox or KVM or VMware) is quite convenient, especially for non 3D-games. However, ...


0

With Bridged Adapter - Assign Ip address to your Windows Server, which is of range 46.4.21.66 - 46.4.21.126. As this was Ubuntu Server's IP range assigned to interface eth0. Advantage of bridged adapter will brings the device to your LAN network. In case if you don't find free IP's of mentioned IP range. There is different method. Allocate two Network ...


1

I think this would work, though I do this for ssh into a Linux VM and not rdesktop. The principle is the same though. In VirtualBox, go into Settings -> Network for your VM and click Port Forwarding. There you set up a rule with Protocol=TCP and Guest Port the default port for rdesktop. Sorry I don't know that number, the man page for rdesktop doesn't say. ...


1

VirtualBox is using a virtualised video card and not any of the physical video cards in your machine. In order to give a virtual machine access to physical hardware, you must pass the hardware to the virtual machine. Passing through PCI devices can be difficult and video cards is even more problematic. On top of that, the NVidia proprietary drivers actively ...


0

I found solution for me: Right click on virtual machine -> setting -> networking and change Attached to: Bridged Adapter After change the setting do command shutdown -h now in your virtual machine. hint: (ip addr help to find ip address). At now your can ssh to virtual machine (from your terminal host machine). Thanks for help.


-1

I ran into the same problem; I solved it configuring the network in the virtualBox configuration → network setting page: I selected "Bridged Networking". http://www.thegeekstuff.com/2012/03/virtualbox-guest-additions/


0

Note that to make the command sudo adduser $USER vboxsf work, you'll need to log off and log in again. Otherwise the new group isn't loaded. You can exit a shell session using exit or by pressing Ctrl + D. A reboot will work too.


0

Have you ran out of disk space? this is a very common error if drive space is too low. df -l and look for 0 avail. Try reinstalling onto a larger disk or alot more disk space on the install. I wouldn't recommend expanding your disksapce as some configuration files might have already become corrupted. ~synight


2

At first you have to configure your postgreql and createdb and import your db into your pg, if your postgresql is running , it's not everything ok.please configure pg_hba.conf file.


0

When you make a new virtual machine (i.e. a guest OS) with VirtualBox it will, by default, make the NIC an Am79C973. Whilst this NIC may be supported by many OSes, this particular NIC does not seem to be supported by CentOS 7. This means that the only NIC which will show up inside your new CentOS 7 VM will be the loopback NIC. What you need to do is ...


2

Normally the vboxnet0 device has address 192.168.56.1. This also shows in your config. Your ssh statement point to another address where '56' and '1' are exchanged. Your ping command probably just pings the hosts vboxnet0 device and since you only have a loopback device in your guest machine I suppose that you did not configure networking within the guest. ...


1

It seems that you haven't loaded the kernel module "vboxdrv". Use 'modprobe' to load the module and then try. In case if something goes wrong try installing again the required packages. There is a pretty good documentation on arch linux.



Top 50 recent answers are included