From: Graeme Seaton <lists@graemes.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] Templates starting on backup
Date: Mon, 5 Oct 2020 15:21:08 +0100 [thread overview]
Message-ID: <5e238f85-d7b0-4cef-13d8-aa2e6012a61e@graemes.com> (raw)
In-Reply-To: <32fe64ea-90b4-abb4-85e9-324420e9776c@proxmox.com>
Hi,
In one case CPU type/Numa/hugepages. In others vmbr's.
Regards,
Graeme
On 05/10/2020 14:42, Thomas Lamprecht wrote:
> Hi,
>
> On 05.10.20 14:15, Graeme Seaton wrote:
>> I store my templates on a common host and move to deployment host as necessary. Unfortunately, when backup up the process tries to start the template and then fails if there is a difference in the hardware configuration between the current host and it's definition.
>>
>> Given that templates (if I understand correctly) are not run directly shouldn't the backup just work with the images since there won't be any dirty blocks to be detected?
>>
> Yes, they have no dirty bitmap by definition, but we start them up so that
> we can re-use our QEMU backup integration for PBS. The VM is not started for
> real, just a QEMU process is running - this shows up in the webinterface
> (because it's a cheap check) - but the backup lock symbol should avoid
> confusions.
>
> Re-using the QEMU built in block drivers to access the templates disks allows
> to avoid duplicating quite some logic and functionality, and solves a few
> edge cases "for free". That's the main reason we use it here.
>
>
> What HW differences are talking here?
>
> cheers,
> Thomas
>
>
next prev parent reply other threads:[~2020-10-05 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 12:15 Graeme Seaton
2020-10-05 13:42 ` Thomas Lamprecht
2020-10-05 14:21 ` Graeme Seaton [this message]
2020-10-05 14:40 ` Thomas Lamprecht
2020-10-05 16:49 ` Graeme Seaton
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=5e238f85-d7b0-4cef-13d8-aa2e6012a61e@graemes.com \
--to=lists@graemes.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=t.lamprecht@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