public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: carsteno-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: VM id in KVM?
Date: Mon, 23 Jul 2007 14:19:41 +0300	[thread overview]
Message-ID: <46A48ECD.7020809@qumranet.com> (raw)
In-Reply-To: <46A48E65.6090105-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

Avi Kivity wrote:
> Carsten Otte wrote:
>> Avi Kivity wrote:
>>>  From a Linux point of view, the pid identifies the VM.  A 
>>> management application can, however, use its own VM identifiers as 
>>> it sees fit, and map the (possibly persistent, gloablly unique, and 
>>> ridiculously long) VMID to the pid.
>> It might be preferable to have something that is persistent over 
>> guest migration. Makes life easier for the management application as 
>> far as I see.
>
> It may make sense to add a vmid to qemu (or to keep it in the 
> management application entirely).  Certainly the kernel doesn't need 
> to know about it.
>

I take it back.  The only entity that can enforce uniqueness is the 
management application, therefore that should be the entity that knows 
about them.

-- 
error compiling committee.c: too many arguments to function


-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

  parent reply	other threads:[~2007-07-23 11:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-23 10:40 VM id in KVM? Jun Koi
     [not found] ` <fdaac4d50707230340o7c2f42ecv7f22611a1e5267ee-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-07-23 11:05   ` Avi Kivity
     [not found]     ` <46A48B63.2030202-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-23 11:12       ` Carsten Otte
     [not found]         ` <46A48D0E.1040803-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-07-23 11:17           ` Avi Kivity
     [not found]             ` <46A48E65.6090105-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-23 11:19               ` Avi Kivity [this message]
     [not found]                 ` <46A48ECD.7020809-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-23 13:32                   ` Daniel P. Berrange
     [not found]                     ` <20070723133234.GA31631-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2007-07-23 13:39                       ` Avi Kivity
     [not found]                         ` <46A4AF95.2070306-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-23 13:45                           ` Daniel P. Berrange
2007-07-23 22:55                       ` Rusty Russell
     [not found]                         ` <1185231355.1803.22.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2007-07-24  1:44                           ` Jun Koi
2007-07-24  5:17                           ` Avi Kivity
     [not found]                             ` <46A58B52.9010405-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-24  5:59                               ` Rusty Russell
2007-07-23 11:35               ` Carsten Otte

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=46A48ECD.7020809@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=carsteno-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox