All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: "François Revol" <revol@free.fr>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] wake-on-lan & IPMI implementation; real power-off and -no-shutdown
Date: Mon, 15 Mar 2010 10:51:30 -0500	[thread overview]
Message-ID: <4B9E5782.9070901@codemonkey.ws> (raw)
In-Reply-To: <4548325200-BeMail@laptop>

On 03/15/2010 10:37 AM, François Revol wrote:
> Le Mon, 15 Mar 2010 15:26:24 +0000, Paul Brook a écrit :
>    
>>> Ideally this would evolve into supporting IPMI, which would allow
>>> managing VMs exactly like physical servers without concern, appart
>>> launching the actual process first.
>>> cf.
>>> http://en.wikipedia.org/wiki/Intelligent_Platform_Management_Interface
>>>        
>>>>> http://openipmi.sourceforge.net/
>>>>>            
>>> Anyone interested in this ?
>>> Anyone tried already ?
>>>        
>> TBH I don't really see the point.
>>
>> This definitely seems like something that should be handled by your
>> your
>> mangement app (via libvirt, or whatever). i.e. have that implement
>> whatever
>> remote protocol you want, and just talk to qemu over the normal
>> monitor
>> interface.
>>      
> Hmm for IPMI that might probably indeed be a better way, moreover since
> they use a parallel subnet on the primary ethernet card...
> Though it would require the implementation to listen to the same
> virtual card, which are mapped differently to the host depending on the
> VM (-net user, ...).
>
> As for WOL, it would still be handy to have I think... btw, do we
> support suspending the emulation via ACPI ? VirtualBox has something
> called "Pause" mode, which I'm not sure actually if it's reflected to
> ACPI, which allows to avoid wasting cpu when not usign the guest,
> though it requires support from the Guest Additions to avoid clock
> drifts.
>    

It's just "stop".

It won't cause time drift in qemu when using pvclock but you will get 
soft lockups in Linux.  I presume you get that with Virtual Box too.

Regards,

Anthony Liguori

> François.
>
>
>    

  reply	other threads:[~2010-03-15 15:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 15:01 [Qemu-devel] wake-on-lan & IPMI implementation; real power-off and -no-shutdown François Revol
2010-03-15 15:26 ` Paul Brook
2010-03-15 15:37   ` François Revol
2010-03-15 15:51     ` Anthony Liguori [this message]
2010-03-15 16:00       ` François Revol
2010-03-15 15:55 ` Daniel P. Berrange
2010-03-15 16:29   ` Anthony Liguori
2010-03-15 16:36     ` François Revol
2010-03-16 17:28     ` Jamie Lokier
2010-03-16 17:44       ` Daniel P. Berrange
2010-03-16 18:22       ` François Revol
2010-03-16 13:53   ` Luiz Capitulino
2010-03-16 14:26     ` François Revol

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B9E5782.9070901@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=qemu-devel@nongnu.org \
    --cc=revol@free.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.