On Fri, Jun 25, 2021 at 7:40 PM Jiatong Shen wrote:
>
> Hello community,
>
> I have a disk with both logical and physical sector size being 4096. I have a
> qcow2 image which is built from a virtual machine has legacy 512 bytes sector
> size.
>
> when I do something like
>
> qemu-img convert -f
Hello community,
I have a disk with both logical and physical sector size being 4096. I have
a qcow2 image which is built from a virtual machine has legacy 512 bytes
sector size.
when I do something like
qemu-img convert -f qcow2 -O host_device disk device
turns out it will not work. mounting a
> This really isn't what the plugin API is intended for -- it's meant
>
> for tracing and similar sorts of "track what the guest is doing" activities.
>
> If you want to model an MMIO device, you're better off just writing a device
>
> model like any of the others in QEMU, I think: the APIs for doi
On Fri, 25 Jun 2021 at 10:25, Kevin Mambu wrote:
> In the scope of my Ph. D subject, I want to model a DMA-like mechanism for
> quick prototyping and evaluation, the plugin emulates an MMIO with
> Control/Status Registers. I am actually able to pass parameters to the
> Control/Status Registers
Thank you for you answer.
> Out of interest what is your use-case for this? The project has very
>
> deliberately avoided adding such an API for writing memory for plugins
>
> to avoid people attempting to bypass the GPL by doing things in plugins.
>
In the scope of my Ph. D subject, I want to mo
