# Best practice disk setup in enterprise environments

**URL:** <https://forums.suse.com/t/best-practice-disk-setup-in-enterprise-environments/27497>\
**Category:** SLES Install-Boot\
**Created:** [October 6, 2015, 9:44pm UTC](https://forums.suse.com/t/best-practice-disk-setup-in-enterprise-environments/27497 "2015-10-06T21:44:59Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![System1](https://avatars.discourse-cdn.com/v4/letter/s/51bf81/32.png) [@System1](https://forums.suse.com/u/System1)\
**Post date:** [October 6, 2015, 9:44pm UTC](https://forums.suse.com/t/best-practice-disk-setup-in-enterprise-environments/27497/1 "2015-10-06T21:44:59Z")

</div>

I’m looking for pointers about best-practice for disk setup of SLES  
as a virtual guest on basically any hypervisor, though primarily  
VMware/KVM/XEN in x86\_64 enterprise environments.  
Mainly I’m hoping for guidance on how to treat /boot and being able  
to use LVM for all filesystems while still be able to resize these  
online without having to cope with partitions.  
The best would be if it had been possible to just create everything  
as logical volumes on the first disk directly without having to  
create any partition. But then there’s the problem of booting off an  
LVM. AFAICT that’s still not supported.  
This is just for the root disk, the data disks are treated as plain  
LVM PV’s with no partition created as that gives the best ability  
to resize online overtime as data grows.

Thanks for your thoughts

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/5/5012ba89e3ffb5220dac47d5ea0ba032e2fe1cb6.png) [@system](https://forums.suse.com/u/system)\
**Post date:** [October 12, 2015, 7:30am UTC](https://forums.suse.com/t/best-practice-disk-setup-in-enterprise-environments/27497/2 "2015-10-12T07:30:17Z")

</div>

John,

It appears that in the past few days you have not received a response to your  
posting. That concerns us, and has triggered this automated reply.

Has your issue been resolved? If not, you might try one of the following options:

- Visit [http://www.suse.com/support](http://www.suse.com/support) and search the knowledgebase and/or check all  
the other support options available.
- You could also try posting your message again. Make sure it is posted in the  
correct newsgroup. ([http://forums.suse.com](http://forums.suse.com))

Be sure to read the forum FAQ about what to expect in the way of responses:  
[http://forums.suse.com/faq.php](http://forums.suse.com/faq.php)

If this is a reply to a duplicate posting, please ignore and accept our apologies  
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your SUSE Forums Team  
[http://forums.suse.com](http://forums.suse.com)

---

<div class="post-metadata">

**Author:** ![Jens-U](https://avatars.discourse-cdn.com/v4/letter/j/d78d45/32.png) [@Jens-U](https://forums.suse.com/u/Jens-U)\
**Post date:** [October 12, 2015, 1:56pm UTC](https://forums.suse.com/t/best-practice-disk-setup-in-enterprise-environments/27497/3 "2015-10-12T13:56:48Z")

</div>

Hi,

I typically set up my VMs with a 500MB partition for /boot and the remainder for LVM.

From trouble with (much) earlier versions I decided to configure LVM on the host machine to consider only explicitly defined PVs (had some Dom0/DomU VG name clashes that lead to nasty results), so activating the guest VG during pygrub handling wouldn’t work here anyhow. Using that dedicated /boot partition isn’t much of a hassle, so I’d say it’s worth it.

Regards,  
Jens