WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] GPLPV + Xen Unstable BSOD
From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
Date: Wed, 25 Feb 2009 12:26:33 +0000
Cc:
Delivery-date: Wed, 25 Feb 2009 04:26:57 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=ssG8FZz9K/q50wdUSRiLlsolK9oVh1AcJwO9onb4MCc=; b=FSDvxhF1OjAyeHs3e2zJjMYPfMgAuBLSgOSPQbiwhbR3zYjCCoa445MI1qbkJUSyVZ IrBKE9ltxZUdU4uCmrTT3hiyK2kdAZUt6Vk6j9VB1uevy17Qxk7pcviOpeYSAB3SYEPQ b/TuLM2Q/U2fJkpO2SmvuJ/bRLiZTFU5fOUGg=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=VbxhWCa1IrBRQ5kk5++tSNQXWJcE7tat8sWnSoLgHkkUDwA1lClXSd2JKOAHdAkoK1 lsHNTFFdMGStn3/ef0US50PnRzSx45eHSDNTJFLze0/RhV3BV8CPICzle7jlks1bUfZD CZSi9Lod+0BL6hgY5qHWhIu2vvxaBf+tlNSA8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <f4527be0902250345h5299ed0du499aee44cbded196@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D0162C941@trantor> <C5CA6606.3469%keir.fraser@xxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0162C942@trantor> <f4527be0902250317m1fb262edj985a9d1f808c9747@xxxxxxxxxxxxxx> <AEC6C66638C05B468B556EA548C1A77D0162C943@trantor> <f4527be0902250328y22c2c9ebgacd591103dac3e4@xxxxxxxxxxxxxx> <f4527be0902250345h5299ed0du499aee44cbded196@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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

<Prev in Thread] Current Thread [Next in Thread>