<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><br></div><div>This is using an AIO configuration in a lab, no chance of a migration storm. I’m just looking for an easy way to move a VM around if I need to. 1GB ethernet is getting mighty slow these days, and any other shared storage is horribly expensive for a consultant’s home lab. 10GB NIC cards are becoming affordable, but the switches, not so much.</div><div><br></div><div><br></div><br><div><div>On Dec 21, 2014, at 5:12 AM, Nir Soffer <<a href="mailto:nsoffer@redhat.com">nsoffer@redhat.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;">]<br>Creating storage domain per vm is not a good idea.<br><br>The system is expecting all storage domain to be accessible by all hosts. So<br>if you have multiple storage domains and one become inaccessible, a host<br>may become non-operational, which will cause migration storm from this host<br>to other hosts. Basically, the more storage domains you have, your system<br>is more fragile.<br><br>Create new storage domains only when you must (e.g. separating testing and<br>production environments). For importing and exporting vms, you can use the<br>export domain.<br><br>Nir</div></blockquote></div><br></body></html>