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

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

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>
>> wrote:
>>> On 10/22/2013 02:51 PM, Shane Johnson wrote:
>>> <snip>
>>>       (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,
>>> -John
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@xxxxxxxxxxxxx
>>> http://lists.xen.org/xen-users
>>> It seemed to fix the irq error, however I'm still getting the
>>> errors.
>>> I'll go through the debugging page on the wiki, and see what I can't dig
>>> up..
>>> -John
>>> John,
>>> 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
>>> Shane
>>> 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
>>> the
>>> logs.
>>> 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
>>> -John
>> 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..
> -John

Shane D. Johnson
IT Administrator
Rasmussen Equipment

Xen-users mailing list



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