2022-02-18 11:49:54 +00:00
# VirtualBox
### guest share
FYI: _remember to mkdir a folder for this_
`sudo mount.vboxsf media /mnt/exchange`
after adding a guest share the users need access which is granted by a group:
2022-03-11 07:18:46 +00:00
`sudo usermod -G vboxsf -a $USER`
sometimes it will generate a protocol error:
```
[ 6.646480] vboxsf: could not stat root of share: -71
[ 6.647218] 06:53:23.826079 automount Error: vbsvcAutomounterMountIt: Failed to mount 'exchange' on '/mnt/exchange': Protocol error (-1,71)
```
2022-04-22 12:44:44 +00:00
the workaround is to choose an new/other folder on the host system.
### vhd
```bash
modprobe nbd
qemu-nbd -c /dev/nbd0 image.vhd
mount /dev/nbd0 /mnt
[..work...]
umount /mnt
qemu-nbd -d /dev/nbd0
modprobe -r nbd
```
libguestfs
```bash
[install libguestfs-tools]
virt-list-partitions FILE_NAME.vhdx
guestmount -a srv-kirikas-storage.vhdx -m DEVICE --ro MOUNT_POINT
2022-07-05 13:45:28 +00:00
```
2022-07-27 11:58:20 +00:00
### vmdk
```
sudo apt install libguestfs-tools
sudo guestmount -a xyz.vmdk -m /dev/sda3 --ro /mnt/vmdk
OR sudo guestmount -a xyz.vmdk -i --ro /mnt/vmdk
sudo -i (you need to be root to access the folder)
```
2022-08-04 13:10:00 +00:00
### migrate from vhdk to vdi
to handle the error `Could not get the storage format of the medium
```
VBoxManage convertfromraw --format VDI your-server.vmdk new-server.vdi
VBoxManage clonehd --format VDI your-server.vmdk
```
but windows fails with bluescreen because of [unknown], maybe the drive driver?
2022-07-05 13:45:28 +00:00
### virtual bridge inside
as soon as you have a bridge inside the VM all the networking traffic is broken.
2023-06-23 05:56:11 +00:00
Maybe it is the copy of the MAC, which breaks it. However, after doing things, it is working now.
## UEFI and extension pack
the extention pack provides PXE-intel.rom. This option ROM needs DDIM support which is not possible by booting with UEFI. It is not sufficant to disable PXE boot, you need to rename/delete the rom-file itself.
