RE: [Xen-devel] "kobject add failed"

["Petersson, Mats" <Mats.Petersson@xxxxxxx>]

> -----Original Message-----
> From: Keir Fraser [mailto:keir@xxxxxxxxxxxxx] 
> Sent: 03 May 2007 17:41
> To: Petersson, Mats; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] "kobject add failed"
> 
> 
> Looks like a dom0 kernel bug?

Yes, that's what I think too... 

I haven't seen it before. Any idea why this would happen now, and not
before?

Why would it happen only when doing two save/restore sessions (of
different domains of course) on the same machine (which I have done
before - but not that recently). 

I got a second backtrace like that. I've since tried to avoid it by
removing the (unnecessary) vif= in the setup of the simple-guest (it's
got no code to deal with network devices anyway). 

--
Mats
> 
>  -- Keir
> 
> On 3/5/07 16:39, "Petersson, Mats" <Mats.Petersson@xxxxxxx> wrote:
> 
> > When runnign two scripts for hvm save/restore iterations at the same
> > time, I got this message after around 150 (combined between the two
> > scripts). The one process is now stuck on "saving"...
> > 
> > kobject_add failed for tap0 with -EEXIST, don't try to 
> register things
> > with the
> > same name in the same directory.
> > 
> > Call Trace:
> >  [<ffffffff802e9af5>] kobject_add+0x16e/0x199
> >  [<ffffffff8034522b>] class_device_add+0xaf/0x441
> >  [<ffffffff802e97c0>] kobject_get+0x12/0x17
> >  [<ffffffff80394a39>] register_netdevice+0x23b/0x30b
> >  [<ffffffff882df972>] :tun:tun_chr_ioctl+0x272/0x4db
> >  [<ffffffff8027e6f0>] do_filp_open+0x2d/0x3d
> >  [<ffffffff80291621>] do_ioctl+0x55/0x6b
> >  [<ffffffff80291889>] vfs_ioctl+0x252/0x26b
> >  [<ffffffff802918fb>] sys_ioctl+0x59/0x7a
> >  [<ffffffff8020a640>] tracesys+0xa7/0xb3
> 
> 
> 
> 



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel