VirtualBox

VirtualBox 是運行於現有作業系統之上的虛擬機監視器，用途是在特製環境（即虛擬機）裡運行作業系統。VirtualBox 處於活躍開發狀態，時常會引入新功能。VirtualBox 支持 Qt，SDL 與無界面模式運行虛擬機。也支持用 Qt 圖形界面和命令行工具管理虛擬機。

為了實現某些主體-客體系統間的整合功能，例如共享目錄與剪貼板、顯卡加速渲染、無縫窗口整合，VirtualBox 需要在某些系統中安裝客體機插件（Guest Addition）。

在 Arch 裡安裝 VirtualBox[編輯 | 編輯原始碼]

以下步驟可以幫你在 Arch 主體系統裡安裝 VirtualBox

安裝基本軟件包[編輯 | 編輯原始碼]

安裝軟件包 virtualbox^包。內核模塊的安裝方式要從下面二選一：

如果使用的是 linux^包內核，建議安裝 virtualbox-host-modules-arch^包
其它的內核，包括 linux-lts^包，請安裝 virtualbox-host-dkms^包

為了讓 virtualbox-host-dkms^包編譯內核模塊，需要安裝對應的內核頭文件（例如linux-lts^包內核的頭文件是 linux-lts-headers^包）。[1] 當 VirtualBox 或內核更新的時候，DKMS 的 Pacman 鈎子會自動編譯內核模塊。

模塊簽名[編輯 | 編輯原始碼]

如果你的 Linux 內核是自行編譯的，並啟用了 CONFIG_MODULE_SIG_FORCE 選項，那麼你需要用編譯內核時所使用的密鑰為所有模塊簽名。

進入內核源碼目錄，執行下面的命令：

# for module in `ls /lib/modules/$(uname -r)/kernel/misc/{vboxdrv.ko,vboxnetadp.ko,vboxnetflt.ko}` ; do ./scripts/sign-file sha1 certs/signing_key.pem certs/signing_key.x509 $module ; done

注意： 哈希算法不必與配置時選擇的算法相匹配，但必須被編譯進內核。

加載 VirtualBox 內核模塊[編輯 | 編輯原始碼]

virtualbox-host-modules-arch^包和 virtualbox-host-dkms^包使用 systemd-modules-load.service 在啟動時自動加載 VirtualBox 的四個內核模塊。若要在安裝之後就加載模塊，可以手動加載一次，或者乾脆重啟。可以從 /usr/lib/modules-load.d/virtualbox-host-modules-arch.conf 或 /usr/lib/modules-load.d/virtualbox-host-dkms.conf 中查看加載的模塊列表。

注意： 如果希望啟動時不自動加載 VirtualBox 模塊，需要將默認的 /usr/lib/modules-load.d/virtualbox-host-modules-arch.conf (或 /usr/lib/modules-load.d/virtualbox-host-dkms.conf) 配置文件屏蔽掉。具體做法是：在 /etc/modules-load.d/ 目錄裡創建同名的空文件。

在 VirtualBox 所使用的內核模塊中，只有 vboxdrv 是必須的。該模塊必須在虛擬機運行之前加載。

手動加載模塊的命令是：

# modprobe vboxdrv

以下模塊不是必需的，但如果你不想在使用高級功能（見下）時再操心，建議都加載上。

vboxnetadp 和 vboxnetflt：這兩個模塊在使用橋接網絡和host-only 網絡功能時，都是需要的。具體來説，vboxnetadp 模塊用於在 VirtualBox 全局配置裡為主體機創建虛擬網卡；vboxnetflt 模塊會在使用了該功能的客體機啟動時起作用。

注意： 如果在 VirtualBox 內核模塊運行期間你更新了模塊（所屬的軟件包），為了使用新版本，你需要手動重新加載這些模塊。在 root 權限下運行 vboxreload 即可重新加載。

從客體系統訪問主機 USB 設備[編輯 | 編輯原始碼]

將需要運行 VirtualBox 的用户名添加到 vboxusers 用户組，USB 設備才能被訪問。

客體機插件光盤[編輯 | 編輯原始碼]

建議在運行 VirtualBox 的主機系統上安裝 virtualbox-guest-iso^包軟件包。這個包裡有個 .iso 鏡像文件，用來為 Arch 之外的客體系統安裝插件。鏡像文件的位置在 /usr/lib/virtualbox/additions/VBoxGuestAdditions.iso，手動在虛擬機的虛擬光驅裡加載這個文件之後，即可在客體機裡安裝插件。

擴展包[編輯 | 編輯原始碼]

Oracle Extension Pack 為虛擬機提供了額外功能。但它並不是以自由軟件協議發佈的，僅供個人使用。這些擴展包可以從 virtualbox-ext-oracle^AUR 安裝，從 seblu 倉庫可以安裝編譯好的版本。

如果你喜歡使用傳統的手動方法來安裝擴展包：通過 GUI 下載並安裝 (File > Preferences > Extensions) 或着手動下載後用 VBoxManage extpack install <.vbox-extpack> 命令來安裝。你需要某種方式（例如 Polkit 等等）在安裝時為 VirtualBox 授予 root 權限。

使用正確的前端[編輯 | 編輯原始碼]

VirtualBox 自帶三個前端：

如果你想通過常規 GUI 使用 VirtualBox，使用 VirtualBox 命令來啟動 VirtualBox。
如果你想在命令行下啟動與管理 VirtualBox，可以使用 VBoxSDL 命令。從 VBoxSDL 啟動的虛擬機，其窗口僅包含虛擬機的畫面，沒有菜單或是其他控制項。
如果你想使用不想由任何 GUI（例如在伺服器上）來使用 VirtualBox，使用 VBoxHeadless 命令。如果還想登錄到這種虛擬機的圖形界面，就需要安裝 VRDP 擴展。

A security feature in Wayland (i.e. when using GDM) disallows VirtualBox to grab all keyboard input. This is annoying when you want to pass window manager shortcuts to your guest OS. It can be bypassed by whitelisting VirtualBox:

$ gsettings get org.gnome.mutter.wayland xwayland-grab-access-rules

$ gsettings set org.gnome.mutter.wayland xwayland-grab-access-rules "['VirtualBox Machine']"

The first command will show if any other applications are already whitelisted. If so, add 'VirtualBox Machine' to that list, rather than having it as the only one.

如果你想通過 web 界面來管理虛擬機，可以安裝 PhpVirtualBox。

若要了解如何創建虛擬機，可以查閱 VirtualBox 手冊。

警吿： 如果你想把在虛擬機的硬盤鏡像放到 Btrfs 文件系統上，在創建鏡像之前，你應該考慮為鏡像所處的文件夾關閉寫時複製。

在 VirtualBox 中安裝 Arch Linux[編輯 | 編輯原始碼]

請參閱 VirtualBox/Install Arch Linux as a guest。

虛擬磁盤管理[編輯 | 編輯原始碼]

VirtualBox 支持的格式[編輯 | 編輯原始碼]

VirtualBox 支持下列虛擬磁盤格式：

VDI: Virtual Disk Image 格式是 VirtualBox 新建虛擬機時默認選用的格式。也是 VirtualBox 的自有開放格式。

VMDK: Virtual Machine Disk 最初是由 VMware 為其產品研發的格式。該格式技術設計文檔最初是閉源的，而現在已經開源，在 VirtualBox 裡完全可用。這種格式有個功能是：把一個虛擬機的鏡像分割成多個 2GB 大小的文件。如果你要把虛擬機鏡像放在不支持大文件的文件系統（例如 FAT32）上，那麼這個功能就非常有用。在其他的虛擬磁盤格式裡，能做到同樣功能的只有 Parallels 的 HDD。

VHD: Virtual Hard Disk 是 Microsoft 為 Windows Virtual PC 與 Hyper-V 研發的格式。如果你想把虛擬機部署到這些平台上，那麼你只能用這種格式。

提示：Windows 7 開始可以直接把 VHD 文件掛載成虛擬盤進行讀寫。而不需要額外安裝軟件。

VHDX (只讀): 這是由 Microsoft 研發的 Virtual Hard Disk 格式的加強版。於 2012-09-04 與 Hyper-V 3.0 同步發佈，二者都是 Windows Server 2012 的功能。該加強版的改進包括性能優化（源於區塊對齊），支持大區塊單位，還有應對斷電的磁盤日誌。VirtualBox 支持該格式的只讀訪問。

HDD (V2): HDD 格式是由 Parallels Inc 研發的，由他們的虛擬機方案（如 Parallels Desktop for Mac）所使用。該格式的新版（v3 和 v4）由於缺少文檔，又是專有格式，未能被 VirtualBox 支持。

注意： 關於該格式「僅支持 V2 版」的説法目前有爭議。VirtualBox 官方手冊聲稱只支持 V2 版，但 Wikipedia 上的説法是 V1 版也能正常工作。如果你能為 V1 的支持狀況做測試驗證，非常歡迎。

QED: QEMU Enhanced Disk 是舊版 QEMU 使用的格式。QEMU 也是一個開源免費的虛擬機方案。該格式於 2010 年設計出來，目的是要比 QCOW2 等格式更優秀。這種格式支持的功能包括全異步 I/O，數據高度完整性，文件備份，稀疏文件。VirtualBox 支持 QED 格式只是為了兼容由舊版 QEMU 創建的虛擬機。

QCOW: QEMU Copy On Write 是 QEMU 現有版本支持的格式。QCOW 支持基於 zlib 實現的透明壓縮與加密（加密功能有缺陷，不推薦使用）。QCOW 包括兩個版本：QCOW 與 QCOW2。QCOW2 取代了舊版。VirtualBox 完全支持舊版 QCOW。QCOW2 包含兩個修訂版：QCOW2 0.10 和 QCOW2 1.1（QEMU 新建的虛擬機默認使用 1.1）。然而 VirtualBox 並不支持 QCOW2。

OVF: Open Virtualization Format 是為了在讓虛擬機在不同監視器方案間得到通用而設計的開放方案。VirtualBox 支持該格式的所有修訂版，具體的支持方式是 VBoxManage import/export 命令，但也有部分功能受限。

RAW: 虛擬磁盤可以不以任何文件格式封裝，而直接以這種 RAW 模式供虛擬機使用。VirtualBox 對此有多種支持方案：將 RAW 磁盤轉換成上述某種格式；將物理盤轉換成 RAW 格式；直接掛載一個指向物理盤或 RAW 格式文件的 VMDK 文件。

轉換虛擬磁盤文件格式[編輯 | 編輯原始碼]

VBoxManage clonehd 這個命令可以實現 VDI, VMDK, VHD 與 RAW 格式間的互轉

$ VBoxManage clonehd inputfile outputfile --format outputformat

以 VDI 轉成 VMDK 為例：

$ VBoxManage clonehd source.vdi destination.vmdk --format VMDK

QCOW[編輯 | 編輯原始碼]

VirtualBox 不支持 QEMU 的 QCOW2 格式。若要讓 VirtualBox 使用 QCOW2 格式的文件，你只能將其轉換成已支持的格式。用 qemu-img^包包提供的 qemu-img 程序可以做到。qemu-img 可以實現 QCOW 格式與 VDI, VMDK, VHDX, RAW 等其他格式間的互轉。具體支持的格式可以通過運行 qemu-img --help 命令查看。

該命令的一般形式是：

$ qemu-img convert -O output_fmt inputfile outputfile

以 QCOW2 轉成 VDI 為例：

$ qemu-img convert -O vdi source.qcow2 destination.vdi

提示：轉換時加上 -p 參數可以實時查看轉換進度

QCOW2 有兩個修訂版： 0.10 和 1.1，用 -o compat=revision 參數可以具體指定。

在宿主機直接掛載並讀寫虛擬磁盤鏡像[編輯 | 編輯原始碼]

VDI[編輯 | 編輯原始碼]

固定大小的 VDI 鏡像（又名靜態鏡像）可以直接在宿主機掛載。動態鏡像則沒法輕鬆掛載。

首先要拿到 VDI 裡數據分區的偏移量 offData：

$ VBoxManage internalcommands dumphdinfo <storage.vdi> | grep "offData"

然後再加上 32256 (例如 69632 + 32256 = 101888)，那麼就用這個命令來掛載：

# mount -t ext4 -o rw,noatime,noexec,loop,offset=101888 storage.vdi /mntpoint/

For VDI disks with more partitions you can also use losetup:

# losetup -o $offData -Pf

After this you should find the partitions under /dev/loop* (e.g. /dev/loop0p1). Then you can mount them as usual (e.g. mount mount /dev/loop0p1 /mnt/).

另一個辦法是用 mount.vdi 腳本來完成掛載。首先要把腳本安裝到 /usr/bin/，然後：

# mount -t vdi -o fstype=ext4,rw,noatime,noexec vdi_file_location /mnt/

還有一個辦法是用 qemu-img^包的內核模塊來實現[2]：

# modprobe nbd max_part=16
# qemu-nbd -c /dev/nbd0 <storage.vdi>
# mount /dev/nbd0p1 /mnt/dir/
# # to unmount:
# umount /mnt/dir/
# qemu-nbd -d /dev/nbd0

如果未能生成分區節點，試試運行命令：partprobe /dev/nbd0。另外，VDI 分區還可以直接用這個命令來映射到節點：qemu-nbd -P 1 -c /dev/nbd0 <storage.vdi>。

Another way is to use vdfuse^AUR:

# vdfuse -a -f storage.vdi mountpoint1

which mounts the disk in mountpoint1 with the PartitionN naming format. Each partition can then be loop-mounted in mountpoint2:

# mount -o loop mountpoint1/PartitionN mountpoint2

VHD[編輯 | 編輯原始碼]

Like VDI, VHD images can be mounted with QEMU's nbd module:

# modprobe nbd

# qemu-nbd -c /dev/nbd0 storage.vhd

# mount /dev/nbd0p1 /mnt

To unmount:

# umount /mnt

# qemu-nbd -d /dev/nbd0

壓緊虛擬磁盤[編輯 | 編輯原始碼]

只有 .vdi 格式的虛擬磁盤文件可以壓緊。具體操作步驟如下。

啟動虛擬機，手動刪除無用文件，或者用自動的清理工具（如 bleachbit^包，同時也支持 Windows）來清理磁盤。

下一步要用零字節來填充可用空間。這有如下的可行方案：

如果你已經在用 Bleachbit 了，在 GUI 菜單裏選擇 System > Free disk space，或者在命令行執行：bleachbit -c system.free_disk_space；
在類 UNIX 系統裏，dd 或 dcfldd^AUR 都可以做到，後者更推薦。（參閱這裏來了解兩者的區別）；

# dcfldd if=/dev/zero of=/fillfile bs=4M

當 fillfile 文件的體積佔滿分區時，會出現這樣的錯誤信息：1280 blocks (5120Mb) written.dcfldd:: No space left on device。這意味着所有的可用空間與未保留區塊都已經被零字節填滿了。因為 ext 類系統會為 root 用户默認保留一部分硬盤空間（見 mkfs.ext4 手冊頁對 -m 參數的解釋，或者用 tune2fs -l 命令來查看具體為 root 保留了多少空間），所以運行這一命令時需要有 root 權限。

前面一步操作完成後，手動把 fillfile 刪掉。

在 Windows 系統裏有兩種辦法：

由 Sysinternals Suite 提供的 sdelete 命令，用法是 sdelete -s -z c:。在虛擬機裡的每一個分區都要執行一遍（當然 c: 這個參數要對應地改成各個分區的盼覆）；
如果你喜歡腳本，可以用這個 PowerShell 實現的方案，但依然要每個分區執行一次。

PS> ./Write-ZeroesToFreeSpace.ps1 -Root c:\ -PercentFree 0

注意： 該腳本需要在有管理員權限的 PowerShell 環境才能運行。默認的 PowerShell 默認配置下，這個腳本無法運行。需要把秩序策略至少調整到 RemoteSigned，而不能是 Restricted。用 Get-ExecutionPolicy 命令可以看到當前的執行策略，用 Set-ExecutionPolicy RemoteSigned 可以設置想要的執行策略。

完成這一步之後，將虛擬機停機。

下一次啟動虛擬機時，推薦先進行文件系統檢查：

在類 UNIX 系統上可以手動運行 fsck 來檢查；

在 GNU/Linux 系統上（包括 Arch）可以在系統啟動時強行執行硬盤檢查。詳見 thanks to a kernel boot parameter；

在 Windows 系統上：

可以用這個命令 chkdsk c: /F。其中 c: 可以替換成所有你希望檢查的盤符；
或者從這裏下載 FsckDskAll。這和前面的 chkdsk 基本一樣，只是不必手動為每個分區執行一遍了。

接下來用 VBoxManage modifyhd 即可完成壓緊過程：

$ VBoxManage modifymedium disk  your_disk.vdi --compact

注意： 如果你的虛擬機有保存過快照，那麼每個 .vdi 文件都要單獨執行一遍壓緊操作。

擴充虛擬硬盤容量[編輯 | 編輯原始碼]

一般方法[編輯 | 編輯原始碼]

如果你在創建虛擬機時給虛擬硬盤分配的容量太小了，VirtualBox 推薦的擴容方案是用 VBoxManage modifyhd 這個命令。然而這個命令只支持 VDI 和 VHD 這兩種格式，而且還需要設置成動態分配容量。如果你想為固定容量的虛擬磁盤擴容，下面的辦法可以適用於 Windows 或類 UNIX 系統的虛擬機。

首先創建一個新的虛擬磁盤：

$ VBoxManage createmedium disk -filename new.vdi --size 10000

--size 參數的值的單位是 MiB，在例子裏 10000 MiB ~= 10 GiB，new.vdi 是新創建的鏡像文件。

注意： 由這個命令創建的鏡像文件默認是動態分配空間的。如果想讓新鏡像和舊鏡像一樣固定空間，需要追加參數 --variant Fixed。

接下來要把舊鏡像的內容複製到新鏡像裡去，這一步驟可能會花些時間：

$ VBoxManage clonemedium disk old.vdi new.vdi --existing

取下舊硬盤鏡像，掛載新鏡像，下面命令中的斜體字部分需要按照你的使用環境來換成真實的值：

$ VBoxManage storageattach VM_name --storagectl SATA --port 0 --medium none
$ VBoxManage storageattach VM_name --storagectl SATA --port 0 --medium new.vdi --type hdd

在上面的命令中，若要獲知儲存控制器的名字與端口號，可以使用命令：VBoxManage showvminfo VM_name。這會打印出如下的輸出（斜體標註的信息是有用的）：

[...]
Storage Controller Name (0):            IDE
Storage Controller Type (0):            PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
Storage Controller Name (1):            SATA
Storage Controller Type (1):            IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  30
Storage Controller Port Count (1):      1
Storage Controller Bootable (1):        on
IDE (1, 0): Empty
SATA (0, 0): /home/wget/IT/Virtual_machines/GNU_Linux_distributions/ArchLinux_x64_EFI/Snapshots/{6bb17af7-e8a2-4bbf-baac-fbba05ebd704}.vdi (UUID: 6bb17af7-e8a2-4bbf-baac-fbba05ebd704)
[...]

下載 GParted Live 可引導鏡像，在虛擬機裡用虛擬光驅加載之，啟動虛擬機，調整分區大小 / 位置，取下鏡像並重啟。這樣擴容就完成了。

注意： 如果虛擬盤用了 GPT 分區表，擴容會導致 GPT 備份頭不再位於磁盤末尾。GParted 會詢問是否要將其修復，此時兩次詢問都要點 Fix。如果是 MBR 分區，就不存在這一問題。

最後，從 VirtualBox 裡註銷舊的鏡像文件，並刪除掉：

$ VBoxManage closemedium disk old.vdi
$ rm old.vdi

VDI 格式的方法[編輯 | 編輯原始碼]

如果你的虛擬磁盤是 VDI 格式的：

$ VBoxManage modifymedium disk your_virtual_disk.vdi --resize the_new_size

然後回到上面的 Gparted 步驟，繼續完成擴容操作。

修改 .vbox 文件來替換磁盤鏡像[編輯 | 編輯原始碼]

如果相比用 GUI 或 VBoxManage 來管理虛擬機，你覺得編輯 XML 文件更加簡單直接。按下面的步驟修改虛擬機對應的 .vbox 文件，即可完成虛擬機的磁盤替換：

ArchLinux_vm.vbox

<HardDisk uuid="{670157e5-8bd4-4f7b-8b96-9ee412a712b5}" location="ArchLinux_vm.vdi" format="VDI" type="Normal"/>

找到 <StorageController> 的子元素 <AttachedDevice>，把 GUID 屬性改成新鏡像文件的值：

ArchLinux_vm.vbox

<AttachedDevice type="HardDisk" port="0" device="0">
  <Image uuid="{670157e5-8bd4-4f7b-8b96-9ee412a712b5}"/>
</AttachedDevice>

注意： 如果你還不知道新鏡像文件的 GUID 值，可以用命令 VBoxManage showhdinfo file 來查看。如果你用 VBoxManage clonehd 命令來處理過虛擬盤，那麼在複製 / 轉換過程完成時，也會打印出 GUID 值。隨便寫一個 GUID 上去是不行的，必須與鏡像文件裡的 GUID 值相對應才行。

將虛擬機從 Linux 宿主系統遷移到其他系統（或遷回）[編輯 | 編輯原始碼]

.vbox 配置文件把虛擬盤和快照文件的位置記錄在 <HardDisks> .... </HardDisks> 標籤裡。如果新宿主系統存放虛擬機文件的路徑與舊宿主系統不同，你可以手動修改 .vbox 文件來調整路徑。如果 .vbox 文件與虛擬盤 / 快照文件位於相同的目錄，也可以用下面的腳本自動修改。該腳本會將修改後的新配置打印到標準輸出。

#!/bin/sh
NewPath="${PWD}/"
Snapshots="Snapshots/"
Filename="$1"

 awk -v SetPath="$NewPath" -v SnapPath="$Snapshots" '{if(index($0,"<HardDisk uuid=") != 0){A=$3;split(A,B,"=");
L=B[2];
 gsub(/\"/,"",L);
  sub(/^.*\//,"",L);
  sub(/^.*\\/,"",L);
 if(index($3,"{") != 0){SnapS=SnapPath}else{SnapS=""};
  print $1" "$2" location="\"SetPath SnapS L"\" "$4" "$5}
else print $0}' "$Filename"

注意：

如果你想把虛擬機遷移到 Windows 宿主系統上去，文件路徑裡應該使用 \ 而不是 /。
這個腳本判斷快照的邏輯是：文件名是否包含 {。
為了在新宿主機上運行起來，首先得在管理界面註冊：點選菜單項 Machine -> Add... 或者按快捷鍵 Ctrl+A ，然後找到 .vbox 配置文件。也可以用命令行：VBoxManage registervm filename.vbox

複製虛擬盤並為其分配新 UUID[編輯 | 編輯原始碼]

VirtualBox 廣泛應用了 UUID。每個虛擬機，虛擬機的每個虛擬盤，都有屬於自己的 UUID。用 VBoxManage list 命令可以列出 VirtualBox 管理的所有資源。

如果你想複製一台虛擬機，僅複製虛擬盤鏡像文件是不夠的。你還得給複製出的新鏡像文件分配一個新的 UUID。否則在同一個 VirtualBox 的環境裏無法同時註冊兩個具有相同 UUID 的鏡像文件。

下面這個命令可以用來為虛擬盤分配新 UUID：

$ VBoxManage internalcommands sethduuid /path/to/disk.vdi

提示：用 VBoxManage clonehd 可以一次性完成複製內容與分配新 UUID

注意： 上述命令可以用於任意 VirtualBox 所支持的鏡像格式。

使用技巧[編輯 | 編輯原始碼]

Tips and tricks[編輯 | 編輯原始碼]

Import/export VirtualBox virtual machines from/to other hypervisors[編輯 | 編輯原始碼]

If you plan to use your virtual machine on another hypervisor or want to import in VirtualBox a virtual machine created with another hypervisor, you might be interested in reading the following steps.

Remove additions[編輯 | 編輯原始碼]

Guest additions are available in most hypervisor solutions: VirtualBox comes with the Guest Additions, VMware with the VMware Tools, Parallels with the Parallels Tools, etc. These additional components are designed to be installed inside a virtual machine after the guest operating system has been installed. They consist of device drivers and system applications that optimize the guest operating system for better performance and usability by providing these features.

If you have installed the additions to your virtual machine, please uninstall them first. Your guest, especially if it is using an OS from the Windows family, might behave weirdly, crash or even might not boot at all if you are still using the specific drivers in another hypervisor.

Use the right virtual disk format[編輯 | 編輯原始碼]

This step will depend on the ability to convert the virtual disk image directly or not.

Automatic tools[編輯 | 編輯原始碼]

Some companies provide tools which offer the ability to create virtual machines from a Windows or GNU/Linux operating system located either in a virtual machine or even in a native installation. With such a product, you do not need to apply this and the following steps and can stop reading here.

Parallels Transporter which is non free, is a product from Parallels Inc. This solution basically consists in an piece of software called agent that will be installed in the guest you want to import/convert. Then, Parallels Transporter, which only works on OS X, will create a virtual machine from that agent which is contacted either by USB or Ethernet network.
VMware vCenter Converter which is free upon registration on the VMware webiste, works nearly the same way as Parallels Transporter, but the piece of software that will gather the data to create the virtual machine only works on a Windows platform.

Manual conversion[編輯 | 編輯原始碼]

First, familiarize yourself with the formats supported by VirtualBox and those supported by third-party hypervisors.

Importing or exporting a virtual machine from/to a VMware solution is not a problem at all if you use the VMDK or OVF disk format, otherwise converting VMDK to VDI and VDI to VMDK is possible and the aforementioned VMware vCenter Converter tool is available.
Importing or exporting from/to QEMU is not a problem neither: some QEMU formats are supported directly by VirtualBox and conversion between QCOW2 to VDI and VDI to QCOW2 is still available if needed.
Importing or exporting from/to Parallels hypervisor is the hardest way: Parallels does only support its own HDD format (even the standard and portable OVF format is not supported!).

To export your virtual machine to Parallels, you will need to use the Parallels Transporter tool described above.
To import your virtual machine to VirtualBox, you will need to use the VMware vCenter Converter described above to convert the VM to the VMware format first. Then, apply the solution to migrate from VMware.

Create the VM configuration for your hypervisor[編輯 | 編輯原始碼]

Each hypervisor have their own virtual machine configuration file: .vbox for VirtualBox, .vmx for VMware, a config.pvs file located in the virtual machine bundle (.pvm file), etc. You will have thus to recreate a new virtual machine in your new destination hypervisor and specify its hardware configuration as close as possible as your initial virtual machine.

Pay a close attention to the firmware interface (BIOS or UEFI) used to install the guest operating system. While an option is available to choose between these 2 interfaces on VirtualBox and on Parallels solutions, on VMware, you will have to add manually the following line to your .vmx file.

ArchLinux_vm.vmx

firmware = "efi"

Finally, ask your hypervisor to use the existing virtual disk you have converted and launch the virtual machine.

提示：

On VirtualBox, if you do not want to browse the whole GUI to find the right location to add your new virtual drive device, you can Replace a virtual disk manually from the .vbox file, or use the VBoxManage storageattach described in #Increasing the size of VDI disks or in the VirtualBox manual page.
Similarly, in VMware products, you can replace the location of the current virtual disk location by adapting the .vmdk file location in your .vmx configuration file.

Virtual machine launch management[編輯 | 編輯原始碼]

Starting virtual machines with a service (autostart)[編輯 | 編輯原始碼]

Find hereafter the implementation details of a systemd service that will be used to consider a virtual machine as a service.

/etc/systemd/system/vboxvmservice@.service

[Unit]
Description=VBox Virtual Machine %i Service
Requires=systemd-modules-load.service
After=systemd-modules-load.service

[Service]
User=username
Group=vboxusers
ExecStart=/usr/bin/VBoxManage startvm %i --type startmode
ExecStop=/usr/bin/VBoxManage controlvm %i stopmode
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target

注意：

Replace username with a user that is a member of the vboxusers group. Make sure the user chosen is the same user that will create/import virtual machines, otherwise the user will not see the VM appliances.
Replace startmode with a VM frontend type, usually gui, headless or separate
Replace stopmode with desired state switch, usually savestate or acpipowerbutton

注意： If you have multiple virtual machines managed by Systemd and they are not stopping properly, try to add KillMode=none and TimeoutStopSec=40 at the end of [Service] section.

Enable the vboxvmservice@your_virtual_machine_name systemd unit in order to launch the virtual machine at next boot. To launch it directly, simply start the systemd unit.

VirtualBox 4.2 introduces a new way for UNIX-like systems to have virtual machines started automatically, other than using a systemd service.

Starting virtual machines with a keyboard shortcut[編輯 | 編輯原始碼]

It can be useful to start virtual machines directly with a keyboard shortcut instead of using the VirtualBox interface (GUI or CLI). For that, you can simply define key bindings in .xbindkeysrc. Please refer to Xbindkeys for more details.

Example, using the Fn key of a laptop with an unused battery key (F3 on the computer used in this example):

"VBoxManage startvm 'Windows 7'"
m:0x0 + c:244
XF86Battery

注意： If you have a space in the name of your virtual machine, then enclose it with single apostrophes like made in the example just above.

Use specific device in the virtual machine[編輯 | 編輯原始碼]

Using USB webcam / microphone[編輯 | 編輯原始碼]

注意： You will need to have VirtualBox extension pack installed before following the steps below. See #Extension pack for details.

Make sure the virtual machine is not running and your webcam / microphone is not being used.
Bring up the main VirtualBox window and go to settings for Arch machine. Go to USB section.
Make sure "Enable USB Controller" is selected. Also make sure that "Enable USB 2.0 (EHCI) Controller" is selected too.
Click the "Add filter from device" button (the cable with the '+' icon).
Select your USB webcam/microphone device from the list.
Now click OK and start your VM.

注意： If your Microphone does not show up in the "Add filter from device" menu, try the USB 3.0 and 1.1 options instead (In Step 3).

Detecting web-cams and other USB devices[編輯 | 編輯原始碼]

注意： This will not do much if you are running a *NIX OS inside of your VM, as most do not have autodetection features.

If the device that you are looking for does not show up on any of the menus in the section above and you have tried all three USB controller options, boot up your VM three seperate times. Once using the USB 1.1 controller, another using the USB 2.0 controller, etc. Leave the VM running for at least 5 minutes after startup. Sometimes Windows will autodetect the device for you. Be sure you filter any devices that are not a keyboard or a mouse so they do not start up at boot. This ensures that Windows will detect the device at start-up.

Access a guest server[編輯 | 編輯原始碼]

To access Apache server on a Virtual Machine from the host machine only, simply execute the following lines on the host:

$ VBoxManage setextradata GuestName "VBoxInternal/Devices/pcnet/0/LUN#0/Config/Apache/HostPort" 8888
$ VBoxManage setextradata GuestName "VBoxInternal/Devices/pcnet/0/LUN#0/Config/Apache/GuestPort" 80
$ VBoxManage setextradata GuestName "VBoxInternal/Devices/pcnet/0/LUN#0/Config/Apache/Protocol" TCP

where 8888 is the port the host should listen on and 80 is the port the VM will send Apache's signal on.

To use a port lower than 1024 on the host machine, changes need to be made to the firewall on that host machine. This can also be set up to work with SSH or any other services by changing "Apache" to the corresponding service and ports.

注意： pcnet refers to the network card of the VM. If you use an Intel card in your VM settings, change pcnet to e1000.

To communicate between the VirtualBox guest and host using ssh, the server port must be forwarded under Settings > Network. When connecting from the client/host, connect to the IP address of the client/host machine, as opposed to the connection of the other machine. This is because the connection will be made over a virtual adapter.

D3D acceleration in Windows guests[編輯 | 編輯原始碼]

Recent versions of Virtualbox have support for accelerating OpenGL inside guests. This can be enabled with a simple checkbox in the machine's settings, right below where video ram is set, and installing the Virtualbox guest additions. However, most Windows games use Direct3D (part of DirectX), not OpenGL, and are thus not helped by this method. However, it is possible to gain accelerated Direct3D in your Windows guests by borrowing the d3d libraries from Wine, which translate d3d calls into OpenGL, which is then accelerated. These libraries are now part of Virtualbox guest additions software.

After enabling OpenGL acceleration as described above, reboot the guest into safe mode (press F8 before the Windows screen appears but after the Virtualbox screen disappears), and install Virtualbox guest additions, during install enable checkbox "Direct3D support". Reboot back to normal mode and you should have accelerated Direct3D.

注意：

This hack may or may not work for some games depending on what hardware checks they make and what parts of D3D they use.
This was tested on Windows XP, 7 and 8.1. If method does not work on your Windows version please add data here.

VirtualBox on a USB key[編輯 | 編輯原始碼]

When using VirtualBox on a USB key, for example to start an installed machine with an ISO image, you will manually have to create VDMKs from the existing drives. However, once the new VMDKs are saved and you move on to another machine, you may experience problems launching an appropriate machine again. To get rid of this issue, you can use the following script to launch VirtualBox. This script will clean up and unregister old VMDK files and it will create new, proper VMDKs for you:

本文或本章節的語言、語法或風格需要改進。參考：Help:Style

原因：The following script parses the output of ls, which is very brittle and known to break.（在Talk:VirtualBox討論）

#!/bin/sh
# Erase old VMDK entries
rm ~/.VirtualBox/*.vmdk

# Clean up VBox-Registry
sed -i '/sd/d' ~/.VirtualBox/VirtualBox.xml

# Remove old harddisks from existing machines
find ~/.VirtualBox/Machines -name \*.xml | while read -r file; do
  line=$(grep -e "type\=\"HardDisk\"" -n "$file" | cut -d ':' -f 1)
  if [ -n "$line" ]; then
    sed -i "${line}"d "$file"
    sed -i "${line}"d "$file"
    sed -i "${line}"d "$file"
  fi
  sed -i "/rg/d" "$file"
done

# Delete prev-files created by VirtualBox
find  ~/.VirtualBox/Machines -name \*-prev -exec rm '{}' \;

# Recreate VMDKs
ls -l /dev/disk/by-uuid | cut -d ' ' -f 9,11 | while read -r ln; do
  if [ -n "$ln" ]; then
    uuid=$(echo "$ln" | cut -d ' ' -f 1)
    device=$(echo "$ln" | cut -d ' ' -f 2 | cut -d '/' -f 3 | cut -b 1-3)

    # determine whether drive is mounted already
    checkstr1=$(mount | grep "$uuid")
    checkstr2=$(mount | grep "$device")
    checkstr3=$(ls ~/.VirtualBox/*.vmdk | grep "$device")
    if [ -z "$checkstr1" ] && [ -z "$checkstr2" ] && [ -z "$checkstr3" ]; then
      VBoxManage internalcommands createrawvmdk -filename ~/.VirtualBox/"$device".vmdk -rawdisk /dev/"$device" -register
    fi
  fi
done

# Start VirtualBox
VirtualBox

Note that your user has to be added to the "disk" group to create VMDKs out of existing drives.

Run a native Arch Linux installation inside VirtualBox[編輯 | 編輯原始碼]

If you have a dual boot system between Arch Linux and another operating system, it can become tedious to switch back and forth if you need to work in both. You may also experience performance or compatibility issues when using a virtual machine, which can impact your ability to do certain tasks.

This guide will let you reuse, in a virtual machine, your native Arch Linux installation when you are running your second operating system. This way, you keep the ability to run each operating system natively, but have the option to run your Arch Linux installation inside a virtual machine.

Make sure you have a persistent naming scheme[編輯 | 編輯原始碼]

Depending on your hard drive setup, device files representing your hard drives may appear differently when you will run your Arch Linux installation natively or in virtual machine. This problem occurs when using FakeRAID for example. The fake RAID device will be mapped in /dev/mapper/ when you run your GNU/Linux distribution natively, while the devices are still accessible separately. However, in your virtual machine, it can appear without any mapping in /dev/sdaX for example, because the drivers controlling the fake RAID in your host operating system (e.g. Windows) are abstracting the fake RAID device.

To circumvent this problem, we will need to use an addressing scheme that is persistent to both systems. This can be achieved using UUIDs. Make sure your boot loader and fstab file is using UUIDs, otherwise fix this issue. Read fstab and Persistent block device naming.

警吿：

Make sure your host partition is only accessible in read only from your Arch Linux virtual machine, this will avoid risk of corruptions if you were to corrupt that host partition by writing on it due to lack of attention.
You should NEVER allow VirtualBox to boot from the entry of your second operating system, which, as a reminder, is used as the host for this virtual machine! Take thus a special care especially if your default boot loader/boot manager entry is your other operating system. Give a more important timeout or put it below in the order of preferences.

Make sure your mkinitcpio image is correct[編輯 | 編輯原始碼]

Make sure your mkinitcpio configuration uses the HOOK block:

/etc/mkinitcpio.conf

...
HOOKS="base udev autodetect modconf block filesystems keyboard fsck"
...

If it is not present, add it and regenerate the initramfs.

Create a VM configuration to boot from the physical drive[編輯 | 編輯原始碼]

Create a raw disk .vmdk image[編輯 | 編輯原始碼]

Now, we need to create a new virtual machine which will use a RAW disk as virtual drive, for that we will use a ~ 1Kio VMDK file which will be mapped to a physical disk. Unfortunately, VirtualBox does not have this option in the GUI, so we will have to use the console and use an internal command of VBoxManage.

Boot the host which will use the Arch Linux virtual machine. The command will need to be adapted according to the host you have.

On a GNU/Linux host

There are 3 ways to achieve this: login as root, changing the access right of the device with chmod, adding your user to the disk group. The latter way is the more elegant, let us proceed that way:

# gpasswd -a your_user disk

Apply the new group settings with:

$ newgrp

Now, you can use the command:

$ VBoxManage internalcommands createrawvmdk -filename /path/to/file.vmdk -rawdisk /dev/sdb -register

Adapt the above command to your need, especially the path and filename of the VMDK location and the raw disk location to map which contain your Arch Linux installation.

On a Windows host

Open a command prompt must be run as administrator.

提示：On Windows, open your start menu/start screen, type cmd, and type Ctrl+Shift+Enter, this is a shortcut to execute the selected program with admin rights.

On Windows, as the disk filename convention is different from UNIX, use this command to determine what drives you have in your Windows system and their location:

# wmic diskdrive get name,size,model

Model                               Name                Size
WDC WD40EZRX-00SPEB0 ATA Device     \\.\PHYSICALDRIVE1  4000783933440
KINGSTON SVP100S296G ATA Device     \\.\PHYSICALDRIVE0  96024821760
Hitachi HDT721010SLA360 ATA Device  \\.\PHYSICALDRIVE2  1000202273280
Innostor Ext. HDD USB Device        \\.\PHYSICALDRIVE3  1000202273280

In this example, as the Windows convention is \\.\PhysicalDriveX where X is a number from 0, \\.\PHYSICALDRIVE1 could be analogous to /dev/sdb from the Linux disk terminology.

To use the VBoxManage command on Windows, you can either, change the current directory to your VirtualBox installation folder first with cd C:\Program Files\Oracle\VirtualBox\

# .\VBoxManage.exe internalcommands createrawvmdk -filename C:\file.vmdk -rawdisk \\.\PHYSICALDRIVE1

or use the absolute path name:

# "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" internalcommands createrawvmdk -filename C:\file.vmdk -rawdisk \\.\PHYSICALDRIVE1

On another OS host

There are other limitations regarding the aforementioned command when used in other operating systems like OS X, please thus read carefully the manual page, if you are concerned.

Create the VM configuration file[編輯 | 編輯原始碼]

注意：

To make use of the VBoxManage command on Windows, you need to change the current directory to your VirtualBox installation folder first: cd C:\Program Files\Oracle\VirtualBox\.
Windows makes use of backslashes instead of slashes, please replace all slashes "/" occurrences by backslashes "\" in the commands that follow when you will use them.

After, we need to create a new machine (replace the VM_name to your convenience) and register it with VirtualBox.

$ VBoxManage createvm -name VM_name -register

Then, the newly raw disk needs to be attached to the machine. This will depend if your computer or actually the root of your native Arch Linux installation is on an IDE or a SATA controller.

If you need an IDE controller:

$ VBoxManage storagectl VM_name --name "IDE Controller" --add ide
$ VBoxManage storageattach VM_name --storagectl "IDE Controller" --port 0 --device 0 --type hdd --medium /path/to/file.vmdk

otherwise:

$ VBoxManage storagectl VM_name --name "SATA Controller" --add sata
$ VBoxManage storageattach VM_name --storagectl "SATA Controller" --port 0 --device 0 --type hdd --medium /path/to/file.vmdk

While you continue using the CLI, it is recommended to use the VirtualBox GUI, to personalise the virtual machine configuration. Indeed, you must specify its hardware configuration as close as possible as your native machine: turning on the 3D acceleration, increasing video memory, setting the network interface, etc.

Finally, you may want to seamlessly integrate your Arch Linux with your host operating system and allow copy pasting between both OSes. Please refer to VirtualBox/Install Arch Linux as a guest#Install the Guest Additions for that, since this Arch Linux virtual machine is basically an Arch Linux guest.

警吿： For Xorg to work in natively and in the virtual machine, since obviously it will be using different drivers, it is best if there is no /etc/X11/xorg.conf, so Xorg will pick up everything it needs on the fly. However, if you really do need your own Xorg configuration, maybe is it worth to set your default systemd target to multi-user.target with systemctl isolate graphical.target as root (more details at Systemd#Targets and Systemd#Change current target). In that way, the graphical interface is disabled (i.e. Xorg is not launched) and after you logged in, you can startx} manually with a custom xorg.conf.

Install a native Arch Linux system from VirtualBox[編輯 | 編輯原始碼]

In some cases it may be useful to install a native Arch Linux system while running another operating system: one way to accomplish this is to perform the installation through VirtualBox on a raw disk. If the existing operating system is Linux based, you may want to consider following Install from existing Linux instead.

This scenario is very similar to #Run a native Arch Linux installation inside VirtualBox, but will follow those steps in a different order: start by #Create a raw disk .vmdk image, then #Create the VM configuration file.

Now, you should have a working VM configuration whose virtual VMDK disk is tied to a real disk. The installation process is exactly the same as the steps described in VirtualBox/Install Arch Linux as a guest, but #Make sure you have a persistent naming scheme and #Make sure your mkinitcpio image is correct.

警吿：

For BIOS systems and MBR disks, do not install a bootloader inside your virtual machine, this will not work since the MBR is not linked to the MBR of your real machine and your virtual disk is only mapped to a real partition without the MBR.
For UEFI systems without CSM and GPT disks, the installation will not work at all since:

the ESP partition is not mapped to your virtual disk and Arch Linux requires to have the Linux kernel on it to boot as an EFI application (see EFISTUB for details);
and the efivars, if you are installing Arch Linux using the EFI mode brought by VirtualBox, are not the one of your real system: the bootmanager entries will hence not be registered.

This is why, it is recommended to create your partitions in a native installation first, otherwize the partitions will not be taken into consideration in your MBR/GPT partition table.

After completing the installation, boot your computer natively with an GNU/Linux installation media (whether it be Arch Linux or not), chroot into your installed Arch Linux installation and install and configure a bootloader.

Install MacOS guest[編輯 | 編輯原始碼]

Before starting the VM, run the following commands on the host machine [3]:

$ VBoxManage modifyvm "MyMacVM" --cpuid-set 00000001 000106e5 00100800 0098e3fd bfebfbff
$ VBoxManage setextradata "MyMacVM" "VBoxInternal/Devices/efi/0/Config/DmiSystemProduct" "iMac11,3"
$ VBoxManage setextradata "MyMacVM" "VBoxInternal/Devices/efi/0/Config/DmiSystemVersion" "1.0"
$ VBoxManage setextradata "MyMacVM" "VBoxInternal/Devices/efi/0/Config/DmiBoardProduct" "Iloveapple"
$ VBoxManage setextradata "MyMacVM" "VBoxInternal/Devices/smc/0/Config/DeviceKey" "ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc"
$ VBoxManage setextradata "MyMacVM" "VBoxInternal/Devices/smc/0/Config/GetKeyFromRealSMC" 1
$ VBoxManage setextradata "MyMacVM" VBoxInternal2/EfiGopMode 4

No keyboard/mouse input when attempting to install Mojave[編輯 | 編輯原始碼]

If you are attempting to install Mojave, after doing the aforementioned steps, the installer will load up but you might not be able to send keyboard or mouse input. The reason seems to be that Mojave no longer supports the USB 1.1 controllers and in order to fix the issue you need to emulating USB 3.0. To do that first install the VirtualBox Extension pack.

Then go to Machine > Settings > USB and select USB 3.0. Input should work from this point onwards.

UEFI interactive shell after restart[編輯 | 編輯原始碼]

If the installer is unable to properly format the bootable drive during installation and you end up in an UEFI shell, enter the following:

Type exit at the UEFI prompt
Select Boot Maintenance Manager
Select Boot From File

You will now be brought to couple of obscure PCI paths. The first one is the one that you just attempted to boot from and it did not work. The second (or third) one should be the one with the MacOS recovery partition that you need to load to continue the installation. Click the second Entry. If it is empty, press Esc to go back and select the third entry. Once you get one with folders click though the folders. It should be something like macOS Install Data > Locked Files > Boot Files > boot.efi. Once you click enter on the boot.efi you should boot into the MacOS installer and resume installation. Note that some of the subdirectories might be missing. Remember that you need to get to a boot.efi.[4]

Move a native Windows installation to a virtual machine[編輯 | 編輯原始碼]

If you want to migrate an existing native Windows installation to a virtual machine which will be used with VirtualBox on GNU/Linux, this use case is for you. This section only covers native Windows installation using the MSDOS/Intel partition scheme. Your Windows installation must reside on the first MBR partition for this operation to success. Operation for other partitions are available but have been untested (see #Known limitations for details).

警吿： If you are using an OEM version of Windows, this process is unauthorized by the end user license license. Indeed, the OEM license typically states the Windows install is tied with the hardware together. Transferring a Windows install to a virtual machine removes this link. Make thus sure you have a full Windows install or a volume license model before continuing. If you have a full Windows license but the latter is not coming in volume, nor as a special license for several PCs, this means you will have to remove the native installation after the transfer operation has been achieved.

A couple of tasks are required to be done inside your native Windows installation first, then on your GNU/Linux host.

Tasks on Windows[編輯 | 編輯原始碼]

The first three following points comes from this outdated VirtualBox wiki page, but are updated here.

Remove IDE/ATA controllers checks (Windows XP only): Windows memorize the IDE/ATA drive controllers it has been installed on and will not boot if it detects these have changed. The solution proposed by Microsoft is to reuse the same controller or use one of the same serial, which is impossible to achieve since we are using a Virtual Machine. MergeIDE, a German tool, developped upon another other solution proposed by Microsoft can be used. That solution basically consists in taking all IDE/ATA controller drivers supported by Windows XP from the initial driver archive (the location is hard coded, or specify it as the first argument to the .bat script), installing them and registering them with the regedit database.
Use the right type of Hardware Abstraction Layer (old 32 bits Windows versions): Microsoft ships 3 default versions: Hal.dll (Standard PC), Halacpi.dll (ACPI HAL) and Halaacpi.dll (ACPI HAL with IO APIC). Your Windows install could come installed with the first or the second version. In that way, please disable the Enable IO/APIC VirtualBox extended feature.
Disable any AGP device driver (only outdated Windows versions): If you have the files agp440.sys or intelppm.sys inside the C:\Windows\SYSTEM32\drivers\ directory, remove it. As VirtualBox uses a PCI virtual graphic card, this can cause problems when this AGP driver is used.
Create a Windows recovery disk: In the following steps, if things turn bad, you will need to repair your Windows installation. Make sure you have an install media at hand, or create one with Create a recovery disk from Vista SP1, Create a system repair disc on Windows 7 or Create a recovery drive on Windows 8.x).

Using Disk2vhd to clone Windows partition[編輯 | 編輯原始碼]

Boot into Windows, clean up the installation (with CCleaner for example), use disk2vhd tool to create a VHD image. Include a reserved system partition (if present) and the actual Windows partition (usually disk C:). The size of Disk2vhd-created image will be the sum of the actual files on the partition (used space), not the size of a whole partition. If all goes well, the image should just boot in a VM and you will not have to go through the hassle with MBR and Windows bootloader, as in the case of cloning an entire partition.

Tasks on GNU/Linux[編輯 | 編輯原始碼]

提示：Skip the partition-related parts if you created VHD image with Disk2vhd.

Reduce the native Windows partition size to the size Windows actually needs with ntfsresize available from ntfs-3g^包. The size you will specify will be the same size of the VDI that will be created in the next step. If this size is too low, you may break your Windows install and the latter might not boot at all.

Use the --no-action option first to run a test:

# ntfsresize --no-action --size 52Gi /dev/sda1

If only the previous test succeeded, execute this command again, but this time without the aforementioned test flag.

Install VirtualBox on your GNU/Linux host (see #Installation steps for Arch Linux hosts if your host is Arch Linux).

Create the Windows disk image from the beginning of the drive to the end of the first partition where is located your Windows installation. Copying from the beginning of the disk is necessary because the MBR space at the beginning of the drive needs to be on the virtual drive along with the Windows partition. In this example two following partitions sda2 and sda3will be later removed from the partition table and the MBR bootloader will be updated.

# sectnum=$(( $(cat /sys/block/sda/sda1/start) + $(cat /sys/block/sda/sda1/size) ))

Using cat /sys/block/sda/sda1/size will output the number of total sectors of the first partition of the disk sda. Adapt where necessary.

# dd if=/dev/sda bs=512 count=$sectnum | VBoxManage convertfromraw stdin windows.vdi $(( $sectnum * 512 ))

We need to display the size in byte, $(( $sectnum * 512 )) will convert the sector numbers to bytes.

Since you created your disk image as root, set the right ownership to the virtual disk image:
```
# chown your_user:your_group windows.vdi
```

Create your virtual machine configuration file and use the virtual disk created previously as the main virtual hard disk.

Try to boot your Windows VM, it may just work. First though remove and repair disks from the boot process as it may interfere (and likely will) booting into safe-mode.

Attempt to boot your Windows virtual machine in safe mode (press the F8 key before the Windows logo shows up)... if running into boot issues, read #Fix MBR and Microsoft bootloader. In safe-mode, drivers will be installed likely by the Windows plug-and-play detection mechanism view. Additionally, install the VirtualBox Guest Additions via the menu Devices > Insert Guest Additions CD image.... If a new disk dialog does not appear, navigate to the CD drive and start the installer manually.

You should finally have a working Windows virtual machine. Do not forget to read the #Known limitations.

Performance tip: according to VirtualBox manual, SATA controller has a better performance than IDE. If you cannot boot Windows off virtual SATA controller right away, it is probably due to the lack of SATA drivers. Attach virtual disk to IDE controller, create an empty SATA controller and boot the VM - Windows should automatically install SATA drivers for the controller. You can then shutdown VM, detach virtual disk from IDE controller and attach it to SATA controller instead.

Fix MBR and Microsoft bootloader[編輯 | 編輯原始碼]

If your Windows virtual machine refuses to boot, you may need to apply the following modifications to your virtual machine.

Boot a GNU/Live live distribution inside your virtual machine before Windows starts up.

Remove other partitions entries from the virtual disk MBR. Indeed, since we copied the MBR and only the Windows partition, the entries of the other partitions are still present in the MBR, but the partitions are not available anymore. Use fdisk to achieve this for example.

fdisk ''/dev/sda''
Command (m for help): a
Partition number (''1-3'', default ''3''): ''1''

Write the updated partition table to the disk (this will recreate the MBR) using the m command inside fdisk.

Use testdisk^包 (see here for details) to add a generic MBR:

# testdisk > Disk /dev/sda... > [Proceed] >  [Intel] Intel/PC partition > [MBR Code] Write TestDisk MBR to first sector > Write a new copy of MBR code to first sector? (Y/n) > Y > Write a new copy of MBR code, confirm? (Y/N) > A new copy of MBR code has been written. You have to reboot for the change to take effect. > [OK]

With the new MBR and updated partition table, your Windows virtual machine should be able to boot. If you are still encountering issues, boot your Windows recovery disk from on of the previous step, and inside your Windows RE environment, execute the commands described here.

Known limitations[編輯 | 編輯原始碼]

Your virtual machine can sometimes hang and overrun your RAM, this can be caused by conflicting drivers still installed inside your Windows virtual machine. Good luck to find them!
Additional software expecting a given driver beneath may either not be disabled/uninstalled or needs to be uninstalled first as the drivers that are no longer available.
Your Windows installation must reside on the first partition for the above process to work. If this requirement is not met, the process might be achieved too, but this had not been tested. This will require either copying the MBR and editing in hexadecimal see VirtualBox: booting cloned disk or will require to fix the partition table manually or by repairing Windows with the recovery disk you created in a previous step. Let us consider our Windows installation on the second partition; we will copy the MBR, then the second partition where to the disk image. VBoxManage convertfromraw needs the total number of bytes that will be written: calculated thanks to the size of the MBR (the start of the first partition) plus the size of the second (Windows) partition. { dd if=/dev/sda bs=512 count=$(cat /sys/block/sda/sda1/start) ; dd if=/dev/sda2 bs=512 count=$(cat /sys/block/sda/sda2/size) ; } | VBoxManage convertfromraw stdin windows.vdi $(( ($(cat /sys/block/sda/sda1/start) + $(cat /sys/block/sda/sda2/size)) * 512 )).

Run a native Windows installation inside VirtualBox[編輯 | 編輯原始碼]

注意： The technique outlined in this section only applies to UEFI systems.

In some cases, it is useful to be able to dual boot with Windows and access the partition in a virtual machine. This process is significantly different from #Move a native Windows installation to a virtual machine in several ways:

The Windows partition is not copied to a virtual disk image. Instead, a raw VMDK file is created;
Changes in the VM will be mirrored in the partition, and vice versa;
OEM licenses should still be satisfied, since the Windows partition still boots directly on the hardware.

警吿： Some of the commands used here can corrupt either the Windows partition, the Arch Linux partition, or both. Use extreme caution when executing commands, and double check that they are being run in the correct shell. It would be a good idea to have a backup of the entire drive ready before beginning this process.

注意： Before proceeding be sure to have access to a Windows installation media (such as the Windows 11 ISO).

Creating the virtual machine[編輯 | 編輯原始碼]

A VirtualBox virtual machine must be manually created. As of now do not add any storage device any disk to the virtual machine, it will be done manually later.

Configure the virtual machine with the following settings (settings panel can be opened by clicking the "Settings" button in the main toolbar):

View: System:
- Tab: Motherboard:
  - mark Enable I/O APIC;
  - mark Enable EFI;
  - mark Hardware Clock in UTC Time if is your case.
- Tab: Processor:
  - mark Enable PAE/NX;
  - mark Enable VT-x/AMD-V;
- Tab: Acceleration:
  - Chose the paravirtualization interface Hyper-V from the drop down menu;
  - mark Enable Nested Paging.

Optionally you can enable also the following settings:

View: Display
- Tab: Screen
  - mark Enable 3D Acceleration. Note that it could cause glitches.

注意： The Hyper-V setting is not required in order for the system to operate correctly, but it may help avoid licensing issues.

Creating virtual machine disks[編輯 | 編輯原始碼]

To access the Windows partitions, create a raw VMDK file pointing to the relevant Windows partitions (root privileges are required to read disk partition table):

# VBoxManage internalcommands createrawvmdk -filename VM_FOLDER/windows.vmdk -rawdisk WINDOWS_DISK -partitions WINDOWS_RESERVED_PARTITION_NUMBER,WINDOWS_BASIC_DATA_PARTITION_NUMBER -relative

Replace capitalized placeholder strings as follow:

VM_FOLDER with the path of the virtual machine folder (usually a subfolder of ~/VirtualBox VMs;
WINDOWS_DISK must be replaced with the block device containing all the Windows partitions (e.g.: /dev/sda or /dev/nvme0n1);
WINDOWS_RESERVED_PARTITION_NUMBER must be replaced with the number of partition labeled "Microsoft reserved partition" (e.g.: if the partition is the /dev/sda2 the number will be 2);
WINDOWS_PARTITION_NUMBER must be replaced with the partition containing the Windows installation (e.g.: if the partition is the /dev/sda3 the number will be 3);

Example:

$ sudo VBoxManage internalcommands createrawvmdk -filename "/home/user/VirtualBox VMs/windows.vmdk" -rawdisk /dev/nvme0n1 -partitions 2,3 -relative

The command will also create an extra file inside the virtual machine folder, "windows-pt.vmdk", that will be just ignored.

注意： windows.vmdk must be re-created if the partition table is changed.

提示：

Partition numbers can be found also by running this command and looking at the MIN column:

lsblk --output NAME,PARTLABEL,FSTYPE,MAJ:MIN,SIZE

NAME        PARTLABEL                    FSTYPE UUID                                 MAJ:MIN   SIZE
nvme0n1                                                                              259:0   931,5G
├─nvme0n1p1 EFI system partition         vfat   90DC-A6B3                            259:1     100M
├─nvme0n1p2 Microsoft reserved partition                                             259:2      16M
├─nvme0n1p3 Basic data partition         ntfs   D2A2A104A2A0EE63                     259:3     200G
...

Now change the virtual disk owner to give access the user and group running VirtualBox.

# chown VIRTUALBOX_RUNNING_USER:VIRTUALBOX_RUNNING_GROUP VM_FOLDER/windows.vmdk VM_FOLDER/windows-pt.vmdk

Replace VIRTUALBOX_RUNNING_USER and VIRTUALBOX_RUNNING_GROUP with the user and the group that will run VirtualBox, which most likely will be your user.

Allowing VirtualBox to read physical partitions[編輯 | 編輯原始碼]

VirtualBox must have raw disk access in order to run a Windows partition. Normally, this would require VirtualBox to be run with full root privileges, but more elegant options are available.

Higher security option: using a dedicated group for the Windows partitions[編輯 | 編輯原始碼]

Here udev is configured to restrict the access to partitions Windows partitions to the vboxusers group, and then the user running VirtualBox is added to the group.

Assigning the disks to the vboxusers group can be done automatically by creating the following file:

/etc/udev/rules.d/99-vbox.rules

#
# Rules to give VirtualBox users raw access to Windows partitions
#

# Microsoft Reserved partition
SUBSYSTEM=="block", ENV{ID_PART_ENTRY_TYPE}=="e3c9e316-0b5c-4db8-817d-f92df00215ae", GROUP="vboxusers"

# Windows partition
SUBSYSTEM=="block", ENV{ID_PART_ENTRY_TYPE}=="ebd0a0a2-b9e5-4433-87c0-68b6b72699c7", GROUP="vboxusers"

#
# Rules to give VirtualBox users raw access to Windows disk
#

# sdb
ENV{ID_PART_TABLE_UUID}=="WINDOWS_DISK_ID_PART_TABLE_UUID", GROUP="vboxusers"

WINDOWS_DISK_ID_PART_TABLE_UUID must be replaced with the value obtained from udevadm info /dev/WINDOWS_DISK (replace WINDOWS_DISK with the disk containing Windows partitions). The UUIDs in these rules correspond to particular GPT partition types while the other capitalized strings are supposed to be written that way, so those does not have to be replaced.

Then tge user running VirtualBox must be added to the vboxusers group. This can be done with the following command:

# usermod -aG vboxusers VIRTUALBOX_RUNNING_USER

Replace VIRTUALBOX_RUNNING_USER and with the user that will run VirtualBox, which most likely will be your user.

Lower security option: using 'disk' group[編輯 | 編輯原始碼]

To be able to add the vmdk file in Virtualbox Virtual Media Manager without running VirtualBox as root, the user running VirtualBox need to be in vboxusers and disk groups.

# usermod -aG disk,vboxusers VIRTUALBOX_RUNNING_USER

Replace VIRTUALBOX_RUNNING_USER and with the user that will run VirtualBox, which most likely will be your user.

警吿： Be aware of the potential security implications of this edit, as you are giving your user account full read-write access all storage devices owned by the disk group.

Setting up a separate ESP partition[編輯 | 編輯原始碼]

Virtual machine EFI boot files will refer to different disks than the ones in the physical EFI partition, so VirtualBox must not make use of the latter but instead of a EFI partition inside a dedicated virtual disk. This disk can be created with the following command:

$ VBoxManage createmedium disk --filename VM_FOLDER/esp.vmdk --size 512 --format VMDK

Replace VM_FOLDER with the folder containing the virtual machine being built.

Adding virtual disks to the virtual machine[編輯 | 編輯原始碼]

Configure the virtual machine storage devices (Settings panel - Storage) as following:

add esp.vmdk as a SATA hard disk attached to the "SATA Port 0";
add windows.vmdk as a SATA hard disk attached to the "SATA Port 1";
mount Windows installation iso into the virtual optical drive .

注意：

for adding a SATA hard disk use the second button on the right of the "Controller: SATA" device;
the virtual optical drive should already be there as "Optical Drive".

Configuring the virtual UEFI firmware and creating Windows boot files[編輯 | 編輯原始碼]

Now start the virtual machine and it should automatically boot from Windows installation disk. After choosing the installation locales click on the "Repair your computer" link, then choose "Troubleshoot" and then " Command Prompt" in order to launch a command prompt from the install media.

Enter the following commands to create a new GPT table in the esp.vmdk disk and install the Windows boot loader onto it using configuration from the existing Windows partition:

Open Diskpart:

X:\ diskpart

List all disks identified by the system:

DISKPART> list disk

The esp.vmkd disk should be labeled as disk 0 due to the fact that was attached to the SATA port 0, ~512MB in size and unpartitioned. The windows.vmdk disk should be labeled as disk 1; note that the column "Size" displays the disk size, not the partition one.

Select the esp.vmdk disk:

DISKPART> select Disk 0

Now create a GPT partition table, a UEFI partition big as the whole disk and assign to it a label and drive letter:

DISKPART> clean
DISKPART> convert gpt
DISKPART> create partition efi size=500
DISKPART> format quick fs=fat32 label="System"
DISKPART> assign letter="S"

Check that the partiton has been correctly created:

DISKPART> list volume

Our newly created UEFI boot partition will be labeled as "SYSTEM" with letter as "S".

Take note of the Windows installation volume letter because it will be used in next steps. Usually its D but it could be different: you can infer it from its label and its size. The size is the same as the Windows installation partition size on your physical hard disk.

Exit diskpart:

DISKPART> exit

Install the Windows boot loader into the EFI partition.

D:
cd Windows\System32
bcdboot D:\Windows /s S: /f UEFI

Now close the command prompt, power off the virtual machine and detach the Windows installation disk (from "Preferences > Devices" remove the optical disk). The virtual machine should now boot from the newly installed boot partition and load the physical Windows installation. It may show some UEFI related errors on the top of the virtual machine window and the first boot may take a while, but if everything has been done correctly you will be able to access your windows installation.

Run an entire physical disk in Virtualbox[編輯 | 編輯原始碼]

注意： You may refer to Virtualbox official documentation 9.8.1. Using a Raw Host Hard Disk From a Guest.

This works the same way as #Run a native Windows installation inside VirtualBox but the vmdk will contain the entire disk rather than one partion, and so you will not need to create a separate ESP or MBR partition as the one in the physical disk will be used.

Create the raw disk:

# VBoxManage internalcommands createrawvmdk -filename /path/to/file.vmdk -rawdisk /dev/sdb

Then follow the same method as in #Run a native Windows installation inside VirtualBox for the configuration and virtual disk attachement.

Set guest starting resolution[編輯 | 編輯原始碼]

You can change the BIOS/UEFI booting resolution using VBoxManage tool. For example:

$ VBoxManage setextradata "Your Virtual Machine Name" "VBoxInternal2/EfiGraphicsResolution" "2560x1440"

Recommended resolutions are 1280x720, 1920x1080, 2048x1080, 2560x1440, 3840x2160, 1280x800, 1280x1024, 1440x900, 1600x900.

SSH from host to guest[編輯 | 編輯原始碼]

The network tab of the virtual machine settings contains, in "Advanced", a tool to create port forwarding. It is possible to use it to forward the Guest ssh port 22 to a Host port, e.g. 3022 :

user@host$ ssh -p 3022 $USER@localhost

will establish a connection from Host to Guest.

SSHFS as alternative to the shared folder[編輯 | 編輯原始碼]

Using this port forwarding and sshfs, it is straightforward to mount the Guest filesystem onto the Host one:

user@host$ sshfs -p 3022 $USER@localhost:$HOME ~/shared_folder

and then transfer files between both.

故障排除[編輯 | 編輯原始碼]

鼠標鍵盤都鎖死在虛擬機裡了[編輯 | 編輯原始碼]

這是因為你的虛擬機捕獲了鍵盤與鼠標的輸入。只要按下右 Ctrl 鍵即可讓輸入焦點回到宿主系統。

如果想要不按切換鍵就能讓鼠標在宿主機與虛擬機之間無縫切換，這需要安裝客户機插件。如果你的虛擬機系統是 Arch Linux，可以參閱前面的章節：#安裝客體機插件。其他系統請參閱 VirtualBox 的官方幫助文檔。

無法新建 64 位虛擬機[編輯 | 編輯原始碼]

如果新建虛擬機時看不到 64 位系統選項，這需要確認你的 CPU 是否支持虛擬化技術（通常稱作 VT-x），並且還要在 BIOS 中啟用。

如果你的宿主系統是 Windows，那麼你得禁用 Hyper-V 功能。因為 Hyper-V 會妨礙 VirtualBox 使用 VT-x。[5]

VirtualBox 圖形管理界面和主機 GTK 主題樣式不匹配[編輯 | 編輯原始碼]

VirtualBox 的 GUI 是基於 Qt 實現的。為了修改這類應用的外觀，見 Uniform look for Qt and GTK applications。

無法向虛擬機鍵入 Ctrl+Alt+Fn[編輯 | 編輯原始碼]

如果你在虛擬機安裝了某個 Linux 發行版，有時會需要按 Ctrl+Alt+F2 進入它的 TTY 界面，或者按 Ctrl+Alt+Backspace 來退出 X 會話。如果你的宿主系統也是 Linux，這些組合鍵默認會首先被宿主系統捕獲。正確的做法是按 Host Key（默認是右 Ctrl）加 F2 來向虛擬機鍵入 Ctrl+Alt+F2。

USB 功能不可用[編輯 | 編輯原始碼]

在宿主系統裏使用虛擬機的用户需要加入到 vboxusers 用户組。如果想要支持 USB 2 設備，還要安裝擴展包。此後在虛擬機的設置裡即可開啟 USB 2 支持，並且通過過濾規則來允許客體系統訪問指定的 USB 設備。

如果用 root 身份運行 VBoxManage list usbhost 命令也沒有列出任何 USB 設備，需要確認一下 /etc/udev/rules.d/ 目錄裡沒有遺留的 VirtualBox 4.x 的 udev 規則。VirtualBox 5.0 起會把 udev 規則文件安裝到 /usr/lib/udev/rules.d/ 目錄。用 pacman -Qo /usr/lib/udev/rules.d/60-vboxdrv.rules 命令可以查看這些 udev 文件是否已經過期。

有時某些舊 Linux 宿主系統無法自動檢測到 USB 子系統，就會出現這個錯誤：Could not load the Host USB Proxy service: VERR_NOT_FOUND。或者可能讓宿主機也識別不了 USB 磁盤，哪怕用户已經加入了 vboxusers 用户組。出現這類問題的原因是 VirtualBox 從 3.0.8 版本開始，從 usbfs 轉向使用 sysfs。如果宿主系統不支持這一改動，你可以在 shell 的啟動腳本（舉例：如果在用 bash 的話，就修改 ~/.bashrc 文件）裡聲明這一環境變量，讓 VirtualBox 回退到舊的行為：

~/.bashrc

export VBOX_USB=usbfs

然後確保這行代碼對環境變量的修改生效：重新登錄，手動加載該文件，啟動一個新 shell 會話，或者乾脆重啟。

另外，還應確保用户加入到了 storage 用户組。

USB 調製解調器在宿主系統不可用[編輯 | 編輯原始碼]

如果你的客體系統正在使用 USB 調製解調器，kill 掉虛擬機進程可能會造成它在宿主系統裏不可用。殺掉並重啟餘下的 VBoxSVC 進程應該可以解決這一問題。

虛擬機啟動時宿主系統卡死[編輯 | 編輯原始碼]

一般來説，這類問題都是在 VirtualBox 或 Linux 內核版本更新之後初次出現。降級回到前一個版本就有可能解決問題。

模擬信號麥克風不可用[編輯 | 編輯原始碼]

如果從模擬信號麥克風輸入的音頻信號在宿主系統可用，但在客體系統裡不可用，可以試試在宿主系統上安裝 PulseAudio 之類的音頻伺服器試試看。

如果裝了 PulseAudio 之後麥克風還是不能用，在菜單項 VirtualBox > Machine > Settings > Audio 裡把 Host Audio Driver 的值改成 ALSA Audio Driver 也許有用。

轉換得來的 ISO 文件出現問題[編輯 | 編輯原始碼]

有些鏡像文件格式無法可靠地轉換到 ISO 格式。例如：ccd2iso^包在轉換時會忽略 .ccd 和 .sub 文件裡的信息，最終產出的 ISO 鏡像裡的文件就可能受損。

為了避免這種情況，可以使用 CDemu 或類似軟件來在 Linux 客體系統裡掛載光盤鏡像。

Host-only 網卡創建失敗[編輯 | 編輯原始碼]

確保所需的內核模塊都已成功加載。詳見 #加載 VirtualBox 內核模塊。

如果還是不幸，點擊文件 > 主機網絡管理器 點擊創建進行手動創建。

插入模塊失敗[編輯 | 編輯原始碼]

如果你在加載模塊時遇到如下錯誤信息：

Failed to insert 'vboxdrv': Required key not available

將模塊簽名，或者在內核配置中禁用 CONFIG_MODULE_SIG_FORCE。

VBOX_E_INVALID_OBJECT_STATE (0x80BB0007)[編輯 | 編輯原始碼]

虛擬機不能平滑退出，就可能出現這個錯誤。試試下面這個命令：

$ VBoxManage controlvm virtual_machine_name poweroff

NS_ERROR_FAILURE 且菜單項缺失[編輯 | 編輯原始碼]

可能是安裝了 virtualbox-ext-oracle^AUR，但是沒有和最新的 virtualbox 版本同步更新。

還可能是創建虛擬機時選擇了 QCOW/QCOW2/QED 虛擬盤格式，有時就會出現這個錯誤。

如果初次啟動虛擬機時遇到下面的錯誤消息：

Failed to open a session for the virtual machine debian.
Could not open the medium '/home/.../VirtualBox VMs/debian/debian.qcow'.
QCow: Reading the L1 table for image '/home/.../VirtualBox VMs/debian/debian.qcow' failed (VERR_EOF).
VD: error VERR_EOF opening image file '/home/.../VirtualBox VMs/debian/debian.qcow' (VERR_EOF).

Result Code: 
NS_ERROR_FAILURE (0x80004005)
Component: 
Medium

退出 VirtualBox，把新建虛擬機的相關文件都刪除，並且在 VirtualBox 的配置文件中找到 MachineRegistry 元素，從這裏刪除你所創建的格式錯誤的虛擬機（一般是其最後一個子元素）：

~/.config/VirtualBox/VirtualBox.xml

...
<MachineRegistry>
  <MachineEntry uuid="{00000000-0000-0000-0000-000000000000}" src="/home/void/VirtualBox VMs/debian/debian.vbox"/>
  <MachineEntry uuid="{00000000-0000-0000-0000-000000000000}" src="/home/void/VirtualBox VMs/ubuntu/ubuntu.vbox"/>
  <MachineEntry uuid="{00000000-0000-0000-0000-000000000000}" src="/home/void/VirtualBox VMs/lastvmcausingproblems/lastvmcausingproblems.qcow"/>
</MachineRegistry>
...

缺少硬件虛擬化導致 OpenBSD 不穩定[編輯 | 編輯原始碼]

據稱在其他的虛擬機平台上，OpenBSD 可以不依賴虛擬化指令集（VT-X，AMD-V）正常運行，VirtualBox 上的 OpenBSD 則不然。具體現象是出現大量的分段錯誤（segfault）。解決辦法是在啟動虛擬機時加上 -norawr0 參數。例如：

$ VBoxSDL -norawr0 -vm name_of_OpenBSD_VM

Windows: "The specified path does not exist. Check the path and then try again."[編輯 | 編輯原始碼]

當在 Windows 客體系統裡運行位於共享目錄裡 .exe 程序，而這一程序又需要管理員權限時，就可能出現這一錯誤信息。[6]

一個解決辦法是把文件複製到虛擬硬盤上再運行。或者直接從UNC 路徑 (\\vboxsvr) 運行程序。詳見 [7]。

Windows 8.x 出現錯誤代碼 0x000000C4[編輯 | 編輯原始碼]

如果你在創建虛擬機時選擇了 Win 8 系統，但在啟動時還是遇到這一錯誤，可以嘗試啟用 CMPXCHG16B CPU 指令集。命令如下：

$ vboxmanage setextradata virtual_machine_name VBoxInternal/CPUM/CMPXCHG16B 1

Windows 8, 8.1 或 10 無法安裝、啟動或報錯 "ERR_DISK_FULL"[編輯 | 編輯原始碼]

修改虛擬機設置，在菜單項 Settings > Storage > Controller:SATA 裡勾選 "Use Host I/O Cache"。

WinXP: 顏色深度不得多於 16 位[編輯 | 編輯原始碼]

如果只顯示 16 位色，桌面圖標看起來會模糊 / 結塊。但是將色深調高時，系統可能會將桌面解像度限制得較低，或者根本不允許改變色身。解決辦法是在 Windows XP 虛擬機裡運行 regedit，並寫入這一項：

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services]
"ColorDepth"=dword:00000004

然後再去「桌面屬性」窗口裏修改色深。如果還是不見效，強制讓屏幕重繪（比如按 Host+f 進入全屏模式）試試。

Windows: 開啟3D加速後屏幕閃爍[編輯 | 編輯原始碼]

VirtualBox > 4.3.14 has a regression in which Windows guests with 3D acceleration flicker.

由於r120678補丁已經添加識別environment variable設置，可像如下啟動VirtualBox：

$ CR_RENDER_FORCE_PRESENT_MAIN_THREAD=0 VirtualBox

請確保沒有VirtualBox服務還在運行，並參考VirtualBox bug 13653。

Arch Linux guest虛擬機中沒有硬件3D加速[編輯 | 編輯原始碼]

virtualbox-guest-utils^包軟件包從5.2.16-2版開始不再包含文件VBoxEGL.so。這導致Arch Linux guest虛擬機沒有適當的3D加速。參見49752 FS# 49752。

要解決此問題，請應用位於FS#49752#comment152254的補丁集。需要對補丁集進行一些修復，才能使其適用於5.2.16-2版。

無法在Wayland上啟動VirtualBox：段錯誤[編輯 | 編輯原始碼]

此問題通常是由Wayland上的Qt引起的，請參見FS#58761。

最好的辦法是，在不影響其餘的Qt應用程式（通常在Wayland中正常運行）的情況下，取消在VirtualBox的desktop entry中的QT_QPA_PLATFORM environment variable設置。

請按照Desktop entries#Modify environment variables中的説明進行操作，並修改Exec：

Exec=VirtualBox ...

為

Exec=env -u QT_QPA_PLATFORM VirtualBox ...

如果不起作用，則可能需要將QT_QPA_PLATFORM設置為xcb：

Exec=env QT_QPA_PLATFORM=xcb VirtualBox ...

Windows: Screen flicker if 3D acceleration enabled[編輯 | 編輯原始碼]

VirtualBox > 4.3.14 has a regression in which Windows guests with 3D acceleration flicker. Since r120678 a patch has been implemented to recognize an environment variable setting, launch VirtualBox like this:

$ CR_RENDER_FORCE_PRESENT_MAIN_THREAD=0 VirtualBox

Make sure no VirtualBox services are still running. See VirtualBox bug 13653.

Cannot launch VirtualBox with Wayland: Segmentation fault[編輯 | 編輯原始碼]

This problem is caused by Qt detecting Wayland (e.g., if XDG_SESSION_TYPE=wayland), while VirtualBox does not work on Wayland yet. See FS#58761 and the upstream bug.

The Qt platform detection can be disabled and X11 forced over Wayland by setting the environment variable QT_QPA_PLATFORM=xcb.

To not affect the other Qt applications (which usually work well with Wayland), QT_QPA_PLATFORM=xcb should only be set when launching VirtualBox.

If starting through the desktop entry, follow the instructions in Desktop entries#Modify environment variables and change the lines starting with Exec=VirtualBox ... to Exec=env QT_QPA_PLATFORM=xcb VirtualBox .... If starting from the shell, alias (Bash#Aliases) virtualbox to env QT_QPA_PLATFORM=xcb virtualbox.

注意： If you have mouse or keyboard related issue in Wayland, you can try above setting too.

Random freezing in guests with intel graphics[編輯 | 編輯原始碼]

With Intel cpu and graphics, allocating more processors for the guest can lower render performance, thus cause random freezing. Allocating less or one processor can help.

Unable to view desktop in fullscreen mode[編輯 | 編輯原始碼]

Disable the Mini Toolbar by selecting Machine > Settings, select the User Interface tab and uncheck the Mini Toolbar checkbox

Random crashes with Windows 10 guest OS with Intel Tiger Lake chipset[編輯 | 編輯原始碼]

Disable split lock detection by adding split_lock_detect=off to the 內核參數s.

Details are described in VirtualBox's Ticket #20180.

Freeze during virtual machine startup with 11th generation Intel CPU[編輯 | 編輯原始碼]

If the message traps: Missing ENDBR and kernel BUG at arch/x86/kernel/traps.c appears in the journal you can try adding ibt=off as a 內核參數. Seems to be linked to FS#74891.

Failed to save the settings when enabling Secure Boot[編輯 | 編輯原始碼]

In VirtualBox 7.0.0, enabling Secure Boot in a virtual machine that was created in a previous VirtualBox version will fail with a nondescript error (FS#76234):

Failed to save the settings.

The solution is to click the Reset Keys to Default button right below the Enable Secure Boot checkbox.

參閱[編輯 | 編輯原始碼]