Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 24

Thread: Cannot open VM after recent OS fix

  1. #11
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    10,927
    Blog Entries
    2

    Default Re: Cannot open VM after recent OS fix

    Quote Originally Posted by rgietzen View Post
    Ok. I'm back at this.

    I'm a little nervous about deleting all of those files. Let me check before doing so. For example, do I want to keep any that say "guest" anywhere? Like these:

    /lib/modules/5.1.7-1-default/kernel/drivers/virt/vboxguest
    /lib/modules/5.1.7-1-default/kernel/drivers/virt/vboxguest/vboxguest.ko
    /usr/include/linux/vboxguest.h
    /usr/src/linux-5.1.7-1/drivers/virt/vboxguest
    /usr/src/linux-5.1.7-1/drivers/virt/vboxguest/Kconfig
    /usr/src/linux-5.1.7-1/drivers/virt/vboxguest/Makefile
    /usr/src/linux-5.1.7-1/include/uapi/linux/vboxguest.h
    Delete the above files.
    In particular, the file ending in ".ko" is likely the one giving you the most problems.


    Do not delete the files below, those are related to your Guests
    Quote Originally Posted by rgietzen View Post

    And what about these ones for the Windows 10:

    /home/VirtualBox VMs/Windows 10/Windows 10.vbox
    /home/VirtualBox VMs/Windows 10/Windows 10.vbox-prev

    And also there are many for the extension pack. I thought that was all related to the guest, not the host. Do I keep all the extension pack files?

    What do you think?
    Although it probably won't make much difference, delete those files related to the extension pack, they will be re-installed when VBox is re-installed.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  2. #12

    Default Re: Cannot open VM after recent OS fix

    Quote Originally Posted by tsu2 View Post
    Delete the above files.
    In particular, the file ending in ".ko" is likely the one giving you the most problems.


    Do not delete the files below, those are related to your Guests


    Although it probably won't make much difference, delete those files related to the extension pack, they will be re-installed when VBox is re-installed.

    TSU
    I removed the suggested files. Then installed Vbox 5.2 via YaST and restarted. I received the error this error:

    Code:
    Kernel driver not installed (rc=-1908)
    
    The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing
    
    '/sbin/vboxconfig'
    
    as root.
    
    If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information.
    
    where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.
    I ran the sbin command and got this:

    Code:
    linux-vqod:~ # /sbin/vboxconfig
    Created symlink /etc/systemd/system/multi-user.target.wants/vboxdrv.service → /usr/lib/systemd/system/vboxdrv.service.
    Created symlink /etc/systemd/system/multi-user.target.wants/vboxballoonctrl-service.service → /usr/lib/systemd/system/vboxballoonctrl-service.service.
    Created symlink /etc/systemd/system/multi-user.target.wants/vboxautostart-service.service → /usr/lib/systemd/system/vboxautostart-service.service.
    Created symlink /etc/systemd/system/multi-user.target.wants/vboxweb-service.service → /usr/lib/systemd/system/vboxweb-service.service.
    vboxdrv.sh: Stopping VirtualBox services.
    vboxdrv.sh: Starting VirtualBox services.
    vboxdrv.sh: Building VirtualBox kernel modules.
    This system is currently not set up to build kernel modules.
    Please install the Linux kernel "header" files matching the current kernel
    for adding new hardware support to the system.
    The distribution packages containing the headers are probably:
        kernel-default-devel kernel-default-devel-5.1.7-1
    This system is currently not set up to build kernel modules.
    Please install the Linux kernel "header" files matching the current kernel
    for adding new hardware support to the system.
    The distribution packages containing the headers are probably:
        kernel-default-devel kernel-default-devel-5.1.7-1
    
    There were problems setting up VirtualBox.  To re-start the set-up process, run
      /sbin/vboxconfig
    as root.  If your system is using EFI Secure Boot you may need to sign the
    kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
     them. Please see your Linux system's documentation for more information.
    I then attempted to install the headers after reading a tutorial. It suggested I go into YaST, then Software Management, then click on Patterns and select Base Development, C/C++ and Linux Kernel Development. Then a restart, but the same error messages are given both by Vbox and in the Konsole when I retry the sbin command.

    I started to look into the EFI secure boot suggestion. Could this be the fix? What do you think?

  3. #13
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    10,927
    Blog Entries
    2

    Default Re: Cannot open VM after recent OS fix

    Quote Originally Posted by rgietzen View Post
    I removed the suggested files. Then installed Vbox 5.2 via YaST and restarted. I received the error this error:

    Code:
    Kernel driver not installed (rc=-1908)
    
    The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing
    
    '/sbin/vboxconfig'
    
    as root.
    
    If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system's documentation for more information.
    
    where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.
    I ran the sbin command and got this:

    Code:
    linux-vqod:~ # /sbin/vboxconfig
    Created symlink /etc/systemd/system/multi-user.target.wants/vboxdrv.service → /usr/lib/systemd/system/vboxdrv.service.
    Created symlink /etc/systemd/system/multi-user.target.wants/vboxballoonctrl-service.service → /usr/lib/systemd/system/vboxballoonctrl-service.service.
    Created symlink /etc/systemd/system/multi-user.target.wants/vboxautostart-service.service → /usr/lib/systemd/system/vboxautostart-service.service.
    Created symlink /etc/systemd/system/multi-user.target.wants/vboxweb-service.service → /usr/lib/systemd/system/vboxweb-service.service.
    vboxdrv.sh: Stopping VirtualBox services.
    vboxdrv.sh: Starting VirtualBox services.
    vboxdrv.sh: Building VirtualBox kernel modules.
    This system is currently not set up to build kernel modules.
    Please install the Linux kernel "header" files matching the current kernel
    for adding new hardware support to the system.
    The distribution packages containing the headers are probably:
        kernel-default-devel kernel-default-devel-5.1.7-1
    This system is currently not set up to build kernel modules.
    Please install the Linux kernel "header" files matching the current kernel
    for adding new hardware support to the system.
    The distribution packages containing the headers are probably:
        kernel-default-devel kernel-default-devel-5.1.7-1
    
    There were problems setting up VirtualBox.  To re-start the set-up process, run
      /sbin/vboxconfig
    as root.  If your system is using EFI Secure Boot you may need to sign the
    kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
     them. Please see your Linux system's documentation for more information.
    I then attempted to install the headers after reading a tutorial. It suggested I go into YaST, then Software Management, then click on Patterns and select Base Development, C/C++ and Linux Kernel Development. Then a restart, but the same error messages are given both by Vbox and in the Konsole when I retry the sbin command.

    I started to look into the EFI secure boot suggestion. Could this be the fix? What do you think?
    The kernel development pattern won't build kernel modules (which are kernel add-ons), it's for building the core parts of the kernel (eg initramfs).
    The required packages for building kernel modules in general can be installed with the following command (assuming you're running the default kernel)
    Code:
    zypper in gcc make kernel-devel kernel-default-devel
    After that, you should be able to successfully install.

    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  4. #14

    Default Re: Cannot open VM after recent OS fix

    Quote Originally Posted by tsu2 View Post
    The kernel development pattern won't build kernel modules (which are kernel add-ons), it's for building the core parts of the kernel (eg initramfs).
    The required packages for building kernel modules in general can be installed with the following command (assuming you're running the default kernel)
    Code:
    zypper in gcc make kernel-devel kernel-default-devel
    After that, you should be able to successfully install.

    TSU
    Bad news. The problem is still there. I ran the code and it did find another package to install. But when I attempt to start up the Vbox, I get the same error message. I ran the sbin command again, but get the same error message.

    Code:
    linux-vqod:~ # /sbin/vboxconfig
    Created symlink /etc/systemd/system/multi-user.target.wants/vboxdrv.service → /usr/lib/systemd/system/vboxdrv.service.
    Created symlink /etc/systemd/system/multi-user.target.wants/vboxballoonctrl-service.service → /usr/lib/systemd/system/vboxballoonctrl-service.service.
    Created symlink /etc/systemd/system/multi-user.target.wants/vboxautostart-service.service → /usr/lib/systemd/system/vboxautostart-service.service.
    Created symlink /etc/systemd/system/multi-user.target.wants/vboxweb-service.service → /usr/lib/systemd/system/vboxweb-service.service.
    vboxdrv.sh: Stopping VirtualBox services.
    vboxdrv.sh: Starting VirtualBox services.
    vboxdrv.sh: Building VirtualBox kernel modules.
    This system is currently not set up to build kernel modules.
    Please install the Linux kernel "header" files matching the current kernel
    for adding new hardware support to the system.
    The distribution packages containing the headers are probably:
        kernel-default-devel kernel-default-devel-5.1.7-1
    This system is currently not set up to build kernel modules.
    Please install the Linux kernel "header" files matching the current kernel
    for adding new hardware support to the system.
    The distribution packages containing the headers are probably:
        kernel-default-devel kernel-default-devel-5.1.7-1
    
    There were problems setting up VirtualBox.  To re-start the set-up process, run
      /sbin/vboxconfig
    as root.  If your system is using EFI Secure Boot you may need to sign the
    kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load
     them. Please see your Linux system's documentation for more information.
    I checked and do have EFI secure boot enabled.

    Do you have any other ideas?

    By the thanks for being patient with me. I'm looking forward to announce a success soon .

  5. #15
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    10,927
    Blog Entries
    2

    Default Re: Cannot open VM after recent OS fix

    The most common ;cause for failure even after adding the appropriate kernel headers and and compiler is that your kernel and kernel-devel packages are out of sync. This often happens when for instance you're currently adding packages not all at once, and it's always good practice to update your system prior to installing new packages.

    Update your system with the following which should re-sync package versions (all latest) and try installing Virtualbox again
    Code:
    zypper up
    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  6. #16
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,887

    Default AW: Cannot open VM after recent OS fix

    Please post:
    Code:
    zypper se -si kernel virtualbox vbox
    Code:
    zypper lr -d
    Code:
    uname -a
    Last edited by Sauerland; 21-Jun-2019 at 08:38.

  7. #17
    Join Date
    Feb 2010
    Location
    Germany
    Posts
    2,478

    Question Re: Cannot open VM after recent OS fix

    Quote Originally Posted by rgietzen View Post
    When I tried to run it at first, it suggested I run /sbin/vboxconfig. That produced an error message something like host "kernel driver" not installed. I figured the software got erased with my OS fix and so I went to YAST and downloaded virtualbox there. But then I realized it was a different version than I had previously installed. It was 5.2, but I had 5.2.18.
    The current Leap 15.0 Oracle VirtualBox version is 5.2.24

    [QUOTE=rgietzen;2905484]
    Code:
    setting /usr/lib/virtualbox/VBoxNetNAT to root:vboxusers 4750. (wrong permissions 0755)                                
    setting /usr/lib/virtualbox/VBoxNetDHCP to root:vboxusers 4750. (wrong permissions 0750)                               
    setting /usr/lib/virtualbox/VBoxNetAdpCtl to root:vboxusers 4750. (wrong permissions 0750)                             
    setting /usr/lib/virtualbox/VBoxHeadless to root:vboxusers 4750. (wrong permissions 0750)
    This ain't an error.
    • It's information that the openSUSE package sets the permissions to something other than what Oracle believes they should be.


    Quote Originally Posted by rgietzen View Post
    The desktop entry file
    file:///root/.local/share/plasma_icons/virtualbox.desktop
    is not valid.
    You're running the VirtualBox VMs from the user “root”?? !!!!!

    Please be aware that, there's a magic Oracle VirtualBox CLI tool: “VBoxManage”

    Please post the following Terminal outputs:
    • VBoxManage list extpacks
    • VBoxManage list --long vms

    Examples are as follows (my VirtualBox VMs run from a “normal” user – not “root” … ):
    Code:
     > VBoxManage list extpacks
    Extension Packs: 1
    Pack no. 0:   Oracle VM VirtualBox Extension Pack
    Version:      5.2.24
    Revision:     128163
    Edition:      
    Description:  USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk Encryption, NVMe.
    VRDE Module:  VBoxVRDP
    Usable:       true 
    Why unusable: 
     >
    Code:
     > VBoxManage list --long vms
    Name:            XXX
    Groups:          /
    Guest OS:        Windows 10 (64-bit)
    UUID:            18dd02ad-3ede-4c7a-bb61-427cde005a3f
    Config file:     /homeXX/User-VMs/XXX/XXX/XXX.vbox
    Snapshot folder: /homeXX/User-VMs/XXX/XXX/Snapshots
    Log folder:      /homeXX/User-VMs/XXX/XXX/Logs
    Hardware UUID:   18dd02ad-3ede-4c7a-bb61-427cde005a3f
    Memory size:     5120MB
    Page Fusion:     off
    VRAM size:       256MB
    CPU exec cap:    100%
    HPET:            off
    Chipset:         piix3
    Firmware:        BIOS
    Number of CPUs:  4
    PAE:             on
    Long Mode:       on
    Triple Fault Reset: off
    APIC:            on
    X2APIC:          off
      .
      .
      .
      .
    USB Device Filters:
    
    <none>
    
    Bandwidth groups:  <none>
    
    Shared folders:
    
    Name: 'tmp', Host path: '/homeXX/User-VMs/XXX/tmp' (machine mapping), writable
    Name: 'WindowsSicherungen', Host path: '/homeXX/User-VMs/XXX/WindowsSicherungen' (machine mapping), writable
    
    Capturing:          not active
    Capture audio:      not active
    Capture screens:    0
    Capture file:       /homeXX/User-VMs/XXX/XXX/XXX.webm
    Capture dimensions: 1024x768
    Capture rate:       512 kbps
    Capture FPS:        25
    Capture options:    ac_enabled=false
    
    Description:
    Windows 10.
    Sigma PhotoPro.
    Silkypix (Pentax).
    Guest:
    
    Configured memory balloon size:      0 MB
    
    
     >

    As an aside, please be aware that, when you upgrade from Leap 15.0 to Leap 15.1, you may, possibly, experience some pain with the VirtualBox upgrade from V5 to V6:
    • The upgrade doesn't handle the VirtualBox Extension Pack upgrade in a pleasant fashion.
    • One has to use the VirtualBox CLI Manager (VBoxManage) to remove the 5.22 or 5.24 Extension Pack and then install the correct V6 Extension Pack …

  8. #18

    Default Re: AW: Cannot open VM after recent OS fix

    Quote Originally Posted by Sauerland View Post
    Please post:
    Code:
    zypper se -si kernel virtualbox vbox
    Code:
    zypper lr -d
    Code:
    uname -a
    Here you go:

    Code:
    linux-vqod:~ # zypper se -si kernel virtualbox vbox
    Loading repository data...
    Reading installed packages...
    
    S  | Name                             | Type    | Version                     | Arch   | Repository                           
    ---+----------------------------------+---------+-----------------------------+--------+--------------------------------------
    i+ | VirtualBox-5.2                   | package | 5.2.30_130521_openSUSE150-1 | x86_64 | VirtualBox for openSUSE 15.0 - x86_64
    i+ | devel_kernel                     | pattern | 20170319-lp150.2.6          | x86_64 | openSUSE-Leap-15.0-Oss               
    i+ | kernel-default                   | package | 5.1.7-1.1                   | x86_64 | (System Packages)                    
    i+ | kernel-default                   | package | 4.12.14-lp150.12.61.1       | x86_64 | openSUSE-Leap-15.0-Update            
    i+ | kernel-default-devel             | package | 4.12.14-lp150.12.64.1       | x86_64 | openSUSE-Leap-15.0-Update            
    i+ | kernel-default-devel             | package | 4.12.14-lp150.12.61.1       | x86_64 | openSUSE-Leap-15.0-Update            
    i+ | kernel-devel                     | package | 5.1.7-1.1                   | noarch | (System Packages)                    
    i+ | kernel-devel                     | package | 4.12.14-lp150.12.64.1       | noarch | openSUSE-Leap-15.0-Update            
    i+ | kernel-devel                     | package | 4.12.14-lp150.12.61.1       | noarch | openSUSE-Leap-15.0-Update            
    i+ | kernel-firmware                  | package | 20190312-lp150.2.16.1       | noarch | openSUSE-Leap-15.0-Update            
    i+ | kernel-macros                    | package | 5.1.7-1.1                   | noarch | (System Packages)                    
    i  | kernel-source                    | package | 4.12.14-lp150.12.64.1       | noarch | openSUSE-Leap-15.0-Update            
    i  | kernel-syms                      | package | 4.12.14-lp150.12.64.1       | x86_64 | openSUSE-Leap-15.0-Update            
    i  | kernel-syms                      | package | 4.12.14-lp150.12.61.1       | x86_64 | openSUSE-Leap-15.0-Update            
    i+ | patterns-devel-base-devel_kernel | package | 20170319-lp150.2.6          | x86_64 | openSUSE-Leap-15.0-Oss
    Code:
    linux-vqod:~ # zypper lr -d
    Repository priorities in effect:                                                                                    (See 'zypper lr -P' for details)
          99 (default priority) :  4 repositories                                                                               
         120 (lowered priority) :  1 repository                                                                                 
                                                                                                                                   
    #  | Alias                     | Name                                    | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                                   | Service                                                        
    ---+---------------------------+-----------------------------------------+---------+-----------+---------+----------+--------+---------------------------------------------------------------------------------------+--------                                                             
     1 | openSUSE-Leap-15.0-1      | openSUSE-Leap-15.0-1                    | No      | ----      | ----    |   99     | rpm-md | hd:///?device=/dev/disk/by-id/usb-SanDisk_Cruzer_Blade_4C530110030614100045-0:0-part2 |                                                                        
     2 | repo-debug                | openSUSE-Leap-15.0-Debug                | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/distribution/leap/15.0/repo/oss/                   |                                                                            
     3 | repo-debug-non-oss        | openSUSE-Leap-15.0-Debug-Non-Oss        | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/distribution/leap/15.0/repo/non-oss/               |                                                                               
     4 | repo-debug-update         | openSUSE-Leap-15.0-Update-Debug         | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/update/leap/15.0/oss/                              |        
     5 | repo-debug-update-non-oss | openSUSE-Leap-15.0-Update-Debug-Non-Oss | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/update/leap/15.0/non-oss/                          |        
     6 | repo-non-oss              | openSUSE-Leap-15.0-Non-Oss              | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/distribution/leap/15.0/repo/non-oss/                     |        
     7 | repo-oss                  | openSUSE-Leap-15.0-Oss                  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/distribution/leap/15.0/repo/oss/                         |        
     8 | repo-source               | openSUSE-Leap-15.0-Source               | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/source/distribution/leap/15.0/repo/oss/                  |        
     9 | repo-source-non-oss       | openSUSE-Leap-15.0-Source-Non-Oss       | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/source/distribution/leap/15.0/repo/non-oss/              |        
    10 | repo-update               | openSUSE-Leap-15.0-Update               | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.0/oss/                                    |        
    11 | repo-update-non-oss       | openSUSE-Leap-15.0-Update-Non-Oss       | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/15.0/non-oss/                                |        
    12 | virtualbox                | VirtualBox for openSUSE 15.0 - x86_64   | Yes     | (r ) Yes  | Yes     |  120     | rpm-md | http://download.virtualbox.org/virtualbox/rpm/opensuse/15.0/x86_64
    Code:
    Linux linux-vqod 5.1.7-1-default #1 SMP Tue Jun 4 07:56:54 UTC 2019 (55f2451) x86_64 x86_64 x86_64 GNU/Linux

  9. #19

    Default Re: Cannot open VM after recent OS fix

    [QUOTE=dcurtisfra;2906491]The current Leap 15.0 Oracle VirtualBox version is 5.2.24

    Quote Originally Posted by rgietzen View Post
    Code:
    setting /usr/lib/virtualbox/VBoxNetNAT to root:vboxusers 4750. (wrong permissions 0755)                                
    setting /usr/lib/virtualbox/VBoxNetDHCP to root:vboxusers 4750. (wrong permissions 0750)                               
    setting /usr/lib/virtualbox/VBoxNetAdpCtl to root:vboxusers 4750. (wrong permissions 0750)                             
    setting /usr/lib/virtualbox/VBoxHeadless to root:vboxusers 4750. (wrong permissions 0750)
    This ain't an error.
    • It's information that the openSUSE package sets the permissions to something other than what Oracle believes they should be.



    You're running the VirtualBox VMs from the user “root”?? !!!!!

    Please be aware that, there's a magic Oracle VirtualBox CLI tool: “VBoxManage”

    Please post the following Terminal outputs:
    • VBoxManage list extpacks
    • VBoxManage list --long vms

    Examples are as follows (my VirtualBox VMs run from a “normal” user – not “root” … ):
    Code:
     > VBoxManage list extpacks
    Extension Packs: 1
    Pack no. 0:   Oracle VM VirtualBox Extension Pack
    Version:      5.2.24
    Revision:     128163
    Edition:      
    Description:  USB 2.0 and USB 3.0 Host Controller, Host Webcam, VirtualBox RDP, PXE ROM, Disk Encryption, NVMe.
    VRDE Module:  VBoxVRDP
    Usable:       true 
    Why unusable: 
     >
    Code:
     > VBoxManage list --long vms
    Name:            XXX
    Groups:          /
    Guest OS:        Windows 10 (64-bit)
    UUID:            18dd02ad-3ede-4c7a-bb61-427cde005a3f
    Config file:     /homeXX/User-VMs/XXX/XXX/XXX.vbox
    Snapshot folder: /homeXX/User-VMs/XXX/XXX/Snapshots
    Log folder:      /homeXX/User-VMs/XXX/XXX/Logs
    Hardware UUID:   18dd02ad-3ede-4c7a-bb61-427cde005a3f
    Memory size:     5120MB
    Page Fusion:     off
    VRAM size:       256MB
    CPU exec cap:    100%
    HPET:            off
    Chipset:         piix3
    Firmware:        BIOS
    Number of CPUs:  4
    PAE:             on
    Long Mode:       on
    Triple Fault Reset: off
    APIC:            on
    X2APIC:          off
      .
      .
      .
      .
    USB Device Filters:
    
    <none>
    
    Bandwidth groups:  <none>
    
    Shared folders:
    
    Name: 'tmp', Host path: '/homeXX/User-VMs/XXX/tmp' (machine mapping), writable
    Name: 'WindowsSicherungen', Host path: '/homeXX/User-VMs/XXX/WindowsSicherungen' (machine mapping), writable
    
    Capturing:          not active
    Capture audio:      not active
    Capture screens:    0
    Capture file:       /homeXX/User-VMs/XXX/XXX/XXX.webm
    Capture dimensions: 1024x768
    Capture rate:       512 kbps
    Capture FPS:        25
    Capture options:    ac_enabled=false
    
    Description:
    Windows 10.
    Sigma PhotoPro.
    Silkypix (Pentax).
    Guest:
    
    Configured memory balloon size:      0 MB
    
    
     > 
    
    As an aside, please be aware that, when you upgrade from Leap 15.0 to Leap 15.1, you may, possibly, experience some pain with the VirtualBox upgrade from V5 to V6:
    • The upgrade doesn't handle the VirtualBox Extension Pack upgrade in a pleasant fashion.
    • One has to use the VirtualBox CLI Manager (VBoxManage) to remove the 5.22 or 5.24 Extension Pack and then install the correct V6 Extension Pack …
    Thanks for offering to help. Yes, I use root as my user desktop. I am aware of the all the warnings and accept responsibility.

    Here are the outputs:

    Code:
    VBoxManage list extpacks
    WARNING: The vboxdrv kernel module is not loaded. Either there is no module
             available for the current kernel (5.1.7-1-default) or it failed to
             load. Please recompile the kernel module and install it by
    
               sudo /sbin/vboxconfig
    
             You will not be able to start VMs until this problem is fixed.
    Extension Packs: 0
    Code:
    linux-vqod:~ # VBoxManage list --long vms
    WARNING: The vboxdrv kernel module is not loaded. Either there is no module
             available for the current kernel (5.1.7-1-default) or it failed to
             load. Please recompile the kernel module and install it by
    
               sudo /sbin/vboxconfig
    
             You will not be able to start VMs until this problem is fixed.
    Name:            Windows 10
    Groups:          /
    Guest OS:        Windows 10 (64-bit)
    UUID:            bb24902d-cefe-4211-83ea-71f4abc72108
    Config file:     /home/VirtualBox VMs/Windows 10/Windows 10.vbox
    Snapshot folder: /home/VirtualBox VMs/Windows 10/Snapshots
    Log folder:      /home/VirtualBox VMs/Windows 10/Logs
    Hardware UUID:   bb24902d-cefe-4211-83ea-71f4abc72108
    Memory size:     4423MB
    Page Fusion:     off
    VRAM size:       128MB
    CPU exec cap:    100%
    HPET:            off
    Chipset:         piix3
    Firmware:        BIOS
    Number of CPUs:  1
    PAE:             off
    Long Mode:       on
    Triple Fault Reset: off
    APIC:            on
    X2APIC:          off
    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
    BIOS APIC mode:  APIC
    Time offset:     0ms
    RTC:             local time
    Hardw. virt.ext: on
    Nested Paging:   on
    Large Pages:     off
    VT-x VPID:       on
    VT-x unr. exec.: on
    Paravirt. Provider: Default
    Effective Paravirt. Provider: HyperV
    State:           powered off (since 2019-06-07T00:01:57.000000000)
    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):            SATA
    Storage Controller Type (0):            IntelAhci
    Storage Controller Instance Number (0): 0
    Storage Controller Max Port Count (0):  30
    Storage Controller Port Count (0):      2
    Storage Controller Bootable (0):        on
    SATA (0, 0): /home/VirtualBox VMs/Windows 10/Windows 10.vdi (UUID: ad6e0c5b-8131-46fa-bcf1-31f016fe2036)
    SATA (1, 0): /root/.config/VirtualBox/VBoxGuestAdditions_5.2.18.iso (UUID: a6487b11-36ca-4193-b286-60434bdfb618)
    NIC 1:           MAC: 0800274BF083, 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 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
    UART 3:          disabled
    UART 4:          disabled
    LPT 1:           disabled
    LPT 2:           disabled
    Audio:           enabled (Driver: ALSA, Controller: HDA, Codec: STAC9221)
    Audio playback:  disabled
    Audio capture: enabled
    Clipboard Mode:  HostToGuest
    Drag and drop Mode: disabled
    VRDE:            disabled
    USB:             disabled
    EHCI:            disabled
    XHCI:            enabled
    
    USB Device Filters:
    
    <none>
    
    Bandwidth groups:  <none>
    
    Shared folders:  
    
    Name: 'VM_Shared_Folder', Host path: '/home/Documents/VM Shared Folder' (machine mapping), writable
    
    Capturing:          not active
    Capture audio:      not active
    Capture screens:    0
    Capture file:       /home/VirtualBox VMs/Windows 10/Windows 10.webm
    Capture dimensions: 1024x768
    Capture rate:       512 kbps
    Capture FPS:        25
    Capture options:    ac_enabled=false
    
    Guest:
    
    Configured memory balloon size:      0 MB

  10. #20
    Join Date
    Mar 2011
    Location
    Sauerland
    Posts
    3,887

    Default AW: Cannot open VM after recent OS fix

    You are running an kernel outside Leap 15.
    And have not installed kernel-default-devel for that Kernel.....

    I would delete the kernel 5.1 and use the Kernel 4.12 shipped with Leap 15

Page 2 of 3 FirstFirst 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
  •