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/
Home Products Support Community News


Re: [Xen-devel] Re: [Xen-users] Xen viridian support/features

To: Florian Manschwetus <florianmanschwetus@xxxxxx>
Subject: Re: [Xen-devel] Re: [Xen-users] Xen viridian support/features
From: Andrew Lyon <andrew.lyon@xxxxxxxxx>
Date: Fri, 24 Jul 2009 22:29:40 +0100
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 24 Jul 2009 14:30:25 -0700
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:cc:content-type :content-transfer-encoding; bh=lq1xw7K+Xzb211QR3R9o4gqUjo3atnFdz8HixBYtgYk=; b=sEbpaoTQ2lHrJ5d+RZyiGFapLKBvMBQA1KXX2gXX7XC/EvTyVLHik1dZkaQiiA9sEB j7bP8U47w9a6Srh2qFyFmUWt18GzVFMNqZEjMB3OdAibif3o/J5epZigCBlX7MdmaiP/ 4EHLZRDPUY+rMW3zwIhhRO4dGHXv56omlS2Vo=
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 :cc:content-type:content-transfer-encoding; b=kHz89ar6q9xtFnULvQc3NVa/2bOXA287jrxSVjUMRzkgPO1AVt39up3Nh/nehS9y3K h27HRJJff7PlydBOm0i7YtQW5NST+6PkrL10NJe+ckti7mqn95dHYC6UoXWdvmkT2w70 /D34ZtBrQHAWOPiw/MtAQtCSUUQrBS1PRF8BE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A6A1203.1060404@xxxxxx>
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: <11B064048F34FD4094CBA16FC04BE2196072A843@ex01> <20090721072326.GN24960@xxxxxxxxxxxxxxx> <20090721171533.GT24960@xxxxxxxxxxxxxxx> <20090723141101.GF5235@xxxxxxxxxxxxxxxxxxxxx> <20090723141953.GE24960@xxxxxxxxxxxxxxx> <20090723142715.GG5235@xxxxxxxxxxxxxxxxxxxxx> <4A68D607.10606@xxxxxxxx> <4A69C7FA.6020506@xxxxxx> <f4527be0907241231g609a7039s432eb6e3fd5a6172@xxxxxxxxxxxxxx> <4A6A1203.1060404@xxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, Jul 24, 2009 at 8:56 PM, Florian
Manschwetus<florianmanschwetus@xxxxxx> wrote:
> Am 24.07.2009 21:31, schrieb Andrew Lyon:
>> On Fri, Jul 24, 2009 at 3:40 PM, Florian
>> Manschwetus<florianmanschwetus@xxxxxx>  wrote:
>>> Uhm, just to get clear in this topic,
>>> the great work of James is not that useful as it supposed in this thread.
>>> It
>>> leaks reliable support for exactly those Windows Versions with best
>>> Hyper-V
>>> integrations.
>>> So there is the choice to exploit Hyper-V guest integration services or
>>> absolutely ugly hacking around in a win2008 x64 guest policies with a
>>> real
>>> great chance to get the guest perfectly and unrecoverable meshed up.
>>> So it would be great at least to have things like shutdown notification
>>> out
>>> of the box, as it will be with an viridian interface implementation
>> When you say "shutdown notification" I assume you mean dom0 telling a
>> hvm guest to shutdown , in which case "xm trigger<domid>  power" seems
>> to do the job with no additional drivers or services required, and
>> should work on most operating systems.
>> Perhaps I misunderstood..
> Hm no it is fine but when I shutdown dom0 the windows system just get killed
> (xm shutdown is issued afaik). Furthermore this won't include a back channel

Yes thats right when the system shuts down xm shutdown is called, I
don't know what happens if a guest fails to shutdown, myself I'd
probably want it to be xm destroyed after a timeout as thats probably
what I'd end up doing anyway, I could easily modify the script for you
so that after trying xm shutdown it sends xm trigger <domid> power to
any remaining domains and if any still fail to shutdown I could make
it destroy them.

Its something I looked into and could do in few minutes, I just didn't
bother because all of our servers have remote kvm and 99% of reboots
are supervised, but let me know if you'd like me to make a patch for


> (does it work?) and not every system surely shutsdown when powerbutton is
> pressed, maybe there must be a bit configured...
> Florian
>> Andy
>> .
>>> Again if xen provides a feature using viridian API win2008 x64 guests
>>> would
>>> use it without ANY modification.
>>> Florian
>>> Am 23.07.2009 23:28, schrieb Jeremy Fitzhardinge:
>>>> On 07/23/09 07:27, Tim Deegan wrote:
>>>>> At 15:19 +0100 on 23 Jul (1248362393), Pasi K?rkk?inen wrote:
>>>>>> Any plans to write support for paravirtual viridian disk/network
>>>>>> backends?
>>>>>> (I assume they have stuff like that implemented in hyper-v).
>>>>> I don't think anyone's doing that, but there is a choice of Xen PV
>>>>> drivers for Windows that will do the job.  Are the PV driver interfaces
>>>>> even public?  I don't remember seeing them in the hyper-v spec, though
>>>>> I
>>>>> haven't read the latest version.
>>>> They were implicitly published, at least to some extent, in the form of
>>>> the big HyperV PV driver dump for Linux.  But I don't think those
>>>> drivers are very featureful yet, though they claim to be planning to
>>>> release more updates.
>>>>     J
>>>> _______________________________________________
>>>> Xen-users mailing list
>>>> Xen-users@xxxxxxxxxxxxxxxxxxx
>>>> http://lists.xensource.com/xen-users
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@xxxxxxxxxxxxxxxxxxx
>>> http://lists.xensource.com/xen-users

Xen-devel mailing list