

No the Apple hypervisor is called hvf, but projects like rust-vmm and QEMU can control and service guests run on that hypervisor. No KVM required.
FLOSS virtualization hacker, occasional brewer
No the Apple hypervisor is called hvf, but projects like rust-vmm and QEMU can control and service guests run on that hypervisor. No KVM required.
virtio-gpu with Vulkan pass through for the VM with a Vulkan to Metal translator in host user space. There are various talks about this including at KVM forum: https://kvm-forum.qemu.org/2024/The_many_faces_of_virtio-gpu_F4XtKDi.pdf
Sure if they needed to bypass ads I can introduce them to Free tube or whatever but for all it’s sins they need moderated exposure to the YouTube experience so they’re equipped enough not to go totally wild when they finally have unfettered access.
I thought my youngest was all about watching hour long Minecraft playthroughs but really they are quite interested in game mechanics and speed running. They are just a lot more tolerant of watching hours of videos around a particular game.
I don’t overly police their content consumption (although we do talk about limiting shorts). The main thing is at the weekend to kick them off the TV after the morning to go and do something more interactive.
When we first let the kids watch YouTube it was on the main TV with it’s own account. We have consistently monitored it and actively prune recommendations while slowly introducing them to the concept of “the algorithm”. From secondary school they pretty much need YouTube on their own PC’s for homework reasons and it’s harder to totally lock down - we use the family link controls to limit it a little but if they tried to get around them they could. The hope is we’ve at least prepared them a little before they have totally unfettered access to the internet.
We did try YouTube kids a little but it was such a garbage experience we just blocked the app everywhere.
The article says it only applied to apps requesting certain permissions. I agree I’m an ideal world it would be nice to get f-droid directly from the Play store but at least according to the article the ability to install it isn’t being blocked here.
From the article it sounds like the limitations come for some app types downloaded directly from a browser. I think this doesn’t affect alternate app stores like f-droid where you are effectively delegating approval to their process.
I have come across the other limitations mentioned with the Home Assistant companion app which I could only get matter registration to work with the version downloaded from the Play store.
Minecraft bedrock edition. There is a native project called mcpe loader but that does break occasionally because of the way it’s done. The waydroid approach is pretty rock solid.
Did Wordpress ever fork our have people just been migrating to alternatives?
Basically you need to hook into decryption engine being used and copy the unencrypted data before it gets sent to the hardware to play. I assume something like Widevine sends the data directly to the system codec for playback so you could look at the syscalls it makes for that.
The other option is to use VirtIO with Native Context support as a software based partitioning scheme that is relatively lightweight compared to the mdev approach.
The kernel on GitHub is just a mirror - the primary source is on kernel.org
Not just that - modern Androids compile apps in a VM these days to reduce the attack surface of the compiler. You can also push other services into VMs that support the main image. You could even push some vendor drivers into VMs and help keep the main kernel less of a vendor fork fest.
Does anyone know what the underlying filesystem is on DSM? The ability to easily replace disks with a degree of redundancy across the 4 bays is the biggest plus point for Synology although I have no doubt all the bits underneath are the Linux storage stack.
It’s a shame because I really like the point and click nature of DSM. Although I’m a happy Linux hacker I don’t want another Linux box to suck up my limited admin time just to store files.
Bold of you to assume we’ll make it that far. I’m not convinced that our current networked CO2 phase isn’t another great filter event.
Android gets a leg up from being built on a FLOSS base but I don’t think it was the community that pushed Android to where it is today. That’s taken a lot of money and resources from Google and it’s phone partners investing in the slightly more open platform than Apple.
That’s not really true. Yes avoiding complex instructions makes the front end easier to pipeline but there are lots of smarts in the backend to do prediction and scheduling to keep the execution units fed. The ISA might be free to use but no one is sharing their highly optimised server silicon architecture designs.
RISC-V’s challenge is can they standardise the software ecosystem enough that things just work across a multitude of chip providers or does everything devolve into specialist distributions taking advantage of each manufacturers “special sauce” custom instructions.
Gaining design wins over Arm’s microcontrollers for bespoke hardware was the easy bit. Replacing stuff in the server space is much harder and something that took Arm decades to make inroads into.
I pay for it so the TV and web experience is ad free. I use PipePipe on my phone because the native client won’t stop pushing shorts at you.
VirtIO was originally developed as a device para-virtualization as part of KVM but it is now an OASIS standard: https://docs.oasis-open.org/virtio/virtio/v1.3/virtio-v1.3.html which a number of hypervisors/VMM’s support.
The line between what a hypervisor (like KVM) does and what is delegated to a Virtual Machine Monitor - VMM (like QEMU) is fairly blurry. There is always an additional cost to leaving the hypervisor to the VMM so it tends to be for configuration and lifetime management. However VirtIO is fairly well designed so the bulk of VirtIO data transactions can be processed by a dedicated thread which just gets nudged by the kernel when it needs to do stuff leaving the VM cores to just continue running.
I should add HVF tends to delegate most things to the VMM rather than deal with things in the hypervisor. It makes for a simpler hypervisor interface although not quite as performance tuned as KVM can be for big servers.