Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

QEMU 7.0

qemu.org

Post reply on HN
Print view View original

41–50 of 97 posts

Re: QEMU 7.0

#41

Post by _8j50 »

belthesar wrote: post #29
_8j50 wrote: post #24

I 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 Fu…

Thanks, I use both Mac and Linux as a host. Fusion is great for work stuff but in general I prefer VirtualBox because I can move around VMs to Linux.

First time hearing about UTM, I decided not to go the M1 route because I need to run X86 VMs, can it emulate x86 on apple silicon?

Re: QEMU 7.0

#42

Post by yepguy »

Macdougall wrote: post #20

Do you guys pronounce it Q-Emu (as in the letter Q then emu as in emulator) or kweemoo?

Q-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.

Re: QEMU 7.0

#43

Post by pm215 »

jaclaz wrote: post #40
pm215 wrote: post #30

Earlier quoted context omitted.

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.

I 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 ma…

Yes, 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.)

Re: QEMU 7.0

#44

Post by anderspitman »

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.

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.

Re: QEMU 7.0

#45

Post by ori_b »

anderspitman wrote: post #44

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?

Use the IRC channel. Or the mailing list.

Re: QEMU 7.0

#46

Post by _vdpp »

anderspitman wrote: post #44

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.…

A QEMU book would be _very_ welcome.

Re: QEMU 7.0

#48

Post by anderspitman »

cpach wrote: post #23
rubyist5eva wrote: post #21

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.

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. See https://wiki.qemu.org/Features/HVF

I'd be very interested to hear experiences from people working with QEMU+HVF. I only have Linux/Windows devices to test on.

Re: QEMU 7.0

#49

Post by binwiederhier »

synergy20 wrote: post #38
binwiederhier wrote: post #14

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!

In this case, I hope your company consider some donations to this wonderful project, good for your business down the road too.

That 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.

Re: QEMU 7.0

#50

Post by gspr »

_8j50 wrote: post #39
cpach wrote: post #28

Earlier quoted context omitted.

“Does anyone know if there are Qemu wrappers with a nice UI/UX?” What operating system are you on?

Linux and MacOS

Linux: virt-manager. Although it doesn't expose all the incredible features of qemu, it's great for "average" use cases.
Post reply on HN