public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] virtualbox in headless configuration broken after update: delayed echo [ RESOLVED, kinda ]
Date: Wed, 17 Jun 2020 20:32:19 +0100	[thread overview]
Message-ID: <3481633.MHq7AAxBmi@lenovo.localdomain> (raw)
In-Reply-To: <10989A22-7F69-45C1-91F8-436EE296D60F@antarean.org>

[-- Attachment #1: Type: text/plain, Size: 1713 bytes --]

On Wednesday, 17 June 2020 18:31:42 BST J. Roeleveld wrote:
> On 17 June 2020 19:01:54 CEST, Michael <confabulate@kintzios.com> wrote:

> >https://wiki.qemu.org/Features/Snapshots2
> 
> Can you point to where in the commands above the memory anf cpu state is
> actually stored and loaded back when reverting to the snapshot? From what I
> see, it is only fhe disk image.
> I really need this feature for lab environments where I need the ability to
> fully roll back to a running instance.

I understand runtime parameters (inc. RAM, CPU cores, et al.) are also 
reflected in the snapshot and have seen this mentioned in the interwebs, but 
as I have not performed an online snapshot myself and therefore I can't 
confirm its validity.  :(

However, all I see in the previous link plus the two below is manipulation of 
VM images.

https://wiki.qemu.org/Features/Snapshots
https://wiki.qemu.org/Features/LiveBlockMigration


> >I've wanted to migrate a qemu qcow2 image file or two of different OS',
> >all
> >currently stored on an ext4 partition on my desktop, to a dedicated
> >partition
> >on the disk.  Would this be possible - how?  Would I need to change the
> >qcow2
> >to a raw image?
> 
> I don't know. One of the reasons I dislike file based images is the lack of
> transparency and tools. LVM is much simpler for disk based snapshots and
> management.
> 
> --
> Joost

I have found QEMU rather esoteric in its command range and options, which has 
changed over time;  with older commands deprecated (e.g. '-drive 
if=virtio,...' replaced with '-blockdev file,...'.  I'd like to migrate a 
Win10 VM to a disk partition, but would not want to mess this up, because I 
would hate to have to reinstall it.

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2020-06-17 19:32 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 [this message]
2020-06-17 19:55                   ` J. Roeleveld
2020-06-17 23:05                     ` Michael
2020-06-17 23:09                     ` William Kenworthy
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=3481633.MHq7AAxBmi@lenovo.localdomain \
    --to=confabulate@kintzios.com \
    --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