From: Mira Limbeck <m.limbeck@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [RFC qemu-server] api: create disks: avoid adding secondary cloud-init drives
Date: Mon, 4 Jul 2022 10:57:56 +0200 [thread overview]
Message-ID: <75071162-a918-df16-6fd2-3434bff42e39@proxmox.com> (raw)
In-Reply-To: <918c79831c6396b610b9bc302564f062f3566385.camel@groupe-cyllene.com>
On 5/16/22 13:04, DERUMIER, Alexandre wrote:
> Le vendredi 06 mai 2022 à 12:11 +0200, Fabian Ebner a écrit :
>> This will break possibly existing workflows like
>> 1. add second cloud-init
>> 2. remove first cloud-init
>> to change the cloud-init storage.
> Also, currently, in the gui, we can't add 2 cloud-init drives
> currently.
>
> But we could add an "move disk" like feature.
> generate current cloudinit config on a new drive and swap isos online.
> (If iso is mounted in the guest os, it's not a problem, as it's
> readonly, and the mountpoint content is updated too)
>
`Move Disk` while the VM is running, should not recreate the disk from
config as this could lead to a changed cloud-init disk.
Offline should be fine, but online `Move Disk` must re-use the current
cloud-init disk.
We had the same issue in the live migration case. We now offline migrate
the cloud-init disk and pass an argument during start on the target node
to skip generating the cloud-init disk as a workaround.
Live migration the same way all other disks are migrated doesn't work
here because the cloud-init disk is readonly mounted in QEMU.
next prev parent reply other threads:[~2022-07-04 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 10:11 Fabian Ebner
2022-05-16 8:32 ` DERUMIER, Alexandre
2022-07-04 8:54 ` Mira Limbeck
2022-05-16 11:04 ` DERUMIER, Alexandre
2022-07-04 8:57 ` Mira Limbeck [this message]
2022-07-04 7:44 ` Fabian Ebner
2022-09-12 16:06 ` [pve-devel] applied: " Thomas Lamprecht
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=75071162-a918-df16-6fd2-3434bff42e39@proxmox.com \
--to=m.limbeck@proxmox.com \
--cc=pve-devel@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