Re: [hwloc-users] hwloc: Topology became empty, aborting!

2023-08-02 Thread Max R. Dechantsreiter
Correction: I have E5-2620v4, which is 8-core Broadwell. Please excuse my error earlier. On Wed, Aug 02, 2023 at 01:23:18PM +, Max R. Dechantsreiter wrote: > Hi Brice, > > Well, the VPS gives me a 4-core slice of an Intel(R) Xeon(R) > CPU E5-2620 node, which is Sandy Bridg

Re: [hwloc-users] hwloc: Topology became empty, aborting!

2023-08-02 Thread Max R. Dechantsreiter
a single hardware core and the hypervisor doesn't care > about emulating topology information correctly. > > Brice > > > > Le 02/08/2023 à 15:23, Max R. Dechantsreiter a écrit : > > Hi Brice, > > > > Well, the VPS gives me a 4-core slice of an Intel(R) Xeon(

[hwloc-users] hwloc: Topology became empty, aborting!

2023-08-02 Thread Max R. Dechantsreiter
Hello, On my VPS I tested my build of hwloc-2.9.2 by running lstopo: ./lstopo hwloc: Topology became empty, aborting! Segmentation fault On a GCP n1-standard-2 a similar build (GCC 12.2 vs. 13.2) seemed to work: ./lstopo hwloc/nvml: Failed to initialize with nvmlInit(): Driver Not Loaded

Re: [hwloc-users] hwloc: Topology became empty, aborting!

2023-08-02 Thread Max R. Dechantsreiter
so badly? > > Brice > > > > Le 02/08/2023 à 14:54, Max R. Dechantsreiter a écrit : > > Hello, > > > > On my VPS I tested my build of hwloc-2.9.2 by running lstopo: > > > > ./lstopo > > hwloc: Topology became empty, aborting! > > Segmentation