Re: [Qemu-devel] Connecting vde and LAN

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Oliver Gerlich wrote: > Ross Kendall Axe schrieb: > >>>Oliver Gerlich wrote: >>> >>> >The "problem" is that I start vde_switch and the bridging not at boot, >but when I want to run Qemu. So then I have to restart Samba to bind to >to br0 i

[Qemu-devel] gtk fullscreen support

Fullscreen mode is working again. Scrollbars and menu bar are not available in fullscreen mode. -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection. /* * QEMU GTK2 display driver * based on SDL driver by Fabrice * * Copyright (c) 2005 Jim Brown * *

Re: [Qemu-devel] Connecting vde and LAN

On Tue, Jul 12, 2005 at 04:49:08AM +0200, Henrik Nordstrom wrote: > It you forget about Ethernet and instead send the packet as a raw IP > packet then it should reach the host, but you must then fake ARP > responses on behalf of the host. > I just tried this with libnet 1.1 (1.1.2.1 to be speci

Re: [Qemu-devel] Connecting vde and LAN

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ross Kendall Axe schrieb: > Oliver Gerlich wrote: > >>>The "problem" is that I start vde_switch and the bridging not at boot, >>>but when I want to run Qemu. So then I have to restart Samba to bind to >>>to br0 instead of eth0. Not so much of a proble

Re: [Qemu-devel] Connecting vde and LAN

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Oliver Gerlich wrote: > > The "problem" is that I start vde_switch and the bridging not at boot, > but when I want to run Qemu. So then I have to restart Samba to bind to > to br0 instead of eth0. Not so much of a problem though... Only I don't > know

Re: [Qemu-devel] problem with loop device

is loop device support compiled in the kernel ? On 7/12/05, Matt Lawrence <[EMAIL PROTECTED]> wrote: > > > [EMAIL PROTECTED] wrote on 07/12/2005 > 11:19:01 AM: > > > On Tuesday 12 July 2005 16:13, Matt Lawrence wrote: > > > I'm running on CentOS4 with a 2.6.11 kernel. After using losetup t

Re: [Qemu-devel] problem with loop device

[EMAIL PROTECTED] wrote on 07/12/2005 11:19:01 AM: > On Tuesday 12 July 2005 16:13, Matt Lawrence wrote: > > I'm running on CentOS4 with a 2.6.11 kernel.  After using losetup to > > configure loop0 and mounting /dev/loop0, I am unable to unmount it.  I keep > > getting "device is busy" message, b

[Qemu-devel] Windows build broken

Hi I hav built the current CVS of QEMU on my WinXP SP2 host with MinGW-3.1.0-1 / MSYS-1.0.10. Now, when starting QEMU, I get a black screen. No BIOS information is printed out and the QEMU window stays black. The console is working and QEMU seems to do something. The laster build I had done was f

Re: [Qemu-devel] problem with loop device

On Tuesday 12 July 2005 16:13, Matt Lawrence wrote: > I'm running on CentOS4 with a 2.6.11 kernel. After using losetup to > configure loop0 and mounting /dev/loop0, I am unable to unmount it. I keep > getting "device is busy" message, but lsof doesn't show anything. > Everything is being built au

[Qemu-devel] question on using qemu serial ports

Hey guys, From the documentation, it looks like serial ports can be sent to 4 places. I'm running Win XP as my guest OS, and would like to send the output of the guest directly to the serial port for reading by a real XP box to debug. Is this possible using QEmu? I'm using the kqemu. Thanks,

[Qemu-devel] problem with loop device

I'm running on CentOS4 with a 2.6.11 kernel. After using losetup to configure loop0 and mounting /dev/loop0, I am unable to unmount it. I keep getting "device is busy" message, but lsof doesn't show anything. Everything is being built automatically by a script, so I know I'm not leaving a termi

Re: [Qemu-devel] trunk sources fails to compile on Debian GNU/Linux 3.1 on AMD64.

On Tuesday 12 July 2005 13:15, Michael Wetherell wrote: > On Tuesday 12 Jul 2005 11:59, Karel Gardas wrote: > > > Qemu's trunk sources obtained from today CVS fails to compile on > > > debian 3.1/amd64 platform. The error is: > > > > > > gcc -g -Wl,-T,/home/karel/cvs/qemu/qemu/x86_64.ld -o qemu-i38

Re: [Qemu-devel] trunk sources fails to compile on Debian GNU/Linux 3.1 on AMD64.

On Tuesday 12 Jul 2005 11:59, Karel Gardas wrote: > > Qemu's trunk sources obtained from today CVS fails to compile on > > debian 3.1/amd64 platform. The error is: > > > > gcc -g -Wl,-T,/home/karel/cvs/qemu/qemu/x86_64.ld -o qemu-i386 > > elfload.o main.o syscall.o mmap.o signal.o path.o osdep.o th

Re: [Qemu-devel] trunk sources fails to compile on Debian GNU/Linux 3.1 on AMD64.

Hello, short followup: exactly the same issue also hits qemu 0.7.0 release. Cheers, Karel On Tue, 12 Jul 2005, Karel Gardas wrote: Hello, Qemu's trunk sources obtained from today CVS fails to compile on debian 3.1/amd64 platform. The error is: gcc -g -Wl,-T,/home/karel/cvs/qemu/qemu/x86

Re: [Qemu-devel] qemu tun networking bug

Thank you very much, Henrik, based on your reply I've found the relevant linux kernel TUN/TAP problem description in http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.11-rc2 and was able to workaround the problem in my case with the small patch: --- qemu-0.7.0/vl.c.orig20

[Qemu-devel] trunk sources fails to compile on Debian GNU/Linux 3.1 on AMD64.

Hello, Qemu's trunk sources obtained from today CVS fails to compile on debian 3.1/amd64 platform. The error is: gcc -g -Wl,-T,/home/karel/cvs/qemu/qemu/x86_64.ld -o qemu-i386 elfload.o main.o syscall.o mmap.o signal.o path.o osdep.o thunk.o vm86.o libqemu.a gdbstub.o -lm /usr/bin/ld:/ho

[Qemu-devel] Re: freeoszoo

Stefano Marinelli <[EMAIL PROTECTED]> wrote: > On Mon, 11 Jul 2005 11:30:23 -0500, <[EMAIL PROTECTED]> wrote: > > They were unable to transfer domain ownership to the new host. And since it > > wasn't renewed, it expired. > > > > I think it's temporarily on 'hold' by the registrar, so the owner c