61–70 of 97 posts
Does anyone know if this release supports emulating the iPhone? If I remember correctly, some ARM extensions and peripherals needed implementing, have they done this for this latest release?
A qemu fork for this was posted on HN a while ago: https://github.com/TrungNguyen1909/qemu-t8030 https://news.ycombinator.com/item?id=30545425
My only lamentation of QEMU is their rapid development. (I did say “only”). We had an open source CPU emulator (of many CPU arch) called “Unicorn” that was a heavy test instrumentation points inserted widely throughout and into QEMU 4.0. I spent 2 solid years on these dynamic API bindings of Unicorn into QEMU. It was an awesome piece of SW that allowed us to recreate the behavior of malware. Asking the QEMU team to i…
Since QEMU devs/maintainers are lurking, i just want to say thank you for a fantastic project. I work for a company (Datto) that backs up Windows/Linux machines, which can then later be run as VMs for disaster recovery. Our product heavily relies on QEMU, and would be significantly harder to implement and maintain without it (believe me, it was built around VBox in the past). Thank you!
Since QEMU devs/maintainers are lurking, i just want to say thank you for a fantastic project. I work for a company (Datto) that backs up Windows/Linux machines, which can then later be run as VMs for disaster recovery. Our product heavily relies on QEMU, and would be significantly harder to implement and maintain without it (believe me, it was built around VBox in the past). Thank you!
I work for an MSP that uses Datto to back up lots of servers and saved our bacon after the Kaseya hack! (Ironic how they're buying you now.) And I remember when you were using VBox, QEMU is much improved. Having QEMU boot up the backed-up VM to a screenshot that you can just email to us really helps prove to auditors that yes, our backups are tested! Now just replace all the spinning hard disks in your data centers w…
First off I want to make it clear that this isn't intended as criticism. I recognize the QEMU devs are busy, do incredible work, and don't owe me anything. That said, I started a project recently that I'm very excited about. It wouldn't be possible without QEMU. I've had to get deeper into somewhat lower-level features, and it's likely I'll have to implement some new devices and interfaces for QEMU itself eventually.…
> Any suggestions for how to get help learning QEMU as a "power user" hoping to eventually contribute as a dev? I'd happily pay for consulting if I knew the right people to ask. I'm not being cheeky: read the source. I worked with qemu for years, and the only way I could get real answers was to find the libvirt functionality and work backwards from it. Once I got good enough with that, I could navigate the qemu codeb…
This is a great suggestion, thanks.
> Almost all the docs are going into libvirt, and libvirt's (IMHO) terrible abstractions. The reality is that almost all the investment in qemu's user-facing capabilities are done via libvirt, so it makes sense.
Yeah it's unfortunate that not many people seem to use QEMU directly. I can't use libvirt for my project because a) I'm targeting windows and b) libvirt seems to assume that it will run with root privileges, and I'm targeting userspace.
Honestly other than a few things like CPU pinning, I haven't seen much to justify libvirt over plain QEMU. This would be especially true if the QEMU CLI was simplified slightly and better documented.
Earlier quoted context omitted.
If that's the case, I wish they'd adopt a year.month style version then! I guess i never thought about their versioning though.
It was simpler to just move from "major.minor and we bump the major infrequently and semi-arbitrarily when the minor is big enough to feel unwieldy" to "bump major for first release of the year" rather than completely change the version number format.
I also didn't know about the leading number being a yearly increment and would have thought 7.0.0 was a substantial change over 6.0.0; setting the number to 2023.0.0 makes that distinction a lot more obvious
Do you guys pronounce it Q-Emu (as in the letter Q then emu as in emulator) or kweemoo?
QEMU is absolutely incredible. I think its most undersold feature is the fact that it runs on Windows hosts[0] thanks to MinGW. This in itself isn't unique, but what is unique is that by default it runs entirely without admin privileges. I've been playing with shipping server apps as QEMU VMs and it works surprisingly well. QEMU itself is small enough (~20MB) to ship the entire thing with the app, including DLLs. Wit…
Do you guys pronounce it Q-Emu (as in the letter Q then emu as in emulator) or kweemoo?
My only lamentation of QEMU is their rapid development. (I did say “only”). We had an open source CPU emulator (of many CPU arch) called “Unicorn” that was a heavy test instrumentation points inserted widely throughout and into QEMU 4.0. I spent 2 solid years on these dynamic API bindings of Unicorn into QEMU. It was an awesome piece of SW that allowed us to recreate the behavior of malware. Asking the QEMU team to i…