VirtualBox

Custom Query (16363 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (2200 - 2202 of 16363)

Ticket Resolution Summary Owner Reporter
#15849 duplicate Micro not working ezu
Description

After upgrading from VBox 5.0.24 to 5.1.2, the micro under Linux is not working anymore. The sound output is still ok. After downgrading to VBox 5.0.24 again, the micro is working again too.

#15847 fixed VBoxService is not started on CentOS 6 after running guest extensions installer -> partially fixed in releases greater than 5.1 James Brown
Description

VBoxService (a.k.a. vboxadd-service) is not started after the guest extensions installer (VBoxLinuxAdditions.run) finishes running. My guest in this case is a minimal CentOS 6 install. It appears that (as of 5.1.x?) vboxadd-service is required for guest IP reporting to work.

This seems undesirable; it means that certain VM features don't work properly until the host is rebooted after installing guest additions (since vboxadd-service is set to start on boot), and completely breaks running Vagrant guests under VirtualBox 5.1.x.

I modified VBoxLinuxAdditions.run to self-execute under /bin/sh -x to get some debugging output; it's at https://gist.github.com/Roguelazer/0db8863bfc328881a16f1e3fb07904e5.

The normal guest additions installer log (VBoxGuestAdditions.log) is attached.

#15846 fixed Booting iPXE using Intel vNIC fails - regression since 5.0.26 => Fixed in SVN Robin Smidsrød
Description

I recently tried to upgrade from VirtualBox 5.0.26 to 5.1.4, and I had to rollback to 5.0.26 again, because I couldn't boot over the network using either my custom-built 56KB iPXE ROM or a stock version of ipxe.dsk (floppy image) booted via floppy emulation. In both cases when I start iPXE shell and run ifstat all of the packets counters show 0. If I run "dhcp" and run ifstat again it fails with error http://ipxe.org/err/040ee1, which indicates that no DHCP response or IPv6 SLAAC response reached the VM. What's actually interesting is that my DHCP server sees the DHCP DISCOVER and returns the DHCP OFFER, but the VM never sees this DHCP OFFER. I tried to enable --nictrace on the VM, which confirmed that the DHCP OFFER was present at that point, but iPXE never received it. Rebuilding ipxe with DEBUG=intel:3 didn't give any obvious pointers to what was wrong.

If I booted with virtio-net instead, everything worked as expected. My assumption is that the iPXE intel driver is no longer capable to speak with the new emulated intel vnic in 5.1.4. Just to confirm that there are no network issues here I booted up a Ubuntu VM and it had no issues communicating with the network and get a DHCP lease. I also tried all three intel vnics, and they behaved slightly different, but all broken in some way which prevented network packets from reaching iPXE. So my assumption is that the problem might be somewhere in the receive (RX) path.

Attached are log files for both 5.0.26 and 5.1.4. Hopefully you'll be able to figure out what the problem is.

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