Comment # 2 on bug 1026994 from Steve Thompson

(In reply to Larry Finger from comment #1)
> I have some questions:
> 1. I think you selected VirtualBox after restarting Leap 42.2. Is that
> correct?
> 2. If the previous answer is yes, did you update 42.2 before installing VB?
> 3. What is the evidence that the 42.1 repo was being used?
> 
> For info, the openSUSE rpm does not build the VB modules on the user's
> computer the way that the Oracle download does. Rather, we rely on OBS
> building the modules and updating them whenever the kernel changes.

1 Yes.
2 By update, you mean did I run yast and pull in patches? Yes
3 There is none now. But I do have a DVD burned with the LEAP 42.1 install that
I have used on 3 systems.

Also, you will probably want this little gem now that I've managed to capture
it and email it to this system (my own Leap 42.2 desktop):

----- 
VirtualBox Graphical User Interface Version 5.1.14_SUSE r112924
� 2004-2017 Oracle Corporation (Qt5.6.1)
Copyright � 2017 Oracle Corporation and/or its affiliates. All rights reserved.

Start gives attempt at build of the "window" for W7, immediately disappears.
Then this message shows up:

Failed to open a session for the virtual machine W7 Home Premium.

AMD-V is disabled in the BIOS (or by the host OS) (VERR_SVM_DISABLED).

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
-----

I have not gone into that machine's bios to do anything other than alter the
boot order.