Tag Info

New answers tagged

0

Ok, the problem was CentOS 7 blocking ports by default. I managed to connect to my server on port 2004 after executing the following command: firewall-cmd --zone=public --add-port=2004/tcp And this command opens the port when the VM reboots: firewall-cmd --zone=public --add-port=2004/tcp --permanent I found the information here.


0

Some consumer-grade routers are confused by the bridged mode of VirtualBox, because then the host and the guest share the same MAC address. I suggest you add a second interface to your VM in host-only mode, for communcation with the host.


0

Most likely if the server is available and you have an IP address for that server you should be able to ssh user@server-ip or ssh server-ip -l user but this will not work if you don't have sshd running on the server to accept ssh/secured tunneling. You need to enable sshd on your server by issuing: sudo /etc/init.d/sshd start You should also look ...


0

It's related to version of VirtualBox, after the mileston it's solved, you have to use: /etc/init.d/vboxdrv setup Maybe you install a new kernel or virtualbox is old.


1

Ditto! I was having this problem too while installing arch on Virtualbox. It was fixed after I did the following. 1) Execute the following to install "mesa" and virtualbox support: pacman -S mesa pacman -S virtualbox-guest-utils 2) Open "/etc/modules-load.d/virtualbox.conf" with nano. nano /etc/modules-load.d/virtualbox.conf and write the following lines ...


2

VirtualBox shared folders are still not suppported on FreeBSD. A FreeBSD ports committer has confirmed this on the FreeBSD mailing lists as of (2014-06-24): Shared Folders for FreeBSD guests are not supported yet [...] There is some draft code and a kernel module for it but it's not working yet. If you want to follow the state of the port, please ...


0

Remember to use sudo. Run it like this and it will work: sudo apt-get install dkms sudo su /etc/init.d/vboxdrv setup see if it work now. I am trying use it too. I was with the same problem. I did on terminal: sudo su and after used the setup where the error says to me. I dont have the virtual machine yet, but this problem(error) is solved with me.


0

I went ahead and downloaded the image. The VMWare image in question is pre-configured to use 2GB of RAM.


3

You only need the grml-zsh-config package like: pacman -S grml-zsh-config ...and maybe to set your default shell to zsh like: chsh -s /usr/bin/zsh [username] You might also want to check what else you can get like: pacman -Ss zsh


2

"Unstable" FreeBSD 10/i386 on VirtualBox, Xen, KVM For FreeBSD installation On FreeBSD boot menu, when booting from installation media, choose: 3. Escape to loader prompt to enter the following commands: set vfs.unmapped_buf_allowed=0 (enter) boot (enter) Then proceed to FreeBSD installation as usual. To run your new FreeBSD system Two solutions: ...


8

Maybe your file system is mounted with noexec option set, so you can not run any executable files. From mount documentation: noexec Do not allow direct execution of any binaries on the mounted filesystem. (Until recently it was possible to run binaries anyway using a command like /lib/ld*.so /mnt/binary. This trick fails since Linux 2.4.25 / ...


3

I think you can set the virtual machine's disk to be immutable in order to get what you want. [...] immutable images only remember write accesses temporarily while the virtual machine is running; all changes are lost when the virtual machine is powered on the next time. As a result, as opposed to "normal" images, the same immutable image can be used with ...


2

Flush the iptables rules just in case (iptables -F). With the network in bridge mode (I assume that was what you were after ideally) run wireshark on the Ubuntu machine and watch for DHCP requests. If you see a request but no response then you're likely looking at network restrictions. Either way wireshark will help you get a better of idea what is ...



Top 50 recent answers are included