hello,
I've tried to run VB 7.0.4 r154605 (Qt5.15.3) on Ubuntu 22.04.1 LTS and XEON e5450 on G41 chipset with built-in video. This happened because I put HDD with OS and vmware player from notebook with i5-6200u processor to this machine and obviously vmware player won't work with such an old cpu complaining about missing required instructions. VB claims to be working BUT, result was overwhelming:
-----------------------------------------
VM Name: winxp
The virtual machine 'winxp' has terminated unexpectedly during startup because of signal 6.
Result Code:
NS_ERROR_FAILURE (0X80004005)
Component:
MachineWrap
Interface:
IMachine {300763af-5d6b-46e6-aa96-273eac15538a}
------------------------------------------
NO FILE with LOG in /home/<user_name>/VirtualBox VMs/xp32 location... no any message in console
--------------------------------------------
vendor_id : GenuineIntel
cpu family : 6
model : 23
model name : Intel(R) Xeon(R) CPU E5450 @ 3.00GHz
stepping : 10
microcode : 0xa0b
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 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm dca sse4_1 xsave lahf_lm pti tpr_shadow vnmi flexpriority vpid dtherm
vmx flags : vnmi flexpriority tsc_offset vtpr vapic
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit mmio_unknown
--------------------------------------------
Distributor ID: Ubuntu
Description: Ubuntu 22.04.1 LTS
Release: 22.04
Codename: jammy
--------------------------------------------
VirtualBox Graphical User Interface
Version 7.0.4 r154605 (Qt5.15.3)
--------------------------------------------
dmesg entries:
[ 98.614630] kernel: vboxdrv: loading out-of-tree module taints kernel.
[ 98.615153] kernel: vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[ 98.622158] kernel: vboxdrv: Found 4 processor cores/threads
[ 98.622999] kernel: vboxdrv: fAsync=0 offMin=0x37b offMax=0x3888
[ 98.723140] kernel: vboxdrv: TSC mode is Synchronous, tentative frequency 2992868464 Hz
[ 98.723144] kernel: vboxdrv: Successfully loaded version 7.0.4 r154605 (interface 0x00330004)
[ 99.288689] kernel: VBoxNetFlt: Successfully started.
[ 99.471353] kernel: VBoxNetAdp: Successfully started.
VB 7.0.4 r154605 (Qt5.15.3) on Ubuntu 22.04.1 LTS and XEON e5450
Re: VB 7.0.4 r154605 (Qt5.15.3) on Ubuntu 22.04.1 LTS and XEON e5450
wonderful! 280 views and no any suggestion what could be wrong, really supportive forum i would say.
-
- Site Moderator
- Posts: 39156
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: VB 7.0.4 r154605 (Qt5.15.3) on Ubuntu 22.04.1 LTS and XEON e5450
These are user forums. You'll get a reply if another user recognizes your symptoms and feels like helping. Your odds would be greatly improved if a log had been provided.
Re: VB 7.0.4 r154605 (Qt5.15.3) on Ubuntu 22.04.1 LTS and XEON e5450
very good conclusion i also would like to see the logs, do you know why vbox may not generate them? is there such cases already?mpack wrote:These are user forums. You'll get a reply if another user recognizes your symptoms and feels like helping. Your odds would be greatly improved if a log had been provided.
btw meanwhile tested on same machine with windows 7 = works!
now upgraded to Version 7.0.6 r155176 (Qt5.15.3) -> result very same:
error:
Result Code:
NS_ERROR_FAILURE (0X80004005)
Component:
MachineWrap
Interface:
IMachine {300763af-5d6b-46e6-aa96-273eac15538a}
and no logs
-
- Site Moderator
- Posts: 20965
- Joined: 30. Dec 2009, 20:14
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Windows, Linux
Re: VB 7.0.4 r154605 (Qt5.15.3) on Ubuntu 22.04.1 LTS and XEON e5450
There will have been more to that error message, including a full English sentence. Please post the whole message, we may be able to help.
Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. In the "Logs" subfolder, zip the VM's "vbox.log", and post the zip file, using the forum's Upload Attachment tab. (Configure your host OS to show all extensions so you can find the "vbox.log", not "vbox.log.1", etc.)
If no logs were made or an error message appeared before the Virtualbox "splash screen" showed, please zip and post the VboxSVC.log in "$HOME/.config/VirtualBox"
Start the VM from full normal shutdown, not save-state. Run until you see the problem happen, then shut down the VM from within the VM's OS if possible. If not possible, close the Virtualbox window for the VM with the Power Off option set.
Right-click the VM in the main Virtualbox window's VM list, choose Show in Explorer/Finder/File Manager. In the "Logs" subfolder, zip the VM's "vbox.log", and post the zip file, using the forum's Upload Attachment tab. (Configure your host OS to show all extensions so you can find the "vbox.log", not "vbox.log.1", etc.)
If no logs were made or an error message appeared before the Virtualbox "splash screen" showed, please zip and post the VboxSVC.log in "$HOME/.config/VirtualBox"