14 ms·
QEMU 7.0
- yjftsjthsd-h 5y agoI personally didn't find most of the list interesting, but this is nice: > RISC-V: support for KVM > RISC-V: support for ratified 1.0 Vector extension, as well as Zve64f, Zve32f, Zfhmin, Zfh, zfinx, zdinx, and zhinx{min} extensions. Always happy to see RISC-V getting fully formed:)
- vbezhenar 5y agoModern computing is somewhat exciting. We finally got two competitive architectures (x86 and arm) and risc-v slowly building its momentum. This can only result in a better outcome: architectures will compete with each other and improve at faster rate; software will be forced to be cross-platform which is known to improve robustness even if you don't care about other platforms (some bugs are more likely to manifest on other platforms).
- hulitu 5y agoWe got more than 2 competitive architechtures. There was Alpha, Sparc, MIPS, PA-RISC, ARM, X86 and POWER. Now Alpha and PA-RISC are dead, POWER and Sparc are niche, MIPS 64 is dead.
- pm215 5y agoQEMU releases are calendar-based, every four months, so "7.0" just means "first release of 2022", not "we got lots of new and shiny stuff so we bumped the major version" :-) More generally, what goes on in QEMU these days is mostly continued progression of existing work rather than sudden new developments: it's an established project making incremental improvements and following along with updates to hardware and other standards.
- johnny22 5y agoIf that's the case, I wish they'd adopt a year.month style version then! I guess i never thought about their versioning though.
- pm215 5y agoIt 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.
- mdaniel 5y agoMerely for your consideration, I believe it'd be possible to match both goals by setting next year's version to 2023.0.0 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
- jaclaz 5y agoHmmm. From the home page: https://www.qemu.org/ https://www.qemu.org/ Latest releases 7.0.0 Apr 19th 2022 6.2.0 Dec 14th 2021 6.1.1 Dec 23rd 2021 And the "full list of releases": https://download.qemu.org/ https://download.qemu.org/ is not any better, I think that starting from 2018 the number means (roughly) the year: 3=2018 (or also early 2019) 4=2019 5=2020 6=2021 7=2022 but I can see no evidence of a 4 month fixed interval release.
- bonzini 5y agoWell, x.y.0 releases are all done on April, October and December.
- pm215 5y agoAs the person who tagged v7.0.0 yesterday, I do in fact know our release cadence :-) As bonzini says, .0.0 is April, .1.0 August and .2.0 December. The x.y.1 are stable-branch releases which happen slightly more irregularly.
- jaclaz 5y agoI don't doubt you know that cadence :), but without the additional info you just provided with the x.y.0 and x.y.1 distinction it didn't seem accurate when compared to the actual dates of the releases. So, to clarify: x is year (counting from 2016=1) ? (OR first release of a year gets a major version bump) IF last digit is 0 then y is to be decoded as: 0=April 1=August 2=December OTHERWISE IF last digit is 1 the y may (or may not) be decoded as above.
- pm215 5y agoYes, except that if the last digit is not 0 then it only tells you "this is on the stable branch that started at the x.y.0 tag", and says nothing about year or month. Stable branch releases usually happen about 4 months after the .0, but there's no regular cadence to them, nor any rule about whether there is none, one, or more from any particular mainline release. (The entire release process for them is largely separate from the main releases.)
- qqque 5y agoDoes 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?
- pabs3 5y agoA qemu fork for this was posted on HN a while ago: https://github.com/TrungNguyen1909/qemu-t8030 https://github.com/TrungNguyen1909/qemu-t8030 https://news.ycombinator.com/item?id=30545425 https://news.ycombinator.com/item?id=30545425
- deleted 5y ago[deleted]
- wyldfire 5y agoThe fact that it's been rebased on 7.0 in the last day makes me think that it has not landed upstream yet.
- joshbaptiste 5y agoThe same guy that started QEMU also started ffmpeg.. two very complex pieces of software https://en.wikipedia.org/wiki/Fabrice_Bellard https://en.wikipedia.org/wiki/Fabrice_Bellard
- jraph 5y agoAnd also QuickJS, and also the Tiny C compiler, and also JSLinux that runs operating systems in the browser, among other things. https://bellard.org/ https://bellard.org/
- jzer0cool 5y agoTwo of the coolest piece of software might I add and continuing on strong today!
- bfz 5y agoWhile this is true, please don't let it overshadow the tremendous work (possibly even the bulk of it by now) by subsequent maintainers. In the ffmpeg case that involved fighting a well-resourced hostile fork over a period of years, in the Qemu case I believe it means at least 10 years of additional substantial feature development. I wonder what Bellard's overall hit rate across all those projects looks like in terms of staying around for chores after delivering the initial act of wizardry
- l33t2328 5y agoWhat is a “hostile fork?”
- sanxiyn 5y agoProbably talking about libav. https://en.wikipedia.org/wiki/Libav https://en.wikipedia.org/wiki/Libav has some pointers.
- feikname 5y agoOne that have the same binary name as yours for compability reasons, but then proceeds to be not so compatible with slight command line options. Thus, made a whole lot of confusion because people didn't expect that depending on what distro they were using they could be using similar but incompatible software with the same executable filename.
- jbverschoor 5y agoNice, let's see when UTM uses it :-)
- binwiederhier 5y agoSince 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!
- greatquux 5y agoI 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 with NVMe so we can get decent performance. :)
- cpach 5y agoI didn’t follow… Who’s buying what?
- password4321 5y agoper Google: https://www.kaseya.com/datto-to-be-acquired-by-kaseya https://www.kaseya.com/datto-to-be-acquired-by-kaseya (Apr 2022) https://en.wikipedia.org/wiki/Kaseya_VSA_ransomware_attack https://en.wikipedia.org/wiki/Kaseya_VSA_ransomware_attack (Jul 2021)
- synergy20 5y agoIn this case, I hope your company consider some donations to this wonderful project, good for your business down the road too.
- binwiederhier 5y agoThat is a fantastic idea. We are a Silver sponsor for Let's Encrypt, so this is not entirely impossible that we'd donate to QEMU as well :-D I'll bring it up to the people who can make these calls.
- diosito 5y ago
- Macdougall 5y agoDo you guys pronounce it Q-Emu (as in the letter Q then emu as in emulator) or kweemoo?
- maneesh 5y agoKey-Moo for me… am I horribly wrong?
- pm215 5y agoPersonally I pronounce it "kwem-yoo" (first syllable starts like 'quest', second syllable like the second-person pronoun 'you'). But I think there are multiple pronunciations floating around...
- yepguy 5y agoQ-Emu for me, with stress on the first and last syllables so that it almost rhymes. It probably sounds more like I'm spelling out Q-M-U.
- anderspitman 5y agoThis seems to be the most common pronunciation, but there's definitely variation: https://youtu.be/yJw9Avhy_vc https://youtu.be/yJw9Avhy_vc
- edgyquant 5y agoI’ve always pronounced it Kim-you, although that’s probably incorrect
- aimor 5y agoI might be the only one that uses the verbose Q E M U.
- rubyist5eva 5y agoHow’s macOS virtualization performance these days? Had to pony up for a Parallels Desktop license as QEMU was 2-3x slower and just wasn’t up to snuff for daily driving on my dev machine.
- cpach 5y agoFrom my toying around with it it seems quite good. But I haven’t done any stress-testing/benchmarking. NB: Important to use the HVF accelerator! Otherwise it will surely be slow. See https://wiki.qemu.org/Features/HVF https://wiki.qemu.org/Features/HVF
- anderspitman 5y agoI'd be very interested to hear experiences from people working with QEMU+HVF. I only have Linux/Windows devices to test on.
- cpach 5y agoFeel free to shoot me an email.
- rubyist5eva 5y agoAny idea if this is enabled by default (or how to check/enable it manually) on UTM.app? I have the "Use Hypervisor" option enabled on the VM but it's dreadfully slow even with just a headless linux server.
- cpach 5y agoStrange. I would guess that it’s enabled by default. You might want to submit a new discussion on their GitHub project: https://github.com/utmapp/UTM/discussions https://github.com/utmapp/UTM/discussions The devs are very active there.
- anderspitman 5y ago
- _8j50 5y agoI like QEMU a lot but VirtualBox is my goto because the cli commands work fairly reliably and simply and I'm ashamed to say the simplicity of the UX is compatible with my laziness. For server workloads KVM/Qemu is great but imho, Vbox or Fusion are the best in my experience. Does anyone know if there are Qemu wrappers with a nice UI/UX? My current use cases aside, it's amazing the number of nice use cases Qemu is made use of. GNS3 was my favorite when I used it many years ago (Cisco IOS).
- cpach 5y ago“Does anyone know if there are Qemu wrappers with a nice UI/UX?” What operating system are you on?
- belthesar 5y agoOn the Linux side of the house, virt-manager is pretty great, though it leans much harder into KVM, so you don't necessarily get all the exotic architecture support of QEMU built in. QtEmu for Windows gets you there, but it's very much so an API frontend, so if you're looking for simple from a choices perspective, this ain't it (though you might figure out your sane defaults and go from there). Since you mentioned Fusion though, I'm guessing you're a Mac user, and UTM might be the ticket for you. The project started as a side-loadable/jailbroken device iOS VM system, but the project also makes a macOS app as well. https://mac.getutm.app/ https://mac.getutm.app/ This works both on Intel and Apple Silicon Macs, though in order to get virtualization acceleration, it's best to run workloads built for your native architecture (ARM on AS, x86(_64) on Intel).
- anderspitman 5y agoQEMU 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. With -accel whpx you can even get pretty solid CPU acceleration. WHPX[1] is sort of like KVM for Windows, only takes a couple clicks and a reboot to enable, and ships on both Windows Home and Pro. Other than the heroes who did the actual work, we probably have Android to thank[2] for this situation. If you're willing to get your hands a little dirty, QEMU is a fairly viable alternative to WSL or even Docker on Windows. [0]: https://qemu.weilnetz.de/w64/ https://qemu.weilnetz.de/w64/ [1]: https://docs.microsoft.com/en-us/xamarin/android/get-started/installation/android-emulator/hardware-acceleration?pivots=windows https://docs.microsoft.com/en-us/xamarin/android/get-started... [2]: https://developer.android.com/studio/run/emulator-acceleration#vm-windows https://developer.android.com/studio/run/emulator-accelerati...
- password4321 5y agohttps://github.com/intel/haxm https://github.com/intel/haxm looks cool, thanks! Windows Home support saves a few bucks.
- anderspitman 5y agoI wonder if there's actually any reason to use HAXM these days, since WHP ships with windows and works for both Intel and AMD CPUs?
- orev 5y agoEnabling Hyper-V on Windows currently causes problems with VirtualBox, so that’s one reason. They’re (vbox) working on fixing it, but it hasn’t landed yet.
- anderspitman 5y ago
- anderspitman 5y agoFirst 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. Honestly I'm struggling to get my foot in the door. My questions on the user mailing list go mostly unanswered. I'm not aware of any QEMU book. Documentation feels sparse and is fragmented across multiple locations and often requires hoping someone has written a blog post about the specific piece you're interested in. I wish there were more descriptions of architecture and design decisions. I hesitate to use the development mailing list since it appears dominated by patches (a ton of them; QEMU is very active), and my requests don't quite seem to be development-level (yet). 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.
- ori_b 5y ago> Any suggestions for how to get help learning QEMU as a "power user" hoping to eventually contribute as a dev? Use the IRC channel. Or the mailing list.
- mysterydip 5y ago> My questions on the user mailing list go mostly unanswered.
- anderspitman 5y agoThey might be referring to the dev mailing list. I've only tried the user mailing list so far.
- _vdpp 5y agoA QEMU book would be _very_ welcome.
- pm215 5y ago
- egberts1 5y agoMy 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 insert some 50-odd test points into the QEMU code was proved to be a maintenance nightmare. Even if it just an #ifdef of C language, it was too “cluttery”, it was still an awesome automated detection of code generation of just the affected malware portion. I still believe this approach to be a significant tangential vector of prime investing for a startup. https://github.com/unicorn-engine/unicorn https://github.com/unicorn-engine/unicorn
- egberts1 5y agoThis is how I found out a snippet of assembly code that can actually distinguished between a KVM hypervisor and most of today’s emulator. https://github.com/unicorn-engine/unicorn/issues/364 https://github.com/unicorn-engine/unicorn/issues/364
- stsquad 5y agoThe upstream now has TCG plugins (https://qemu.readthedocs.io/en/latest/devel/tcg-plugins.html https://qemu.readthedocs.io/en/latest/devel/tcg-plugins.html) which allow for a degree of instrumentation. The implementation is architecture agnostic and also tested within the code base. There are still features missing but it does provide a base for dynamic analysis of guest code.
- egberts1 5y agoRight but there are many analysis code written under Unicorn-engine that are architecture-specific. I do not think we could do that yet with the new QEMU TCG plug-in framework.
- stsquad 5y agoThe plugins have access to the instruction stream to make architecture specific decisions. What I meant by architecture independent is that it doesn't involve per-guest annotations in the frontends to handle - any guest using the common translator loop (which is all of them now) can be instrumented by plugins. However I absolutely agree its not currently as full featured as we would like. The next step when I get time is re-factoring the handling of register values in the core QEMU code so we can expose them to the plugins in a clean API.
- phendrenad2 5y agoQEMU is great for debugging the Linux kernel. But does anyone know if there are any paid alternatives? (QEMU is a bit clunky and the configuration is arbitrary and frequently broken)