<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="http://dev1galaxy.org/extern.php?action=feed&amp;tid=6182&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / [SOLVED] Creating a VM using GPT partitions]]></title>
		<link>http://dev1galaxy.org/viewtopic.php?id=6182</link>
		<description><![CDATA[The most recent posts in [SOLVED] Creating a VM using GPT partitions.]]></description>
		<lastBuildDate>Tue, 28 Nov 2023 20:01:03 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: [SOLVED] Creating a VM using GPT partitions]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=45738#p45738</link>
			<description><![CDATA[<p>Thanks for that! If I decide to even do this I might try that.</p><p>You&#039;re correct that this really isn&#039;t really an issue. When a customer of ours ends up needing that much space we have them add a new disk and just add it to our LVM logical volume as a raw disk with no partitions at all. We did however have one customer that increased the existing disk to well over 2 TB which we were not able to fully use due to the DOS partitions, and VM doesn&#039;t let you get it back.</p><p>I was hoping to avoid that but I&#039;m starting to think it&#039;s not worth it...especially if it gets into changing stuff to use EFI etc. That could even end up causing worse issues.</p><p>Thanks again!<br />Tom</p>]]></description>
			<author><![CDATA[dummy@example.com (tlathm)]]></author>
			<pubDate>Tue, 28 Nov 2023 20:01:03 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=45738#p45738</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Creating a VM using GPT partitions]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=45732#p45732</link>
			<description><![CDATA[<p>On virtual hardware, you would boot from a virtual optical disk by attaching a bootable iso file (probably a live-iso). Then you could do whatever you need to do to the virtual hard disk. That&#039;s how it works with virtualbox and qemu. I haven&#039;t used vmware since debian etch, but I assume it will let you do the same.</p><p>I think you&#039;re worrying about a non-existent problem. If you ever need more than 2T of space, you could just attach a larger virtual disk and move part of the filesystem onto it. You don&#039;t need 2T for the operating system.</p>]]></description>
			<author><![CDATA[dummy@example.com (fsmithred)]]></author>
			<pubDate>Tue, 28 Nov 2023 19:18:14 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=45732#p45732</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Creating a VM using GPT partitions]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=45730#p45730</link>
			<description><![CDATA[<p>Actually that gets into several things that get very confusing about all this.</p><p>For example, if I&#039;m creating a new VM that I plan on installing Devuan, I&#039;m actually unclear as to how I even could partition it ahead of time. On real hardware I&#039;d just boot from some removable drive, mount the disk, and format it. I have no idea how to do that in this case.</p><p>Things get even more confusing regarding the boot. I&#039;m unclear as to what VM even does for a new VM regarding legacy BIOS boot vs EFI. Maybe there are some options there though I don&#039;t recall any. Very confusing.</p><p>I may just try the approach in that link and see if it works.</p><p>Tom</p>]]></description>
			<author><![CDATA[dummy@example.com (tlathm)]]></author>
			<pubDate>Tue, 28 Nov 2023 18:49:52 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=45730#p45730</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Creating a VM using GPT partitions]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=45728#p45728</link>
			<description><![CDATA[<p>I can&#039;t check that, but I can suggest that you partition the disk manually as gpt using gdisk or gparted. Then when you run the installer, you can select the partitions you created.</p><p>If you use gpt with legacy bios boot, you need a special partition, at least 1MB size, with no filesystem on it (&quot;unformatted&quot; in gparted) and with a flag of ef02 (in gdisk) or bios_grub (in gparted).</p>]]></description>
			<author><![CDATA[dummy@example.com (fsmithred)]]></author>
			<pubDate>Tue, 28 Nov 2023 17:41:32 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=45728#p45728</guid>
		</item>
		<item>
			<title><![CDATA[[SOLVED] Creating a VM using GPT partitions]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=45727#p45727</link>
			<description><![CDATA[<p>I&#039;m looking to create a VM using VMware workstation player that initially will have a 250 GB disk, but I&#039;d like to force it to use GPT partitions. The reason is that there can be cases where at some point there&#039;s a need to increase a partition to more than 2 TB. From what I&#039;ve read I don&#039;t think that GPT partitions would get used in that case by default(?).</p><p>I found an interesting post related to Debian here:</p><p><a href="https://unix.stackexchange.com/questions/518377/where-does-the-debian-installer-choose-mbr-vs-gpt" rel="nofollow">https://unix.stackexchange.com/question … mbr-vs-gpt</a></p><p>That is, to add this to the end of the boot command line:</p><div class="codebox"><pre><code>d-i:partman-partitioning/default_label=gpt</code></pre></div><p>Can anyone confirm whether or not that works, and most importantly, if the resulting install would actually boot correctly?</p><p>Thanks in advance!<br />Tom</p>]]></description>
			<author><![CDATA[dummy@example.com (tlathm)]]></author>
			<pubDate>Tue, 28 Nov 2023 16:13:01 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=45727#p45727</guid>
		</item>
	</channel>
</rss>
