xenbusb_nop_confighook_cb timeout

[Egoitz Aurrekoetxea Aurre]

I'm going to take a look at it tomorrow… today impossible as told you before… but if anyone too has some time to check it too, could be nice… because I'm pretty busy this days :)


El 14/11/2012, a las 17:51, Mark Felder <feld at feld.me> escribió:

> Hi guys,
> 
> I've been in contact with Bob Ball at Citrix and he's passed on this
> information after confirming the bug we're seeing. I was hoping
> someone on the list could help track this down.
> 
>> I experienced the CDROM issue on XenServer 6.0 and 6.1.  I've seen 
>> http://www.mail-archive.com/freebsd-xen@freebsd.org/msg01369.html which
>> suggests that there was a fix in Xen 4.1.2, which is surprising since
>> XenServer 6.1 uses Xen 4.1.3 and still exhibits the problem.
>> http://xenbits.xen.org/gitweb/?p=qemu-xen-4.2-testing.git;a=commit;h=effd5676225761abdab90becac519716515c3be4
>> refers to another regression from 4.1.2 to 4.1.3 relating to the CDROM,
>> but it appears as though this regression was not merged into XenServer
>> (i.e. the Xen 4.1.3 used in XenServer did not require this further patch).
>> 
>> http://xen.1045712.n5.nabble.com/Xen-4-1-1-HVM-guest-cdrom-trouble-lost-interrupts-ata-failed-commands-frozen-td4953147.html#a5028910
>> gives one potential fix, which I believe is the one referenced in the
>> release notes for 4.1 - however, I've applied this to my Xen and it
>> does not appear to enable FreeBSD guests to boot with CDs attached.
>> Could you confirm this from the other perspective and try the
>> equivalent guest kernel patch?
>> 
>> diff --git a/arch/x86/pci/xen.c b/arch/x86/pci/xen.c
>> index 8214724..6b57f90 100644
>> --- a/arch/x86/pci/xen.c
>> +++ b/arch/x86/pci/xen.c
>> @@ -308,8 +308,7 @@ int __init pci_xen_init(void)
>> 
>> int __init pci_xen_hvm_init(void)
>> {
>> -       if (!xen_feature(XENFEAT_hvm_pirqs))
>> -               return 0;
>> +       return 0;
>> 
>> #ifdef CONFIG_ACPI
>>        /*
>> 
>> This appears to be a patch for Linux, and I've not located the 
>> equivalent file in FreeBSD (I'm assuming this is down to my 
>> inexperience in FreeBSD!)
>> 
>> I believe that this probably means we have a problem in Xen with 
>> booting FreeBSD guests that hasn't been tracked down, would you agree?
>> Have either of you seen this working on later versions of OpenSource 
>> Xen? (i.e. not XenServer?)  
> _______________________________________________
> freebsd-xen at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-xen
> To unsubscribe, send any mail to "freebsd-xen-unsubscribe at freebsd.org"