From: Fabian Ebner <f.ebner@proxmox.com>
To: pve-user@lists.proxmox.com
Subject: Re: [PVE-User] Conversion LXC -> VM, mountpoint to volume?
Date: Wed, 27 Oct 2021 09:21:02 +0200 [thread overview]
Message-ID: <20397418-36a4-4361-9f2a-8cbc71c7684c@proxmox.com> (raw)
In-Reply-To: <8gol4i-t141.ln1@hermione.lilliput.linux.it>
Hi,
I don't think that's possible without moving the data. The LXC
mountpoint is a ZFS file system, but for a VM you need a ZFS volume,
which is a virtual block device, so renaming won't work.
Am 26.10.21 um 18:55 schrieb Marco Gaiarin:
>
> In my home server i've an LXC container with an additional mountpoint, that
> contain a lot of data (1.5TB).
>
> I need to convert the LXC to a VM; there's no trouble to reinstall the base
> machine, but if possible i don't want to 'move' 1.5TB of data...
>
>
> Can i simply (a rename suffices? I'm using ZFS as storage) convert an LXC
> mountpoint to an VM (additional) volume?
>
>
> Thanks.
>
next prev parent reply other threads:[~2021-10-27 7:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 16:55 Marco Gaiarin
2021-10-27 7:21 ` Fabian Ebner [this message]
2021-10-29 10:32 ` Marco Gaiarin
2021-10-28 8:04 ` devzero
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20397418-36a4-4361-9f2a-8cbc71c7684c@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox