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
you.
Andy
> (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
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home