All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bandan Das <bsd@redhat.com>
To: "ROZUMNY\, VICTOR" <vr9723@att.com>
Cc: "kvm\@vger.kernel.org" <kvm@vger.kernel.org>, "WEINSTEIN\,
	MICHAEL A" <mw8935@att.com>
Subject: Re: One off question: Hot vertical scaling of a KVM?
Date: Wed, 19 Aug 2015 14:48:08 -0700	[thread overview]
Message-ID: <jpgvbcbdk6f.fsf@linux.bootlegged.copy> (raw)
In-Reply-To: <029D7C716947D747B131EF6F51EA2F9217D4F4FD@GAALPA1MSGUSRAG.ITServices.sbc.com> (VICTOR ROZUMNY's message of "Wed, 19 Aug 2015 20:50:18 +0000")

"ROZUMNY, VICTOR" <vr9723@att.com> writes:

> Hello-
>
> Your site states that one off questions might could be answered via
> email so here I am.
>
> I have limited knowledge of KVM, but it is my understanding that in
> order to vertically scale RAM for a KVM the guest needs to be shut
> down, resized, and rebooted, resulting in a 5-10 minute interruption
> of service.
What's vertical scaling ? You mean, increase the amount of memory
the guest sees ? You could use Qemu memory hotplug I think but that
requires that the guest has been booted with enough number of
"dimm" slots.

Bandan

> Is this true and if so do you know of any efforts to change this
> behavior?
>
> Thank you!
>
> v.
>
> Vic Rozumny | Principal Technical Architect AIC - AT&T Integrated
> Cloud | Complex Engineering
>
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-08-19 21:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19 20:50 One off question: Hot vertical scaling of a KVM? ROZUMNY, VICTOR
2015-08-19 21:48 ` Bandan Das [this message]
2015-08-20 11:24   ` ROZUMNY, VICTOR

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=jpgvbcbdk6f.fsf@linux.bootlegged.copy \
    --to=bsd@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mw8935@att.com \
    --cc=vr9723@att.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 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.