Earlier quoted context omitted.
Crappy? Windows 7 was the last good Windows.
You don't like being plastered with ads and news articles about Trump every time you open your start menu??
Is it maybe because I'm using Win10 Pro, not Home?
161–170 of 205 posts
Earlier quoted context omitted.
Crappy? Windows 7 was the last good Windows.
You don't like being plastered with ads and news articles about Trump every time you open your start menu??
Is it maybe because I'm using Win10 Pro, not Home?
Earlier quoted context omitted.
Yes, quite different. It's basically a project that allows you to use Linux as a hypervisor. A very popular project. https://en.m.wikipedia.org/wiki/Kernel-based_Virtual_Machine
Thanks!
I am really curious about this. As a pentester, I run use Linux on my laptop and I spend a lot of time working inside a Kali VM with VirtualBox. How much performance improvement can we expect with the KVM backend ?
If you don't mind, I have a specific question regarding this setup. I've been looking into getting into pentesting, mostly for fun. I decided on messing around with HackTheBox as a starting point. Seeing as you need to connect to their VPN, it seems like a good idea to me to separate this activity from my personal network. Which networking setup do you use for your pentesting VM? Ideally, I'd want a setup where the V…
Can someone ELI5 what this is and does it benefit someone like me who occasionally spins up VirtualBox VMs for various OSes?
I'm not an expert in this field, but my best TL;DR is that VirtualBox and other VMM's (virtual machine monitor) used to ship with their own hypervisors (the thing that let's you run virtual machines). However, now Linux has its own hypervisor/framework (KVM) and now VirtualBox can use KVM to do all the functionalities their own hypervisor used to do.
Someone please correct me if I'm wrong
I'm running a Ryzen5600G on Arch and recently switched from VirbualBox to QEMU/KVM and couldn't be happier. Webcam, USB drives, Hardware Video Acceleration, all working without issue (after a pretty tough learning curve getting it set up).
Earlier quoted context omitted.
I thought virt manager was ok but honestly your complaints about it are specific and fair.
Virtual box has graphical configuration for a ton of different options. It also “just works” in many cases and is relatively easy to use. I am surprised the open source community has not built better gui tools, and no project, closed or open has made configuring pcie passthrough easy. I have always wanted to be able to run Windows in a virtualized session with my GPU for gaming, and use my onboard APU for the Linux h…
This is the thing that isn't surprising.
In order to make a better GUI tool, you have to understand how the internals work. Then you don't care to use a GUI tool because you know how to use the command line or edit the configuration files. The people who want better GUI tools are the people who don't know how to make them.
In order to change this, the people who want GUI tools but don't know how to make them have to provide some incentive (typically money) to the people who know how to make them but don't want them, e.g. via donations or some kind of commercial agreement. And if they stand around and wonder why nobody else has fixed their problem for them instead of doing the thing that causes it to be fixed, an object at rest tends to remain at rest.
Earlier quoted context omitted.
I thought virt manager was ok but honestly your complaints about it are specific and fair.
Virtual box has graphical configuration for a ton of different options. It also “just works” in many cases and is relatively easy to use. I am surprised the open source community has not built better gui tools, and no project, closed or open has made configuring pcie passthrough easy. I have always wanted to be able to run Windows in a virtualized session with my GPU for gaming, and use my onboard APU for the Linux h…
"GPU passthrough with libvirt qemu kvm" https://wiki.gentoo.org/wiki/GPU_passthrough_with_libvirt_qe...
"PCI passthrough via OVMF" https://wiki.archlinux.org/title/PCI_passthrough_via_OVMF :
> The Open Virtual Machine Firmware (OVMF) is a project to enable UEFI support for virtual machines. Starting with Linux 3.9 and recent versions of QEMU, it is now possible to passthrough a graphics card, offering the virtual machine native graphics performance which is useful for graphic-intensive tasks
KVM-GPU-Passthrough: https://github.com/BigAnteater/KVM-GPU-Passthrough
Practical thing is not having to recompile 3rd party drivers (vbox ko) every time kernel gets upgraded. Tho DKMS tries to take care of that without admin intervention, it's not always bug free. On the other side VirtualBox the software application is designed to integrate with the desktop well, VNCing into the guest is not an alternative to this. I hope efforts will be made in FreeBSD world too against its bhyve hype…
I cannot even imagine using a distro that can't manage to get DKMS/kernel module updates to be reliable. I don't think I've ever had a problem with DKMS in NixOS ever; not a single time. edit: downvoting me won't make your distro any more competent.
I think the backlash has more to do with the comment's tone.
Earlier quoted context omitted.
That's odd about the core count. I only get that behavior if my host system only has 1 CPU to begin with (tested in qemu/KVM with nesting). Could you comment on your host system parameters a bit?
This is definitively not expected. You could also try setting the CPU/Mem configuration via VBoxManage. Maybe you get a good error message then. `VBoxManage modifyvm --cpus ` `VBoxManage modifyvm --memory `
Earlier quoted context omitted.
I wish there was a port of UTM to linux
Gnome Boxes is an attempt at a similar interface, but yeah, it's not quite as polished.