> such as swap on ramdisk if you're running a kernel that murders itself when it has no swap. Thanks for that reminder. I forget how practical that is at times. I agree with throwing ram and trimming swap space down. On windows they want a huge swap so the system can dump. I think the last time I cared to spend the time to trouble shoot a windows machine via a dump was over 12 years ago. Maybe more. Is a lot cheaper and quicker to just start rebuilding most of the time. Christopher G. Stach II wrote: > ----- "Adam" <adam0x54 at gmail.com> wrote: > >> There is no need for a second img to use as swap right? > > Rereading your original message got me to wondering whether the examples you saw were putting swap on local storage and the filesystems on remote storage. You can do that for swap performance, but then you can't migrate VMs with the stock tools. It's better to just allocate a decent swap space, store it over the network, and avoid using swap (allocate more RAM, turn down swappiness, etc.) You can also just not use a disk for swap space, such as swap on ramdisk if you're running a kernel that murders itself when it has no swap. >