VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (946 - 948 of 16363)

Ticket Resolution Summary Owner Reporter
#13048 invalid Network Boot pxelinux 6.02 crash vboxuser49
Description

Pxe booting the latest version of pxelinux (6.02 at this time) crashes virtualbox. Prior versions of pxelinux(4 and 5) are unaffected. I have confirmed pxelinux 6.02 is working on physical machines and vmware with the same setup.

Log:

00:00:17.026679 iPXE (PCI 00:0D.0) starting execution...ok                                      
00:00:17.026685 iPXE initialising devices...ok                                                  
00:00:17.026692                                                                                 
00:00:17.026698                                                                                 
00:00:17.026704                                                                                 
00:00:17.026711 iPXE 1.0.0+ -- Open Source Network Boot Firmware -- http://ipxe.org             
00:00:17.026717 Features: DNS TFTP PXE PXEXT Menu                                               
00:00:17.026726                                                                                 
00:00:17.026732 net0: 08:00:27:4b:81:22 using 82540em on PCI00:03.0 (open)                      
00:00:17.026737   [Link:up, TX:0 TXE:0 RX:0 RXE:0]                                              
00:00:17.026743 DHCP (net0 08:00:27:4b:81:22).............. ok                                  
00:00:17.026749 net0: 192.168.56.2/255.255.255.0 gw 192.168.56.1                                
00:00:17.026754 Next server: 192.168.56.1                                                       
00:00:17.026760 Filename: pxelinux.0                                                            
00:00:17.026766 tftp://192.168.56.1/pxelinux.0... ok                                            
00:00:17.026771                                                                                 
00:00:17.026777 PXELINUX 6.02 PXE 2013-10-13 Copyright (C) 1994-2013 H. Peter Anvin et al       
00:00:17.026783                                                                                 
00:00:17.026788                                                                                 
00:00:17.026794                                                                                 
00:00:17.026800                                                                                 
00:00:17.026805                                                                                 
00:00:17.026811                                                                                 
00:00:17.026817                                                                                 
00:00:17.026823                                                                                 
00:00:17.026828 --------------------------------------------------------------------------------
00:00:17.026834 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
00:00:17.026845 emR3Debug: rc=VINF_EM_TRIPLE_FAULT
00:00:18.026847 Changing the VM state from 'RUNNING' to 'GURU_MEDITATION'.

#16477 obsolete VM crashes with BSOD if 4 CPUs configured on 4 core host vboxuser4
Description

I have a CPU:

Intel(R) Core(TM) i5-4690 CPU @ 3.50GHz Intel64 Family 6 Model 60 Stepping 3, GenuineIntel Microcode signature: 0000001C

If I configure Windows 7 VM to use 4 vCPU with up to CPU load limit of 100% the VM crashes reproducible. If I go down to 2 or 3 vCPU for the VM all is fine.

  • Host is running on Windows 7 SP1 Enterprise
  • The VM has 4 GB RAM assigned and the host has 16GB.
  • HDD on host is SSD drive, in VM SSD is not checked.
  • PAE/NX is disabled (default).

The BSOD says BAD_SYSTEM_CONFIG_INFO (0x74) and cannot dumped for unknown reasons (0xC0000010). See attached screenshot for the full STOP message

#14796 obsolete Virtualbox guest hangs using RDP vboxuser2
Description

I have been experiencing guest slow performance issues while connecting remotly using RDP. It appears as if the guest OS hangs or locks up. This was not the case as I have determined that if I go into the console settings and disable the remote display server for the guest and then re-enable it, the remote display works again.

The guest is running: Red Hat Enterprice Server 6.6 (Santiago) With kernel: 2.6.39-400.215.12.el6uek.686 4gb ram and 4 cpus one bridged network adaptor.

The host is Fedora 22 although this slowness/hang condition was occuring on CentOS 6 and 7 as well.

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