Opened 9 years ago
Closed 4 years ago
#14249 closed defect (obsolete)
5.0.0_RC3-101495 : RTR3InitEx faild with rc=1018
| Reported by: | emanuele lombardi | Owned by: | |
|---|---|---|---|
| Component: | VM control | Version: | VirtualBox 4.3.28 |
| Keywords: | VirtualBox-5.0.0_RC3 rc=1018 RTR3InitEx | Cc: | |
| Guest type: | Linux | Host type: | Linux |
Description
Dear VM-errs,
I succesfully create and run my virtualbox VM (SLES12) on my Windows7 and on my SLES11SP3 (HP DL585G7, kernel 3.0.101-0.47.55)
Unfortunately the same VM doesn't boot on my Silicon Graphics UV2000 with 256 cores. It is a single image machine and it runs the same OS and kernel version of the HP DL585G7. I'm aware that UV2000 is a "unusual" machine, but I hope you will help me the same.
Since the guest VM properly runs on the DL582G7, I think there must be something wrong how virtualbox deals with the UV2000 (or viceversa, of course!)
To explore the problem I used on the UV2000 the lates virtual boxes I could download: 4.3.29-101478 and 5.0.0_RC3-101495
If I use VirtualBox-4.3.29-101478 at boot of the VM I get these kind of errors and the boot freezes:
BUG: soft lockup - CPU#3 stuck for 22s! [watchdog/3:21]
If I use VirtualBox-5.0.0_RC3-101495 things are worst since the booting phase not even starts and I get these messages:
RTR3InitEx failed with rc=1018 please try reinstalling Virtualbox
The virtual machine "lavoro7" has terminated unexpectedly during startup with exit code 1 (0x1)
Result Code: NS_ERROR_FAILURE (0x800004005) Component: MachineWrap Interface: Machine {.....}
I'll be greatful for any help, Emanuele
Here it follow the output of /proc/cpuinfo and lscpu on both the SLES11P3 machines:
DL585G7 (the one which works) : more /proc/cpuinfo : processor : 0 vendor_id : AuthenticAMD cpu family : 16 model : 9 model name : AMD Opteron(tm) Processor 6128 stepping : 1 cpu MHz : 1995.042 cache size : 512 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 8 apicid : 16 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 5 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdp e1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc extd_apicid amd_dcm pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_l egacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt nodeid_msr npt lbrv svm_lock nrip_save pausefilter bogomips : 3990.08 TLB size : 1024 4K pages clflush size : 64 cache_alignment : 64 address sizes : 48 bits physical, 48 bits virtual power management: ts ttp tm stc 100mhzsteps hwpstate DL585G7 (the one which works) : lscpu : Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 16 On-line CPU(s) list: 0-15 Thread(s) per core: 1 Core(s) per socket: 8 Socket(s): 2 NUMA node(s): 4 Vendor ID: AuthenticAMD CPU family: 16 Model: 9 Stepping: 1 CPU MHz: 1995.042 BogoMIPS: 3990.14 Virtualization: AMD-V L1d cache: 64K L1i cache: 64K L2 cache: 512K L3 cache: 5118K NUMA node0 CPU(s): 0,2,4,6 NUMA node1 CPU(s): 8,10,12,14 NUMA node2 CPU(s): 9,11,13,15 NUMA node3 CPU(s): 1,3,5,7 UV2000 (the faulty one): more /proc/cpuinfo : processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 45 model name : Intel(R) Xeon(R) CPU E5-4640 0 @ 2.40GHz stepping : 7 microcode : 1809 cpu MHz : 2400.092 cache size : 20480 KB physical id : 0 siblings : 8 core id : 0 cpu cores : 8 apicid : 0 initial apicid : 0 fpu : yes fpu_exception : yes cpuid level : 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_t sc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer xsave avx lahf_lm ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid bogomips : 4800.18 clflush size : 64 cache_alignment : 64 address sizes : 46 bits physical, 48 bits virtual power management: UV2000 (the faulty one): lscpu : Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 256 On-line CPU(s) list: 0-255 Thread(s) per core: 1 Core(s) per socket: 8 Socket(s): 32 NUMA node(s): 32 Vendor ID: GenuineIntel CPU family: 6 Model: 45 Stepping: 7 CPU MHz: 2400.092 BogoMIPS: 4800.56 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 256K L3 cache: 20480K NUMA node0 CPU(s): 0-7 NUMA node1 CPU(s): 8-15 NUMA node2 CPU(s): 16-23 NUMA node3 CPU(s): 24-31 NUMA node4 CPU(s): 32-39 NUMA node5 CPU(s): 40-47 NUMA node6 CPU(s): 48-55 NUMA node7 CPU(s): 56-63 NUMA node8 CPU(s): 64-71 NUMA node9 CPU(s): 72-79 NUMA node10 CPU(s): 80-87 NUMA node11 CPU(s): 88-95 NUMA node12 CPU(s): 96-103 NUMA node13 CPU(s): 104-111 NUMA node14 CPU(s): 112-119 NUMA node15 CPU(s): 120-127 NUMA node16 CPU(s): 128-135 NUMA node17 CPU(s): 136-143 NUMA node18 CPU(s): 144-151 NUMA node19 CPU(s): 152-159 NUMA node20 CPU(s): 160-167 NUMA node21 CPU(s): 168-175 NUMA node22 CPU(s): 176-183 NUMA node23 CPU(s): 184-191 NUMA node24 CPU(s): 192-199 NUMA node25 CPU(s): 200-207 NUMA node26 CPU(s): 208-215 NUMA node27 CPU(s): 216-223 NUMA node28 CPU(s): 224-231 NUMA node29 CPU(s): 232-239 NUMA node30 CPU(s): 240-247 NUMA node31 CPU(s): 248-255
Change History (4)
comment:2 by , 9 years ago
The above error (SUPR0GipMap: failed rc=-1018) seems to be related to the allocation of memory. This could help since my UV2000 has a very large memory of 1024Gb. It might be possible my RAM size is above some VirtualBox hardcoded memory limit? I had a look at https://www.virtualbox.org/browser/vbox/trunk/src/VBox/HostDrivers/Support/SUPDrv.cpp and https://git.ipxe.org/mirror/virtualbox/.git/blame/74cb3b17a7cd5fa4c4a9a8ae62ddd9517433aff3:/src/VBox/HostDrivers/Support/SUPDrv.c but I'm not good enough....
comment:3 by , 9 years ago
Shouldn't be a memory size issue... VirtualBox has been tested on a system with 1TB of RAM a while ago (otherwise we wouldn't list 1TB as the memory size limit, it should be higher).
comment:4 by , 4 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
I noticed that when the above error "RTR3InitEx failed with rc=1018 please try reinstalling Virtualbox" occur, in /var/log/messages I see: