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. 1) Is there any ETA that it would work? 2) Is there a way to trace from the host into VirtualBox to see what is going on? This must be possible with the proper syntax, but I''m not sure. I have 2 different environments setup. 1) Indiana running 83a inside of VB, and 2) 83a with Indiana running inside of VB, if either would be preferable to have as the host. -- Alan DuBoff - Solaris x86 IHV/OEM Group
On Sat, 01 Mar 2008 01:32:56 -0800 (PST) Alan DuBoff <Alan.Duboff at Sun.COM> 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. > > 1) Is there any ETA that it would work? > > 2) Is there a way to trace from the host into VirtualBox to see what > is going on? This must be possible with the proper syntax, but I''m > not sure. > > I have 2 different environments setup. 1) Indiana running 83a inside > of VB, and 2) 83a with Indiana running inside of VB, if either would > be preferable to have as the host.Have you tried specifying the execname of the VB process when writing your D script? That''s the first thing that springs to mind. James C. McPherson -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog
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. -dp -- Daniel Price - Solaris Kernel Engineering - dp at eng.sun.com - blogs.sun.com/dp
On Sun, 2 Mar 2008, Adam Leventhal wrote:> Hi Alan, > > This is the first I''ve heard of it. You should file a bug. > > AdamI will do that today, I''m just heading into the office and need to get to a meeting. This afternoon I will do that. -- Alan DuBoff - Solaris x86 IHV/OEM Group
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