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

QEMU v4.0.0 released

qemu.org

Post reply on HN
Print view View original

161–168 of 168 posts

Re: QEMU v4.0.0 released

#161

Post by yrro »

jolmg wrote: post #122
fulafel wrote: post #79

Earlier quoted context omitted.

There's a lot to be said for running qemu from the command line, vs the complexity and opaqueness of libvirt. For example you can put the invocation in a script and check it into version control, and it will work on anyone's Linux box. You can easily debug the config and be suire about what options qemu was given. Yes, there may be many switches in the invocation, but at least they are in one place, the invocation sy…

You're splitting the option value for -drive into multiple arguments. Here's an idea to fix that while keeping the same style: qemu-system-x86_64 \ -display none \ -m 2048 \ -serial stdio \ -drive "$(printf "%s" file=/export/cirros.qcow2, \ format=qcow2, \ if=virtio )"

If you don't mind using bash:

    args=(
     -display none
     -m 2048
     -serial stdio
    # -disabled-option
    )

    qemu-system-x86_64 "${args[@]}"
The array syntax means you can ditch the tedious backslashes and easily comment individual lines.

Re: QEMU v4.0.0 released

#162

Post by [deleted] »

yrro wrote: post #161
jolmg wrote: post #122

Earlier quoted context omitted.

You're splitting the option value for -drive into multiple arguments. Here's an idea to fix that while keeping the same style: qemu-system-x86_64 \ -display none \ -m 2048 \ -serial stdio \ -drive "$(printf "%s" file=/export/cirros.qcow2, \ format=qcow2, \ if=virtio )"

If you don't mind using bash: args=( -display none -m 2048 -serial stdio # -disabled-option ) qemu-system-x86_64 "${args[@]}" The array syntax means you can ditch the tedious backslashes and easily comment individual lines.

[deleted]

Re: QEMU v4.0.0 released

#163

Post by kashyapc »

yrro wrote: post #161
jolmg wrote: post #122

Earlier quoted context omitted.

You're splitting the option value for -drive into multiple arguments. Here's an idea to fix that while keeping the same style: qemu-system-x86_64 \ -display none \ -m 2048 \ -serial stdio \ -drive "$(printf "%s" file=/export/cirros.qcow2, \ format=qcow2, \ if=virtio )"

If you don't mind using bash: args=( -display none -m 2048 -serial stdio # -disabled-option ) qemu-system-x86_64 "${args[@]}" The array syntax means you can ditch the tedious backslashes and easily comment individual lines.

Ah, indeed. Thanks for the nice trick to avoid the tedium.

Re: QEMU v4.0.0 released

#164

Post by rcarmo »

selvakn wrote: post #73
rcarmo wrote: post #10

Earlier quoted context omitted.

I'm using it extensively, but as a build tool: https://github.com/multiarch/qemu-user-static (See https://taoofmac.com/space/blog/2019/04/21/2300 and https://github.com/insightfulsystems/alpine-python )

Same here. Use it to build tools targeting arm architecture (rpi, etc) on a x86_64 machine, that too in docker.

My experience is that building for ARMv7 is relatively quick, but ARMv6/armhf is MUCH slower. I have no idea why, really.

Will be trying ARM64 soon, as soon as I have a suitable development board.

Re: QEMU v4.0.0 released

#165

Post by jolmg »

yrro wrote: post #161
jolmg wrote: post #122

Earlier quoted context omitted.

You're splitting the option value for -drive into multiple arguments. Here's an idea to fix that while keeping the same style: qemu-system-x86_64 \ -display none \ -m 2048 \ -serial stdio \ -drive "$(printf "%s" file=/export/cirros.qcow2, \ format=qcow2, \ if=virtio )"

If you don't mind using bash: args=( -display none -m 2048 -serial stdio # -disabled-option ) qemu-system-x86_64 "${args[@]}" The array syntax means you can ditch the tedious backslashes and easily comment individual lines.

You're right about the ability to comment, but it doesn't save you from the tedious commas:

  drive_args=(
      file=/export/cirros.qcow2,
      format=qcow2,
      if=virtio
  )

  qemu_args=(
      -display none
      -m 2048
      -serial stdio
      -drive "$(printf "%s" "${drive_args[@]}")"
  )

  qemu-system-x86_64 "${qemu_args[@]}"
Personally, I prefer it with the backslashes if I don't need to comment.

Re: QEMU v4.0.0 released

#166

Post by planteen »

planteen wrote: post #71
rbanffy wrote: post #67

I always wanted (but never succeeded) in emulating SPARC guests using QEMU. Is there a comprehensive list of systems and hardware emulated? I suspect a lot of people in the HN crowd would be curious about emulating Alphas, even if for only running Genera. Having a collection of emulated Unix workstations is an upgrade in terms of space saved.

I got Debian for SPARC64 running under QEMU a few months ago. I wanted a big endian system for testing. I'll post the link on steps if I can find it. It was on GitHub IIRC.

My memory was faulty - I did MIPS on QEMU to get big endian.

The steps are here for posterity: https://github.com/kholia/mips-hacking

Re: QEMU v4.0.0 released

#167

Post by rstuart4133 »

I clicked on the story because of the major version number bump, then belatedly realised they had moved to time based version numbering. The major version number gets incremented every year.

So the version number is essentially meaningless now - the year of release (eg, QEMU v2019.0.0) would give you more information. I can't say I'm a fan.

Re: QEMU v4.0.0 released

#168

Post by kristianp »

drmpeg wrote: post #107
unixhero wrote: post #96

Earlier quoted context omitted.

Ooh really? That works?

Yes. Here's a screenshot of Netscape 4.76. http://www.w6rz.net/netscape.png That was with a Solaris 8 disk image that I found here: https://github.com/cclark64/qemu_solaris_sparc

Has anyone got a Modula-2 compiler for old Solaris versions? Then I can re-live the monochrome (2-color) xterm experience from the 90s.
Post reply on HN