{"id":507,"date":"2022-09-09T13:14:56","date_gmt":"2022-09-09T20:14:56","guid":{"rendered":"https:\/\/sysprogs.com\/tutorials\/?p=507"},"modified":"2022-09-12T16:02:40","modified_gmt":"2022-09-12T23:02:40","slug":"visualkernel-qemu-integration","status":"publish","type":"post","link":"https:\/\/sysprogs.com\/VisualKernel\/documentation\/qemu\/","title":{"rendered":"VisualKernel QEMU Integration"},"content":{"rendered":"

VisualKernel is fully integrated with QEMU<\/a> – an open-source virtualization engine.<\/p>\n

QEMU has a very basic GUI compared to VMWare and VirtualBox, however it is the only virtualization platform that supports kernel debugging on hosts that have the Windows Hyper-V platform enabled. See the Acceleration<\/a> section for more details.<\/p>\n

Overview<\/h2>\n

You can manage the installed QEMU virtual machines via Tools->VisualKernel->Manage Qemu Virtual Machines<\/strong>:<\/p>\n

\"\"<\/a><\/p>\n

<\/a>Editing Settings<\/h2>\n

VisualKernel provides basic GUI for creating new QEMU virtual machines and editing their settings. You can customize the basic parameters (CPU\/RAM\/Storage) or tweak the command line directly:\"\"<\/a><\/p>\n

<\/a>Network Connection<\/h2>\n

Unlike VMWare and VirtualBox that require installing a dedicated network driver, Qemu works by virtualizing individual TCP connections. E.g. it can be configured to map port 22 on the guest to port 2222 on the Windows machine. You can then connect to the guest using the localhost:2222<\/strong> syntax.<\/p>\n

VisualKernel will normally manage the SSH ports automatically. Each time you start a VM, it will find an unused port on the Windows machine, allocate it for the QEMU VM and set the project-level $(SSHPort)<\/strong> variable to the allocated port number. You can override this behavior via the Network<\/strong> page of the QEMU VM settings:\"\"<\/a><\/p>\n

<\/a>Acceleration<\/h2>\n

In order to provide reasonable performance on Windows hosts, QEMU requires the Hyper-V platform to be enabled via Control Panel -> Add\/Remove Programs -> Turn Windows features on or off<\/strong>: \"\"<\/a><\/p>\n

Note that enabling the Hyper-V platform (also needed for WSL 2) forces any other virtualization software to use the Hyper-V engine (WHPX). As of September 2022, QEMU is the only engine that supports kernel debugging when using Hyper-V.<\/p>\n

<\/a>Snapshots<\/h2>\n

Like many other virtualization tools, QEMU supports creating snapshots of the virtual machines. You can use the Snapshots view under the VisualGDB QEMU Manager to create, restore or delete snapshots:\"\"<\/a><\/p>\n

<\/a>QEMU Monitor<\/h2>\n

QEMU provides a way to fine-tune the VM behavior by running commands via the QEMU monitor. You can find the comprehensive list of supported commands on this page<\/a>. You can use the “Launch QEMU Monitor” link in the bottom right part of the QEMU VM Manager window to automatically connect to the QEMU monitor and issue commands to it:<\/p>\n

\"\"<\/a><\/p>\n

<\/a>Troubleshooting<\/h2>\n

VisualKernel stores the QEMU VM configuration in the XML files with the .qvm<\/strong> extension. The directory with the .qvm<\/strong> file typically also contains the following files with the same name:<\/p>\n\n\n\n\n\n\n\n
File<\/td>\nMeaning<\/td>\n<\/tr>\n
<VM>.cmd<\/td>\nContains the exact command line used to launch the QEMU executable. You can run this file manually to reproduce various issues.<\/td>\n<\/tr>\n
<VM>.log<\/td>\nContains the debug output from QEMU.<\/td>\n<\/tr>\n
<VM>.run<\/td>\nContains the PID of the QEMU process and the port numbers allocated to SSH and other services.<\/td>\n<\/tr>\n
<VM>.snap<\/td>\nAssigns meaningful names and descriptions to the internal QEMU snapshot IDs.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

VisualKernel is fully integrated with QEMU – an open-source virtualization engine. QEMU has a very basic GUI compared to VMWare<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[57],"tags":[56,26],"_links":{"self":[{"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/posts\/507"}],"collection":[{"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/comments?post=507"}],"version-history":[{"count":8,"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/posts\/507\/revisions"}],"predecessor-version":[{"id":543,"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/posts\/507\/revisions\/543"}],"wp:attachment":[{"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/media?parent=507"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/categories?post=507"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sysprogs.com\/tutorials\/wp-json\/wp\/v2\/tags?post=507"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}