How’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.
QEMU 7.0
21–30 of 97 posts
Re: QEMU 7.0
#22Do you guys pronounce it Q-Emu (as in the letter Q then emu as in emulator) or kweemoo?
Key-Moo for me… am I horribly wrong?
Re: QEMU 7.0
#23How’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.
From 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.
Re: QEMU 7.0
#24I 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).
Re: QEMU 7.0
#25The same guy that started QEMU also started ffmpeg.. two very complex pieces of software https://en.wikipedia.org/wiki/Fabrice_Bellard
While 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…
What is a “hostile fork?”
Re: QEMU 7.0
#26Earlier quoted context omitted.
While 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…
What is a “hostile fork?”
Probably talking about libav. https://en.wikipedia.org/wiki/Libav has some pointers.
Re: QEMU 7.0
#27The same guy that started QEMU also started ffmpeg.. two very complex pieces of software https://en.wikipedia.org/wiki/Fabrice_Bellard
While 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…
While I agree we shouldn’t lionize individuals, I think we should also acknowledge there is great value in being the one to start something.
Re: QEMU 7.0
#28I 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 mad…
“Does anyone know if there are Qemu wrappers with a nice UI/UX?”
What operating system are you on?
Re: QEMU 7.0
#29I 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 mad…
On 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/ 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).
Re: QEMU 7.0
#30Earlier quoted context omitted.
QEMU 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 oth…
Hmmm. From the home page: 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/ 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.
As 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.