btw. it took like 5 minutes for vbox to start executing my
vm... and its like 20 seconds to change the iso image in
the virtual cdrom drive. and the installer had me to click
10 times to confirm all the drivers getting installed.
every new version of vbox seems to make it worse.
maybe use vmware
ah! e820 scan makes sense. we do that in the 9boot loader only. the
kernel never switches back to realmode.
--
cinap
i just installed the latest version of vbox 4.2.6 on windows xp
and 9front boots just fine. there where no changes related
to supporting vbox. the only problem we had was a bug in realemu some
time ago that got exposed with the vbox vesa bios but that doesnt
apply to stock plan9. maybe 9load proble
On Jan 25, 2013, at 9:32 PM, Gorka Guardiola wrote:
> In the standard plan 9, e820 scan. When disabled, a vesa bug which 9front
> circunvents with realemu.
This fits also the description given. Going to real mode is broken in the
standard plan 9 in virtualbox.
G.
In the standard plan 9, e820 scan. When disabled, a vesa bug which 9front
circunvents with realemu.
On Jan 25, 2013, at 8:46 PM, James Chapman wrote:
> It hangs during booting.
>
> The same as this I think:
>
> https://forums.virtualbox.org/viewtopic.php?f=4&t=52431
>
>
> On Jan 25, 2013,
It hangs during booting.
The same as this I think:
https://forums.virtualbox.org/viewtopic.php?f=4&t=52431
On Jan 25, 2013, at 9:15 PM, cinap_len...@gmx.de wrote:
> whats the problem with this version?
>
> --
> cinap
>
whats the problem with this version?
--
cinap
this patch is wrong. it changes fsysversion() which leaves
t.msize uninitialized.
static
Xfid*
fsysversion(Xfid *x, Fid*)
{
Fcall t;
if(x->msize < 256)
return respond(x, &t, "version: message size too small");
if(t.msize > Maxblock)
t.msize
I have had recent sucess with VirtualBox 4.1.24. The current version
of VirtualBox (4.2.6) didn't work for me.
You can get older version of virtualbox from here:
https://www.virtualbox.org/wiki/Download_Old_Builds
James
On Fri, Jan 25, 2013 at 8:18 PM, wrote:
> vmware, kvm/qemu, vbox should a
also, maybe you just give it a try on real hardware.
its not really rocket science.
--
cinap
vmware, kvm/qemu, vbox should all work.
--
cinap
Hello everyone,
I'd like to play with acid.
However, I run p9p (on linux), and thus acid is not really fully
functional.
What is currently the easiest way to set up an environment in which I
could play with acid? Is it running proper plan9 on a virtual machine?
(If yes, which is then the simplest
On Fri Jan 25 04:59:21 EST 2013, rgandha...@gmail.com wrote:
> Thanks for the detailed explanation Eriq. I couldn't find a pci binary that
> supported -m option.
> I have
> # pci -help
> usage: pci [-vb] [vid/did ...]
there aren't any long options in plan 9, so the old way to say
that was "pci -
On Fri Jan 25 08:07:59 EST 2013, cinap_len...@gmx.de wrote:
> the latest changes in libdraw:
>
> Display*
> initdisplay(char *dev, char *win, void(*error)(Display*, char*))
> {
> - char buf[128], info[NINFO+1], *t, isnew;
> + char buf[NINFO+1], info[NINFO+1], *t, isnew;
>
> this is wro
the latest changes in libdraw:
Display*
initdisplay(char *dev, char *win, void(*error)(Display*, char*))
{
- char buf[128], info[NINFO+1], *t, isnew;
+ char buf[NINFO+1], info[NINFO+1], *t, isnew;
this is wrong. the real bug is here:
if((n=read(ctlfd, info, sizeof info)) <
Thanks for the detailed explanation Eriq. I couldn't find a pci binary that
supported -m option.
I have
# pci -help
usage: pci [-vb] [vid/did ...]
Thanks
rg
On Thursday, January 24, 2013 8:22:16 AM UTC-8, erik quanstrom wrote:
> On Thu Jan 24 05:09:23 EST 2013, rgandha...@gmail.com wrote:
>
>
16 matches
Mail list logo
