[Xen-devel] EVTCHNOP_failure / xen 4.11
Hi, When I upgrade to Xen 4.11, I got the following when creating any guest: (XEN)_event_channel.c:319:d0v3_EVTCHNOP_failure:_domain_1,_error_-22 (XEN)_event_channel.c:319:d0v3_EVTCHNOP_failure:_domain_1,_error_-22 (XEN)_event_channel.c:319:d0v3_EVTCHNOP_failure:_domain_1,_error_-22 (XEN)_event_channel.c:319:d0v3_EVTCHNOP_failure:_domain_1,_error_-22 (XEN)_event_channel.c:319:d0v3_EVTCHNOP_failure:_domain_1,_error_-22 (XEN)_event_channel.c:319:d0v3_EVTCHNOP_failure:_domain_1,_error_-22 (XEN)_event_channel.c:319:d0v3_EVTCHNOP_failure:_domain_1,_error_-22 (XEN)_event_channel.c:319:d0v3_EVTCHNOP_failure:_domain_1,_error_-22 (XEN)_event_channel.c:319:d0v3_EVTCHNOP_failure:_domain_1,_error_-22 (XEN)_event_channel.c:319:d0v3_EVTCHNOP_failure:_domain_1,_error_-22 This behavior is not seen when using Xen 4.10-stable. Any idea? Best Regards, Yessine daoud ᐧ ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Xen-devel] Slow HVM boot time, was "HVM boot time optimization"
Hello, I tried to debug the issue and this what I found: the HVM boot takes some time at the following section (qemu/pc-bios/optionrom/linuxboot.S) /* Load kernel and initrd */ read_fw_blob_addr32_edi(FW_CFG_INITRD) (ramdisk about 3M takes ~~7.s) read_fw_blob_addr32(FW_CFG_KERNEL) (vmlinuz about 7M takes ~~15.s) read_fw_blob_addr32(FW_CFG_CMDLINE) #define read_fw_blob_addr32(var) \ read_fw var ## _ADDR; \ mov %eax, %edi; \ read_fw_blob_pre(var); \ /* old as(1) doesn't like this insn so emit the bytes instead: \ addr32 rep insb (%dx), %es:(%edi); \ */ \ .dc.b 0x67,0xf3,0x6c #define read_fw_blob_addr32_edi(var) \ read_fw_blob_pre(var); \ /* old as(1) doesn't like this insn so emit the bytes instead: \ addr32 rep insb (%dx), %es:(%edi); \ */ \ .dc.b 0x67,0xf3,0x6c Any idea how to speed the I/O read ? Thanks. ᐧ 2018-02-12 15:42 GMT+01:00 Wei Liu <wei.l...@citrix.com>: > On Mon, Feb 12, 2018 at 09:27:25AM +0100, Yessine Daoud wrote: > > Hello, > > > > Thank you for your quick response. > > Any hints how can I "fix" this "issue"? *Any workaround? > > > > Honestly I have no idea why it is slow unless there is more logging > available. > > Wei. > ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
