lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-id: <20180508194135.GA27020@zrhn9910b>
Date:   Tue, 08 May 2018 21:41:36 +0200
From:   damian <linux_dti@...oud.com>
To:     Hans de Goede <hdegoede@...hat.com>
Cc:     gregkh@...uxfoundation.org, arnd@...db.de,
        linux-kernel@...r.kernel.org
Subject: Re: Bug in vboxguest: After commit Merge tag 'char-misc-4.17-rc3'

On Tue, 08. May 13:42, Hans de Goede wrote:
> Hi Damian,
> 
> On 02-05-18 22:46, damian wrote:
> >Hello Greg,
> >
> >it is PATCH 3 virt: vbox: Use __get_free_pages insteas of kmalloc for DMA32 memory.
> 
> Thank you for the bug report, I've tried to reproduce this problem
> but for me everything works fine.
> 
> Does your virtual-machine have more then 4G of RAM configured for its
> use?  If yes then what is likely happening is that you also have
> the out-of-tree version of the vboxguest modules installed and prior
> to the commit in question the out of tree version of the driver is
> loading, because before that commit the vboxguest driver in the
> mainline kernel fails to load on machines with more then 4G.
> 
> Or alternatively before the commit in question you may not have
> any version of the vboxguest driver loaded.
> 
> Using the upstream version of the driver should not make a noticeable
> difference, but before the vboxguest driver became a part of the
> mainline kernel the virtualbox upstream developers have done a
> cleanup / redesign of the userspace API of the vboxguest driver,
> so the vboxguest driver will only work with recent virtualbox-guest-additions
> and since you are using Ubuntu 16.04 chances are that you are
> using that with Ubuntu's quite old bundled virtualbox-guest-additions
> which will not work with the new driver and may be causing this
> issue.
> 
> Can you try upgrading your virtualbox-guest-additions to 5.2.10
> please?
> 
> Also if the above does not help, a couple of follow up
> questions to help this pin down further:
> 
> 1) Are you using vbox's 3d pass through functionality
> 2) Which desktop-environment are you using?
> 
> Regards,
> 
> Hans

Hi Hans,

i will check my configutation and will come back
At the moment i dont use use the virtualbox-guest-additions, i use the driver from the staging area. 

because i had after every new kernel release problms with this driver. 


regards
Damian



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ