Let me first say, that it does work for Linux guest. It doesn’t work on Windows guest because there is a know bug (/issue) with the default hardware layout – made of i440FX BIOS. VirtManager would not allow us to replace the settings, so we need to create the VM ourselves using XML. You can export your XML settings (of an existing VM) using the command
virsh dumpxml > /tmp/VM_NAME.xml
There are relevant fields there which you might want to save for later, like MAC addresses, network settings, and so on.
You can use this XML file to build your VM anew. Note that you will want to modify the network settings, the name and the UUID. Also – you will need a newer QEMU command (through the package qemu-system-x86), you can find in the Centos updates repository, . It has been providing me with /usr/bin/qemu-system-x86_64 command, which I am using, instead of the default qemu command used by default by VirtManager.
My Windows VM XML file (as a reference you can copy and use) is provided below. Major modifications are required to the hardware settings of the Windows VM – moving from PCI to PCIE, changing from IDE to SATA or VirtIO – and the provided XML gives a good reference of how this file should look like. This was taken from a machine tested to allow USB hot-add/remove via the method provided in my previous post.
SSH is a wonderful tool. One of its best features is the ability to pierce a firewall and let you go through it. If you’re using the dynamic port (-D as argument in command line openSSH), you actually get a SOCKS5 proxy over which you can transport all your desired data. This allows you the…
If you’ve ever tried to run modern versions of ssh, rsync, or other essential tools on an old Linux system, you know the pain. OpenSSL errors, OpenSSL support, or even library dependency hell. The Problem With Old Linux Systems Sometimes, you’re stuck with an old Linux system that you can’t update, and you need these…
Assuming your storage is capable of replication, a bunch of VMs could be happily replicated to an alternate location, where you can start them on will (and on crisis, most likely). This procedure, in theory, is rather simple. I have discovered that it is less so, especially if your system goes into testing once a…
This is a tricky one. I have had to waste a lot of time. The trick is to use 32bit browser (extract firefox into $HOME/firefox and run it from there. Details below), and a full JDK package from Sun. JRE is not good enough! I have a $HOME/bin/firefox32 script which looks like this: #!/bin/bash exec…
This blog is my extended memory, and as such, its task is to remind me things I tend to forget, saving me the time required to search them again. So here is another one of these things. The network settings syntax for RHEL8/OEL8 or any of their compatible systems, when you want to pass these…
