[Autogenerated] In order to get more insight into interrupt, an I R Q L S.
It's going to be useful.
To set up some remote channel debugging scenario where we have a host machine,
and a target machine,
we debugging where we can set breakpoints within the kernel or device drivers,
and So the target machine will be completely frozen up until now.
We've only done local co debugging which is very easy.
To set up but also its limited because we can't set up break point,
and we can't set a particular state of the system because the system,
is always moving and So I want to show you how to set up this
remote co debugging connection between a target,
and a host, assuming the target is a virtual machine.
In that case, the setting, up is usually fairly straight forward.
To do First, we need to go, to the target the thing,
that You would like to debug the actual machine,
the actual virtual machine.
In this case, open, an elevated command window,
and set, up debugging using the network.
This always works with virtual machines.
So this is the command line, to set.
We need to specify the IP of the host where the debugger is the port we'd
like to use on the host which should be some available.
Port and then an optional key, that we can specify as a way,
to secure, the communication between the target.
And and the host, and to make that connection unique.
If we specify a key,
then the command will take it otherwise it will generate a key for us.
And So then we need to restart the system because we
first have to restart the system one.
So that these settings can take effect on the host system.
On the other hand, we just need to launch, win debug usually elevated.
That's going to be the safest thing, to do and then select network,
debugging, and use the same port key as we set up on the target.
And Assuming everything goes well, we'll get a connection.
So let's see an example of that in, in practice