On Fri, Nov 09, 2018 at 05:31:00AM +, Chris Knadle wrote:
> A logical place to check or the lack of BIOS virtualization features and show
> an
> error message for this would be within the .postinst script for the virtualbox
> package in Debian. This way when Virtualbox is installed the user
> Or an user error. In either case, I don't get what a 32-bit _x86_ virtual
> machine would be good for. Are you teaching some code archeology?
Not at all.
We're trying to make it compulsory for first year students to have a Unix
installation on their personal machine. In practice, this means
> Filing a bug on src:virtualbox with severity 'wishlist' or 'normal' for this
> issue to discuss it with the maintainer of the virtualbox package(s) seems a
> logical thing to do.
Unfortunately, we're speaking about running Debian under VirtualBox under
Windows, so it would need to be something
On Fri, Nov 09, 2018 at 01:40:59PM +0100, Adam Borowski wrote:
If his students were doing code archaeology or deep embedded, such areas
require enough base skills that getting spooked by 32 vs 64 bits would be
beyond them.
Everyone starts somewhere, even code archaeologists. At my former
On Fri, Nov 09, 2018 at 11:36:36AM +, Jonathan Dowland wrote:
> On Fri, Oct 26, 2018 at 10:41:32PM +0200, Adam Borowski wrote:
> > Or an user error. In either case, I don't get what a 32-bit _x86_ virtual
> > machine would be good for. Are you teaching some code archeology? Do you
> > want
On Fri, Oct 26, 2018 at 10:41:32PM +0200, Adam Borowski wrote:
Or an user error. In either case, I don't get what a 32-bit _x86_ virtual
machine would be good for. Are you teaching some code archeology? Do you
want to prepare 32-bit images for something deeply embedded? Neither sounds
an
Paul Wise:
> On Fri, Nov 9, 2018 at 1:32 PM Chris Knadle wrote:
>
>> A logical place to check or the lack of BIOS virtualization features and
>> show an
>> error message for this would be within the .postinst script for the
>> virtualbox
>> package in Debian. This way when Virtualbox is
On Fri, Nov 9, 2018 at 1:32 PM Chris Knadle wrote:
> A logical place to check or the lack of BIOS virtualization features and show
> an
> error message for this would be within the .postinst script for the virtualbox
> package in Debian. This way when Virtualbox is installed the user installing
Juliusz Chroboczek:
>> When discussing virtual machines it would be helpful to mention which virtual
>> machine hypervisor is being used, because the resulting behavior can differ
>> depending on hypervisor.
>
> It was VirtualBox under Windows. The underlying issue was that VT-x was
> disabled
If VT-x is disabled, the virtual machine will be sluggish, so if it
works, it'll be a bad experience.
Don't do that.
On Thu, Nov 8, 2018 at 11:04 AM Juliusz Chroboczek wrote:
>
> > When discussing virtual machines it would be helpful to mention which
> > virtual
> > machine hypervisor is being
> When discussing virtual machines it would be helpful to mention which virtual
> machine hypervisor is being used, because the resulting behavior can differ
> depending on hypervisor.
It was VirtualBox under Windows. The underlying issue was that VT-x was
disabled in the BIOS, and hence
>> I've been encouraging my students to install Debian on their personal
>> machines, and we've found out that a lot of them get the wrong Debian
>> installer:
>>
>> - some of them attempt to install an AMD64 version of Debian in
>> a 32-bit-only virtual machine;
> Why are they creating 32-bit
> This is not what I get.
> - 32bit debian on 64bit machine: this should be working fine
> - 64bit debian on 32bit machine: I get the attached message
> If it's not what they get, there is some bug and more investigation is
> needed.
I no longer have access to their machines, so I'm
Why are they creating 32-bit virtual machines?
At least with virtualbox 32-bit VMs can run on any host. 64-bit VMs require
VT-x which is all too often disabled in the BIOS.
Le vendredi 26 octobre 2018 à 14:41:31+0200, Juliusz Chroboczek a écrit :
> […]
> Could somebody please speak with the installer people so they make sure
> that the installation fails with a friendly user message in both of the
> cases outlined above?
Regardless of the discussion, you can, and
On Fri, Oct 26, 2018 at 08:17:11PM +0100, Ben Hutchings wrote:
> On Fri, 2018-10-26 at 14:41 +0200, Juliusz Chroboczek wrote:
> > I've been encouraging my students to install Debian on their personal
> > machines, and we've found out that a lot of them get the wrong Debian
> > installer:
> >
> >
On Fri, 2018-10-26 at 14:41 +0200, Juliusz Chroboczek wrote:
> Hi,
>
> I've been encouraging my students to install Debian on their personal
> machines, and we've found out that a lot of them get the wrong Debian
> installer:
>
> - some of them attempt to install an AMD64 version of Debian in
Hello,
Juliusz Chroboczek, le ven. 26 oct. 2018 14:41:31 +0200, a ecrit:
> In both cases, the installer crashes with no useful error message
This is not what I get.
- 32bit debian on 64bit machine: this should be working fine
- 64bit debian on 32bit machine: I get the attached message
If it's
On Fri, Oct 26, 2018 at 02:41:31PM +0200, Juliusz Chroboczek wrote:
> I've been encouraging my students to install Debian on their personal
> machines, and we've found out that a lot of them get the wrong Debian
> installer:
>
> - some of them attempt to install an AMD64 version of Debian in
>
19 matches
Mail list logo
