Just tried kvm-61. Ran up an existing, well-used, VM image. kvm-intel
crashed instantly. First KVM problem ever in several months of use.
(Haven't told the VMWare-huggers at work yet. They tend towards
superciliousness in respect of open source virtualisation solutions.)
Standardish Slackware
While we tried to make debugging inside the guest work, this
was never really tested, so it's likely broken. I'll try to
look at what it will take to make it work; I don't think there's
much needed.
That sounds encouraging -- I had imagined there might be some
impossibility factor in sharing
Can hardware breakpoints be set (and trapped, and handled) inside a guest
OS (specifially Windows XP2)?
I noticed the other day that software (malicious code, in fact) packed with
the EXE compressor PELock won't run under QEMU+KVM. I guessed that this was
because h/w breakpoints aren't being
[making Windbg's serial protocol work between two VMs]
Instead you might run in parallel to the VM a script
that does while(1) kill -SIGIO vm_pid.
The first 'kill -SIGIO' kills the whole VM instantly.
kvm-55 with its own kernel module.
G'day folks.
Apologies if this is a FAQ. Is there any way to get Windbg working between
two Windows guests? I have recently switched from QEMU+KQEMU to QEMU/KVM
(better speed and a Vista-ready BIOS got me interested). I never did get
Windbg working at all with QEMU+KQEMU. Now I am rather closer
