The presenter chats with Milo.
The presenter chats with Milo.
I don’t recall in virt-manager off the top of my head. But if you make changes in the XML of a domain, you do have to shutdown/restart the domain before they’re effective. And just to be safe, I would say to shutdown the domain, then check the XML, then start up again.
You do say you’re just using qemu, so if that’s the case and you aren’t using libvirt in front of it, shutdown the VM, make sure your qemu command specifies an e1000 network device, and run again.
I can check virt-manager when I get some free time this evening, if that’s what you want/need.
You may need to shut down the VM, check the device config to ensure it’s set to e1000, then boot it back up. The PCI ID on your original post belongs to the virtio-net device.
Instead of trying to backport the virtio device drivers to that version, I’d recommend editing the VM to use the emulated e1000 NIC.
When you see the Windows and Apple icons on a game, that indicates native Windows and MacOS support. The Steam logo is native SteamOS/Linux. You’ll also see a “SteamOS/Linux” section on the system requirements.
WAN would be the Internet uplink port. A 2.5G WAN port is a 2.5 gigabit Ethernet port. 2.5 gigabit and o a lesser extent 5 gigabit Ethernet are a standard that’s becoming rapidly available on a lot of hardware. OP is stating that for a device shipping near the end of 2024, a new router that is shipping with only 1 GbE instead of 2.5 GbE is a problem.
Not really. WAN has always been WAN. Wireless has always been WLAN.
Centralized logging like Graylog or Grafana Loki can help with a lot of this.
7000 series run AVX512 as two 256 bit data paths, while the 9000 series has a native 512 bit data path for AVX512.
It looks like you’ve created a partition for Linux - you need to delete this partition. Leave it as “unallocated” or “free space”. Then the Fedora installer will see it as space it can install to. The installer will handle creating the actual partition.
Standard Dynamic Range. It’s a term adopted to differentiate non-HDR video from HDR video.
The quotes are there because there’s spaces in the file name. You don’t see them in the GUI because they’re not actually there. They’re added by the ‘ls’ command to help with copy/pasting of file names. You can add ‘export QUOTING_STYLE=literal’ to your ~/.bashrc to permanently suppress them, or just do ‘ls -N’ as a one off.
Then you probably don’t know about Spectre and Meltdown from a few years ago. Same family of problem on x86-64 (so Intel and AMD chips).