From owner-freebsd-questions@freebsd.org Wed Jul 6 05:08:05 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4C7E5B71D47 for ; Wed, 6 Jul 2016 05:08:05 +0000 (UTC) (envelope-from mail@bontempi.net) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 21E9B1BA1 for ; Wed, 6 Jul 2016 05:08:04 +0000 (UTC) (envelope-from mail@bontempi.net) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E839C2008C; Wed, 6 Jul 2016 01:08:02 -0400 (EDT) Received: from web1 ([10.202.2.211]) by compute1.internal (MEProxy); Wed, 06 Jul 2016 01:08:02 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=bontempi.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=XN1EzBlMwbprTc3aPrVIExDtWbk=; b=b5Zg3j hqinCYfmNlVWaVsFmKWPPglqUuMXLHTxqIihSd2QCnrvAciNXXXad0H/2nQcrqWY UyvrN96DCfqCqMYZRegCtpAadfYKcoAuxsn0QmIOszFw/jHnUM+rOLOjNq2YUfwy ALT/eSBu7XS4ZggBiw7+7FZW573RAzw1W+PHo= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=XN1EzBlMwbprTc3 aPrVIExDtWbk=; b=JrN5kFh4pHavg5Vf08p8hYxzmQQDG/uSIxbVw+7kGXIj8Xe bnYGIFNskXkCvvhFSGQEjL2uw7lIH+NSC3azWW/xLggrxpY7p2W3rbTzONkePaWR I70kK2lEbcTpGBuYgp1fQnUr64TLfwpBvwX2VK2GratQ3VvUjYNCc4YhyUsY= Received: by mailuser.nyi.internal (Postfix, from userid 99) id B282A6A149; Wed, 6 Jul 2016 01:08:02 -0400 (EDT) Message-Id: <1467781682.1892374.658066521.076DEF67@webmail.messagingengine.com> X-Sasl-Enc: ERzsPhVecWHhh5WEiJm1S1iPKT9Qpt3GbAbygRpQNke1 1467781682 From: mail@bontempi.net To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Mailer: MessagingEngine.com Webmail Interface - ajax-22cd3445 In-Reply-To: <20160705163611.70ba678b@Papi> References: <20160705083230.47d99a62.freebsd@edvax.de> <329cfc15-988a-11fc-e9f4-7423e21e1cf6@bananmonarki.se> <20160705163611.70ba678b@Papi> Subject: Re: How to make smooth USB access available to Virtualbox vm Date: Wed, 06 Jul 2016 05:08:02 +0000 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Jul 2016 05:08:05 -0000 On Tue, 5 Jul 2016, at 19:36, Mario Lobo wrote: > On Tue, 5 Jul 2016 19:27:01 +0200 > Bernt Hansson wrote: >=20 > > On 2016-07-05 16:15, Manish Jain wrote: > > > On 07/05/16 12:02, Polytropon wrote:=20=20 > > >> On Tue, 5 Jul 2016 08:10:49 +0200, CeDeROM wrote:=20=20 > > >>> The USB support on VirtualBox is highly unreliable and version > > >>> dependant - it works with some releases and with some releases it > > >>> does not work as expected - not only on FreeBSD (I also use OSX > > >>> version). This is really annoying when USB stops working after an > > >>> update to a new version and you depend on this USB access with > > >>> your work :-(=20=20 > > >> Just an idea: > > >> > > >> Why not mount the USB stick on the FreeBSD host system (or even > > >> have Gnome automount it), then make the mount directory accessible > > >> to the "Windows" guest through localhost FTP, localhost SAMBA, or > > >> another means of virtual network? > > >> > > >> It sounds so stupid - it could actually work! ;-) > > >>=20=20 > > > Sounds a bit far-fetched and would anyway need to be implemented all > > > over again every time I install FreeBSD. > > > > > > Just wondering if this is possible - I remember there was an > > > application (Nero, I think) - which made it possible to copy/paste > > > to CD/DVD RW from Explorer itself, without the need to actually > > > burn it via a CD/DVD frontend. Is there any way I can use a CD/DVD > > > just as a part of the regular filesystem ? If that is possible, the > > > need for USB support in vbox would largely be mitigated. > > > > > > Is there any other non-USB device which can fill in the need to make > > > shared data available to the guest machine ? IOMEGA floppies I > > > think are no longer used, but if there is something which provides > > > seamless access, I would not mind buying some hardware to solve the > > > problem for good (considering the magnitude of the problem, make > > > that 'for very good'). > > > > > > Thanks for any tips.=20=20 > > Perhaps this is worth a try. > >=20 > > http://linux.bytesex.org/misc/webfs.html > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > "freebsd-questions-unsubscribe@freebsd.org" >=20 >=20 > From my side, I've been having woes with VBox usb usage, to the point > that I wrote to the developers of VB directly. What follows is the > conversation I had with Mr. Frank Mehnert | Software Development > Director, VirtualBox. >=20 > ME: >=20 > > I've been using VB with FreeBSD since its early days, when > > USB 1.0 used to be the standard. > >=20 > > Now a days, it is no longer viable, even if we downgrade the USB > > connection through the OS to usb 1.0. The device shows up on the guest > > but that is as far as it goes. It simply doesn't work. > >=20 > > I see that you have pre-compiled extension packs for Windows and Linux > > hosts. VB compiles and works great through the ports in FreeBSD. The > > highest available official version 4.3.38 but through the works of > > Jung-uk Kim, I am running 5.0.20 right now! If it wasn't for this USB > > issue, VB would be completely operational on FBSD! > >=20 > > You probably have been asked about this a lot, but do you see a > > possibility anywhere in the future, of providing a pre-compiled > > extension pack for FreeBSD? I never understood why Windows and Linux > > have it and FreeBSD doesn't. Is there a particular reason for it? > >=20 > > Is there anyway I can help with this matter? Anybody in particular I > > can plead for this? > >=20 > > Again, my apologies for barging in, and thank you for reading and for > > your time.=20=20 >=20 > Frank: >=20 > hard to say. I guess if the USB devices worked in the past then this > was probably because the due to the missing Extension Pack the devices > were forced to use the USB 1 mode. >=20 > Providing Extenicode for FreeBSD is not impossible but would require > some effort. The most important part is probably to find a compatible > build environment. >=20 > I don't say "No" in general but we need to think about this in more > detail. >=20 > Kind regards, >=20 > Frank =20 I know that the subject line reads =C2=ABHow to make smooth USB access available to Virtualbox vm=C2=BB, but I was wondering if anybody has successfully shortcut that issue by using Bhyve with the -s switch? As per the wiki [1], =C2=ABThe bhyve hypervisor now supports Microsoft Windows virtual machines as of FreeBSD HEAD SVN tag r288524=C2=BB=20 [1] https://wiki.freebsd.org/bhyve/Windows Priyadarshan