VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1864 - 1866 of 16363)

Ticket Resolution Summary Owner Reporter
#13730 obsolete Passthrough control disabled in GUI for CDROM drive stevecoh1
Description

The passthrough control for a CDROM drive is always greyed out for me. The only ways I can change its value are by VBoxManage or by directly editing the VM configuration file.

#10253 duplicate Windows guests on Linux 64-bit host freezes intermittently steveatoracle
Description

I have an Oracle Linux 5.6 Linux 64-bit host with VirtualBox 4.1.8 The host details: 16 cores 140 GB ram Disc controller: Raid,etc. 1 - 1GB Ethernet connection (motherboard NIC)

Currently, I have 5 VM guests, 3 Windows 2008 64-bit and 2 OL 5.6 64-bit

The host is not heavily utilized at this point.

What I am seeing is in the Windows Guest OS (accessed via Remote Desktop), if I do any type of activity the requires networking (i.e. Open FireFox, copy files to a mapped network share, etc.), then I see the CPU for that particular VM spike to 100%+ for a period of time (it varies but 1-3 minutes) and the guest is unresponsive (I have tested Remote Desktop and directly via the console).

The Windows Guest are bridged using Adapter 1: Intel PRO/1000 MT Server (Bridged adapter, eth1)

On the Linux Guest, I see similar, but the cpu spikes quickly and then drops within seconds.

I am not sure if the guest's are having a network contention issue on the host.

Each VM has a unique network MAC / hardware address

I am using the native VirtualBox Intel NICs

I see this behavior on a second Linux host with VirtualBox 4.1.6 as well and Windows 7 65-bit guests.

I have attached the VM log, I can provide whatever further debugging you require.

#13261 duplicate F20 kernel crash. tainted vbox kernel modules steve_b
Description

I regularly get ABRT reporting kernel crashes after i use vbox (w7 64 guest) ABRT reports

WARNING: CPU: 0 PID:9335 at drivers/usb/core/urb.c:476 usb_submit_urb+0x28d/0x5c0()

"A kernel problem occurred, but your kernel has been tainted (flags:GOE).
Kernel maintainers are unable to diagnose tainted reports.
Tainted Modules: vboxpci,vboxnetadp,vboxnetflt,vboxdrv."

This error has occurred both in F19 and F20 and with at least the last 3 vbox releases. currently running 4.3.14-95030-Linux_amd64. Have updated fedora weekly and have not seen any change. This kernel crash doesn't appear to impinge performance of either the host or guest but is getting annoying as it can happen 2 or 3 times a day. screenshot of ABRT report attached.

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