Andreas Stagl wrote:
Hi Frank,
Hi, Maciek,
What is the output of
dpkg --print-architecture
?
Oh... it says i386.
You probably have "mixed" installation (i386 userland and amd64 kernel).
I had once that. (First installed i386 debian and next upgraded kernel
to amd64)
Yes, this might have been the case. I remember that I once had
troubles with the amd64-iso-images... so I installed i386 and made an
update to amd64 using apt. Might be that this was on that machine.
So you should install amd64 debian (entire system not only kernel),
This might be a little problem, because the machine I'm talking about
is already located at my ISPs computing center... so that I've no
physical access to it. :-( Is there no other way for a clean switch to
amd64?
or make small amd64 chrooted environment (in order to install VBox)
(Once I did so . Now I come back to pure i386 :-)
Hmm... never did this. Do you have a link for a good Howto?
In this case (no physical it access and amd64 kernel ) it should work
:-) (require few GB of disk space ).
First you have to debootstrap amd64 system into directory (package
required : debootstrap) (with --arch switch. Exact command line syntax
you can find in man .In case of trouble I can help )
Next create chroot I used schroot (package schroot ) (You should edit
/etc/schroot/schroot.conf and point "location" to dir where lies
bootstraped system )
Now you should be able to
# schroot -c "name of chroot"
switch to amd64 environment and install amd64 virtualbox and other
necessary packages.
Now you should be able to start virtualbox (after setting DISPLAY shell
variable )
Regards
Maciek Kaliszewski
PS
I wonder how correct (amd64) vboxdrv come into existence :-) .
Because gcc all libs are i386 and i386 virtualbox has precompiled i386
version of this drv or I am wrong .
_______________________________________________
vbox-users mailing list
[email protected]
http://vbox.innotek.de/mailman/listinfo/vbox-users
