Re: using bit-field to define a qom register

>If you mean the MemoryRegionOps read and write functions, Yes, I mean that. I understand that "MemoryRegionOps read and write functions, those work only with byte offsets." But, I must set a value into a qom register using C bit fields in the guest source code. If I use the extract32/deposit32 fun

Re: using bit-field to define a qom register

On Sun, 11 Jul 2021 at 09:12, Hiroko Shimizu wrote: > > >If you mean the MemoryRegionOps read and write functions, > Yes, I mean that. I understand that "MemoryRegionOps read and write > functions, those work only with byte offsets." > But, I must set a value into a qom register using C bit field

Qemu-kvm KDE VM steels my mouse

Hi All, Host Fedora 34 Xfce 4.14 qemu-kvm-5.2.0-8.fc34.x86_64 Guest: Fedora-KDE-Live-x86_64-34-1.2.iso Problem: my mouse is confined to the VM, unless I throw . But when I do so, KDE also logs me out and I have to log back into KDE every time and my mouse gets re-confined. This behav

Re: Open serial port to attach via GDB

Thanks for the reply. Now it becomes much clearer. Regards, Dmitrii.

Re: How can I expose qemu-guest-agent QMP capabilities to the qmp tcp server in qemu on the same TCP socket port?

A user on stackoverflow answered me that "proxying" is not implemented ( https://stackoverflow.com/questions/68162860/how-can-i-expose-qemu-guest-agent-qmp-capabilities-to-the-qmp-tcp-server-in-qemu), so I ask here for a confirmation: Is exposing 2 tcp ports the only way to communicate via TCP sock