VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (517 - 519 of 16363)

Ticket Resolution Summary Owner Reporter
#5285 fixed 64 Bit Guest does not work with nested Pagetables under 32-Bit Windows XP -> fixed in SVN/3.0.10 toad
Description

Without nested Pagetables, the vm starts normally. With nested Pagetables, the vm crashes early in the Kernelstartup.

#1540 invalid 64 bit / PAE support inot functional under fedora 8 x86_64 jboyerjr@…
Description

with pae support enable on fedora x86_64 with the following Intel core duo chip: # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 15 model name : Intel(R) Core(TM)2 CPU 6320 @ 1.86GHz stepping : 6 cpu MHz : 1867.000 cache size : 4096 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 2 fpu : yes fpu_exception : yes cpuid level : 10 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 lm constant_tsc arch_perfmon pebs bts rep_good pni monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr lahf_lm bogomips : 3726.22 clflush size : 64 cache_alignment : 64 address sizes : 36 bits physical, 48 bits virtual power management:

a centos 5 64bit guest states upon boot that the cpu is not support by the kernel i am booting

#6774 fixed 64 bit FreeBSD guest under 32 bit FreeBSD host crashes Walter Thomson
Description

I am running a 64 bit FreeBSD guest under a 32 bit FreeBSD host with VirtualBox 3.1.8 (the same defect applies also to earlier 3.1.x versions). The guest typically crashes when running "configure" for compiling some 3rd-party software, especially when the C compiler seems to be called. See the attached screenshot.

Interestingly, I could compile the complete 64 bit version of FreeBSD inside the guest ("make buildworld buildkernel") without any problems, but I cannot seem to get across simple configure stages for "ports" software.

Once, not only the guest crashed, but the host as well. This led me to the suspicion that maybe some part of the memory management of VirtualBox is broken, and in that single case also corrupted the host's memory. Also, since this seems to happen when gcc in the guest is called, maybe this has something to do with allocating larger amounts of memory on the stack?

The VBox.log file is from the crashed instance (guest-only crash, no apparent malfunction in host). The VBox.log.1 file is from a boot and then shutdown of the guest without trying to install any of the ports.

From reading other bug reports on VirtualBox, I have the impression that quite many people experience instabilities when trying to run 64 bit guests on 32 bit hosts. Maybe this report gives some hints.

uname -a on host machine: FreeBSD campanula.xyzzy 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Feb 20 10:15:50 CET 2010 root@…:/usr/VOL/OBJ/FreeBSD/RELENG_8_0_0_RELEASE/src/sys/XYZZY_SMP_NA_ATM i386

uname -a on guest machine: FreeBSD v802.xyzzy 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Sat May 22 18:22:29 UTC 2 010 root@…:/usr/obj/.../gandalf/d/12s1e/SRC/FreeBSD/HEAD/src/sys/XY ZZY_SMP_NA amd64

I am also attaching the boot messages of the guest machine. This is the boot after the crash providing the VBox.log above; it shows fsck running to repair the virtual disk's unclean shutdown.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy