Dnia poniedziałek 17 sierpień 2009 o 21:03:12 Dave Allan napisał(a):
Łukasz Mierzwa wrote:
[...]
Let me make that little more clear:
1. Lets assume I have one storage node that is acting as a iscsi target.
2. This storage node has one big block device (RAID of some kind) that
will be used
? Are there better ways to *manage* volumes for virtual
machines using iscsi?
Thanks for any tips.
Łukasz Mierzwa
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
virtual machine with this volume
But can I create iscsi volume without pool?
Does it makes any sense? Are there better ways to *manage* volumes for virtual
machines using iscsi?
Thanks for any tips.
Łukasz Mierzwa
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman
2009/8/14 Dave Allan dal...@redhat.com
Łukasz Mierzwa wrote:
Hi Łukasz,
I will try to answer your questions inline.
Hi,
I'm trying to setup pool of machines (nodes) for virtual machines hosting
and I got few question about shared storage. My main requirements are:
1. central
2009/5/20 Chris Lalancette clala...@redhat.com
Łukasz Mierzwa wrote:
Dnia wtorek 19 maj 2009 o 22:20:06 Daniel P. Berrange napisał(a):
On Tue, May 19, 2009 at 09:29:15PM +0200, ??ukasz Mierzwa wrote:
Hi,
can someone explain me how migration works in libvirt? I got 2 machines
on target host before migration? Some info in 'virsh
help migrate' would be nice, and maybe '--persistent' option to auto-define it
on target before migration.
Thanks for help.
Łukasz Mierzwa
--
Libvir-list mailing list
Libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list
.
Does this strike anyone else as useful behavior?
Not only useful but a must have for me. Do You really want all Your virtual
machines to die when libvirtd dies? Not if You are doing anything serious.
Also this means that You can upgrade libvirt without stopping everything.
Łukasz Mierzwa
