kvm-guest-drivers-windows VS telescope

There's mature VirtIO drivers for just about everything already, under the virtio-win umbrella: https://github.com/virtio-win/kvm-guest-drivers-windows

My desktop PC is using libvirt+qemu (on an Arch host. I use Arch, btw) to PCI passthru my RTX 4090 GPU to a Windows guest. I installed the guest initially with emulated SATA for the main drive. Once Windows was up and running, I installed virtio-win and the guest is now using virtIO accelerated drivers for the network interface, main disk. I'm also sharing some filesystems using virtio-fs.

So, I started configuring the PC with ubuntu desktop (since I need a GUI for my use case). Then I setup a windows KVM with this. In my use case, I want the windows VM to be always connected to a VPN (Mullvad) that has the toggle of LAN connections turned on. This is because I want to use sunshine on the KVM to stream my desktop to a firestick. This is how I have been configuring one PC till now for my family to be able to watch TV. The issue is that I cannot use sunshine or parsec cos there are no encoders in the VM, thus the performance sucks. (I could use software encoders, but I would use too much CPU for windows VM, which would make me unable to run a LLM (this was my plan) )

Note also: it just got an experimental Windows driver!

[1]https://github.com/virtio-win/kvm-guest-drivers-windows/pull...

virtio-GPU for Windows for now is just a basic display driver, without any kind of acceleration, so there shouldn't be any difference between using it and QXL, which is fully emulated and in it, if necessary, you can increase the VRAM to be able to use high resolutions, as explained here. Note: this link is just from a quick search, I tried this for myself some time ago but my intention was not to increase the resolution but just to find out if it was possible to have some kind of 3D acceleration, as it happens in VirtualBox, but is not possible yet.

The only sorta-responsive display tech I've found is Virt with GL (3D) enabled. And if your physical box has 4k video you can forget about going anywhere near full screen with that guest VM.

I suggest you open a new issue in the repository describing this, or search if there is one open reporting the same. Also, keep in mind that as an early stage it might be a good idea to avoid copying important files using this, you could end up losing data unless you do an integrity check (recently I tried installing a game on the VM in a host directory and it didn't work. I'm thinking of an alternative or going back to using VirtualBox, since the shared folders worked very well for this purpose).

The problem was really bad with latest virtio drivers, so I downgraded to version 204, as per: https://github.com/virtio-win/kvm-guest-drivers-windows/issues/623

It all starts with an old 400 error that was occurring in Telescope for a while now, first documented here.

Sattelite for the back end

There are a few places to start with this, one is that we have an issue in Telescope that relates to what I think is the session no longer existing in certain situations that results in a 400. This will give me an opportunity to take a look at Telescopes auth flow. I still am kind of unfamiliar with Telescope despite having been in the last OSD course. I know that we use passport SAML in Telescope however and in the new project we will use a different library called SAMLIFY.

The project is currently in the planning phase, and being part of the development team, I have been researching ways to add relevant bits of Satellite in the Remix Blues Stack project, we intend on using for Starchart.

As a good well-established project, Telescope provides a great environment setup guide, which covers most use cases.

It's been a year since I was supposed to work on Telescope for a class. When the war in Ukraine started in February 24th, 2022, I almost fully stopped contributing. Now, this year I am trying to do more, even though it's not my class anymore. Because I wish that I did more back then.

This week, I decided to setup Telescope locally. I had previously contributed to telescope and had set it up already. However, I faced some problems starting it up locally after a shutdown and startup sequence. This was hard to debug since there was no error message, just containers on docker would not start up even after waiting for several minutes. These problems would fix after a restart or just randomly after a few tries. So, I decided to go through the setup again.

Task This week, I try to revisit my setup for running the Telescope project, a single page website that aggregates blog posts.

This week, I finished implementing the feature for filtering out irrelevant feed URLs. Previously, I had added a function for the filtering but had to write the test for it.

The two PRs(1 2) mentioned last time were merged without a hitch. For the one that's about parsing Twitch channel feed URL, the maintainer and I agreed that there should be a follow-up issue opened to expand it to YouTube Channel(s). They also found another bug in the sign-up that should exist as its own issue about the RSS feed URL(s) having incorrect domain. For details about them, please see my last post.