Hi all, That's the exactly use case we've intended for when we've wrote this patch and have tested it as well. On my tests the patch worked for both 32 and 64 bit machines for Windows Server 2003, 2008 and 2012 and it seemed to be working just fine. I've also benchmarked it against the good old char device and it was superior on a scale of magnitude. Feel free to ask me if you encounter any issues and I'll gladly respond.
Itamar, Guardicore On Mon, Apr 4, 2016 at 3:48 PM, Sameeh Jubran <sam...@daynix.com> wrote: > Hello All, > > I've tested windows live debugging using the Firewire device and it seems > to be good. > > Test case scenario: > Kernel-Mode Debugging over a 1394 as detailed in: > https://msdn.microsoft.com/en-us/library/windows/hardware/ff556866(v=vs.85).aspx > . > > Setup: > Two separate VMs, both running Windows 2012 X64. One as Host VM ( > which runs the debugger ) and the other as Target VM ( which is being > debugged ). > > Qemu Command line: > > On the Host VM: > -chardev socket,id=serial10,path=/tmp/debug-serial2,server,nowait \ > -device ohci-1394,chardev=serial10,idserial10 > > On the Target VM: > -chardev socket,id=serial10,path=/tmp/debug-serial2 \ > -device ohci-1394,chardev=serial10,idserial10 > > Results: > I've successfully connected to the Target VM using WindbgX64 and ran basic > debugging functions such as "Break" and "stack trace". > Moreover I've successfully viewed live trace output from virtio-net driver > while running Iperf test and ping. > > Tested-by: Sameeh Jubran <sam...@daynix.com> > > > ------ Original Message ------ > From: "Ladi Prosek" <lpro...@redhat.com> > To: qemu-devel@nongnu.org > Cc: peter.mayd...@linaro.org; "Ladi Prosek" <lpro...@redhat.com>; > ita...@guardicore.com; afaer...@suse.de; itamar.t...@gmail.com > Sent: 3/17/2016 10:11:33 AM > Subject: Re: [Qemu-devel] [PATCH] add 1394 OHCI device > > Just a friendly ping after two weeks of silence. >> >> Thanks, >> Ladi >> >> >> >
