On Sat, 14 Aug 2021 at 08:24, lejeczek wrote:
> -> $ qemu-img create -f qcow2 -b -o
> encrypt.key-secret=3fd57349-3671-4cf2-ab00-f13b8ba00a4d
> /00.GLUSTER-mnt/VMs3/enc.locallan.qcow2 -F qcow2
> ./enc.locallan.qcow2.bkp
> qemu-img: Invalid image size specified. You may use k, M, G,
> T, P or E
LS,
Suppose I want to simulate, using qemu, a Ryzen znver3 processor, what
-cpu flag do I set?
The current list for qemu does not include any Ryzen/Threadripper cpu.
So, I can optimize code using -mtune of -march for gcc, but these flags
do not correspond with qemu's processor list.
Hi,
Thanks for your time. That is indeed what I am looking for yes, but
directFB hasn't been developed for 6 years now. And from reading about
the topic, SDL was buggy and had some issues. (some other project tried
to do the same with only SDL that directFB did)
From what I can understand,
Dear Pavel,
Thank you again for the answers.
I had another question -
How is it possible to just use the request id while recording and use
it during replay? Don't we have to record other parameters of the disk
I/O request (like offset, bytes, iov buffer etc.) ?
Best Regards,
Arnabjyoti Kalita
Hi guys.
I am trying to backup qcow2s which are luks encrypted but I
fail and I wonder if it's my syntax being crooked or
something is not working in qemu(-img).
Non-encrypted qcow2 works fine and I only add encryption
bits to cmd line, here:
-> $ qemu-img create -f qcow2 -b -o
On 11/08/2021 23.38, Kjell via wrote:
Howdy,
I hate to ask stupid questions in the wrong places, but I just can't find
anything and it puzzles me. Forgive me any ignorance too please.
Is it possible, or would it be, to be able to run qemu (qemu-kvm) without X
in the framebuffer using the
