VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2083 - 2085 of 16363)

Ticket Resolution Summary Owner Reporter
#16150 fixed Cmd-Tab broken between builds 111660 and 111724 => Fixed in SVN Socratis
Description

Host: Mac
Using Cmd-Tab in a guest (let's say Win, OSX) used to act as a Win/Cmd/Super-Tab shortcut key within the guest. That behavior changed between builds 111660 and 111724. Now Cmd-Tab "stays" in the host, i.e. switches between apps in the host. Not sure if it is intentional or not.

#16260 fixed OSX guests: all net cables disconnected between r112052 and r112114 Socratis
Description

Most of my VMs have 4 network cards, 3 of them connected:

  1. HostOnly, in the 192.168.20.0/24 range.
  2. VBoxIntNet, in the 192.168.30.0/24 range.
  3. Bridged, with my Airport card, usually cable=disconnected.
  4. VBoxNATNet, in the 192.168.40.0/24 range, usually disconnected for Windows guests.

Starting with rev. 112114, all my network connections only on OSX guests are showing that the cable is not connected in the guest, i.e. there's no network whatsoever. Reverting to rev. 112052 magically connects the cables that were already connected in the configuration, i.e. 3/4. I tried rev. 112124 and that fails as well.

I changed the network adapters, since the OSX guests are the only ones using the "Intel PRO/1000 MT Server", but it made no difference.

All my other guests, (Windows, Ubuntu, Manjaro, Fedora, Mint, you name it) do not have that problem. Only the OSX guests.

From a 10.8 guest (for which I'll include the logs), excerpt of "ifconfig" for NIC1 (HostOnly), rev. 112052:

en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=2b<RXCSUM,TXCSUM,VLAN_HWTAGGING,TSO4>
	ether 08:00:27:44:24:b5 
	inet6 fe80::a00:27ff:fe44:24b5%en0 prefixlen 64 scopeid 0x4 
	inet 192.168.20.101 netmask 0xffffff00 broadcast 192.168.20.255
	media: autoselect (1000baseT <full-duplex>)
	status: active

and excerpt of "ifconfig" for NIC1 (HostOnly), rev. 112114:

en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=2b<RXCSUM,TXCSUM,VLAN_HWTAGGING,TSO4>
	ether 08:00:27:44:24:b5 
	media: autoselect (<unknown type>)
	status: inactive

I have tried all of my OSX VMs, from 10.5 to 10.12, with the same results.

#16375 fixed Ubuntu 16.04 LiveCD Guru Meditation on Win-64 host, works on the same Win-32 host (Intel Pentium D) Socratis
Description
  • Host: Pentium-D based, triple-booting Win7-32/Win7-64/Win10-64.
  • Guest: Ubuntu 16.04-64 LiveCD.
  • vbox: Default 5.1.12 template for Ubuntu-64, with 64MB vRAM assigned.
  • VirtualBox: 5.1.12

While starting the VM on the Win7-32 host works fine, starting the exact same VM on the Win7-64 or Win10-64 version on the same host, causes a Guru Meditation:

VCPU0: Guru Meditation 1155 (VINF_EM_TRIPLE_FAULT)

The issue was brought to my attention by another user (mycroft1) in the thread Meditation Guru critical error on Windows Host, and since I had an almost identical system, I gave it a try with the above mentioned results. The system is a rather old one with an Intel Pentium D @ 3.2 GHz with 2 physical / 2 logical CPUs.

From the logs, one of the very few differences between the 32- and the 64-bit of Win7 (and Win10-64), is that at the 32-bit version log, there are the following extra lines:

00:00:03.238127 [/REM/] (level 1)
00:00:03.238129   64bitEnabled <integer> = 0x0000000000000001 (1)
...
00:00:03.318995 REM: VBoxREM64
00:00:03.319101 Using 64-bit aware REM

and there's a difference between them:

00:00:03.243747 PGM: Host paging mode: PAE+PGE         : Win7-32
00:00:05.044710 PGM: Host paging mode: AMD64+PGE+NX    : Win7-64/Win10-64

Logs and other information are already available on the thread, they can be duplicated here if you want, just say the word.

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