Hey tnx for the reply.
I thought about ftping, but the network is not even installed at that point of the installation. Unless there is a way to make it work manually, I don't know.
I also don't think we should spend too much time on the problem, as it happens only with VBOX v1.6.2 and less, and v2.0+ don't have the problem. I am trying to fix backwards compatibility, which in this case is less critical.
The file, a log file of the errors encountered during installation of opensuse 11.1beta, is held in the in-mem fs, I see it and I can create a tarball from it by using a save command developers provided me.
Once the tarball of the log file is saved in the in-mem fs, I need to transfer it outside the VM so that I can send it over internet and attach it in my bug filed for that problem (repos failed to initialized, installation halts there).
USB: not installed (VBox does not support usb so early in install), so can't transfer.
Network: not installed, so can't transfer.
Copy on other hard disk: cannot use the mount command which seems not to be created or enabled, so can't transfer.
Basically I can't get that log file out of the VM and into the real world. Did I take the red or the blue pill? lollll
As said, if you aren't sure of what to do, no worries as this is not a critical problem and is fixed using latest VBox versions, cuz the installation does work and does not halt when trying to initialize the repos.
But I am a curious guy and I like knowing what's going on and how to fix it, so this is why I was asking.

Besides, almost everything can work under linux, the thing is just to find how.

That's the challenges I like.
tnx