From: Ira Weiny <ira.weiny@intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
Sumitra Sharma <sumitraartsy@gmail.com>
Cc: Ira Weiny <ira.weiny@intel.com>,
"Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
<linux-fsdevel@vger.kernel.org>
Subject: Re: Inbox vboxsf not working
Date: Wed, 16 Aug 2023 10:02:48 -0700 [thread overview]
Message-ID: <64dd0138c68f2_2a8edb294d5@iweiny-mobl.notmuch> (raw)
In-Reply-To: <2d29fd54-b8c9-6efc-49b2-c83c56463db7@redhat.com>
Hans de Goede wrote:
> Hi,
>
> On 8/16/23 13:45, Sumitra Sharma wrote:
> > On Wed, Aug 16, 2023 at 09:28:51AM +0200, Hans de Goede wrote:
> >> Hi Sumitra,
> >>
[snip]
> >
> > Hi Hans,
> >
> > Can you please specify what you mean by "vbox guest functionality"? Are you talking about the guest addition utilities which VirtualBox offers and about which you warned not to install them? [*]
>
> Yes.
>
> Virtualbox consists of 2 parts:
>
> 1. The hypervisor / hw-emulator on which virtual-machines run. This hypervisor itself runs on the host.
>
> 2. The guest addition utilities which can be installed inside a guest / virtual-machine running on top of VirtualBox. These allow things like copy and pasting between the guest and host and sharing a folder on the host with the guest.
>
> The host always uses out of tree kernel-modules.
Hans,
Thanks for this clarification. This is my fault for leading Sumitra to
believe that the in tree modules could replace the guest additions for the
VirtualBox hypervisor.
>
> The guest can use the in tree kernel modules.
>
> > How can I make the in-tree vbox modules run?
>
> You can use these and specifically the vboxsf and vboxguest modules by
> installing Fedora 38 Workstation x86_64 as a virtualbox *guest* / inside
> a virtualbox vm and then share a folder on the host with the guest.
>
I took your original email to mean that some in tree modules could be out
of sync with the interfaces used by code coming from Oracle.
I'm curious are there also out of tree modules for the guest support?
Thank you again,
Ira
next prev parent reply other threads:[~2023-08-16 17:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALPt=azKNntv31d510UMkYXbcrsOj08aODVozsoKhLY6Gd-fgg@mail.gmail.com>
2023-08-16 7:28 ` Inbox vboxsf not working Hans de Goede
2023-08-16 11:45 ` Sumitra Sharma
2023-08-16 13:25 ` Hans de Goede
2023-08-16 17:02 ` Ira Weiny [this message]
2023-08-16 17:33 ` Hans de Goede
[not found] ` <CALPt=azRw4YxH+0r=CJfY+pZhAsGB9Am0n04gJ0kqpiND3q2sw@mail.gmail.com>
2023-08-27 15:18 ` Hans de Goede
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=64dd0138c68f2_2a8edb294d5@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=fmdefrancesco@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=sumitraartsy@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).