d
you please suggest a possible solution?
Regards,
Dmitrii Bundin
On Thu, Jul 8, 2021 at 12:13 PM Peter Maydell wrote:
> The more usual way to connect to the QEMU gdbstub is to
> have it listen on a TCP port and connect gdb to that. You can
> do that by passing QEMU "-s -S" (and no -gdb option), which will
> make it pause on startup and use the default TCP port
Thanks for the reply. Now it becomes much clearer.
Regards,
Dmitrii.
I have problems with sending shortcuts to the Ubuntu guest. Like Alt +
Tab, Ctrl + Alt + T, Alt + F4, etc... It's sent to the host instead
even though the QEMU window is active. Is there a way to
change/configure such behavior?
For example Alt + F4 closes the guest itself, not the active guest
win
It turned out that compiling QEMU with --enable-sdl option does the
desired hotkeys interception for the guest.
--
Regards,
Dmitrii
QEMU version 6.1.0
I have a QEMU configuration file qemu.cfg containing the following section:
[accel]
accel = "kvm"
So to run qemu I use the command
qemu-system-x86_64 -readconfig qemu.cfg -cpu host ubuntu.img
Is there a way to put -cpu host into the config file as well? I tried
[accel]
acce
QEMU version 6.1.0
I have a QEMU configuration file qemu.cfg containing the following section:
[accel]
accel = "kvm"
So to run qemu I use the command
qemu-system-x86_64 -readconfig qemu.cfg -cpu host ubuntu.img
Is there a way to put -cpu host into the config file as well? I tried
[accel]
acce
When debugging Linux Kernel running in QEMU with GDB it's not possible to
access the Kernel function located in .text.init. Example:
(gdb) disas start_kernel
Dump of assembler code for function start_kernel:
0x83160ff3 <+0>: Cannot access memory at address
0x83160ff3
Removi
> Could it be address space randomisation having an effect?
Not sure, since I explicitly disabled kaslr. I appended nokaslr in the GRUB
command line. With kaslr enabled it's not possible to access any of the
virtual address in the kernel space.
The thing is removing --enable-kvm -cpu host makes i
