Visual Studio profiling not working on VirtualBox 5

[Willshak]

Visual Studio (2013, ...) did not support CPU sampling in VBox 4 and earlier (see https://www.virtualbox.org/ticket/12495), and it seems it still doesn't work in VBox 5.0.4 (Win7 x64 host, Win 2008 R2 x64 guest, paravirtualization = hyperv, HPET on):

Profiling started.
Profiling process ID 3984 (Envobi.AE.Demo).
Process ID 3984 has exited.
Data written to C:\Projects\AE\Envobi.AE.Demo150922.vsp.
Profiling finished.
PRF0025: No data was collected.
Profiling complete.

Do you know if this is supposed to be working in VBox 5, or when it might get addressed?

Thanks,
Kristian

[KelvinSmith]

Enable

Code: Select all

Collect .NET object allocation information

under the property pages:

1. In Performance Explorer, right-click the performance session, and then click Properties.
2. On the Performance Session Property Pages dialog box, click the General tab, and select the Collect .NET object allocation information check box.
3. To collect .NET object lifetime data, select the Also collect .NET object lifetime information check box.

[Willshak]

Thanks for responding.

I've now tried the above, but get (almost) the same result:

Profiling started.
Profiling process ID 4780 (Envobi.OperationOverhead).
Process ID 4780 has exited.
Data written to C:\Projects\Envobi.Snippets\Envobi.OperationOverhead150924(1).vsp.
Profiling finished.
File contains no data buffers
File contains no data buffers
Analysis failed
Profiling complete.


Any other ideas on how to get CPU Sampling to work in VS under VirtualBox 5?

Thanks,
Kristian

[michaln]

If this is about emulating/exposing performance monitoring MSRs then there has been no change in that area in VirtualBox 5.0. Did something or someone give you an impression that there was?

As to when it might get addressed, hard to say. No customer ever asked for it so it's on an extremely long list of "would be nice to have" features.

[Willshak]

It was more of a hope on my side that one of the VB5 hyper-v or timer additions would allow Visual Studio to do CPU sampling as if VB5 was a physical machine - it sounds like that's not the case then unfortunately.

Cheers,
Kristian

[michaln]

Nope, sorry. Those two are pretty much completely unrelated.