Virt-Manager Oddities, and slackware from source builds
Hello slackers! My first problem, is that I'm trying to setup virt-manager. I recently built it and its deps through sbopkg, I checked the slackdocs page on it and set up a libvirt group for my current non-root account.
the problem is, I open it up, and get this error message Code:
Unable to connect to libvirt. For my second problem, I am installing slackware on an old laptop that I want to take with me for the sake of travel. except that the performance is not up to my standards, so I figured I'd build the kernel by hand, then I remember my attempts at gentoo, the reasons I went back to slack, and figured "why not build the other programs?" so I downloaded the sources of 14.2. How I would automate the process of chmodding and executing the .SlackBuild(s) of the sources? I for one don't want to do this all by hand as it would cost me more time than I'm willing to spend on it. |
Did you start libvirt? Directions are on the read me here:
https://slackbuilds.org/slackbuilds/...libvirt/README It needs to be set to start at boot. |
Quote:
EDIT: Also, I tried making a test VM, and libvirt spat out the following: Code:
Unable to complete install: 'unsupported configuration: this QEMU does not support 'qxl' video device' |
You need: https://slackbuilds.org/repository/1...f86-video-qxl/
and I also usually install: https://slackbuilds.org/repository/1...spice-vdagent/ You need to start it up without qxl enabled and then install qxl, power off, enable qxl, start up and qxl will work in the VM. |
back to square two
Hoo boy...
What an adventure I've had this past few weeks with slackware. so here's what happened. Something went really wrong in between messing with virt-manager's options while root. somehow I did something that caused my system to not be able to detect any screens, so I had to backup my data and reinstall slackware from the bare command line. Eventually I managed to not only get a Windows 7 VM working, but I managed to install the virtio drivers from redhat onto the machine for better performance... unfortunately, this did not include gaming performance; the moment I tried to start a backed up copy of xonotic, all my plans went down the toilet. So I pulled out the extra GPU I had bought specifically as a host GPU for passthrough, and put my stronger, gaming GPU on the other bus, and tried to pass it through immediately for shiz and giggles. got an error that I don't remember, so I reinstalled slackware again to be safe. two hours of untangling virt-manager deps later, I got my win7 VM working again. I tried to pass it through to my VM on my fresh install, and it puked out this error. Code:
Error starting domain: internal error: qemu unexpectedly closed the monitor: 2018-09-12 04:21:55.339+0000: Domain id=1 is tainted: high-privileges
My best-case-scenario goal, is something like this: http://www.youtube.com/watch?v=ssfvpLXK8po given my hardware is AMD-based, it'd be far from exact. At the very least, I want to pass my GPU through to a windows 7 VM, and be able to game smoothly on it, while keeping all my writing and other stuff on slackware. Machine specs for reference
|
I am using exact the same motherboard and processor on my main desktop and three graphics cards, two are used for passthrough: an amd 7350 graphics and an nvidia quadro fx 3800.
Even though I don't use libvirt, because I could not get the passthrough to work, I have made this little command called vms. See here https://www.linuxquestions.org/quest...es-4175637126/ I have been using it to successfully run linuxes, windows, macos and freebsd with full 3d hardware acceleration. Have a look here for pointers about passthrough, even if you don't use vms, it might be useful https://docs.slackware.com/howtos:em...ci-passthrough Also, for audio on a windows guest, the best way is to buy a cheap pci sound card and pass it through to the guest, or buy a cheap usb card and pass through the host's usb controller. Windows usually have smaller buffer sizes for audio and because of this, there are clicks and pops here and there caused by buffer underruns and on top of that a lot of latency, especially when running games and videos. |
Quote:
Can you please make it clear that you're using alienbob's slackbuild of VDE, and not the slackbuilds.org's slackbuild? I figured this out only after searching for TigerVNC and finally understanding how you managed to get that to work, as the slackbuilds.org version of VDE refuses to compile. other than that, I've managed to boot an iso of my windows 7 disc, so I'll continue to look through the manuals on VMS, so far it's promising! |
Quote:
You need VDE if you want to use VDE network, I have to remove that from REQUIRES, since it's really an optional dependency. |
Quote:
https://github.com/Ponce/slackbuilds...2/network/vde2 |
Quote:
I am marking this thread as solved, since I am not using virt-manager anymore, and my other questions I have made in a different thread. |
All times are GMT -5. The time now is 08:12 AM. |