QEMU/KVM on ThinkPad X230T Laptop with Dual-boot: Difference between revisions

From WikiMLT
Line 13: Line 13:
</syntaxhighlight>
</syntaxhighlight>
== Setup the virtual machine ==
== Setup the virtual machine ==
The setup of the virtual machine is done via the <code>virt-manager</code> GUI. The first "special" thing according to my setup is that both operating systems are installed in UEFI mode, so the virtual machine should be UEFI too. In order to pass-through the physical SSD/HDD you need to do setup ad follow.<syntaxhighlight lang="xml" line="1">
The setup of the virtual machine is done via the <code>virt-manager</code> GUI. The first "special" thing according to my setup is that both operating systems are installed in UEFI mode, so the virtual machine should be UEFI too. In order to pass-through the physical SSD/HDD you need to do setup ad follow.
<syntaxhighlight lang="xml" line="1" highlight="5">
<disk type="block" device="disk">
<disk type="block" device="disk">
   <driver name="qemu" type="raw" cache="none" discard="unmap"/>
   <driver name="qemu" type="raw" cache="none" discard="unmap"/>
Line 20: Line 21:
   <address type="drive" controller="0" bus="0" target="0" unit="0"/>
   <address type="drive" controller="0" bus="0" target="0" unit="0"/>
</disk>
</disk>
</syntaxhighlight>In most how-to manuals they suggest to use <code><target dev="vdX" bus="virtio"/></code> ,  
</syntaxhighlight>
In most how-to manuals they suggest to use <code><target dev="vdX" bus="virtio"/></code>,


== References ==
== References ==

Revision as of 09:08, 13 August 2022

I was in need to ac­cess Win­dows 10 from Kali Lin­ux on my dual boot­ed Leno­vo ThinkPad X230T de­vice. So here are the things I've done to achieve that.

Test the Vir­tu­al­iza­tion Ca­pa­bil­i­ties of the Sys­tem

Check weath­er the sys­tem sup­ports vir­tu­al­iza­tion and it is en­abled via the BIOS. The fol­low­ing com­mand must re­turn at least 1:

egrep -c '(vmx|svm)' /proc/cpuinfo

In­stall QE­MU, KVM, LIB­VIRT

sudo apt install qemu-system-x86 libvirt-daemon libvirt-clients bridge-utils virt-manager virtinst libosinfo-bin ovmf remmina

To get rid of the pass­word di­a­logue – "Sys­tem pol­i­cy pre­vents man­age­ment of lo­cal vir­tu­al­iza­tion sys­tems" – I've added my Lin­ux user to the lib­virt group.

sudo usermod -aG libvirt $USER

Set­up the vir­tu­al ma­chine

The set­up of the vir­tu­al ma­chine is done via the virt-man­ag­er GUI. The first "spe­cial" thing ac­cord­ing to my set­up is that both op­er­at­ing sys­tems are in­stalled in UE­FI mode, so the vir­tu­al ma­chine should be UE­FI too. In or­der to pass-through the phys­i­cal SSD/HDD you need to do set­up ad fol­low.

<disk type="block" device="disk">
  <driver name="qemu" type="raw" cache="none" discard="unmap"/>
  <source dev="/dev/sda"/>
  <target dev="sda" bus="sata"/>
  <address type="drive" controller="0" bus="0" target="0" unit="0"/>
</disk>

In most how-to man­u­als they sug­gest to use <tar­get dev="vdX" bus="virtio"/>,

Ref­er­ences