tech-kern archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Fixing tap(4) behaviour

On Sat, Nov 29, 2008 at 09:21:43PM +0100, Quentin Garnier wrote:
> On Sat, Nov 29, 2008 at 03:05:46PM -0500, Arnaud Lacombe wrote:
> > Hi Folks,
> > 
> > People currently using qemu(1) need to use a dirty static fd-based
> > trick to link the created interface to qemu(1). This is due to the
> > fact that 1) qemu doesn't check the return value of the stat(2)
> > syscall and 2) our tap(4) cloner device provide nothing to know the
> > created interface's unit. I fixed this by making the cloner device
> That's not true.  You should have read tap(4)'s manual page.  Besides,
> I have always told people how qemu was supposed to do that, and I think
> that someone had actually made a patch for qemu at some point but I
> guess it was lost.

Also, the qemu-dm in xentool3-hvm (and I guess xentools33) works with tap
just fine. pkgsrc/sysutils/xentools3-hvm/patches/patch-ar has the
changes that are needed for this (and also other, unrelated changes).
From memory it's just the TAPGIFNAME part that is needed.

Manuel Bouyer <>
     NetBSD: 26 ans d'experience feront toujours la difference

Home | Main Index | Thread Index | Old Index