On Thu, Aug 11, 2005 at 06:00:12PM +0100, Paul Brook wrote:
> > I guess this means that VDE would have to provide a kernel-layer
> > component which grabs the packets from eth0 and provides the faked eth0
> > for the Host OS...
>
> You can do all this with the standard linux tools. Something like
After further installing my new amd64 box (yes, if_sk works now :)
I just tried a few guests with qemu-system-x86_64:
amd64 guests, no kqemu:
KANOTIX-64-2005-03.iso (kernel 2.6.11 iirc, booted in text mode
without `quiet') hangs after printing `Brought up 1 CPUs'
5.4-RELEASE-amd64-disc1.iso (F
On Thu, Aug 11, 2005 at 06:24:51PM +0200, Oliver Gerlich wrote:
> Couldn't we avoid these incompatibilities if we would route packets only
> on the Ethernet level? If the Qemu networking setup on the host involves
> IP addresses or such things, we're already on the wrong OSI layer I think...
>
> I guess this means that VDE would have to provide a kernel-layer
> component which grabs the packets from eth0 and provides the faked eth0
> for the Host OS...
You can do all this with the standard linux tools. Something like the
following(untested) script. ifrename is part of the Linus Wireles
Henrik Nordstrom wrote:
On Wed, 10 Aug 2005, Jim C. Brown wrote:
[...]
The above should work for most situations where the host is a just a
host on the LAN, but if the host is a LAN server for broadcast Ethernet
protocols such as DHCP some additional configuration of each such
service may be
>
>I don't know if it has already been said on this list. Forgive me if
so.
I've already reported this some time ago. The impression I get is that
not too
many developers are using 64-bit machines...
The following patch works fine on 64 and 32 bit machines (Linux and OS
X).
diff -c -2 -
On Wed, 10 Aug 2005, Jim C. Brown wrote:
I was thinking that perhaps vde_packet could be modified to use a tap device
(for example tap0). Since the guests can't communicate to the address thats on
tap0, it doesn't matter what address it gets - the host address of tap0 and the
ip addresses of the
> > Actually that'd be a fairly neat trick... As an alternative, IIRC
> > there's a user space API for writing USB drivers under Linux - using that
> > you could
>
> get
>
> > access to both local and remote (IP encapsulated) USB devices, albeit not
> > in a cross-platform (host-wise) way.
>
>
Nardmann, Heiko schrieb:
> Am Mittwoch, 10. August 2005 10:14 schrieb Adam Bradley:
>> Yves Trudeau wrote:
>> > Filip Navara a écrit :
>> >> Yves Trudeau wrote:
>> >>> Hi,
>> >>>I am trying to use a VMWare Win2k image in Qemu-0.7.1. I imported
>> >>> the image with qemu-img successfully but wh
>-Original Message-
>From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
>Sent: Thursday, August 11, 2005 01:57 AM
>To: qemu-devel@nongnu.org
>Subject: [Qemu-devel] bug in Sparc part ?
>
>I don't know if it has already been said on this list. Forgive me if so.
I've already reported this some
Am Mittwoch, 10. August 2005 10:14 schrieb Adam Bradley:
> Yves Trudeau wrote:
> > Filip Navara a écrit :
> >> Yves Trudeau wrote:
> >>> Hi,
> >>>I am trying to use a VMWare Win2k image in Qemu-0.7.1. I imported
> >>> the image with qemu-img successfully but when I lauch qemu, I have
> >>> the
11 matches
Mail list logo
