Re: oh no something is definitly wrong adieu debian.
>
> Just to clarify your procedure - vbox is installed, but you are
> running vncserver just from host box, not inside vbox right?
Once the vbox guest wheezy is installed and has a vcnserver runing on
it, you may use any vncviewer you may have on your intranet to connect
to it.
my exact setup is
my thin client with vncviewer on it.
a host where I have vbox on it (in a computer room)
I access the server with the evil vncviewer that 'pure' sysadmin on
server would reject. yet it works enough to let vbox display the guest
console with wheezy login screen so I can log on this one (doesn't
crash) and do the sysadmin of the wheezy guest, i.e install
vnc4server, tweak .vnc, start vncserver.
back to my thin client i can use vncviewer to access the wheezy
vncserver session.
In the real life (non vbox) the path is similar, i.e a virtual console
to the computer room server, a wheezy install (in my case was un
squeeze update, but install would do the same) sysadmin vnc4server,
.vnc, xstartup, vncserver. Then from my thinclient access my server
vncsession, and crash it the same way.
So the vbox path given is to avoid a bug fixer to buy a server :)
Did I filled a bug report? no, the problem is knows since about a year
and a half, and as I said reported thousand of time on the net, so I
guessed it was already reported.
Cheers,
Phi
Reply to: