[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Xen 4.2 Windows 8 Issues

On 10/23/2013 03:10 PM, Shane Johnson wrote:
Only thing I would hesitate over is it isn't a release version and may
still have bugs in it.  As for that patch, it's over 3 years old.  I
would imagine it's in the version you're running. I would see what
version it was written for and what you're running and maybe a little
research to see if the patch was accepted.  I think your best bet
would be either stable or, if you don't mind helping the developers
debug it, the 4.3.0-RC6 you mentioned.


On Wed, Oct 23, 2013 at 1:55 PM, John Wargo <wargo.john25@xxxxxxxxx> wrote:
On 10/23/2013 08:15 AM, Shane Johnson wrote:

Some other things I have thought of while reviewing your problem.  I
don't remember where I read it but I remember reading that someone
couldn't get passthrough working during install and only by waiting
till Windows 7 I believe it was was fully installed then they
installed the driver and then enabled passthrough.  Another thing you
might want to try is reducing the amount of RAM you are throwing at
the DomU to below 4G I think it is.  I know there are some posts on
the forums about people having issues with this and if I remember
right there is a solution for running more memory but I don't know
exactly what it is.


On Wed, Oct 23, 2013 at 4:53 AM, John Wargo <wargo.john25@xxxxxxxxx> wrote:

On 10/22/2013 08:37 PM, Shane Johnson wrote:

On Tue, Oct 22, 2013 at 4:30 PM, John Wargo <wargo.john25@xxxxxxxxx>

On 10/22/2013 02:51 PM, Shane Johnson wrote:


       (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x0090, fault
address = 0xffffffc0
[truncated output, only first 10 iterations are shown...]

What is the best way to go about solving this problem?
As always just ask for more info,

Xen-users mailing list

It seemed to fix the irq error, however I'm still getting the
I'll go through the debugging page on the wiki, and see what I can't dig

I know when I have need help before, I was asked to include the
verbose output of the create command and the log files mentioned in
the submitting a bug section. From looking at those logs,  those on
here who know a heck of a lot more that I do where able to spot what
my problem was.  If you can't find it with the steps on the debugging
wiki that may be the next best step.  Also some details on your
hardware and a file or screen print of your xl list command would also
probably be beneficial.

Good luck

After some debugging, here is what I've been able to come up with, if
there's an issue with attachments, just let me know how to properly post

Included in the zip :
create.xen     - The result of "xl create -d ./win8.cfg"
dmesg-boot.xen - The result of "xl dmesg" immediately after boot
dmesg-win8.xen - The result of "xl dmesg" after failing to install
windows 8
grub           - My grub configuration file (/etc/default/grub)
info.xen       - The result of "xl info"
win8.cfg       - The configuration file I'm using for windows 8


Sorry John,
Memory isn't as good as it used to be.  I went back and read the
entire conversation again and I think something clicked.  (Or maybe
just broke).  Try disabling viridian.  I just remembered when I loaded
Win8.1 just to test it out to see if it was bad as everyone said, I
ran into something similar.  If I remember correctly I completely
disabled viridian or at least until I had 8.1 up and running.
Like I said I'm not an expert on this.
Looking over your logs I don't see anything that stands out.
Hopefully something here helps.  If not hopefully one of the guru's
will step in.
Just out of curiosity, Is there is reason for disabling the IOMMU
remapping in your grub file?

Hmm, I disabled the VGA passthrough, and it all seems to work fine, I'm
going to try passing my GPU
through now that it's installed, but I doubt that it'll work.

I'm using an XFX Radeon 7850 for passthrough, it's reported to work, so I
think that it's the issues
that I've been having with my AMD FX-6300 processor and IOMMU..

If anybody knows of how to fix these issues, that would be great..

I was browsing the wiki earlier today, and I found this :
It's a source-code patch for xen. How do I apply it?
Also, I'm thinking about building Xen-4.3.0-RC6 from source, is there a
reason why I shouldn't try to see if a fix has been implemented there?


After installing the xen drivers and the catalyst drivers, I rebooted windows. Upon restarting, it went back to the "Configuring Devices n%" screen, where it proceeded to crash once again. This time though, the crash didn't bring down my entire system. The entire dmesg output is filled with "(XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x0090, fault address = 0xffffffc0" (or at least until the terminal buffer). The full file is attached. Any thoughts?


Attachment: win8-catalyst.xen
Description: Text document

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.