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

QEMU 6.0

qemu.org

Post reply on HN
Print view View original

11–20 of 90 posts

Re: QEMU 6.0

#12

Post by my123 »

Liquid_Fire wrote: post #3
simojk wrote: post #2

Does QEMU support TSO when used with Apple Silicon?

Doesn't that require installing custom kernel extensions to enable, as there is no API to enable it?

Setting ACTLR_EL1 in a virtual machine (through Hypervisor.framework) is an option.

Re: QEMU 6.0

#13

Post by rijoja »

hulitu wrote: post #4

Are there any option for emulation of 68k machines ?

yeah I was able to run Debian's m68k version in QEMU quite successfully with almost no hassle.

Re: QEMU 6.0

#14

Post by tofflos »

Semi-related question... I recently spent an evening trying to familiarize myself with virtualization tooling and my initial impression was that the CLI experience for kvm and hyper-v was rather clunky compared to let's say docker, gcloud, ignite and kubectl. Also a lot of the learning material seems to be oriented towards GUI. It could be that I just haven't spent enough time with kvm and hyper-v. I've spent a LOT of time on those other tools so maybe I'm just more used to them.

Is there good CLI tooling available for virtualization? I would say that I'm looking for the "on-prem" experience where I start by configuring a virtual network, download some unmodified ISOs directly from the operating system vendor, provision my headless virtual machines with a combination of Powershell, Answer files, Bash and Kickstart. I then provide services like DHCP and DNS using my virtual machines rather than the built-in mechanism provided by the virtualization tooling.

Re: QEMU 6.0

#15

Post by arsome »

tofflos wrote: post #14

Semi-related question... I recently spent an evening trying to familiarize myself with virtualization tooling and my initial impression was that the CLI experience for kvm and hyper-v was rather clunky compared to let's say docker, gcloud, ignite and kubectl. Also a lot of the learning material seems to be oriented towards GUI. It could be that I just haven't spent enough time with kvm and hyper-v. I've spent a LOT o…

You're comparing VM tooling with container tooling, there's going to be substantial differences in level of abstraction. I might suggest you look at the libvirt platform, it's a wrapper around KVM essentially, but there's virsh which I've found reasonably straight forward to work with.

Re: QEMU 6.0

#17

Post by swiley »

tofflos wrote: post #14

Semi-related question... I recently spent an evening trying to familiarize myself with virtualization tooling and my initial impression was that the CLI experience for kvm and hyper-v was rather clunky compared to let's say docker, gcloud, ignite and kubectl. Also a lot of the learning material seems to be oriented towards GUI. It could be that I just haven't spent enough time with kvm and hyper-v. I've spent a LOT o…

Just run qemu-system-blah. I thought the CLI for that was pretty intuitive.

Re: QEMU 6.0

#18

Post by kevindurb »

tofflos wrote: post #14

Semi-related question... I recently spent an evening trying to familiarize myself with virtualization tooling and my initial impression was that the CLI experience for kvm and hyper-v was rather clunky compared to let's say docker, gcloud, ignite and kubectl. Also a lot of the learning material seems to be oriented towards GUI. It could be that I just haven't spent enough time with kvm and hyper-v. I've spent a LOT o…

You should try out vagrant, let’s you have a config file for your vm and you can choose different providers like libvirt, virtualbox, etc

Re: QEMU 6.0

#19

Post by viraptor »

tofflos wrote: post #14

Semi-related question... I recently spent an evening trying to familiarize myself with virtualization tooling and my initial impression was that the CLI experience for kvm and hyper-v was rather clunky compared to let's say docker, gcloud, ignite and kubectl. Also a lot of the learning material seems to be oriented towards GUI. It could be that I just haven't spent enough time with kvm and hyper-v. I've spent a LOT o…

You're looking at different abstraction levels. I'd make comparisons like: kvm:unshare, qemu-system:docker, kube:virsh.

If your want high level networking stuff, use virsh or virt-manager GUI. Or maybe proxmox if you want a whole distribution for it.

Re: QEMU 6.0

#20

Post by tenebrisalietum »

tofflos wrote: post #14

Semi-related question... I recently spent an evening trying to familiarize myself with virtualization tooling and my initial impression was that the CLI experience for kvm and hyper-v was rather clunky compared to let's say docker, gcloud, ignite and kubectl. Also a lot of the learning material seems to be oriented towards GUI. It could be that I just haven't spent enough time with kvm and hyper-v. I've spent a LOT o…

I had some QEMU VMs running for a while on a home server that were more or less started by command line. You can specify everything as command line parameters.

I wrote a script that pulled some info from a sourced-in bash "config file" for a given VM (such as amount of CPUs, RAM, and where the disks were), executed the appropriate ip commands to create the taps needed for network access (including a private inter-VM network), and then built/ran the long QEMU command with it in a screen session.

Which file is the ISO for the virtual CD ROM is just another QEMU command line parameter.

I had my own bind running in a VM and created a view on the same subnet as the private VM network. Since this was only a few VMs I didn't bother with DHCP, I just statically assigned IPv4s. I used VNC to setup the OS in them.

Post reply on HN