public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Dor Laor <dor.laor@qumranet.com>
To: Rik Theys <Rik.Theys@esat.kuleuven.be>
Cc: kvm@vger.kernel.org
Subject: Re: best practices for kvm setup?
Date: Tue, 15 Jul 2008 10:54:54 +0300	[thread overview]
Message-ID: <487C57CE.6070903@qumranet.com> (raw)
In-Reply-To: <487C3AD0.3080402@esat.kuleuven.be>

Rik Theys wrote:
> Hi,
>
> I'm looking into virtualizing some of our servers onto two (or more) 
> physical nodes with either KVM or Xen. What are the 'best practices' 
> for running virtual _servers_ with KVM? Any good/bad experiences with 
> running KVM for virtual servers that have to run for months on end?
>
> I've installed ubuntu 8.04 because it should have KVM as the default 
> virtualization tool and is the only 'enterprise' distribution with kvm 
> right now. I used one host to act as an iSCSI target and installed 
> ubuntu with KVM on two other nodes. I can create a virtual server with 
> virt-manager, but it seems live migration is not (yet) supported by 
> libvirt/virsh? So how are other people running their KVM virtual 
> servers? Do you create a script for each virtual server and invoke kvm 
> directly? How do you do the live migration then? Launch the script 
> with an 'incoming' parameter on the target host, and run the migrate 
> command manually? 
If libvirt does not support migration than you'll need to automate it 
yourself, we use a daemon to exec/migrate VMs. AFAIK, except for 
libvirt* there is no other free tool for it.
> Or is there an other (automated) way? I once tried the live migration 
> on a test host and if I recall correctly, the kvm process kept on 
> running on the source host even after the server was migrated to the 
> target? Is that the expected behaviour?
>
This is works-as-designed, the idea is that a 3rd party mgmt tool get 
the result of the migration process and closes one of the 
source/destination. Without 3rd party, the destination cannot continue 
the source got end-of-migration message and the opposite on failure.

> What type of shared storage is best used with KVM (or Xen for that 
> matter)? Our physical servers will be connected to a SAN. Should I 
> create volumes on my san and export them to my physical servers where 
> I can then use them as /dev/by-id/xxx disk in my KVM configs? Of 
> should I configure my two servers into a GFS cluster and use files as 
> backend for my KVM virtual machines? What are you using as shared 
> storage?
>
We use NFS and it works pretty well, your proposals are also valid 
options. Just make sure an image is not accessed in parallel by 2 hosts.
> Regards,
>
> Rik
>
>
> Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
>
> -- 
> 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:[~2008-07-15  7:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-15  5:51 best practices for kvm setup? Rik Theys
2008-07-15  7:54 ` Dor Laor [this message]

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=487C57CE.6070903@qumranet.com \
    --to=dor.laor@qumranet.com \
    --cc=Rik.Theys@esat.kuleuven.be \
    --cc=kvm@vger.kernel.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