New answers tagged virtual-machine
Docker makes LXC easier to use: Notable features Filesystem isolation: each process container runs in a completely separate root filesystem. Resource isolation: system resources like cpu and memory can be allocated differently to each process container, using cgroups. Network isolation: each process container runs in its own ...
Turning off 3D acceleration in the VM's configuration will fix it. There's a bug with some of the packages on the CD. After installing to the VM and running updates you can turn 3D acceleration back on. Here is the ask.fedoraproject link that I saw: https://ask.fedoraproject.org/question/10024/fedora-18-impossible-to-use-on-vmware-9/ and the bug report: ...
If you're running the NFS server from within the qemu virtual machine, (the guest), then you should be able to go into the qemu guest and run this command: ifconfig -a It should return output sort of like this: eth0 Link encap:Ethernet HWaddr 00:18:51:D4:AA:12 inet addr:192.168.1.103 Bcast:192.168.1.255 Mask:255.255.255.0 ...
I think you don't need a VM for that at all. You can create your own Archiso, have a look at this: https://wiki.archlinux.org/index.php/Archiso
well, the most intuitive way I always do is: $ dmesg | grep -i vmware
You can resize the filesystem in place, with GParted. Create the test image: dd if=/dev/zero of=extfs bs=1M count=20 mkfs.ext4 extfs I'm not using resize2fs, because it resizes the file, rather than leaving free space. sudo losetup /dev/loop0 extfs sudo ln -s /dev/loop0 /dev/loop0p1 # needed for GParted to be able to resize it gksudo gparted /dev/loop0 ...
I use Mock on Ubuntu to build RPM packages. One of the things mock does is create and maintain chroots (similar to pbuilder for Debian), so you could try creating a chroot with it and building from there.
I never tried it, but it seems that febootstrap can install a CentOS.
I would leave it. I believe ACPI does more than just power management. For example I believe there is a ACPI event that is sent in via the VM Host to the guests when you want them to shutdown or reboot. Excerpt from Manual:KVM: shut-down issue ACPI shut-down command to KVM guest, if guest does not support ACPI, command have no effect. reboot ...
Strictly speaking, no you don't need acpid in a virtual machine nor on a real system. But you should install acpid in a VM as it typically handles the power button press which is simulated by the hypervisor if you shutdown a VM. So for practically reasons, yes you should install acpid on a VM. P.S: acpid doesn't really do power management
There is absolutely no reason not to do so, as long as everything you want to do in the host and client works as you want. I used this setup on my Sony PCG-Z505 with VMware from early 2000 until mid 2003. Host: Windows 98 and client SuSE Linux. The main reason for that setup were that I could use the imap server under Linux from the host Outlook Express ...
Top 50 recent answers are included