[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-users] VGA Passthrough of AMD HD8670D IGP to HVM Win7 results in "Code 43"
Hello everyone, For the past few days, I've been trying to pass the GPU of my AMD A-10 6800K APU to a HVM Windows 7 guest, but haven't had any luck yet.pardon me If I'm doing anything wrong, this is my first post to this list. I've tried to follow numerous guides to get VGA passthrough to work; currently, I'm running Linux Mint 13 XFCE and did most of what this guide proposes: http://forums.linuxmint.com/viewtopic.php?f=42&t=112013 However, with Mint as well as with Debian wheezy, I wasn't able to start DomUs with the xen from the repositories; some seconds after xm create or xl create, the host computer would reboot; I haven't figured out why. The same holds with xen 4.3 compiled from source, at least on Mint. However, the most recent xen from the mercurial repository allows me to start DomUs. Also, when using Mint, I had to upgrade from the stock 3.2.0-23 kernel to 3.8.0-26 from the backports, otherwise the machine would reset immediately or shortly after xen tried to load the linux kernel. Again, having limited experience with debugging linux or xen problems, I was unable to figure out why. Finally having installed Windows 7 I installed the most recent AMD catalyst drivers in the DomU. After that, in the Device Manager, the graphics card shows up, but with a yellow triangle; a double click on the GPU gave me "Code 43" as an explanation of what went wrong. What I found with google only points to nVidia-users having that problem. I also tried to set gfx_passthru to 1, but then xl create would complain: libxl: error: libxl_dm.c:1275:device_model_spawn_outcome: domain 2 device model: spawn failed (rc=-3) libxl: error: libxl_create.c:1075:domcreate_devmodel_started: device model did not start: -3 libxl: error: libxl_dm.c:1306:libxl__destroy_device_model: Device Model already exited and /var/log/xen/qemu-dm-orthowin.log would contain qemu-system-i386: -gfx_passthru: invalid option For reference, here is the kernel config: http://pastebin.com/kwUWkyP2 My DomU configuration: http://pastebin.com/E9jkkJXj The output of xl info: http://pastebin.com/nj1ykFXJ The output of xl dmesg: http://pastebin.com/MS96knmL
The output of dmesg: http://pastebin.com/2sQFuCuJ Please note, as it might be related to my issue, that what comes at the end of the dmesg output seems suspicious to me (RIP [<ffffffff81012861>] xen_spin_lock+0x21/0x50 and the lines around that) I hope that I have provided enough information for further investigation. The computer is not in any kind of production-use, so please feel free to request things that will or may require me to reinstall the operating system or some of its components. As the hardware is new, I'd not be happy if I had to do something that would risk permanent damage. :) Should this be the wrong mailing list for this kind of post, please let me know where I can send it to instead. Thank you very much for your time, any help is highly appreciated, not only regarding my primary problem (getting VGA passthrough to work) but also the others mentioned, especially since they might be related. _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |