Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #185031 > unrolled thread

Virtualbox for stretch and buster not in repos

Back to article view | Back to linux.debian.user

Contents

  Virtualbox for stretch and buster not in repos Robert Menes <viewtiful.icchan@gmail.com> - 2017-08-11 13:10 +0200
    Re: Virtualbox for stretch and buster not in repos Sven Hartge <sven@svenhartge.de> - 2017-08-11 13:20 +0200
      Re: Virtualbox for stretch and buster not in repos Hans <hans.ullrich@loop.de> - 2017-08-11 13:40 +0200
      Re: Virtualbox for stretch and buster not in repos Mark Fletcher <mark27q1@gmail.com> - 2017-08-15 06:40 +0200
        Re: Virtualbox for stretch and buster not in repos RavenLX <ravenlx@sitesplace.net> - 2017-08-18 14:50 +0200
          Re: Virtualbox for stretch and buster not in repos Sven Hartge <sven@svenhartge.de> - 2017-08-18 15:20 +0200
            Re: Virtualbox for stretch and buster not in repos RavenLX <ravenlx@sitesplace.net> - 2017-08-18 16:10 +0200
              Re: Virtualbox for stretch and buster not in repos Dejan Jocic <jodejka@gmail.com> - 2017-08-18 16:30 +0200
                Re: Virtualbox for stretch and buster not in repos Mario Castelán Castro <marioxcc.MT@yandex.com> - 2017-08-18 16:40 +0200
                  Re: Virtualbox for stretch and buster not in repos Mario Castelán Castro <marioxcc.MT@yandex.com> - 2017-08-18 17:10 +0200
                Re: Virtualbox for stretch and buster not in repos RavenLX <ravenlx@sitesplace.net> - 2017-08-22 15:00 +0200
                  Re: Virtualbox for stretch and buster not in repos Dejan Jocic <jodejka@gmail.com> - 2017-08-22 20:40 +0200
              Re: Virtualbox for stretch and buster not in repos Patrick Bartek <nemommxiv@gmail.com> - 2017-08-18 16:50 +0200
                Re: Virtualbox for stretch and buster not in repos Mario Castelán Castro <marioxcc.MT@yandex.com> - 2017-08-19 00:30 +0200
                Re: Virtualbox for stretch and buster not in repos RavenLX <ravenlx@sitesplace.net> - 2017-08-19 00:30 +0200
                  Re: Virtualbox for stretch and buster not in repos Patrick Bartek <nemommxiv@gmail.com> - 2017-08-19 03:00 +0200
                    Re: Virtualbox for stretch and buster not in repos Mario Castelán Castro <marioxcc.MT@yandex.com> - 2017-08-19 03:30 +0200
                      Re: Virtualbox for stretch and buster not in repos Patrick Bartek <nemommxiv@gmail.com> - 2017-08-19 06:30 +0200
                      Re: Virtualbox for stretch and buster not in repos Zenaan Harkness <zenaan@freedbms.net> - 2017-08-19 09:10 +0200
                        Re: Virtualbox for stretch and buster not in repos Mario Castelán Castro <marioxcc.MT@yandex.com> - 2017-08-19 18:10 +0200
                          Re: Virtualbox for stretch and buster not in repos Zenaan Harkness <zenaan@freedbms.net> - 2017-08-19 23:50 +0200
                        Re: Virtualbox for stretch and buster not in repos Gilles Mocellin <gilles.mocellin@nuagelibre.org> - 2017-08-19 21:00 +0200
                          Re: Virtualbox for stretch and buster not in repos Mario Castelán Castro <marioxcc.MT@yandex.com> - 2017-08-19 21:50 +0200
      Re: Virtualbox for stretch and buster not in repos The Wanderer <wanderer@fastmail.fm> - 2017-08-31 16:10 +0200
        Re: Virtualbox for stretch and buster not in repos Sven Hartge <sven@svenhartge.de> - 2017-08-31 16:30 +0200
          Re: Virtualbox for stretch and buster not in repos Greg Wooledge <wooledg@eeg.ccf.org> - 2017-08-31 16:40 +0200
    Re: Virtualbox for stretch and buster not in repos Hans <hans.ullrich@loop.de> - 2017-08-11 13:20 +0200

Page 2 of 2 — ← Prev page 1 [2]

#185527

On Sat, Aug 19, 2017 at 11:02:58AM -0500, Mario Castelán Castro wrote:
> On 2017-08-19 17:02 +1000 Zenaan Harkness <zenaan@freedbms.net> wrote:
> >Which TUI/GUI do you use?
> 
> I do not know what is TUI.

Text User Interface / command line.


> I don't use any GUI. I write Bash scripts
> that call QEMU with the required options and I use “qemu-img” from the
> command line when needed.

Hm. Nice way to go.


> >I've been struggling to create a Host-only network. In VirtualBox
> >(and VMWare from version 1 or very early) I could basically just
> >tick a check box for "Host only network", and name one or more shared
> >folders.
> 
> The easiest way to do this in QEMU is to use the “-net
> user,restrict=on,hostfwd=...” option. The hostfwd part is optional, but you
> will require if you want host–guest network connectivity.
> 
> This way, networking is handled in user space. A more efficient approach
> is to use kernel-managed networking. It is my understanding that for this,
> one may use the TUN and TAP virtual Linux devices, but I have never done
> it.

Some years back I was using OpenVPN for a while, so got a little
experience with TAP back then.


> >I realise I probably have to mount the SAMBA horse again. And for
> >libre software, I'm willing to do all this.
> 
> Why do you want to use SAMBA? Install a SSH server in the guest and access
> it from the host using scp, sftp or rsync. Rsync is the most efficient.

This sounds like a great idea! SAMBA's brittleness in configuration
(due to my dunceness) when trying to make it work with XP, W7 or now
it would be W10 in the VM, has just never been a comfortable easy
thing, for me.

Years ago I even ran cygwin sshd from memory - but I'm certain
there's cygwin ssh client, so I could use that even from the Windows
side. Thank you very much for the reminder :)

[toc] | [prev] | [next] | [standalone]

#185512

Le samedi 19 août 2017, 17:02:23 CEST Zenaan Harkness a écrit :
> On Fri, Aug 18, 2017 at 08:23:13PM -0500, Mario Castelán Castro wrote:
> Which TUI/GUI do you use?

Unless you really don't wnt libvirt, you should look at virt-manager.

[toc] | [prev] | [next] | [standalone]

#185519

[Multipart message — attachments visible in raw view] — view raw

On 2017-08-19 20:47 +0200 Gilles Mocellin <gilles.mocellin@nuagelibre.org>
wrote:
>Unless you really don't wnt libvirt, you should look at virt-manager.

Thanks for the suggestion. I will take a look into libvirt in the
unlikely case that my current approach becomes insufficient in the future.
So far it works fine.

Regards.

[toc] | [prev] | [next] | [standalone]

#186234

[Multipart message — attachments visible in raw view] — view raw

On 2017-08-11 at 07:18, Sven Hartge wrote:

> Robert Menes <viewtiful.icchan@gmail.com> wrote:
> 
>> Is there a reason why virtualbox hasn't migrated into stretch or 
>> buster yet?
> 
> Short Answer: Because of Oracle.
> 
> Longer Answer:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794466
> 
> Summary: Virtualbox will at the current state of affairs never be in 
> Testing or any stable release or stable-backports ever again.

Today, I noticed that the virtualbox* packages are available in testing
again (when they showed up to be upgraded as part of a routine
dist-upgrade).

Per the latest comment on that bug report, three days ago, it's been
downgraded in severity so that these packages can be in testing until
the situation can be re-evaluated at the time of the next release freeze.

Whether this will actually be permitted to persist until then, or be
reversed by people who disagree with the rationale, is an open question
- but for the time being, this seems to be available again.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man.         -- George Bernard Shaw

[toc] | [prev] | [next] | [standalone]

#186237

The Wanderer <wanderer@fastmail.fm> wrote:
> On 2017-08-11 at 07:18, Sven Hartge wrote:
>> Robert Menes <viewtiful.icchan@gmail.com> wrote:
 
>>> Is there a reason why virtualbox hasn't migrated into stretch or
>>> buster yet?
>> 
>> Short Answer: Because of Oracle.
>> 
>> Longer Answer:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794466
>> 
>> Summary: Virtualbox will at the current state of affairs never be in
>> Testing or any stable release or stable-backports ever again.

> Today, I noticed that the virtualbox* packages are available in
> testing again (when they showed up to be upgraded as part of a routine
> dist-upgrade).

> Per the latest comment on that bug report, three days ago, it's been
> downgraded in severity so that these packages can be in testing until
> the situation can be re-evaluated at the time of the next release
> freeze.

> Whether this will actually be permitted to persist until then, or be
> reversed by people who disagree with the rationale, is an open
> question - but for the time being, this seems to be available again.

I think this depends entirely on the Release Managers and the Security
Team if they allow new upstream versions to fix security bugs instead
of backporting the fixes to the original version in a release.

Until now IIRC only Firefox and Chromium and MySQL (since remove and
replaced by MariaDB) had such an exception.

Time will tell if the same is granted to Virtualbox.

Grüße,
S°

-- 
Sigmentation fault. Core dumped.

[toc] | [prev] | [next] | [standalone]

#186238

On Thu, Aug 31, 2017 at 04:22:50PM +0200, Sven Hartge wrote:
> I think this depends entirely on the Release Managers and the Security
> Team if they allow new upstream versions to fix security bugs instead
> of backporting the fixes to the original version in a release.
> 
> Until now IIRC only Firefox and Chromium and MySQL (since remove and
> replaced by MariaDB) had such an exception.

This has also happened with BIND, PostgreSQL, and Samba.  With Samba,
we've even had major feature changes in the middle of a stable release. :(

> Time will tell if the same is granted to Virtualbox.

[toc] | [prev] | [next] | [standalone]

#185033

Am Freitag, 11. August 2017, 07:08:41 CEST schrieb Robert Menes:
Did you install the virtualbox-dkms package?

If yes, did it build?

If yes, can you modprobe virtualbox?

If everything fails, try kvm and aqemu as a substitute.

Best

Hans
> Hi all,
> 
> On my home desktop, I'm running Debian on the testing channel (currently
> at "buster"). A recent apt-get upgrade appears to have broken or removed
> a few vital virtualbox packages, including virtualbox-dkms.
> 
> Launching any VM in virtualbox throws this error message:
> 
> [error]
> 
> The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there
> is a permission problem with /dev/vboxdrv. Please reinstall virtualbox-dkms
> package and load the kernel module by executing
> 
> 'modprobe vboxdrv'
> 
> as root.
> 
> where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The
> support driver is not installed. On linux, open returned ENOENT.
> 
> [/error]
> 
> Running modprobe as the error message suggests, though, gives me:
> 
> modprobe: FATAL: Module vboxdrv not found in directory
> /lib/modules/4.11.0-1-amd64
> 
> Current I'm running the 4.11.0-1-amd64 kernel, but can easily boot and run
> a 4.9 kernel (which is the last good working kernel I have).
> 
> apt-cache search on my desktop doesn't bring up results for any virtualbox
> package, except for 'virtualbox-guest-additions-iso'.
> 
> Is there a reason why virtualbox hasn't migrated into stretch or buster
> yet? While only a minor inconvenience of having to boot with another
> kernel, I would like to have the newer packages available for a consistent
> upgrade.
> 
> Thanks, all.
> 
> --Robert

[toc] | [prev] | [standalone]

Page 2 of 2 — ← Prev page 1 [2]

Back to top | Article view | linux.debian.user

csiph-web