RE: [Xen-devel] domains not shutting down properly-theproblemisbackagain

["James Harper" <james.harper@xxxxxxxxxxxxxxxx>]

> > Perhaps multiprocessor dom0, plus a bug in the dom0 kernel which
means
> > that
> > the VCPU which Xen notifies for the virq is not the one which dom0
> kernel
> > is
> > expecting to receive the notification to? What do you use as dom0
> kernel?
> >
> 
> That appears to be the problem.
> 
> 1. xenstore starts up and binds VIRQ_DOM_EXC to port 18
> 2. xend starts and sets the number of cpus to 1 (dom0-cpus = 1)
> 3. xen notifies xenstore on port=18, vcpu=1, but vcpu 1 doesn't exist
> anymore so the event never gets anywhere
> 
> The curious thing is that IOCTL_EVTCHN_BIND_VIRQ explicitly sets vcpu
=
> 0, so why is the event getting delivered to vcpu 1???
> 

Something is making a call to evtchn_bind_vcpu...

James

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