Closed bretton closed 6 months ago
I think this can be closed, once we established that the current iteration works with disks >2TB (I didn't have any server to test this myself).
I had reverse situations where I couldn't run qemu packaged version with the right iso. Therefore, use the old, lightweight version of qemu
I had reverse situations where I couldn't run qemu packaged version with the right iso. Therefore, use the old, lightweight version of qemu
At Hetzner, simply using the qemu version provided by whatever they use as a package source (/what is installed by default) works ok - which to me is preferable to downloading some static binary off “the net”
In practice, we probably will have to provide options to use different versions of tooling depending on the hosting environment.
Do you happen to have problem reports with the current version of the script?
At Hetzner, simply using the qemu version provided by whatever they use as a package source (/what is installed by default) works ok - which to me is preferable to downloading some static binary off “the net”
In addition to Hetner, there are other common cloud providers (OVH, Vultr, DigitalOcean), on which you also need to somehow check the script.
Do you happen to have problem reports with the current version of the script?
Both of these reports seem to be completely unrelated to the version of qemu used though (one is about you not liking key based authentication, the other one about running qemu on systems without hw virtualization support).
At Hetzner, simply using the qemu version provided by whatever they use as a package source (/what is installed by default) works ok - which to me is preferable to downloading some static binary off “the net”
In addition to Hetner, there are other common cloud providers (OVH, Vultr, DigitalOcean), on which you also need to somehow check the script.
Certainly, but I assume we take that bit by bit based on user feedback (I assume that, eg, digital ocean also allows installing a recent version of qemu from a (somehow) trusted source).
At Hetzner, simply using the qemu version provided by whatever they use as a package source (/what is installed by default) works ok - which to me is preferable to downloading some static binary off “the net”
In addition to Hetner, there are other common cloud providers (OVH, Vultr, DigitalOcean), on which you also need to somehow check the script.
Certainly, but I assume we take that bit by bit based on user feedback (I assume that, eg, digital ocean also allows installing a recent version of qemu from a (somehow) trusted source).
You are based on the assumption that "the new packaged version of qemu will work as it should". I am based on the assumption that "a particular version of qemu will work as it should".
At Hetzner, simply using the qemu version provided by whatever they use as a package source (/what is installed by default) works ok - which to me is preferable to downloading some static binary off “the net”
In addition to Hetner, there are other common cloud providers (OVH, Vultr, DigitalOcean), on which you also need to somehow check the script.
Certainly, but I assume we take that bit by bit based on user feedback (I assume that, eg, digital ocean also allows installing a recent version of qemu from a (somehow) trusted source).
You are based on the assumption that "the new packaged version of qemu will work as it should". I am based on the assumption that "a particular version of qemu will work as it should".
(at least my) goal is to make this a viable solution for professional applications. This means, anything that is based on downloading some random binary off the net is a non-starter. There’s always room for extra options for people to replace binaries with whatever they prefer/might work for them (-q mystatidbinarycopiedfromsomewhere), but you can’t expect people doing serious business (the kind where you’re actually accountable what happens to your client’s data) to rely on a random binary downloaded from some obscure internet address.
And yes, this means that sometimes things will break when there is a qemu update. And then we will have to adapt.
continuity: this can be closed with a successful hetzner test over 2TB disk size
continuity: this can be closed with a successful hetzner test over 2TB disk size
marking closed, we have installs with larger disks at Xneelo which has similar setup to Hetzner servers
The source post links to a statically compiled qemu binary at
there is also a copy at
This binary is QEMU 2.2.0, the current version is 7.0.0, dated
Apr 19th 2022
.The command line parameters are:
Useful notes:
../../qemu-system-x86_64 -parameter value
bios-256k.bin
and must be set as parameter-bios bios-256k.bin
-k keymaps/en-us
if in same directory as bios files, and onlyen-us
has been tested-vnc 127.0.0.1:1
and then use SSH to proxy connect to VNC