Announcement

Collapse
No announcement yet.

VirtualBox USB support borked on windows guests after today's update

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    VirtualBox USB support borked on windows guests after today's update

    Installed an update today which included virtualbox and virtualbox guest additions. After the update, none of my windows guests would open(Win10, Win7, WinXP and Win2000). Expanding the error message indicated a problem with the usb configuration. For each windows guest I disabled the usb controller in virtualbox and each time was able to successfully boot up the windows guest.

    Figuring I probably needed to update the VBoxGuestAdditions, I reinstalled said package on each windows guest. Following that, I went to enable the usb controller in each windows guest vm. However, upon doing so the only option available was for the USB 1.1 controller. Previously, there were options for USB 2 in Win2000 and WinXP and USB 3 in Win7 and Win10. All the windows guests now boot with their USB controllers enabled but for USB I'm limited to USB 1.1. Anyone else having issues or any suggestions on how to correct this problem?
    Last edited by kilgoretrout; Jul 04, 2022, 04:48 PM.
    Tags: None
    • Top
    • Bottom
    #2
    Further investigation revealed that virtualbox-ext-pack is no longer installed. That package is necessary for USB 2 and 3 support in virtualbox. I attempted to install the package and got:
    Code:
    sudo apt install virtualbox-ext-pack
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
virtualbox-ext-pack : Depends: virtualbox (< 6.1.32-dfsg-z) but 6.1.34-dfsg-3~ubuntu1.22.04.1 is to be installed or
virtualbox-6.1 but it is not installable[FONT=monospace] [/FONT]
    Finally, checked out the package version for virtualbox-ext-pack and it's 6.1.32-1 while all the other virtualbox packages are 6.1.34-1. So apparently, with the last update a new virtualbox-ext-pack package was never made.
    Last edited by kilgoretrout; Jul 04, 2022, 05:10 PM.
    • Top
    • Bottom

    Comment

      #3
      Have you checked for updates again since trying to install things? Your local mirror might not be fully caught up at the moment, perhaps.

      The correct version seems to be out there for both offending packages:

      https://packages.ubuntu.com/jammy-up...albox-ext-pack

      https://packages.ubuntu.com/jammy-updates/virtualbox



      • Top
      • Bottom

      Comment

        #4
        Originally posted by claydoh View Post
        Have you checked for updates again since trying to install things? Your local mirror might not be fully caught up at the moment, perhaps.
        I think so.

        Curious, I looked up virtualbox-ext details in my updated jammy, and it said the version available was 6.1.32. Using sudo software-properties-qt I changed the "Download from" from my local server to the "Main server", and it reloaded the index. Now muon says the version available is 6.1.34.
        Regards, John Little
        • Top
        • Bottom

        Comment

          #5
          As of this morning, I still have the 6.1.32-1 package on my repo. I downloaded the updated package from this source:

          http://archive.ubuntu.com/ubuntu/poo...2.04.1_all.deb

          After installation, the problem was fixed.
          The package seemed to be in some in-between state from the proposed multiverse repo to the official multistate repo. The package itself is just a downloader that downloads the extension package from some other non-ubuntu repo. I assume that's because of some oracle licensing issues where the package is free for personal use but not for commercial distribution.

          Edit: Checked my kubuntu 20.04 installation on another box and it has the 6.1.34-1 extension package. All this points to some problem with the 22.04 repo which will hopefully be corrected in the near future.
          Last edited by kilgoretrout; Jul 05, 2022, 08:26 AM.
          • Top
          • Bottom

          Comment

            #6
            I'll wager that updates have been 'phased', a new feature in the version of Apt found in Hirsuite and Jammy.

            apt policy virtualbox and apt policy virtualbox-ext-pack will show information.

            Link dump
            https://www.phoronix.com/scan.php?pa...Phased-Updates
            https://discourse.ubuntu.com/t/phase...in-21-04/20345
            https://ubunlog.com/en/apt-2-2-0-lle...r-fases-y-mas/
            https://wiki.ubuntu.com/StableReleaseUpdates#Phasing
            https://people.canonical.com/~ubuntu...d-updates.html

            Oddly, as Virtualbox stuff is on the list, I wonder why you are seeing one being phased, and the other not being phased.
            On my quickie Jammy virtual machine, all VB packages are marked as phased no matter which mirror I use.



            • Top
            • Bottom

            Comment

              #7
              Oddly, as Virtualbox stuff is on the list, I wonder why you are seeing one being phased, and the other not being phased.
              On my quickie Jammy virtual machine, all VB packages are marked as phased no matter which mirror I use.
              One possible/probable explanation is that I forced and upgrade from 20.04 last month.
              • Top
              • Bottom

              Comment

              Previous template Next
              Working...
              X