shpitz461

Yes please, looks like a useful tool. Just saw it mentioned by Techno Tim.

Looks like theme override doesn't work. But changing the colors using colormaps works like a charm. You can download colormaps from here: https://store.kde.org/browse?cat=371&ord=latest Then in Krusader, goto Settings > Configure > Colors. Disable 'Use the default KDE colors'. Click 'Import color-scheme' and select the colormap you downloaded from the site. I'm using this one, looks good: https://store.kde.org/p/1462837

If they are in the same group then you cannot pass each one to a separate VM. Did you try to edit the xml manually and passthrough the device(s)? Should be as simple as adding to the <devices> section something like: <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x28' slot='0x00' function='0x0'/> </source> </hostdev> or 0x29 for the other chip.

What happens if you configure a new VM exactly the same way and choosing i440fx instead of Q35, same everything, does it still crash? Is the crashing happening before you even install Widows? or after installation? What happens if you remove the vbios.rom from the xml?

You don't need to do that, there's a 'User Scripts' plugin that is easy to use.

You can't just use any linux package, it needs to be specific to Slackware15. Here's a link to the packages distro: http://slackware.cs.utah.edu/pub/slackware/slackware64-current/slackware64/ But borgbackup is not there, you'll have to either find the right package, or compile and build the package yourself. To build it yourself you can just use SlackBuilds.org: https://slackbuilds.org/repository/15.0/system/borgbackup/?search=borgbackup

Any changes I make to the xml in the cpu section breaks the image and it won't boot. As soon as I restore the original xml with 2 vcpu (no hyperthreads) it works fine. Working XML: Broken XML:

Hi Ed, I'm having the same issue, tried the fix but still the same. I'm running on AMD Epyc. It turns out I had to remove the nvram file manually (located in /var/lib/libvirt/qemu/nvram). Also, if I make any changes to the cpu allocation, it won't boot for the 1st time. So i kept the cpu assigned to 0 and 2 from the original template, and set ram to 16GB in the xml. Now i'm doing the initial boot and install, I'll try to change cpu allocations after it's up and running (if that happens...) Thanks!

My Postgres password has special characters, how do I escape them? Getting an error when starting the container for the 1st time about invalid db URI. Thanks

Nope, it appears the 1108 is incapable of sr-iov. I just use it for providing cache pools. I do have the 1508 (PCIe 4.0) and it works great, has sr-iov support, and each drive is in its own group: So given the choice, go with the 1508 even if you have Gen-3 drives, it should be backward compatible.

Have you checked your components for overheating? I had placed my SAS controller in a slot where it didn't get cooled properly by the case fans, resulting in drive errors and freezing/crashing. Have you changed any hardware that might trigger this issue? You can also try to install Windows/linux on a spare drive and boot it for a few days/weeks and see if it's stable, monitoring temps along the way. You can also try to move pci cards around and see if it does anything good.

I had a similar issue happen to me, what was happening to me was because the controller was getting too hot. I'm running an SAS9305-16i. To solve the issue, I moved the card to a slot where I had case fans blow directly on it. The hdds are fine, because the controller got so hot, it will report erroneous errors. So check your controller temps. You can do that using storcli64, using the following command: You should be able to find the utility on Broadcom's site.

I'll give it a shot, thanks!

I have a similar issue with iotop, something is up with my python2 package, i get an error launching iotop, which i can only fix by uninstalling both iotop and python2 packages, then reinstall both. After a reboot issue comes back.

You can also create a VM with slackware 15 iso, and then build your own packages using slackbuilds.org. Then put those packages in /boot/extra to auto-install.