Received: by 10.192.165.148 with SMTP id m20csp5196193imm; Wed, 9 May 2018 00:37:31 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpxUieTAJ/qWQb6nMAs1cTxSyKDqmgG03x/0pTK6RDDttaQUuE0ThxUH11AHT8UOftYUZbZ X-Received: by 2002:a17:902:9349:: with SMTP id g9-v6mr42502313plp.375.1525851451267; Wed, 09 May 2018 00:37:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525851451; cv=none; d=google.com; s=arc-20160816; b=0Vck54RwtF4z4rGW6JBmzDGtY2C6hNEjWfjDUZu0/p3lZogcaf9IY0dN165pbCZU5d OL4huwFr4CleCOf19v4J/q1eocW3HqhX8BF6C6q97mxy7wqvqloCtxM64LIlrBDi5Ke3 ZaSXI6yeNqX3fFcNb/Jg0MtNNgcGRcKctVCT3auw5hggSznRwZSkvMjUYCOZ0N8hqZ4f wN0DUye/+Cbpin8Ah5A0ril9vr/XucrpELyWARJAFQ0lzwMrIIsnAW/Z4vy8nkUbFT5o 4DPlxu7uIyc7qANRKGp7c7Ezd9wJ5VVxYIiXwKNZ6jeQaUcIP3ILgJlwCtvYpyBnCDH+ 3W1g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:to:subject:arc-authentication-results; bh=SCovB25dLQ2lz/kLr1tMXI4L7SBybbsWJiiQ+IySEX0=; b=RaOlWNziBfmuVWlHdRFzXUmgxidbMGIzln/t4WUkCXJ9ZaUMDT78LlIkN2vuODj4Zu 7a7wdmf7qLj2abKs/kLw3xd+RhLd9vJj6tZLZhUWvDht00EtEFvMH32yuY6p8h0t45p6 fik6pYLA+jpvTyghT5XThorbf/EEEXz2g+YjWc24/w6Ku+EE096N+lW7cTKbvyI4yOoM nHVWD1S28Mw6Rbnni3w0z9tCbpG+Mb27d+IGErfr13bmQBYSfke5eNumTWOH3/zRGAoj 2KAq4/1g9/oFmyVLeOshJTrlmWg9GJ/3TDUWmCUgYlQV5AdWubzvT5AkjU+dp3Z7hkjg sWKQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id r9-v6si26145166plo.442.2018.05.09.00.37.16; Wed, 09 May 2018 00:37:31 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933784AbeEIHge (ORCPT + 99 others); Wed, 9 May 2018 03:36:34 -0400 Received: from mail-wm0-f41.google.com ([74.125.82.41]:37358 "EHLO mail-wm0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933766AbeEIHgd (ORCPT ); Wed, 9 May 2018 03:36:33 -0400 Received: by mail-wm0-f41.google.com with SMTP id l1-v6so25798062wmb.2 for ; Wed, 09 May 2018 00:36:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=SCovB25dLQ2lz/kLr1tMXI4L7SBybbsWJiiQ+IySEX0=; b=iRtLKrfTyAbHSIkjifMpJCRlRWb17oV5xiZx9cu4dhkjq9W9CYV9/Y36/Q8cztUlTq FU15Z9OBwCkB0xsYcRbKHCFAp8J5yq35dFjHSdf/Hgw9kawr+QD5NLIZcAB9mN97jnAb AWMaiIHs/7A6hSJKpvsZc6dbvblnsIYZebHqfPdBi+qTvCb5TsnNy++VYdRWJJ6JnOX6 yqFZDFzFY3AnjLEO8E/d1wZdbe0uOQOYHE7mHu1WBC/0TEccOj9sg1wLvgR0HI2RLBms afgCKIOQMvr2pB1U2ravvDjl83t1FsfNVraLGquGvLfNZzXamr0fi+YzZPDdAaBPom2E 6b2Q== X-Gm-Message-State: ALQs6tACPwgNcrlc2QpTj1nsExMd4FARmDGYHYzLLsCalzRNZrXLEe8V zReMwzams1oZ0CCdEXGe7ivNPFEjSEo= X-Received: by 2002:a50:b5e3:: with SMTP id a90-v6mr57979778ede.69.1525851392042; Wed, 09 May 2018 00:36:32 -0700 (PDT) Received: from shalem.localdomain (546A5441.cm-12-3b.dynamic.ziggo.nl. [84.106.84.65]) by smtp.gmail.com with ESMTPSA id j22-v6sm16015580eda.72.2018.05.09.00.36.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 09 May 2018 00:36:31 -0700 (PDT) Subject: Re: Bug in vboxguest: After commit Merge tag 'char-misc-4.17-rc3' To: gregkh@linuxfoundation.org, arnd@arndb.de, linux-kernel@vger.kernel.org References: <20180502193735.GA2444@zrhn9910b> <20180502200615.GB16341@kroah.com> <20180502204612.GA2089@zrhn9910b> <20180508194135.GA27020@zrhn9910b> From: Hans de Goede Message-ID: Date: Wed, 9 May 2018 09:36:30 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180508194135.GA27020@zrhn9910b> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 08-05-18 21:41, damian wrote: > 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. Ah I see, you may still have the Ubuntu pkg for them installed though, which may be an old version which actually starts to try and do stuff now that there is a vboxguest driver in mainline too, but that old version does not support the new, stable API as merged into the mainline. So if you don't care about the add-ons instead of upgrading yopu can also remove the Ubuntu pkg for them. Regards, Hans