On Mon, 3 Mar 2008, Dan Price wrote: > On Sat 01 Mar 2008 at 01:32AM, Alan DuBoff wrote: >> It doesn't seem possible to run dtrace under VirtualBox, as it seems to >> reset the VDI it is run within. I've done some searching and nothing comes >> up for virtualbox and dtrace, on either the virtualbox site or >> opensolaris.org. >> > > I hit this too, Alan-- specifically > > dtrace -n fbt::: > > was bad news for me when run inside the VM. > > I passed this along to the virtualbox folks via one of our liasons. Hopefully > it will be fixed soon.
Dan, Thanks for the info, I'll try to follow up on the VM team side also. It's kinda moot for me, I'm trying to trace the ae driver, which fails under Indiana, but I found out that 1.5.6 has the e1000g rather than the pcn (at least per the Windows install, I haven't installed or run it though). I suspect 1.5.6 will use the e1000g when we get it for OpenSolaris. I would like to know how to do that though, and wasn't sure if that is possible. In theory it should be possible to trace down into the VB, shouldn't it? I admit I don't spend enough time with dtrace, and often use it on the command line to issolate out driver calls. I would like to know how to do that though, I'm sure that could be handy, from outside the VB. -- Alan DuBoff - Solaris x86 IHV/OEM Group _______________________________________________ dtrace-discuss mailing list [email protected]
