From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: VM id in KVM? Date: Mon, 23 Jul 2007 14:17:57 +0300 Message-ID: <46A48E65.6090105@qumranet.com> References: <46A48B63.2030202@qumranet.com> <46A48D0E.1040803@de.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel To: carsteno-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org Return-path: In-Reply-To: <46A48D0E.1040803-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org 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. -- 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/