Fedora 22 unresponsive (VBox5, Yosemite)

[darknerd]

Hello. I created a new VirtualBox system and attempted to install Fedora 22. I selected the defaults, put a 40 GB dynamically sized drive, turned off Audio chipsets, and setup port mapping (2222 to 22) for SSH. When I use the Fedora 22 Live CD, and then click Install, it initially works, responsive to keyboard commands and such. When it loads the GUI, things change. I can use a mouse cursor, but then I cannot click on anything, and the keyboard, doesn't seem to work. I cannot interact with the environment.

Code: Select all

$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.10.5
BuildVersion:	14F27

Code: Select all

$ system_profiler
...
    VirtualBox:

      Version: 5.0.0
      Obtained from: Identified Developer
      Last Modified: 9/24/15, 2:17 PM
      Kind: Intel
      64-Bit (Intel): Yes
      Signed by: Developer ID Application: Oracle America, Inc. (VB5E2TV963), Developer ID Certification Authority, Apple Root CA
      Location: /Applications/VirtualBox.app
      Get Info String: Oracle VM VirtualBox Manager 5.0.0, © 2007-2015 Oracle Corporation
...
    Hardware Overview:

      Model Name: MacBook Pro
      Model Identifier: MacBookPro11,3
      Processor Name: Intel Core i7
      Processor Speed: 2.5 GHz
      Number of Processors: 1
      Total Number of Cores: 4
      L2 Cache (per Core): 256 KB
      L3 Cache: 6 MB
      Memory: 16 GB
      Boot ROM Version: MBP112.0138.B15
      SMC Version (system): 2.19f12
...

Code: Select all

$ vboxmanage showvminfo fedora
Name:            fedora
Groups:          /
Guest OS:        Fedora (64-bit)
UUID:            d01d97a0-034a-4bfc-b2ac-2aefcda30ac9
Config file:     $HOME/VirtualBox VMs/fedora/fedora.vbox
Snapshot folder: $HOME/VirtualBox VMs/fedora/Snapshots
Log folder:      $HOME/VirtualBox VMs/fedora/Logs
Hardware UUID:   d01d97a0-034a-4bfc-b2ac-2aefcda30ac9
Memory size:     768MB
Page Fusion:     off
VRAM size:       12MB
CPU exec cap:    100%
HPET:            off
Chipset:         piix3
Firmware:        BIOS
Number of CPUs:  1
PAE:             off
Long Mode:       on
CPUID Portability Level: 0
CPUID overrides: None
Boot menu mode:  message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI:            on
IOAPIC:          on
Time offset:     0ms
RTC:             UTC
Hardw. virt.ext: on
Nested Paging:   on
Large Pages:     on
VT-x VPID:       on
VT-x unr. exec.: on
Paravirt. Provider: Default
State:           powered off (since 2015-10-14T20:26:36.903000000)
Monitor count:   1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address: 
Teleporter Password: 
Tracing Enabled: off
Allow Tracing to Access VM: off
Tracing Configuration: 
Autostart Enabled: off
Autostart Delay: 0
Default Frontend: 
Storage Controller Name (0):            IDE
Storage Controller Type (0):            PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  2
Storage Controller Port Count (0):      2
Storage Controller Bootable (0):        on
Storage Controller Name (1):            SATA
Storage Controller Type (1):            IntelAhci
Storage Controller Instance Number (1): 0
Storage Controller Max Port Count (1):  30
Storage Controller Port Count (1):      1
Storage Controller Bootable (1):        on
IDE (1, 0): /dontbackup/distros/Fedora-Live-Workstation-x86_64-22-3.iso (UUID: 3ac3f2d7-7cd3-439b-abc8-c60f6eeac499)
SATA (0, 0): $HOME/VirtualBox VMs/fedora/fedora.vmdk (UUID: fe947ef3-3504-4a8e-9a99-21b41c0bcfa1)
NIC 1:           MAC: 0800271354D1, Attachment: NAT, Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 1 Settings:  MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, receive: 64)
NIC 1 Rule(0):   name = SSH, protocol = tcp, host ip = , host port = 2222, guest ip = , guest port = 22
NIC 2:           disabled
NIC 3:           disabled
NIC 4:           disabled
NIC 5:           disabled
NIC 6:           disabled
NIC 7:           disabled
NIC 8:           disabled
Pointing Device: USB Tablet
Keyboard Device: PS/2 Keyboard
UART 1:          disabled
UART 2:          disabled
LPT 1:           disabled
LPT 2:           disabled
Audio:           disabled
Clipboard Mode:  disabled
Drag and drop Mode: disabled
VRDE:            disabled
USB:             enabled
EHCI:            disabled
XHCI:            disabled

USB Device Filters:

<none>

Bandwidth groups:  <none>

Shared folders:  <none>

Video capturing:    not active
Capture screens:    0
Capture file:       $HOME/VirtualBox VMs/fedora/fedora.webm
Capture dimensions: 1024x768
Capture rate:       512 kbps
Capture FPS:        25

Guest:

Configured memory balloon size:      0 MB

Code: Select all

$ tail -f VBox.log 
00:00:14.918935 OHCI: USB Operational
00:00:20.906900 NAT: Link up
00:00:26.442781 Display::handleDisplayResize: uScreenId=0 pvVRAM=00000001164b3000 w=1024 h=768 bpp=32 cbLine=0x1000 flags=0x1
00:00:26.442823 GUI: UIFrameBufferPrivate::NotifyChange: Screen=0, Origin=0x0, Size=1024x768, Sending to async-handler
00:00:26.442861 GUI: UIMachineView::sltHandleNotifyChange: Screen=0, Size=1024x768
00:00:26.442871 GUI: UIFrameBufferPrivate::handleNotifyChange: Size=1024x768
00:00:26.442883 GUI: UIFrameBufferPrivate::performResize: Size=1024x768, Directly using source bitmap content
00:00:28.157880 NAT: IPv6 not supported
00:00:28.420735 NAT: DHCP offered IP address 10.0.2.15
00:00:28.427128 NAT: DHCP offered IP address 10.0.2.15

[darknerd]

I'm watching this in Activity Monitor, VirtualBox 5 might be having performance issues with Fedora 22 on Yosemite. I am seeing the process consume over 105 % CPU and have 6:34.08 CPU Time (26 threads, 5208), when attempting to go into the window and do a single mouse click. Right now I only have Terminal and Firefox and Fedora 22 Live CD installer is the only virtual system I have running now.

When I turn off mouse integration, I get slightly better interaction, several seconds later I can see the mouse cursor move. The CPU Time keeps jumping up, at 15:20.82, now. After a few minutes, the mouse click was picked up. It is really hard to use this, as any input device event seems to consume enormous resources and takes a few minutes to get picked up by the virtual guest system.

I don't have this level of performance hit with other systems I have successfully installed and used (El Capitan, Windows 10, Ubuntu 14.04)

[loukingjr]

I'm at a loss to understand your post or why you are running off a Fedora 22 LiveCD.

FWIW, I installed Fedora 22 as a guest on 5/26/15 while I was still on Yosemite and it was working fine then, and still works fine on El Capitan.

Could you clarify what your post is about? BTW, VB 5.0.6 is the current version.

[darknerd]

I'm at a loss to understand your post or why you are running off a Fedora 22 LiveCD.

FWIW, I installed Fedora 22 as a guest on 5/26/15 while I was still on Yosemite and it was working fine then, and still works fine on El Capitan.

Could you clarify what your post is about? BTW, VB 5.0.6 is the current version.

Why Post? Fedora 22 installer unusable due to performance to respond to interface events, like a mouse click, on Virtualbox for an unknown reason. Expected behavior is that it would take less than a second to respond to a mouse click. Actual behavior is that a mouse click can take over 30 seconds. Is that not clear?

Why LiveCD?: Installation instructions for Fedora 22 say to use the LiveCD and select install. Thus I am using the LiveCD, I downloaded "Fedora-Live-Workstation-x86_64-22-3.iso", and clicked on "Install to Hard Drive".



The guest system is responsive until I click "Install to Hard Drive", then when I get to the next step, where I select the language, the performance comes to a crawl. It takes about a minute to respond to a mouse click.

Works on my system: And that is great that it works on your system, but logically, that does not guarantee it will work universally on the set of all other systems. There might be some bug, configuration, setting, etc. that causes a problem.

[Perryg]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

[darknerd]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

I attached the most recent logs.

When I was using tail -f on the logs, it got to the "NAT: DHCP offered IP address 10.0.2.15" and everything was fine. When it slowed down, I did not see any further logs.

[Perryg]

Code: Select all

00:00:00.920790   RamSize           <integer> = 0x0000000030000000 (805 306 368, 768 MB)

First thing I would suggest is that you increase the amount of RAM allocated to the guest to 2GB. You can reduce this once installed and running if you must.

Code: Select all

00:00:00.904147 File system of '/Users/joaquin.menchaca/VirtualBox VMs/fedora/fedora.vmdk' is hfs

I wonder why you changed the default format to vmdk instead of VDI which is the VirtualBox container format.


Note: don't get hung up on the network yet. Not until you either get a full boot off the livd cd or have it installed. If you want to test the network stack as an issue disable it in the settings and start the live boot. Select to try instead of install and see if it fully boots.