On Thu, Jul 25, 2013 at 05:16:21AM +0100, Kerin Millar wrote
2) What vncviewer or vncconnect parameters do I use to get to the
qemu session?
Assuming both server and client are run locally, connecting to either
localhost:0 or localhost:5900 should work.
Thanks. That helped me to get
On 25/07/2013 09:54, Walter Dnes wrote:
On Thu, Jul 25, 2013 at 05:16:21AM +0100, Kerin Millar wrote
2) What vncviewer or vncconnect parameters do I use to get to the
qemu session?
Assuming both server and client are run locally, connecting to either
localhost:0 or localhost:5900 should
On Thu, July 25, 2013 11:17, Kerin Millar wrote:
On 25/07/2013 09:54, Walter Dnes wrote:
On Thu, Jul 25, 2013 at 05:16:21AM +0100, Kerin Millar wrote
I stumbled over the solution to my final problem by accident. When
booting off the install cd, you have 15 seconds to hit any key, or
else
On 25/07/2013 10:26, J. Roeleveld wrote:
On Thu, July 25, 2013 11:17, Kerin Millar wrote:
On 25/07/2013 09:54, Walter Dnes wrote:
On Thu, Jul 25, 2013 at 05:16:21AM +0100, Kerin Millar wrote
I stumbled over the solution to my final problem by accident. When
booting off the install cd,
On Thu, Jul 25, 2013 at 11:26:36AM +0200, J. Roeleveld wrote
Not all VNC-clients do this.
Which do you use?
In my case, it's tightvnc, which does not auto-resize. And in linux
tightvnc, {F8} brings up the dialogue.
--
Walter Dnes waltd...@waltdnes.org
I don't run desktop environments; I
On Thu, Jul 25, 2013 at 10:17:41AM +0100, Kerin Millar wrote
That's correct if you want optimal performance in
X.org. The best option is -vga vmware in conjunction with
x11-drivers/xf86-video-vmware.
The last time I used qemu a few years ago, I ended up running wine
from the guest as an X
So I emerged QEMU, which pulled in some dependancies. Things are not
going well...
1) The following warning shows up in elog...
WARN: pretend
You have decided to compile your own SeaBIOS. This is not supported
by upstream unless you use their recommended toolchain (which you are
not). If
On 24/07/13 17:50, Walter Dnes wrote:
So I emerged QEMU, which pulled in some dependancies. Things are not
going well...
1) The following warning shows up in elog...
WARN: pretend
You have decided to compile your own SeaBIOS. This is not supported
by upstream unless you use their
On 24/07/2013 10:50, Walter Dnes wrote:
So I emerged QEMU, which pulled in some dependancies. Things are not
going well...
1) The following warning shows up in elog...
WARN: pretend
You have decided to compile your own SeaBIOS. This is not supported
by upstream unless you use their
On Wed, 24 Jul 2013 11:57:41 +0100, Kerin Millar wrote:
WARN: pretend
You have decided to compile your own SeaBIOS. This is not supported
by upstream unless you use their recommended toolchain (which you are
not). If you are intending to use this build with QEMU, realize you
will not
On 24/07/2013 14:16, Neil Bothwick wrote:
On Wed, 24 Jul 2013 11:57:41 +0100, Kerin Millar wrote:
WARN: pretend
You have decided to compile your own SeaBIOS. This is not supported
by upstream unless you use their recommended toolchain (which you are
not). If you are intending to use this
Thanks to all who replied. sys-firmware/seabios needed the binary
flag and sys-firmware/ipxe needed the qemu and vmware flags. It's
starting now, and most of my problems are solved.
I still have permission problems as a regular user with qemu-kvm, but
qemu-system-i386 works. Root can start
On 25/07/2013 04:24, Walter Dnes wrote:
Thanks to all who replied. sys-firmware/seabios needed the binary
flag and sys-firmware/ipxe needed the qemu and vmware flags. It's
starting now, and most of my problems are solved.
I still have permission problems as a regular user with qemu-kvm,
13 matches
Mail list logo
