VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2182 - 2184 of 16363)

Ticket Resolution Summary Owner Reporter
#15875 fixed Resizing problem with linux guests -> fixed in releases higher than 5.1.4 mskov
Description

Starting from VirtualBox 5.1.0 resizing of linux guests doesn't work well anymore. Sometimes it works, sometimes it takes a few seconds to resize and sometimes the screen doesn't resize at all (that happens on the same running instance of a VM, without restarting it). We observed this problem on VirtualBox 5.1.0, 5.1.2 and 5.1.4 (with the corresponding version of guest additions installed). The problem occurred both for the Ubuntu 15.04 guest and for a Debian 8 guest.

After every (!) restart of the VM I see the following messages in the system log:

Sep 01 18:40:36 sirrix-VirtualBox vboxadd.sh[654]: Starting the VirtualBox Guest Additions.
Sep 01 18:40:36 sirrix-VirtualBox vboxadd-x11.sh[706]: Installing the Window System drivers.
Sep 01 18:40:36 sirrix-VirtualBox vboxadd-x11.sh[714]: Installing X.Org Server 1.17 modules.
Sep 01 18:40:37 sirrix-VirtualBox vboxadd-x11.sh[727]: Setting up the Window System to use the Guest Additions.
Sep 01 18:40:37 sirrix-VirtualBox vboxadd[533]: You may need to restart the the Window System (or just restart the guest system)
Sep 01 18:40:37 sirrix-VirtualBox vboxadd[533]: to enable the Guest Additions.
Sep 01 18:40:37 sirrix-VirtualBox vboxadd-x11.sh[735]: Installing graphics libraries and desktop services components.
Sep 01 18:40:37 sirrix-VirtualBox vboxadd-x11.sh[748]: Window system drivers installed.
Sep 01 18:40:37 sirrix-VirtualBox vboxadd.sh[794]: .
Sep 01 18:40:37 sirrix-VirtualBox systemd[1]: Started vboxadd.service.

The VBox.log from 5.1.4 with an Ubuntu guest (guest additions 5.1.4) is attached.

If we revert the additions to 5.0.20 - all works fine (with virtualbox 5.1.4).

#15873 obsolete Problems with hardening / VM crashing on 5.1.14 - RHEL5 ThunderFox
Description

Hello,

I have a virtual machine which has previously been ported from VMWare running RHEL5. This uses the Legacy paravirtualization mode for kernel compatibility, as for unknown reasons, this is the only way it used to run.

Porting was done a few months ago, by creating a new VM with the old VHD running on VBX 4.x up to 4.3.12, on Windows 7. The VM has always ran without problems.

After a system upgrade we moved onto Windows 10 and VBX 5.0.26. Since this upgrade, we keep running into errors related to the hardening feature. The error/behaviour is not always the same, and after 20-something tries in a row, the VM eventually starts and all is good.

In order to solve the hardening issue we decided to upgrade VBX to 5.1.0 and then 5.1.4. With these, the hardening errors remain. But even worse (the motivation for opening this ticket) is that when we manage to successfully boot the VM, there is a Kernel Panic and the vm halts with error "Kernel Panic - Not syncing: NMI watchdog".

We've gone back to 5.0.26 for the time being and all is working smoothly.

  • How do we solve the errors related to hardening?
  • How do we solve the error related to the kernel crashing on the most recent versions of VirtualBox? This seems to be completely unrelated to the hardening issues.

To add some extra data, I've looked up previous tickets opened on the hardening feature, and the issue for all of them seems to be reproducible. Ours does not occur in a consistent form, and sometimes the VM is allowed to start, which points to a bug rather than a safety issue.

You'll fine attached all the needed files and screenshots including the hardening.log.

We've tested this in both a HP machine with an AMD A8 PRO processor, as well as a Dell machine with a Core i7 processor. Both are running Windows 10 and the same versions of Virtualbox.

Going back to VBX4 is not a possibility since NDIS6 support is not available.

#15872 fixed LPT, Cannot attach to host driver (VERR_INTERNAL_ERROR_3) Electron-John
Description

Summary: I am setting up a virtual box (ver. 5.1.4r110228 (Qt5.5.1) ) to run older, expensive software on a virtual Windows 2000 machine. There is a physical parallel port dongle that is needed. I have found and followed the tutorial on setting up the port (Enabling and Configuring Parallel (LPTx) Ports). I get an error that looks internal to Virtual Box. The virtual machine will not even continue past the error.

What I have done after the error:

1) Researched the forums:

A) Found several posts about parallel ports but none addressed the internal error I was getting. Nevertheless I tried some of the suggestions to no avail. Ultimately, my most reliable forum post was the tutorial.

B) Found a stale ticket (4279 - now obsolete) that ultimately was no use.

2) Posted in VitualBox on Windows Hosts, titled "parallel device 0 cannot attach to host driver" by Electron-John, 27, Aug 2016, 23:26.

A) That post has all the details, and both the log file and hardening log file. (Copies attached to this ticket.)

3) I have found the following on Microsoft's developer pages:

A) https://msdn.microsoft.com/en-us/library/windows/hardware/ff543952(v=vs.85).aspx[[BR]]

B) If the link doesn't work or is blocked, try web searching "features of system-supplied drivers" and look for a microsoft link that has "ff543952" in it. This is current as of 31, Aug. 2016)

C) I am not experienced enough to figure out, on 64 bit Windows hosts, if VirtualBox needs to supply a vendor-supplied parallel port driver. I do not fully comprehend what the workaround is for 64 bit Windows hosts.

At this point I do not know how to resolve the internal error.

I have attached the log files and a copy of the original post.

Thank you in advance.

Electron John

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