From: "Daniel P. Berrange" <berrange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: carsteno-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org,
kvm-devel
<kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: VM id in KVM?
Date: Mon, 23 Jul 2007 14:45:04 +0100 [thread overview]
Message-ID: <20070723134504.GB31631@redhat.com> (raw)
In-Reply-To: <46A4AF95.2070306-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
On Mon, Jul 23, 2007 at 04:39:33PM +0300, Avi Kivity wrote:
> Daniel P. Berrange wrote:
> >When managing QEMU & KVM guests, libvirt provides 3 identifiers with
> >varying levels of uniqueness
> >
> > - ID - a integer unique amongst all active guests on a host
> > - Name - a string uninque amongst all active & inactive guests on a host
> > - UUID - 32 byte hex string unique globally
>
> Does libvirt also provide a lighter-weight interface that doesn't know
> about names and uuids? I imagine a cluster-wide management solutions
> will want to keep all configuration in a central database and just tell
> libvirt "start a guest with this configuration".
Name is mandatory, if you omit the UUID it will generate one for its own
internal tracking purposes. You can also create a guest without having to
pre-define a config file - it will disappear with no trace once the guest
is shutdown.
Regards,
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
-------------------------------------------------------------------------
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/
next prev parent reply other threads:[~2007-07-23 13:45 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
[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 [this message]
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=20070723134504.GB31631@redhat.com \
--to=berrange-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=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