Page 1 of 4 123 ... LastLast
Results 1 to 10 of 39

Thread: Virtualbox stopped working after a windows update

  1. #1

    Default Virtualbox stopped working after a windows update

    I was using virtual box, just fine for months already, running win 10 64 bit ( for a game)

    Yesterday got a windows update and today it seems to have stopped working.

    So I download a fresh iso from microsoft, deleted the old one made a new VM, but now I get again the same error I had with the old version.



    Code:
    Message from syslogd@linux-2ls4 at Jul 9 17:50:33 ...
    kernel:[ 1485.580528] !!Assertion Failed!!
    Message from syslogd@linux-2ls4 at Jul 9 17:50:33 ...
    kernel:[ 1485.580528] Expression: pCritSect->s.Core.NativeThreadOwner == hNativeSelf
    Message from syslogd@linux-2ls4 at Jul 9 17:50:33 ...
    kernel:[ 1485.580528] Location : /home/abuild/rpmbuild/BUILD/VirtualBox-6.1.22/src/VBox/VMM/VMMAll/PDMAllCritSect.cpp(575) int PDMCritSectLeave(PPDMCRITSECT)
    Message from syslogd@linux-2ls4 at Jul 9 17:50:33 ...
    kernel:[ 1485.580564] ffffa5d903a8e000 : ffffffffffffffff != 00007ff9747f8640; cLockers=-1 cNestings=1
    I am totally confused. This happens when I try to start windows 10 after adding the win 10 iso, Instead of the windows 10 install I should get.

    When I checked in virtual box it says I am running the newest version.

    Anybody has any idea on what is wrong ?
    Did virtual box got updated yesterday ? I remember installing the latest updates for tumbleweed yesterday.

    Could this be kernel related ?

  2. #2
    Join Date
    Oct 2014
    Location
    Italy
    Posts
    2,214

    Default Re: Virtualbox stopped working after a windows update

    Not sure to understand what your problem really is, but Tumbleweed kernel was updated to 5.13 and current VirtualBox 6.1.22 is not compatible with that.
    If you still have a 5.12.x kernel in your system please try to boot with it and see if your problem is gone.
    Otherwise you should wait for VBox 6.1.24 that hopefully wll be compatible with 5.13 kernels.
    Tumbleweed Gnome on i7 4720HQ + Geforce GTX960M
    testing Leap 15.3

  3. #3

    Default Re: Virtualbox stopped working after a windows update

    To keep it short virtual box stopped working. (I do not know if it broke after win10 update or after the tumbleweed update)

    But I will check what kernel I am running.

    Code:
    guus@linux-2ls4:~> uname -r 
    5.13.0-1-default
    

  4. #4

    Default Re: Virtualbox stopped working after a windows update

    So I need to install an older kernel ?

  5. #5
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    31,703
    Blog Entries
    15

    Default Re: Virtualbox stopped working after a windows update

    Quote Originally Posted by Gps2010 View Post
    So I need to install an older kernel ?
    Hi
    It should still be there, just select that at grub in advanced options....

    Code:
     zypper se -si kernel-default
    
    S  | Name                 | Type    | Version     | Arch   | Repository
    ---+----------------------+---------+-------------+--------+----------------------
    i+ | kernel-default       | package | 5.12.13-1.1 | x86_64 | (System Packages)
    i+ | kernel-default       | package | 5.13.0-1.2  | x86_64 | Main Repository (OSS)
    i+ | kernel-default-devel | package | 5.12.13-1.1 | x86_64 | (System Packages)
    i+ | kernel-default-devel | package | 5.13.0-1.2  | x86_64 | Main Repository (OSS)
    Consider switching to a different technology not bound by this, libvirt/qemu?

    You can also specify keeping kernel versions in /etc/zypp/zypp.conf in the section `multiversion.kernels`.
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  6. #6

    Default Re: Virtualbox stopped working after a windows update

    Thank you will have a look at grub screen.



    Consider switching to a different technology not bound by this, libvirt/qemu?
    How do I switch to that ?

  7. #7
    Join Date
    Jun 2008
    Location
    Podunk
    Posts
    31,703
    Blog Entries
    15

    Default Re: Virtualbox stopped working after a windows update

    Quote Originally Posted by Gps2010 View Post
    Thank you will have a look at grub screen.





    How do I switch to that ?
    Hi
    Whilst Leap based, still applicable;
    https://doc.opensuse.org/documentati...alization.html

    Likely mean creating a new machine....
    Cheers Malcolm °¿° SUSE Knowledge Partner (Linux Counter #276890)
    SUSE SLE, openSUSE Leap/Tumbleweed (x86_64) | GNOME DE
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below... Thanks!

  8. #8

    Default Re: Virtualbox stopped working after a windows update

    I had already created a new virtual machine in Virtual box, but instead of Virtual box I should be using xen or kvm ?

    Then I won't have this problem again ? A kernel update breaking my virtual machine ?

  9. #9
    Join Date
    Oct 2014
    Location
    Italy
    Posts
    2,214

    Default Re: Virtualbox stopped working after a windows update

    Quote Originally Posted by Gps2010 View Post
    I had already created a new virtual machine in Virtual box, but instead of Virtual box I should be using xen or kvm ?

    Then I won't have this problem again ? A kernel update breaking my virtual machine ?
    I never used xen and some time passed since I last used kvm so other members may know better, but AFAIK the kernel part of kvm is included in the mainline kernel and no "foreign" kernel module is needed; so you won't have _this_ problem again.
    You need to define a new virtual machine, but maybe you can reuse the same disk image you used with VBox, depending on how it was defined.
    Generally speaking I found that VBox is easier to use to the casual user, but as you discovered "the hard way" using it on a Tumbleweed host is not always smooth.
    Tumbleweed Gnome on i7 4720HQ + Geforce GTX960M
    testing Leap 15.3

  10. #10

    Default Re: Virtualbox stopped working after a windows update

    I already have a love / hate relation with computers for many years.

    Tumbleweed fits that profile.



    I did find the 5.12 kernel in grub.

    Gonna do some searching for an easy explanation on how to use kvm.

    VB is easier for first time users of an virtual machine, but who knows what might I might find. Lets try you tube too.

    I already deleted the virtual machine in VB, looking back I should not have done that.

Page 1 of 4 123 ... LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •