mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: damian <linux_dti@icloud.com>
To: Hans de Goede <hdegoede@redhat.com>
Cc: gregkh@linuxfoundation.org, arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: Bug in vboxguest: After commit Merge tag 'char-misc-4.17-rc3'
Date: Tue, 08 May 2018 21:41:36 +0200	[thread overview]
Message-ID: <20180508194135.GA27020@zrhn9910b> (raw)
In-Reply-To: <c589f2f9-e8e3-7f54-e1ab-9ac3baf700bf@redhat.com>

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

  reply	other threads:[~2018-05-08 19:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-02 19:37 damian
2018-05-02 20:03 ` Damian Tometzki
2018-05-02 20:06 ` Greg KH
2018-05-02 20:46   ` damian
2018-05-02 21:08     ` Hans de Goede
2018-05-08 11:42     ` Hans de Goede
2018-05-08 19:41       ` damian [this message]
2018-05-09  7:36         ` Hans de Goede
2018-05-09 20:18           ` damian
2018-05-09 20:20             ` damian

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180508194135.GA27020@zrhn9910b \
    --to=linux_dti@icloud.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®