On Mon, May 08, 2006 at 07:05:19PM +0200, Oliver Gerlich wrote:
> > Currently I'm working on a version that doesn't require a kernel module to
> > do this - it will have the limitation of only supporting tcp/ip packets when
> > talking between host/guest.
>
> Are you sure that limitation is not to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim C. Brown schrieb:
> On Sat, May 06, 2006 at 01:12:50AM +0200, Oliver Gerlich wrote:
>
>>Don Kitchen schrieb:
>>
>>>Next, it seems the *one* thing QEMU lacks that you-know-who does correctly
>>>is networking, specifically bridged mode. I know about
On Fri, May 05, 2006 at 02:51:28PM -0700, Don Kitchen wrote:
> $ qemu-img info someimage
> image: someimage
> file format: qcow
> virtual size: 75G (80026361856 bytes)
> disk size: 304K
>
> For files with a backing file, has anyone thought about having it print out
> the name of the backing file?
On Sat, May 06, 2006 at 01:12:50AM +0200, Oliver Gerlich wrote:
> Don Kitchen schrieb:
> > Next, it seems the *one* thing QEMU lacks that you-know-who does correctly
> > is networking, specifically bridged mode. I know about creating a tap device
> > and sticking it into a bridge (really hasn't wor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Don Kitchen schrieb:
> Next, it seems the *one* thing QEMU lacks that you-know-who does correctly
> is networking, specifically bridged mode. I know about creating a tap device
> and sticking it into a bridge (really hasn't worked for me, but that's th
First some suggestions for what they're worth...
$ qemu-img info someimage
image: someimage
file format: qcow
virtual size: 75G (80026361856 bytes)
disk size: 304K
For files with a backing file, has anyone thought about having it print out
the name of the backing file? Particularly this would b
