Panda record/replay on nested vm fails with assertion error about panda

[AndrewFasano]

I don't think the issue is the nested VM setup, I suspect record and replay is hitting some edge cases in windows 10 boot. Boot is generally a stress test of record and replay since lots of hardware interactions happen that the RR system has to get perfectly right. Most of our work on and testing of PANDA's RR system was done long before Windows 10 was out (IIRC we tested booting windows XP and maybe windows 7 in addition to a few linux distros and got those working).

Even for non-RR uses, getting Windows 10 to work well under panda can be a bit of a pain - you can find some discussion in our slack, but it seems like you can do it if you disable lots of unnecessary services and OS options, but it's (unfortunately) not something that just works. When we eventually upgrade to a newer version of QEMU this should be a lot easier.

Depend on your goals (and if you already got Windows 10 working well under normal panda use), I'd recommend either:

• Try to start your recording after boot with your Windows 10 guest
• Try an older version of Windows

[Phasip]

Thank you, this saves me the trouble of setting up a dedicated panda system!

Panda without replay works fine for my windows 10 guest (very slow, but this is expected)
The original issue was for a booted system - but what I want to do involves both networking and usb so maybe that was the culprit at that point.

I'll close this as there is already a task for newer QEMU.