search for: azx_get_response

Hi developers, I met some domU issues and the log suggests missing interrupt. Details from here: http://www.gossamer-threads.com/lists/xen/users/263938#263938 In summary, this is the suspicious log: (XEN) vmsi.c:122:d32767 Unsupported delivery mode 3 I''ve checked the code in question and found that mode 3 is an ''reserved_1'' mode. I want to trace down the source of this

...e errors. Since Xen never boots successfully - there is no log message. So I captured the output with video and posted screenshots at http://skippyvondrake.com. Maybe it''s a hardware issue. The motherboard has Intel chipset x58 (if that helps). The first message of interest: hda_intel: azx_get_response timeout Followed by stuff like "failed command: READ FPDMA QUEUED" And near the end: ni_cp: Failed to load firmware "radeon/TURKS_pfp.bin" disabling GPU acceleration -Skippy

I''ve seen a recent report claiming that it works: http://linux-bsd-sharing.blogspot.pt/2012/10/howto-xen-413-windows-8-hvm-domu-with.html However, in my case, with a slightly different HW configuration the story is totally different. :-（ My config: HW: I7-3770 + AsRock H77M-ITX board Dom0: Debian Wheezy stock xen (v4.1.3) + Debian stock kernel (3.2.x / 3.6.x) 64 bit version. Note that