You are not logged in.

#1 2017-04-07 05:48:37

Hacksign
Member
Registered: 2012-07-30
Posts: 131

VirtualBox caused system hang-up.

I'm sorry for this thread, as I can not offer any log to indicate why this happened.

If I just execute command VirtualBox in my shell, I can get the GUI front end of virtualbox.
But system will hang-up as long as I start any virtual machine.
Time point of system hang-up is the virtual machine's black window appears.
Anyone knows why this happend ?

Here is somthing u may want to know:

hacksign@XSign [13:41:04] : ~ 
>> pacman -Q|grep -i virtualbox
virtualbox 5.1.18-1
virtualbox-guest-iso 5.1.18-1
virtualbox-host-modules-arch 5.1.18-3
hacksign@XSign [13:45:35] : ~ 
>> lsmod | grep -i vbox
vboxnetflt             28672  0
vboxnetadp             28672  0
vboxpci                24576  0
vboxdrv               385024  3 vboxnetadp,vboxnetflt,vboxpci

And I cant get any useful information with command 'dmesg -w' and the stdout of my shell which VirtualBox command is executed.
As the system is dead, I can get any log....
----------------------------------------Below is added 2017-04-19 UTC+0--------------------------------------------------
well as tom.ty89 said, system without VT-x/AMD-V is all right.
so, this seems like a virtualization problem.
anyone has same problem like me ?

Last edited by Hacksign (2017-04-19 06:26:38)

Offline

#2 2017-04-07 10:05:02

tom.ty89
Member
Registered: 2012-11-15
Posts: 897

Re: VirtualBox caused system hang-up.

Does it hang if you boot a (32-bit) system with VT-x/AMD-v option in virtualbox disabled?

Offline

#3 2017-04-07 10:58:12

Hacksign
Member
Registered: 2012-07-30
Posts: 131

Re: VirtualBox caused system hang-up.

tom.ty89 wrote:

Does it hang if you boot a (32-bit) system with VT-x/AMD-v option in virtualbox disabled?

No, everything all right if I boot an system with out VT-x/AMD-v option under 'settings -> system -> hardware accelerate'.
BTW, I have enabled Intel VT-d in my BIOS.

Offline

#4 2017-04-19 06:24:37

Hacksign
Member
Registered: 2012-07-30
Posts: 131

Re: VirtualBox caused system hang-up.

Anyone knows how can I fix this problem ?

Offline

#5 2017-04-20 12:48:03

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,868

Re: VirtualBox caused system hang-up.

Please post brand and model of your motherboard and processor as well as lscpu output .

Are you running latest bios/uefi firmware ?


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#6 2017-04-21 02:22:33

Hacksign
Member
Registered: 2012-07-30
Posts: 131

Re: VirtualBox caused system hang-up.

Laptop Model: X1 Carbon 3rd
CPU Model:i7-5600U

BIOS/UEFI: not upgrade since got this laptop

lscpu output:

[hacksign@XSign ~]$ lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    2
Core(s) per socket:    2
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 61
Model name:            Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz
Stepping:              4
CPU MHz:               878.674
CPU max MHz:           3200.0000
CPU min MHz:           500.0000
BogoMIPS:              5189.84
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              4096K
NUMA node0 CPU(s):     0-3
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 pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch epb intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx xsaveopt dtherm ida arat pln pts

Offline

#7 2017-04-22 16:05:27

Lone_Wolf
Member
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 11,868

Re: VirtualBox caused system hang-up.

BIOS/UEFI: not upgrade since got this laptop

If that was more then a few weeks ago, please check if there is a new version.

Also there are many types of lenovo X1 carbon laptops and their site doesn't list 1st / 2nd / 3rd gen , you'll have to be more specific.

please post full dmesg / journalctl -b output .


Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.


(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Offline

#8 2017-04-26 02:31:57

Hacksign
Member
Registered: 2012-07-30
Posts: 131

Re: VirtualBox caused system hang-up.

Lone_Wolf wrote:

BIOS/UEFI: not upgrade since got this laptop

If that was more then a few weeks ago, please check if there is a new version.

Also there are many types of lenovo X1 carbon laptops and their site doesn't list 1st / 2nd / 3rd gen , you'll have to be more specific.

please post full dmesg / journalctl -b output .

I've managed upgrade my BIOS to the newest version (release date 2016-12-07 version 1.16), but the hang up problem persists.

More specific detail of my laptop(you can get a more readable page here):

Model	20BS0035US			
Product	X1 Carbon (3rd Gen)			
Region	US			
Machine Type	20BS			
TopSeller	TopSeller			
Processor	i7-5600U (2C, 2.6 / 3.2GHz, 4MB, 1600MHz)			
vPro	vPro			
Graphics	Intel HD Graphics 5500			
Memory (soldered)	8GBx1			
Display	14" WQHD (2560x1440) IPS			
Multi-touch	10-point multi-touch			
Storage	512GB SSD PCIe			
Optical	None			
WLAN & Bluetooth	Intel 7265 ac + BT4.0			
WWAN	WWAN upgradable			
SIM Card	None			
Monitor Cable	None			
Camera	720p			
Backlit Keyboard	Backlit Keyboard			
Fingerprint Reader	Fingerprint Reader			
Battery Cells	8-cell (50Wh)			
Power Adapter (watt)	65W			
Preload	Windows 8.1 Pro 64-bit			
Base Warranty	3-year depot			
Global	No			
Ann Date (mm/yy)	01/15			

and below is my "journal -b -f 1>log.log 2>&1" output(after execute this command, I triggered a hang up) :
10:24:20 is time point I boot my virtual machine in virtualbox.

-- Logs begin at Wed 2016-05-11 19:16:52 CST. --
4月 26 10:21:47 XSign dhclient[3280]: bound to 192.168.1.100 -- renewal in 298 seconds.
4月 26 10:21:47 XSign NetworkManager[330]: <info>  [1493173307.7618] device (wlp4s0): Activation: successful, device activated.
4月 26 10:21:47 XSign dbus[326]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
4月 26 10:21:47 XSign systemd[1]: Starting Network Manager Script Dispatcher Service...
4月 26 10:21:47 XSign dbus[326]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
4月 26 10:21:47 XSign nm-dispatcher[3342]: req:1 'up' [wlp4s0]: new request (0 scripts)
4月 26 10:21:47 XSign nm-dispatcher[3342]: req:1 'up' [wlp4s0]: completed: no scripts
4月 26 10:21:47 XSign systemd[1]: Started Network Manager Script Dispatcher Service.
4月 26 10:24:20 XSign NetworkManager[330]: <info>  [1493173460.3664] manager: (vboxnet0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/5)
4月 26 10:24:36 XSign wpa_supplicant[376]: wlp4s0: WPA: Group rekeying completed with 4c:5e:0c:3d:4b:3f [GTK=CCMP]
4月 26 10:25:00 XSign kernel: SUPR0GipMap: fGetGipCpu=0xb

Offline

#9 2017-04-26 05:52:43

seth
Member
Registered: 2012-09-03
Posts: 49,985

Re: VirtualBox caused system hang-up.

ceterum censeo: "pacman -Qi intel-ucode"?

Offline

#10 2017-04-26 07:14:58

Hacksign
Member
Registered: 2012-07-30
Posts: 131

Re: VirtualBox caused system hang-up.

seth wrote:

ceterum censeo: "pacman -Qi intel-ucode"?

install this packeage(and reboot) didn't solve hang up problem.

Offline

Board footer

Powered by FluxBB