VM crash while installing AsteriskNOW -> fixed in SVN

[David Clymer]

When attempting to install AsteriskNOW (rPath linux + Anaconda), I always reach a point (seemingly random) where the VM crashes. I have little indication of the problem source other than what the Logs contain.

Host info

---

OS: Debian GNU/Linux "Lenny" Kernel: 2.6.22-3-686

I've attached the VM sesssion log.

[David Clymer]

VM Session Log

[David Clymer]

The installer seems to be running kernel version 2.6.22.16-0.1.gcc3.4.x86.i686. The crash occurs in graphical and text mode installers, and it seems to happen at one of two places; while loading the installer, or right after (or at the end of) installing all software packages. Its unclear what is happening on the guest OS at those points.

[David Clymer]

A friend of mine was able to install AsteriskNOW using vbox 1.5.6, but he also got the crashes most of the time. He claimed to have got it to work (the installer kernel at least) using kernel options: noacpi noapic nofb text

When I attempt to run the installed system on my virtualbox (v1.5.4), it (virtualbox) continues to crash every time it tries to boot - at one of 2 places: following "Initializing hardware..." or following "Checking for new hardware" regardless of what kernel options i supply

[David Clymer]

The vm _does_ boot occasionally. I was just able to boot, having changed nothing from the last attempt.

[David Clymer]

Successful boot log

[Sean]

Log File from SKrause

[Sean]

PNG File from SKrause

[Sean]

I am also experiencing random crashes, mostly at the begging of the install. I have attached the log/pic files.

[David Clymer]

Just to be clear, this issue DOES apply to the latest version of virtualbox (1.5.6). The problem is very consistent.

I am using an AMD64 processor with virtualization extensions. The problem occurs regardless of whether VT-x/AMD-V is turned on or off.

[David Clymer]

Continued failure using virtualbox svn r7848

[Frank Mehnert]

This problem is reproducible and even 1.6.0 does not contain a fix, sorry.

[Frank Mehnert]

This should work fine with 1.6.2 and VT-x or AMD-V enabled.

[greggh]

I also have this problem. I am running VirtualBox 1.6.2. with Suse 10.3 (2.6.22.5-31-bigsmp #1 SMP 2007/09/21 22:29:00 UTC i686 i686 i386 GNU/Linux).

I have tried VT-x or AMD-V enabled without success. I have tried changing many of the settings. Recreated new VM's, but no luck.

[Frank Mehnert]

Are you sure that your host supports VT-x or AMD-V? Please attach a VBox.log file of 1.6.2 when you enabled hardware virtualization.

[greggh]

Logs with VT and without VT enabled.

[Frank Mehnert]

gregh, actually VT-x was not enabled (this can be clearly seen in the logs). Please could you check your BIOS settings if VT-x is disabled?

[Eduardo Castillo]

I also have this problem. No solution yet?

[Frank Mehnert]

Did you actually read the last comments? You should be fine if you are able to enable VT-x/AMD-V for that VM.

[greggh]

Okay ... I did a bit of research. It looks like although my Laptop bios allows me to set this in the bios, it is still disabled. So it looks like I shall not get it right no matter not. I am using an HP nc6400. I shall have to do the installation of Asterisk manually ... install bit by bit myself :-(

thanks

[David Clymer]

I'd like to confirm that this is still an issue for me. I'm running Virtualbox v1.6.2 OSE, _with_ VT-x/AMD-V enabled according to the virtualbox interface.

Host:

david@gorilla:~$ uname -r 2.6.25-2-amd64 david@gorilla:~$ aptitude search '~i' |grep virtualbox i virtualbox-ose - x86 virtualization solution - binaries i virtualbox-ose-modules-2.6-amd6 - PC virtualization solution modules for Lin i A virtualbox-ose-modules-2.6.25-2 - PC virtualization solution modules for Lin

[David Clymer]

failure using version 1.6.2 OSE with AMD-V enabled.

[David Clymer]

AMD-V enabled, according to GUI

[David Clymer]

More host information. Processor has support for virtualization extensions:

david@gorilla:/vm/VirtualBox/Machines/AsteriskNOW/Logs$ cat /proc/cpuinfo 
processor	: 0
vendor_id	: AuthenticAMD
cpu family	: 15
model		: 107
model name	: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
stepping	: 1
cpu MHz		: 1000.000
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
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 rdtscp lm 3dnowext 3dnow rep_good pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch
bogomips	: 2006.21
TLB size	: 1024 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc 100mhzsteps

processor	: 1
vendor_id	: AuthenticAMD
cpu family	: 15
model		: 107
model name	: AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
stepping	: 1
cpu MHz		: 1000.000
cache size	: 512 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
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 rdtscp lm 3dnowext 3dnow rep_good pni cx16 lahf_lm cmp_legacy svm extapic cr8_legacy 3dnowprefetch
bogomips	: 2006.21
TLB size	: 1024 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 40 bits physical, 48 bits virtual
power management: ts fid vid ttp tm stc 100mhzsteps

[Frank Mehnert]

vezult, please attach the VBox.log file of your VM session here.

[David Clymer]

I attached the log along with my report. Please refer to the attachment named AsteriskNOW-2008-07-11-15-54-35.log

[Frank Mehnert]

vezult, sorry, I somehow missed your log file the first time. Unfortunately, your host CPU is a Pentium 4 which lacks of support for VT-x and AMD-V. The VM info dialog only shows the desired setting for that VM. But during startup it was detected that your host CPU actually does not have a VT-x / AMD-V capable CPU and therefore such support was not activated. Silently not enabling VT-x / AMD-V is a bug which has to be fixed. AsteriskNOW currently requires support for hardware virtualization. We will try to make it work in the normal mode as well but again, this will currently not work with 1.6.2.

[David Clymer]

Um...Perhaps you'll want to reread the document I referred you to; the lines 399 to 453 inclusively. You may even find the /proc/cpuinfo dump that I posted to be instructive.

I do apreciate that someone is monitoring this issue, but am beginning to feel as if effort to provide useful information is being wasted. I'm quite certain that I am running a dual-core, 64 bit AMD processor with AMD-V, and am even pretty sure that it is enabled, according to the VM session log that I posted.

[Frank Mehnert]

Next try. You provided four log files, I investigated the first two (AsteriskNOW-2008-02-25-11-51-20.log and AsteriskNOW-2008-02-29-17-30-35.log) which indeed show a Pentium 4. The third and the fourth log, AsteriskNOW-2008-04-11-15-39-13.log show the log for and AMD processor. However, AMD-V is not enabled as one can clearly seen:

00:00:07.258 HWACCM: No VMX or SVM CPU extension found. Reason VERR_SVM_DISABLED
00:00:07.258 HWACCM: VMX MSR_IA32_FEATURE_CONTROL=0

So AMD-V is either disabled in your BIOS, by your Linux host or VirtualBox is not able to enable AMD-V for some other reason. Please make 100% sure that you didn't disable AMD-V in the BIOS.

[Daniel Baum]

Crash log with VB 2.0.0 while installing AsteriskNOW-1.0.2.1-x86 on Vista

[Daniel Baum]

Crash log with VB 2.0.0 while installing AsteriskNOW-1.0.2.1-x86 on Vista

[Daniel Baum]

Installing of AsteriskNOW (1.0.2.1-x86 on Vista) still crashes with VB 2.0.0. Crash log is attached.

[Frank Mehnert]

phasemaster, the priority for improving the support for VT-x / AMD-V is currently higher than fixing the raw mode (VT-x/AMD-V disabled). You should be able to run Asterisk if you enable the VT-x mode for that VM, your processor is capable of this mode. Enable VT-x in the VM settings check if it is actually used when the VM is running (check the session information dialog, HostKey+N).

[Daniel Baum]

Frank, thank you for that tip. It works indeed if VT-x/AMD-V is enabled!

I am a laymen with respect to VM, but if VT-x/AMD-V mode is your priority, I wonder why VT-x/AMD-V is not enabled by default in case a CPU supporting that mode is detected? Anyhow, I am happy now. This is a great piece of software!