VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1723 - 1725 of 16363)

Ticket Resolution Summary Owner Reporter
#13981 obsolete guest xp crashes by direct3d in FBSD10 x64 o_0
Description

hello, virtualbox(win xp sp3 + direct3D VBoxGuestAdditions) crashes every time guest OS(xp-sp3) tries access direct3d (like with dxdiag.exe).

$uname -a FreeBSD alpha 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 21:02:49 UTC 2014 root@…:/usr/obj/usr/src/sys/GENERIC amd64

% dri-10.4.6,2 = up-to-date with index virtualbox-ose-4.3.26 = up-to-date with index virtualbox-ose-kmod-4.3.26 = up-to-date with index

% [50.438] (II) intel(0): [DRI2] DRI driver: i965

(gdb) bt #0 0x0000000817c55f33 in convert_color_type (span=0x8620, srcType=0, newType=152, output=8) at ../../src/mesa/swrast/s_span.c:948 #1 0x0000000817040f4f in crServerDispatchProgramStringARB (target=34336, format=34933, len=152, string=0x814c828c4)

at /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.26/src/VBox/HostServices/SharedOpenGL/crserverlib/server_projmatrix.c:328

#2 0x00000008170fac49 in crUnpackExtend () at /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.26/out/freebsd.amd64/release/obj/VBoxOGLgen/unpack.c:6428 #3 0x00000008170f84f8 in crUnpack (data=<optimized out>, opcodes=<optimized out>, num_opcodes=<optimized out>, table=<optimized out>)

at /usr/ports/emulators/virtualbox-ose/work/VirtualBox-4.3.26/out/freebsd.amd64/release/obj/VBoxOGLgen/unpack.c:4107

#14 0x000000080082c4f5 in ?? () from /lib/libthr.so.3 #15 0x0000000000000000 in ?? () Backtrace stopped: Cannot access memory at address 0x7ffffef30000

(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198856) thanx

#6223 fixed guest windows 7 (32 or 64 bit) almost hangs when changing guest network card settings => fixed in svn Mihai Hanor
Description

Host: XP SP3 32 bit, fully updated, E6400, 2GB RAM
Guest: Windows 7 RTM, 32 bit unpatched, 64 bit unpatched, then patched; all clean install, no guest additions, no other programs/drivers; VT enabled, 1 virtual cpu, 512MB guest RAM, 2D/3D acceleration disabled, two Intel 82540EM network adapters enabled (or more), all in bridged mode; audio set to null, usb off

Steps to reproduce:

  1. You need a clean install; by default, the network adapters have all network protocols enabled and tcp/ip is set to auto (dhcp enabled).
  2. Access the Properties window of one adapter (Local Area Connection)
  3. Uncheck all the following protocols: Client for Microsoft Networks, QoS Packet Scheduler, File and Printer Sharing for Microsoft Networks, Internet Protocol Version 6, Link Layer Topology Discovery IO Driver, Link Layer Topology Discovery Responder. Don't close the window yet.
  4. Access the Internet Protocol Version 4 Properties windows and manually set an IP address and a gateway (eg. 192.168.0.123, 255.255.255.0)
  5. Click OK, then Close. After clicking Close, the guest could hang. If it doesn't, try the same steps with the following adapter. If that doesn't work, reset the settings of all the adapters (TCP/IP V4 to DHCP auto, and recheck all protocols), shutdown the VM, then restart it.

If the guest hangs occurs, the VirtualBox.exe host process consumes all processing time of one CPU core. The process is one of those listed as MSVCR71.dll!endthreadex+0x31. See the attached file. The VM will respond to input (keyboard and mouse) every few seconds or tens of seconds, for a fraction of a second. Several times I've managed to recover the VM, by starting the guest's task manager with ctrl+shift+esc, although that could be a coincidence.

#8678 obsolete guest window size is ignored Mike Wilson
Description

Using a guest window with smaller size than the guest desktop (using scrollbars to access the different areas of the guest desktop) is not honoured between restarts.

Setting a smaller window size on a 1600x1200 guest and shutting it down results in this data in the virtual machine xml file:

      <ExtraDataItem name="GUI/LastNormalWindowPosition" value="4,20,985,785"/>

The above looks fine, but when starting up the guest again, it expands to a larger size and updates the stored window position to this larger size (noticeable after shutting down again):

      <ExtraDataItem name="GUI/LastNormalWindowPosition" value="4,20,1592,1155"/>

Ticket #7042 is probably a related bug, where the guest window size is lost on every switch in and out of fullscreen.

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