From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] virtualbox in headless configuration broken after update: delayed echo [ RESOLVED, kinda ]
Date: Thu, 18 Jun 2020 07:09:45 +0800 [thread overview]
Message-ID: <99c8a40a-19b9-1837-85a9-4e405abfc8ad@iinet.net.au> (raw)
In-Reply-To: <F67226EA-6496-491A-892C-8BCAF977B29B@antarean.org>
On 18/6/20 3:55 am, J. Roeleveld wrote:
> On 17 June 2020 21:32:19 CEST, Michael <confabulate@kintzios.com> wrote:
>> On Wednesday, 17 June 2020 18:31:42 BST J. Roeleveld wrote:
>>> On 17 June 2020 19:01:54 CEST, Michael <confabulate@kintzios.com>
>
> This brings another problem I have with KVM/QEMU: all howtos and documents I find show long commandline options to just start the VM.
> I have not found one where I can provide all the config in a single file and use that. Allowing me to duplicate settings by simply copying the file and changing a few lines.
>
> KVM/Qemu seems to be written to be used together with virt-manager which, for me, lacks important features to make it usable in production.
>
> --
> Joost
>
>
Until a few months ago I was using Qemu/KVM/VirtManager with snapshots
for linux and Windows VM's running network services - the trick is
redundancy and suspend.
Using libvirt, suspend the VM which copies ram to disk, then snapshot
((I used btrfs) both the ram and storage and restart the VM - takes
seconds (so redundancy may be needed) - at this point I backup'ed the
snapshot and deleted it.
When using snapshots of live systems, I had problems restoring some of
the more active VM's which this avoids.
BillK
next prev parent reply other threads:[~2020-06-17 23:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 13:19 [gentoo-user] virtualbox in headless configuration broken after update: delayed echo n952162
2020-06-16 19:07 ` [gentoo-user] virtualbox in headless configuration broken after update: delayed echo [ RESOLVED, kinda ] n952162
2020-06-16 20:36 ` J. Roeleveld
2020-06-16 21:08 ` n952162
2020-06-17 4:48 ` J. Roeleveld
2020-06-17 5:42 ` n952162
2020-06-17 6:32 ` J. Roeleveld
2020-06-17 17:01 ` Michael
2020-06-17 17:31 ` J. Roeleveld
2020-06-17 19:32 ` Michael
2020-06-17 19:55 ` J. Roeleveld
2020-06-17 23:05 ` Michael
2020-06-17 23:09 ` William Kenworthy [this message]
2020-06-18 9:21 ` Michael
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=99c8a40a-19b9-1837-85a9-4e405abfc8ad@iinet.net.au \
--to=billk@iinet.net.au \
--cc=gentoo-user@lists.gentoo.org \
/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