Live data from Hacker News

QEMU 10.1.0

wiki.qemu.org

51–60 of 61 posts

Re: QEMU 10.1.0

#51
post #19

Earlier quoted context omitted.

If you use it rarely, I can high recommend the excellent QuickEMU [0] Any VM is just a `quickget ubuntu 24.04` and `quickemu --vm ubuntu-24.04.conf` away. The conf file is just a yaml that is very readable and can give you more cores/ram/disk easily. Just run `quickget` to get a list of OS's to download. [0] https://github.com/quickemu-project/quickemu

Doesn't the 'q' in 'qemu' stand for "Quick" ?

Looks like it does :) Maybe take it up with Martin Wimpress, who probably meant it as a way to jar us all just a tad (knowing him from podcasts he probably has a witty and funny response to such inquiries).

Re: QEMU 10.1.0

#52

> Experimental support for compiling to WASM using Emscripten. Neat. This will unlock various online "playgrounds" for a number of CPU architectures, among other interesting use cases. Likely this was possible beforehand, but it's nice to see it added as a feature to the project directly.

Could be cool for interactive simulator of microcontroller/embedded in browser.

Re: QEMU 10.1.0

#53
post #13
post #3

QEMU is truly excellent software, from the perspective of a person who very rarely needs to emulate another architecture. It "just works" and has wonderful integrations with basically everything I could want.. sometimes it feels like magic: even if the commandline UX is a bit weird in places. I've always wondered though how it works with KVM: I know KVM is a virtualisation accelerator that enables passing through nat…

qemu/kvm in enabling the cloud is huge but that's not the only place it really makes a tremendous difference. One example where it's essential is new OS development. They all basically first target the qemu machine with its virtual hardware. It makes development much faster compared to running on real hardawre while easily enabling debug output without needing cables and the like.

Eh, we just used stuff like bochs and vmware prior.

Re: QEMU 10.1.0

#54
post #44
post #5

Earlier quoted context omitted.

Not everything uses qemu. Some do. More use KVM. Not everything does. Example: https://firecracker-microvm.github.io/

I've found QEMUs microvm to be faster at boot while having nicer tooling and a cleaner upgrade path if needing more features. Aside from hype I'm actually not sure why anyone would still use firecracker.

Mainly because of the much larger attack surface of QEMU.

Re: QEMU 10.1.0

#55
post #13

Earlier quoted context omitted.

qemu/kvm in enabling the cloud is huge but that's not the only place it really makes a tremendous difference. One example where it's essential is new OS development. They all basically first target the qemu machine with its virtual hardware. It makes development much faster compared to running on real hardawre while easily enabling debug output without needing cables and the like.

Eh, we just used stuff like bochs and vmware prior.

I didn't mean qemu is the only option.

Re: QEMU 10.1.0

#57
post #55

Earlier quoted context omitted.

I didn't mean qemu is the only option.

My point is that the appearance qemu/kvm didn't really practically change the space much.

Oh I understand what you're saying. You're probably right. Collectively virtualization allows a lot but qemu might not be as exclusive as I said. (I think there are only a few years between bocsh/vmware and qemu/xen.)

EDIT: I didn't mean to sound like ChatGPT. It happened naturally :)

Re: QEMU 10.1.0

#58
post #3

QEMU is truly excellent software, from the perspective of a person who very rarely needs to emulate another architecture. It "just works" and has wonderful integrations with basically everything I could want.. sometimes it feels like magic: even if the commandline UX is a bit weird in places. I've always wondered though how it works with KVM: I know KVM is a virtualisation accelerator that enables passing through nat…

> I've always wondered though how it works with KVM Other people have given some more comprehensive explanations, but I'll try to put it as simply as possible. Plain QEMU has a CPU emulation layer called TCG. The machine basically consists of memory (RAM and MMIO devices) and CPUs (CPU registers and state). When QEMU has set up the machine and is ready to run, it calls TCG to say "given this memory and this initial C…

And there are other emulated accelerators that QEMU leverages:

https://wiki.gentoo.org/wiki/QEMU#Introduction

Re: QEMU 10.1.0

#60
post #25

Didn't realize there was a MIPS build of Windows NT. Which led me to wikipedia to find there were a lot of other architectures supported in the past.

In my last job, I was on the team that handled the Windows NT bulid on DEC Alpha. Native Alpha apps were much faster than the equivalent Intel NT machines. Apropos to this topic, DEC had a sybsystem called FX!32 that was sort of like what Rosetta does for Apple Silicon, allowing Intel apps to be run at useable speeds on Alpha. https://en.wikipedia.org/wiki/FX!32

If I still had my UltraSPARC, I'd be wanting to find the SPARC port of Windows NT.
Post reply on HN