On Sun, Feb 26, 2017 at 11:13 PM, Ed Greshko wrote:
>
>>> Let me add that I am using Oracle VirtualBox (from
>>> http://www.virtualbox.org/):
>>>
>>> VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64
>> As am I
>>
>> The procedure I gave you will get you going as I did me.
>>
>> I'll report this
On 02/27/17 04:42, Ed Greshko wrote:
> On 02/26/17 23:15, Paul Smith wrote:
>> Let me add that I am using Oracle VirtualBox (from
>> http://www.virtualbox.org/):
>>
>> VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64
> As am I
>
> The procedure I gave you will get you going as I did me.
>
> I'll
On 02/26/17 23:15, Paul Smith wrote:
> Let me add that I am using Oracle VirtualBox (from
> http://www.virtualbox.org/):
>
> VirtualBox-5.1-5.1.14_112924_fedora25-1.x86_64
As am I
The procedure I gave you will get you going as I did me.
I'll report this against selinux soon.
--
Fedora Use
On Sun, Feb 26, 2017 at 2:27 PM, Paul Smith wrote:
>>>
After doing the updates of today (selinux included), virtualbox stopped
working:
# /usr/lib/virtualbox/vboxdrv.sh setup
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
>>
On 02/26/17 22:27, Paul Smith wrote:
> But after doing
>
> dnf --allowerasing downgrade selinux-policy selinux-policy-targeted
>
> the reported problem disappears.
I just wanted to add to what I just posted.
The system I thought was fully updated wasn't. After updating to the
latest selinux
On 02/26/17 22:27, Paul Smith wrote:
> But after doing
>
> dnf --allowerasing downgrade selinux-policy selinux-policy-targeted
>
> the reported problem disappears.
OK
Then, after upgrading the selinux again and rebooting or rmmod what is
already loaded
Try
ausearch -c 'modprobe' --raw |
On Sun, Feb 26, 2017 at 2:18 PM, Paul Smith wrote:
>>
>>> After doing the updates of today (selinux included), virtualbox stopped
>>> working:
>>>
>>> # /usr/lib/virtualbox/vboxdrv.sh setup
>>> vboxdrv.sh: Building VirtualBox kernel modules.
>>> vboxdrv.sh: Starting VirtualBox services.
>>> vboxd
On Sun, Feb 26, 2017 at 12:32 PM, Ed Greshko wrote:
>
>> After doing the updates of today (selinux included), virtualbox stopped
>> working:
>>
>> # /usr/lib/virtualbox/vboxdrv.sh setup
>> vboxdrv.sh: Building VirtualBox kernel modules.
>> vboxdrv.sh: Starting VirtualBox services.
>> vboxdrv.sh:
On 02/26/17 19:37, Paul Smith wrote:
> After doing the updates of today (selinux included), virtualbox stopped
> working:
>
> # /usr/lib/virtualbox/vboxdrv.sh setup
> vboxdrv.sh: Building VirtualBox kernel modules.
> vboxdrv.sh: Starting VirtualBox services.
> vboxdrv.sh: Building VirtualBox kerne
Dear All,
After doing the updates of today (selinux included), virtualbox stopped working:
# /usr/lib/virtualbox/vboxdrv.sh setup
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: modprobe
10 matches
Mail list logo