Re: [Xen-devel] GPLPV + Xen Unstable BSOD

[Andrew Lyon <andrew.lyon@xxxxxxxxx>]

On Wed, Feb 25, 2009 at 11:45 AM, Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:
> On Wed, Feb 25, 2009 at 11:28 AM, Andrew Lyon <andrew.lyon@xxxxxxxxx> wrote:
>> On Wed, Feb 25, 2009 at 11:20 AM, James Harper
>> <james.harper@xxxxxxxxxxxxxxxx> wrote:
>>>>
>>>> On Wed, Feb 25, 2009 at 11:08 AM, James Harper
>>>> <james.harper@xxxxxxxxxxxxxxxx> wrote:
>>>> >> On 25/02/2009 02:48, "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
>>>> > wrote:
>>>> >>
>>>> >> > My Xen Signature is 'XenVMMXenVMM', and my Hypercall area is page
>>>> >> > aligned. Any suggestion as to why you might be getting 'Microsoft
>>>> > Hv'? I
>>>> >> > suspect that maybe Xen unstable is trying to make itself look
>>> like a
>>>> >> > Microsoft HyperV system so that Windows behaves a bit better, but
>>>> >> > obviously that has introduced other problems. Can you turn that
>>> off?
>>>> > You
>>>> >> > might ultimately need it turned on but if you turn it off and it
>>>> > works I
>>>> >> > will be a bit more certain about the problem.
>>>> >>
>>>> >> Probably 'viridian=1' is in the domain config file. So that can
>>> simply
>>>> > be
>>>> >> removed to revert to old CPUID behaviour. Or even explicitly put
>>>> >> 'viridian=0' in the config file.
>>>> >
>>>> > Andrew: Can you please try with that option?
>>>>
>>>> Exactly right, I had viridian=1 in the config file, thats the reason I
>>>> wanted to use unstable, becuase it has viridian support which will set
>>>> the "relaxed timer" cpuid bit to prevent bsod with code 101 which I
>>>> get on 3.3.x,
>>>
>>> I was afraid of that :)
>>>
>>>> I have removed the setting and tried the install again,
>>>> it did not crash and the drivers were all detected normally, I've not
>>>> tried booting up with the drivers loaded yet as my xp vm has decided
>>>> to install a load of updates as it shuts down, as soon as its finished
>>>> I will try booting up with the drivers loaded.
>>
>> Booting up now.. seems ok so far.
>
> Just to let you know, seems to work perfectly with viridian=0, the
> emulated devices have disappeared in device manager too :).

Are the emulated devices hidden becuase your device hiding patch has
been merged into qemu unstable? I didnt patch Xen unstable or qemu
with anything at all, but all of the emulated devices apart from cdrom
are gone once the drivers are loaded, and even when I show hidden
devices they are not listed.

Nice :).

Andy

>
>>
>>>>
>>>> Anwyay, viridian seems to be the problem, can it be easily fixed?
>>>>
>>>
>>> I could make available an installer for you to test if you want, but
>>> it's very beta at the moment, and probably not for a few days anyway as
>>> there is at least one bug I know of that will cause you pain :)
>>
>> That would be great, at the moment the bsod 101 causes my system to
>> lockup if the crashing vm has a pci passthrough device so I'm already
>> in quite a bit of pain.
>>
>> Thanks for looking into this James, great work as usual :).
>>
>> Andy
>>
>>>
>>> James
>>>
>>>
>>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel