74 items | 2 visits
D C's List: Virtualization
-
-
su dnf download kernel-devel-4.0.4-301.fc22.i686 rpm -ivh --oldpackage kernel-devel-4.0.4-301.fc22.i686.rpm /etc/init.d/vboxdrv setup
-
-
Aug 27, 14
sudo mount -t vboxsf -o rw,uid=1000,gid=1000 share ~/host
-
Now mount it with the following command:
- Code: Select all Expand viewCollapse view
sudo mount -t vboxsf share ~/host
-
To mount the SF so that you are the owner of the files, use this command:
- Code: Select all Expand viewCollapse view
sudo mount -t vboxsf -o rw,uid=1000,gid=1000 share ~/host
-
-
-
Jul 26, 12
"VBoxManage clonehd source.vhd target.vdi --format vdi"
-
-
I ran into this same problem myself a little while back.
....
Firstly create a new vdi, under ~/.VirtualBox/HardDisks
#VBoxManage createhd -filename new.vdi --size 10000 --remember
#VBoxManage clonehd old.vdi new.vdi --existing
....
Cheers Steve
This worked for me!
-
-
-
May 26, 12
"mount -o noatime,noexec /dev/nbd0p1 /tmp/vdi/"
-
May 26, 12
"I've got the same problem just now...
It worked correctly with nbd as module and "modprobe nbd max_part=16". "-
I've got the same problem just now...
It worked correctly with nbd as module and "modprobe nbd max_part=16".
-
-
-
VBoxManage modifyhd <your filename> --resize 100000. That command would be for 100GB
-
-
Feb 24, 12
In order to have a KVM-Qemu management console, you should start KVM with something like:
-monitor telnet:127.0.0.1:3010,server,nowait,ipv4-
In order to have a KVM-Qemu management console, you should start KVM with something like:
-monitor telnet:127.0.0.1:3010,server,nowait,ipv4
-
-
-
qemu-system-x86_64 -m 512 -cdrom yourimagehere.iso
-
List Comments
(0)
List Info