Re: [win-pv-devel] Upcalls not enabled on a processor

[RafaÅ WojdyÅa <omeg@xxxxxxxxxxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2015-06-22 00:44, RafaÅ WojdyÅa wrote:
> Hi,
> 
> I've been testing the full pvdrivers package under Qubes and I see 
> this problem happening sometimes. It seems that xenvif waits
> forever for backend state to change. Debug output seems to suggest
> that something else is the real cause of the problem and xenvif is
> just the first victim:
> 
> XENVIF|FrontendAcquireBackend: =====> 
> XENVIF|FrontendWaitForBackendXenbusStateChange: 
> /local/domain/2/backend/vif/14/0: ====> Unknown 
> XENBUS|StoreProcessWatchEvent: 55b5 
> (/local/domain/2/backend/vif/14/0/state) 
> XENVIF|FrontendWaitForBackendXenbusStateChange: 
> /local/domain/2/backend/vif/14/0: <==== (Closed) 
> XENVIF|FrontendSetXenbusState: device/vif/0: ====> Initialising 
> XENBUS|StoreProcessWatchEvent: 5599 (device/vif/0/state) 
> XENBUS|StoreProcessWatchEvent: 55af (device/vif/0/state) 
> XENVIF|FrontendSetXenbusState: device/vif/0: <==== Initialising 
> XENVIF|FrontendWaitForBackendXenbusStateChange: 
> /local/domain/2/backend/vif/14/0: ====> Closed 
> XENBUS|StoreProcessWatchEvent: 55b6 
> (/local/domain/2/backend/vif/14/0/state) 
> XENVIF|FrontendWaitForBackendXenbusStateChange: 
> /local/domain/2/backend/vif/14/0: <==== (InitWait) 
> XENBUS|StoreProcessWatchEvent: 55b7 
> (/local/domain/2/backend/vif/14/0/online) XENVIF|FrontendPrepare:
> <==== XENVIF|FrontendSetState: device/vif/0 in state 'PREPARED' 
> XENVIF|FrontendConnect: ====> XENVIF|FrontendSetNumQueues: 2 
> XENVIF|ReceiverConnect: ====> XENBUS|CacheCreate: ====>
> (device_vif_0_queue-0_receiver_gnttab) XENBUS|CacheCreate: <==== 
> XENBUS|EvtchnOpen: 9 XENBUS|EvtchnBind: fail1 (c00000bb) 
> XENBUS|CacheCreate: ====> (device_vif_0_queue-1_receiver_gnttab) 
> XENBUS|CacheCreate: <==== XENBUS|EvtchnOpen: 10 XENBUS|EvtchnBind:
> fail1 (c00000bb) XENVIF|ReceiverConnect: <====
> 
> EvtchnBind fails with STATUS_NOT_SUPPORTED and that's caused by 
> upcalls not being enabled on the processor. What can be the cause
> of this? EvtchnInterruptEnable is being called but apparently 
> HvmSetEvtchnUpcallVector fails because I see no debug output that 
> should be present if it succeeds. I guess I should check the 
> hypervisor logs for any clues...
> 
I've done some more testing and I'm even more confused. The hypervisor
log doesn't show any relevant errors or other messages. Then if I
don't install xenvif and xennet in my HVM, the problem goes away. I
*think* the hang only occurs with a debug build but I need to verify tha
t.

Also the "upcalls not enabled" error might be a red herring. I added
some more diagnostic output to xen.sys and apparently this occurs even
during normal HVM boot:

XENBUS|EvtchnInterruptEnable: ====>
XEN|HvmSetEvtchnUpcallVector: errno -38
XEN|HvmSetEvtchnUpcallVector: errno -38

Then again, during a normal boot (without xenvif/xennet) EvtchnBind
doesn't fail anywhere...

I also noticed a lot of the following even during normal HVM operation:
XEN|HvmPagetableDying: errno -22
...but it's probably harmless?

- -- 
RafaÅ WojdyÅa
Qubes Tools for Windows developer
-----BEGIN PGP SIGNATURE-----

iQEcBAEBAgAGBQJViJNSAAoJEIWi9rB2GrW7LNUH/igdRGgnrUAlR+oY8gzKEWB2
riqCYAHSRvlAPQTIaTfhM09zfWeAgC8fxNwvx/9PLwjE38O93zXwerhCrk8BhSM/
HcanJYHup+Onccibbfps1om0B6Bja0Zxsnp6cXrLMd9PJDkUTmNBFdpeqnGK0uMv
u7QbYK50Zrjxta7rI6ZQr2V0FcgMjDQC8zSsqwv6RFdnF1CSKNweDXZ7m5bQS9Qk
Qp9J+Chg4FLGXxrH8wMj4X326AdsIlXg7pa05XUtr1WWfJ+RzHTVO4e5R3A0zk77
sV2qX7bKqiig5/gvfIvkLjQj65ZNurF+miERopP+Wuitx6vSs98i+3QKy2+hybU=
=0NPc
-----END PGP SIGNATURE-----

_______________________________________________
win-pv-devel mailing list
win-pv-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel