VirtualBox hangs after mb/cpu upgrade

[jim-fitz]

I just lost a mb on an old system, so had to upgrade it and replace the cpu. I enabled intel
virtualization in the bios as part of the upgrade. NO other changes -- still booting from
the same disk, same os, same guest os-es, everything. VirtualBox 4.3.8 was installed at that point.

I had trouble bringing up a guest, but I figured that there might be some issues with running the old
kernel modules.

I reinstalled. It dies. I upgraded to 5.1.6. After getting that to install, it hangs when I run VirtualBox. 100% cpu utilization on all cpus. No clue where to go from here.

This may seem like more than one question. It is not. I would really prefer to go forward to 5.1.6,
but provide the information on the 4.3.8 version as there may be a single problem underlying both failures.

More info will be in an attachment. When I try to submit, it tells me that 'You must be a member for 1 days and have 1 posts before you can post urls.'. I have draft copies of the failure running back days, and I see no urls in my text. I even went so far as to split ip addresses so they didn't look like ip addresses.

[socratis]

I added verbatim your .txt file and I added some "code" tags. There's no need to download simple text

---

I just lost a mb on an old system, so had to upgrade it and replace the cpu. I enabled intel virtualization in the bios as part of the upgrade. NO other changes -- still booting from the same disk, same os, same guest os-es, everything. VirtualBox 4.3.8 was installed at that point.

I had trouble bringing up a guest, but I figured that there might be some issues with running the old kernel modules.

I reinstalled. The installation dies, as near as I can tell while building the modules. By 'die', I mean the machine crashes. If I do the install on the base console, I see the following:

Code: Select all

!!Assertion failed!!
Expression: (null)
Location: /tmp/vbox.o/SUPDrv.c(5374) supdrvGipCpuIndexFromCpuid
int3: 0000 [#1] SMP

The failed install leaves me with /lib/modules/3.10.17/misc/vboxdrv.ko, and no other modules. The last lines in the vbox-install.log file are:

Code: Select all

  (cat /dev/null;   echo kernel//tmp/vbox.0/vboxdrv.ko;) > /tmp/vbox.0/modules.order
  make -f /usr/src/linux-3.10.17/scripts/Makefile.modpost
    find /tmp/vbox.0/.tmp_versions -name '*.mod' | xargs -r grep -h '\.ko$' | sort -u | sed
         's/\.ko$/.o/' | scripts/mod/modpost   -i /usr/src/linux-3.10.17/Module.symvers
         -I /tmp/vbox.0/Module.symvers  -o /tmp/vbox.0/Module.symvers -S -w -s -T -
    gcc -Wp,-MD,/tmp/vbox.0/.vboxdrv.mod.o.d  -nostdinc -isystem 
         /usr/lib64/gcc/x86_64-slackware-linux/4.8.2/include -I/usr/src/linux-3.10.17/arch/x86/include
         -Iarch/x86/include/generated  -Iinclude -I/usr/src/linux-3.10.17/arch/x86/include/uapi
         -Iarch/x86/include/generated/uapi
    ld -r -m elf_x86_64 -T /usr/src/linux-3.10.17/scripts/module-common.lds --build-id
         -o /tmp/vbox.0/vboxdrv.ko /tmp/vbox.0/vboxdrv.o /tmp/vbox.0/vboxdrv.mod.o

All of the files in /tmp/vbox.0 have zero length.

I figured my current 4.3.8 was a little old, and since 5.1.6 is available, I decided to upgrade. I installed 5.1.6. Several times. I finally got it to install with no problems when I did it without X running. However, whenever I run VirtualBox the system hangs. I even removed and started with fresh .VirtualBox and 'VirtualBox VMs' directories. Same thing. Depending upon the window manager I run, I get an outline of the VirtualBox window, an outline filled in with blue, of a mostly-filled-in window. However, in all cases, CPU utilization climbs through the roof (100% on all cpus), and I am required to reboot the machine. Nothing shows in any system log at this point.

I have the following in VBoxSVC.log:

Code: Select all

VirtualBox XPCOM Server 5.1.6 r110634 linux.amd64 (Sep 12 2016 18:31:19) release log
00:00:00.022863 main     Log opened 2016-10-07T20:39:33.563475000Z
00:00:00.022865 main     Build Type: release
00:00:00.022868 main     OS Product: Linux
00:00:00.022868 main     OS Release: 3.10.17
00:00:00.022869 main     OS Version: #1 SMP Wed Oct 23 16:28:33 CDT 2013
00:00:00.022889 main     DMI Product Name: All Series
00:00:00.022894 main     DMI Product Version: System Version
00:00:00.022958 main     Host RAM: 64251MB total, 62287MB available
00:00:00.022961 main     Executable: /opt/VirtualBox/VBoxSVC
00:00:00.022961 main     Process ID: 11433
00:00:00.022962 main     Package type: LINUX_64BITS_GENERIC
00:00:00.023671 main     IPC socket path: /tmp/.vbox-root-ipc/ipcd
00:00:00.146519 nspr-2   VirtualBox: object creation starts
00:00:00.148434 nspr-2   Home directory: '/home/local/root/.VirtualBox'
00:00:00.183910 nspr-2   Successfully initialised host USB using sysfs
00:00:00.199354 nspr-2   NAT: resolv.conf: nameserver 192 . 168 . 1 . 200
00:00:00.199374 nspr-2   HostDnsMonitor: old information
00:00:00.199377 nspr-2     no server entries
00:00:00.199380 nspr-2     no domain set
00:00:00.199381 nspr-2     no search string entries
00:00:00.199383 nspr-2   HostDnsMonitor: new information
00:00:00.199384 nspr-2     server 1: 192 . 168 . 1 . 200
00:00:00.199386 nspr-2     domain: fitzrandolph.com
00:00:00.199388 nspr-2     search string 1: fitzrandolph . com
00:00:00.199393 nspr-2   HostDnsMonitorProxy::notify
00:00:00.203198 nspr-2   VD: VDInit finished
00:00:00.215704 nspr-2   VirtualBox: object created
00:00:45.306689 main     VirtualBox: object deletion starts

and in selectorwindow.log:

Code: Select all

VirtualBox GUI VM Selector Window 5.1.6 r110634 linux.amd64 (Sep 12 2016 18:31:19) release log
00:00:01.569334 Log opened 2016-10-07T20:39:33.841495000Z
00:00:01.569334 Build Type: release
00:00:01.569336 OS Product: Linux
00:00:01.569336 OS Release: 3.10.17
00:00:01.569337 OS Version: #1 SMP Wed Oct 23 16:28:33 CDT 2013
00:00:01.569344 DMI Product Name: All Series
00:00:01.569348 DMI Product Version: System Version
00:00:01.569384 Host RAM: 64251MB total, 62284MB available
00:00:01.569386 Executable: /opt/VirtualBox/VirtualBox
00:00:01.569386 Process ID: 11405
00:00:01.569387 Package type: LINUX_64BITS_GENERIC
00:00:01.569397 Qt version: 5.6.1
00:00:01.662754 GUI: UIMediumEnumerator: Medium-enumeration started...
00:00:01.883082 GUI: UIMediumEnumerator: Medium-enumeration finished!

So, right now I can't go back to 4.3.8, the install dies. I can't go forward to 5.1.6, it hangs after coming up. Where do I go from here? Is this a BIOS incompatability? A cpu incompatability? Something else? I don't care if I go back or forward, just to something that runs. Willing to take any ideas.

Code: Select all

distribution:  Slackware 14.1
uname -a:  Linux vorlich 3.10.17 #1 SMP Wed Oct 23 16:28:33 CDT 2013 x86_64 Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz GenuineIntel GNU/Linux
qt:  4.8.5
sdl:  1.2.15

/proc/cpuinfo contains:
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 79
model name      : Intel(R) Core(TM) i7-6800K CPU @ 3.40GHz
stepping        : 1
microcode       : 0xb00001a
cpu MHz         : 3400.000
cache size      : 15360 KB
physical id     : 0
siblings        : 12
core id         : 0
cpu cores       : 6
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 20
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_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3
                  fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx
                  f16c rdrand lahf_lm abm 3dnowprefetch ida arat epb xsaveopt pln pts dtherm tpr_shadow vnmi
                  flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx smap
bogomips        : 6796.59
clflush size    : 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:

(and another 11 copies, one per each cpu, available on request).

This may seem like more than one question. It is not. I would really prefer to go forward to 5.1.6, but provide the information on the 4.3.8 version as there may be a single problem underlying both failures.