From: James Sparenberg <James.Sparenberg@vudu.com>
To: unlisted-recipients:; (no To-header on input)
Cc: libvirt-users <libvirt-users@redhat.com>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [libvirt-users] Questions on how to reset ID numbers for virt Guests.
Date: Wed, 11 Sep 2013 18:32:00 +0000 [thread overview]
Message-ID: <5230B720.7080309@vudu.com> (raw)
In-Reply-To: <20130911075944.GA23194@redhat.com>
Ok. and trust me right now it feels like my experiments will hit the wrap number ;). As for the other part. Thanks, now when my boss takes a look and panics I've got an answer. ;) I really appreciate the help.
James Sparenberg
Sys Admin III Linux
Vudu Inc a Walmart Company
On 09/11/2013 12:59 AM, Daniel P. Berrange wrote:
On Wed, Sep 11, 2013 at 09:47:07AM +0200, Paolo Bonzini wrote:
Il 11/09/2013 00:27, James Sparenberg ha scritto:
I'm doing some experimenting in our Development lab and as a result
I'm kickstarting over and over Virtual guests. This is of course
causing the guest Id to increment by one with each test. I've
googled around and tried searching the list but have not found out
how (if at all) it would be possible to reset the ID number back to 1
more than is in use. Also is there a limit where I run out of ID's?
(for example does it only go up to 99?)
No, there is no limit.
Well, 'int' will wrap eventually, but you'd need to have created
a hell of alot of guests for that to be a problem :-)
I don't know the answer to your other question, so I'm adding the
libvirt-users mailing list.
If you restart libvirtd, it reset itself to start allocating IDs
at the max current used ID of any running guest.
Daniel
next prev parent reply other threads:[~2013-09-11 18:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 22:27 Questions on how to reset ID numbers for virt Guests James Sparenberg
2013-09-11 7:47 ` Paolo Bonzini
2013-09-11 7:59 ` [libvirt-users] " Daniel P. Berrange
2013-09-11 18:32 ` James Sparenberg [this message]
2013-09-11 18:40 ` Eric Blake
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=5230B720.7080309@vudu.com \
--to=james.sparenberg@vudu.com \
--cc=kvm@vger.kernel.org \
--cc=libvirt-users@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).