Hot answers tagged virtual-machine
You can use libguestfs tools to access filesystems in a virtual machine image. mkdir ~/mnt guestmount -a /path/to/vm-image.vdi -m /dev/sda1 ~/mnt … edit files … fusermount -u ~/mnt Libguestfs uses QEMU, which may use KVM. KVM and VirtualBox cannot be used at the same time. If you have VirtualBox running, either close it and make sure that the kvm kernel ...
With default settings, software in a Windows 7 guest would not be able to access the keyboard input from outside of Virtualbox such as the host or another running guest. Access to the host OS resources would have to be permitted explicitly in some way to permit the guest control. However, human error can always sabotage the implicit security controls. ...
You can do this, if you have a third machine where you can run a GUI. For instance, I've setup Windows 7 running in Xen server (a bare-metal hypervisor with only ssh access to the server). I connected to it using RDP (remote desktop), from other Windows machines as well as using an RDP client on OS X.
Isn't it a problem of permissions ? On linux after creating a new OS through VB, I always need to add the current user to the vboxsf group in order to be able to mount the shared folder, please post the output of groups $(whoami) ... To add yourself to vboxsf: sudo usermod -aG vboxsf $(whoami)
When I have a centOS6 on Virtualbox I usually add in /etc/rc.local(guest machine side) a line like this : mount -t vboxsf -o umask=0000,gid=48,uid=48 name-of-the-shared-folder /path/of/the/mounted/directory this should mount the shared folder automatically at VM startup. PS: if you have one you can get your current domain name by opening a terminal and ...
I believe QEMU wants a disk image file and /dev/mapper/windows-vm is a block device. According to the Arch wiki you can pass QEMU a partition, but this would require you to run mkfs on the block device. The wiki then goes on to say that this approach is problematic since you cannot install a bootloader to a partition (which I do not think is 100% accurate). ...
You do not have a listener on 127.0.0.1:7000 (or 0.0.0.0:7000) on the guest. Check for a listener on the guest using: netstat -an|grep 7000 See if a line like x.x.x.x:7000 0.0.0.0:* LISTEN exists and on which interface it is bound. The GatewayPorts directive does not make sense in this configuration since it applies only for remote portforwarding.
I have tried both and I am in fact running both in production environment. My experience: nfs is rock stable, of acceptable speed, but once the guest starts reading a lot of files or reading quickly a huge file, the host performance goes very noticeably down. This is especially pronounced if you run several guests and they start accessing the filesystem ...
Only top voted, non community-wiki answers of a minimum length are eligible