Connecting Kemper Profiling Amplifier To VM Aborts the VM

[Janne Rönkkö]

Connecting Kemper Profiling Amplifier (KPA) ​http://www.kemper-amps.com/ via USB to a virtual machine aborts the VM.

I have tried with both Linux and Windows guests. No problems when connecting KPA to Linux or Windows machine directly.

Nothing is written to VBox.log when KPA is connected to VM. The VM just shuts down and the state in VirtualBox GUI becomes "Aborted".

In the attached VBox.log you can see bootup of Kubuntu 14.04 VM. After the VM had booted up, I connected KPA to it (nothing written to VBox.log at this point).

In the lsusb-kpa.txt you can see the output of command lsusb -v -d 133e:0001

[Janne Rönkkö]

Here is a bit more info (I'm using Archlinux with systemd):

$ coredumpctl dump 24024
           PID: 24024 (VirtualBox)
           UID: 1000 (janne)
           GID: 1000 (janne)
        Signal: 6 (ABRT)
     Timestamp: Sun 2015-08-02 07:32:32 EEST (9s ago)
  Command Line: /usr/lib/virtualbox/VirtualBox -startvm Kubuntu 14.04
    Executable: /usr/lib/virtualbox/VirtualBox
 Control Group: /user.slice/user-1000.slice/session-c1.scope
          Unit: session-c1.scope
         Slice: user-1000.slice
       Session: c1
     Owner UID: 1000 (janne)
       Boot ID: cc50a17845e14501ac93aacf0f393351
    Machine ID: a6bbd94b3bee24f47bde03a2000003e6
      Hostname: kafir
      Coredump: /var/lib/systemd/coredump/core.VirtualBox.1000.cc50a17845e14501ac93aacf0f393351.24024.1438489952000000
       Message: Process 24024 (VirtualBox) of user 1000 dumped core.
Refusing to dump core to tty.

The vbox-stdout.txt contains stdout from VirtualBox -startvm 'Kubuntu 14.04' command

Backtrace from generated coredump:

#0  0x00007f826002c528 in raise () from /usr/lib/libc.so.6
#1  0x00007f826002d93a in abort () from /usr/lib/libc.so.6
#2  0x00007f826006abb2 in __libc_message () from /usr/lib/libc.so.6
#3  0x00007f82600700fe in malloc_printerr () from /usr/lib/libc.so.6
#4  0x00007f82600708db in _int_free () from /usr/lib/libc.so.6
#5  0x00007f81ff7234aa in ?? () from /usr/lib/virtualbox/VBoxDD.so
#6  0x00007f8238a66b2b in ?? () from /usr/lib/virtualbox/VBoxVMM.so
#7  0x00007f8238a670b6 in ?? () from /usr/lib/virtualbox/VBoxVMM.so
#8  0x00007f8238a68a95 in PDMR3UsbCreateProxyDevice () from /usr/lib/virtualbox/VBoxVMM.so
#9  0x00007f82389abeeb in ?? () from /usr/lib/virtualbox/VBoxVMM.so
#10 0x00007f82389aceef in ?? () from /usr/lib/virtualbox/VBoxVMM.so
#11 0x00007f823893d03f in ?? () from /usr/lib/virtualbox/VBoxVMM.so
#12 0x00007f823893d48c in ?? () from /usr/lib/virtualbox/VBoxVMM.so
#13 0x00007f82389aae7a in ?? () from /usr/lib/virtualbox/VBoxVMM.so
#14 0x00007f825fcae19c in ?? () from /usr/lib/virtualbox/VBoxRT.so
#15 0x00007f825fd2840b in ?? () from /usr/lib/virtualbox/VBoxRT.so
#16 0x00007f82605a6354 in start_thread () from /usr/lib/libpthread.so.0
#17 0x00007f82600e0bfd in clone () from /usr/lib/libc.so.6

I have coredump file available but the FTP server referenced in wiki (https://www.virtualbox.org/wiki/Core_dump) does not work so I was unable to upload the coredump. Please let me know where I can upload the coredump file.

[Janne Rönkkö]

With VirtualBox 5.0.2 and newer Kemper OS (3.1.4) there is no crash anymore.

The previous Kemper OS version was 3.0.2