HyperV: Synthetic Debugging device
Status from this message: Queued, thanks.
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest4 patches 1 replyApplied
- v24 patches 7 repliesSuperseded
- v14 patches 9 repliesSuperseded
Changes in v3 from the cover letter
Fixed review from Paolo changes from QLIST*RCU to non RCU
Patches in v3 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | hyperv: SControl is optional to enable SynIchw/ | +76 | 0 replies | |
| 2/4 | hyperv: Add definitions for syndbginclude/ target/ | +89 | 0 replies | |
| 3/4 | hyperv: Add support to process syndbg commandsdocs/ hw/ include/ +5 more | +451 | 0 replies | |
| 4/4 | hw: hyperv: Initial commit for Synthetic Debugging devicehw/ hw/ hw/ | +408 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [PATCH v3 0/4] HyperV: Synthetic Debugging device
This patchset adds support for the synthetic debugging device.
HyperV supports a special transport layer for the kernel debugger when running in HyperV.
This patchset add supports for this device so you could have a setup fast windows kernel debugging.
At this point of time, DHCP is not implmeneted so to set this up few things need to be noted.
The scenario I used to test is having 2 VMs in the same virtual network
i.e a Debugger VM with the NIC:
-nic tap,model=virtio,mac=02:ca:01:01:01:01,script=/etc/qemu-ifup
And it's IP is going to be static 192.168.53.12
And the VM we want to debug, to which we need to have the englightments
and vmbus configured:
-cpu host,hv-relaxed,hv_spinlocks=0x1fff,hv_time,+vmx,invtsc,hv-vapic,hv-vpindex,hv-synic,hv-syndbg \
-device vmbus-bridge \
-device hv-syndbg,host_ip=192.168.53.12,host_port=50000,use_hcalls=false \
-nic tap,model=virtio,mac=02:ca:01:01:01:02,script=/etc/qemu-ifup \
Then in the debuggee VM we would setup the kernel debugging in the following way:
If the VM is older than Win8:
* Copy the proper platform kdvm.dll (make sure it's called kdvm.dll even if platform is 32bit) bcdedit /set {GUID} dbgtransport kdvm.dll
bcdedit /set {GUID} loadoptions host_ip="1.2.3.4",host_port="50000",nodhcp bcdedit /set {GUID} debug on
bcdedit /set {GUID} halbreakpoint on
Win8 and late:
bcdedit /dbgsettings net hostip:7.7.7.7 port:50000 nodhcp
This is all the setup that is required to get the synthetic debugger configured correctly.
v3:
Fixed review from Paolo changes from QLIST*RCU to non RCU
Jon Doron (4):
hyperv: SControl is optional to enable SynIc
hyperv: Add definitions for syndbg
hyperv: Add support to process syndbg commands
hw: hyperv: Initial commit for Synthetic Debugging device
docs/hyperv.txt | 15 ++ hw/hyperv/Kconfig | 5 + hw/hyperv/hyperv.c | 352 ++++++++++++++++++++++++--- hw/hyperv/meson.build | 1 + hw/hyperv/syndbg.c | 402 +++++++++++++++++++++++++++++++ include/hw/hyperv/hyperv-proto.h | 52 ++++ include/hw/hyperv/hyperv.h | 58 +++++ target/i386/cpu.c | 2 + target/i386/cpu.h | 7 + target/i386/kvm/hyperv-proto.h | 37 +++ target/i386/kvm/hyperv-stub.c | 6 + target/i386/kvm/hyperv.c | 52 +++- target/i386/kvm/kvm.c | 76 +++++- 13 files changed, 1024 insertions(+), 41 deletions(-) create mode 100644 hw/hyperv/syndbg.c
Signature · 1 line
2.35.1