> > > > > If there is no backing file or snapshot you still need to fill
> > > > > the cluster with zeroes, and that's going to be slower with
> > > > > larger clusters.
> > > > If not fill zeroes and only write guest data ,what`s wrong could
> > > > happen ?
> > > The following could happen
Hi, Lukas,
Yeah, this version does works fine together with the old instructions!!!
Thanks very much for your help.
Thanks
shuang-shuan, guo
-- Original --
From: "Lukas Straub";
Date: Thu, Aug 23, 2018 03:16 AM
To: "shuang-shuan,guo";
Cc: "qemu-discuss";
S
Hi, what is the recommended way to control the initialization order of
nodes in the device tree (that is, encode dependencies)?
I am working with Xilinx fork of Qemu (circa v2.11), I didn't
check yet if the device tree parsing logic changed in master.
In the following text, visited != initialized
Hello,
Well the "best" version of COLO (that I know of) is
https://github.com/coloft/qemu/tree/colo-v5.1-developing-COLO-frame-v21-with-shared-disk
together with the old Instructions (see
https://wiki.qemu.org/index.php?title=Features/COLO&oldid=7150#Test_environment_prepare
for an older Version o
Currently WM_CLASS(STRING) is "qemu-system-x86_64".
I would like to change it to "qemu-XP", "qemu-W10",etc...
I success to chane -name qemu-XP but it doe not change the WM_CLASS...
Thanks for any help..
PC
Thank you, Fam.
I did the following, and this time QEMU doesn't complain anything.
But what's the semantics of omitting the "bitmap" parameters?
And, how to continue with incremental backups after that?
If I repeat the snippet below, there will be error message:
{"id":"libvirt-381290","error":{"c
On Wed, Aug 22, 2018 at 11:41 PM David Lee wrote:
> If I repeat the snippet below, there will be error message:
> {"id":"libvirt-381290","error":{"class":"GenericError","desc":"Need a
> root block node"}}
>
> What's happening?
I guess it is because the previous backup jobs were still in progress.
On Wed, 08/22 22:20, David Lee wrote:
> Hi, list
>
> I was trying "drive-backup" for incremental backups, and so far so
> good for individual drives.
> The question is that, when I grouped the drive-backup into a
> transaction, I got errors like:
>
> {"id":"libvirt-377183","error":{"class":"Gener
Hi, list
I was trying "drive-backup" for incremental backups, and so far so
good for individual drives.
The question is that, when I grouped the drive-backup into a
transaction, I got errors like:
{"id":"libvirt-377183","error":{"class":"GenericError","desc":"a
sync_bitmap was provided to backup_
On Wed, Aug 22, 2018 at 8:05 AM Peter Hull wrote:
>
Further information: with odin1440 (which is just text mode), if I use
'-display curses' or '-display sdl' the mapping is also incorrect but
if I use '-display curses -k en_us' it is correct, or very nearly so.
On Sat, 11 Aug 2018 19:39:56 +0200
Oleksandr Natalenko wrote:
> Hi.
>
> On 11.08.2018 14:23, Ming Lei wrote:
> > Please test for-4.19/block:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git/log/?h=for-4.19/block
> >
> > This slow boot issue should have been fixed b
I am talking about a text-based guest console with (possibly) a muxed
monitor console (aka qemu console).
If I understood correctly, the former can only be got with -display
curses and only when qemu is running on the foreground to attach the
current pseudo-tty and nothing else: no pipes and no so
Hi All,
I have a Dell laptop with a UK keyboard running Windows 10 64-bit and
QEMU 3.0.0.
Some of the keys do not seem to be mapped correctly in the guest.
Specifically, on my keyboard, between L and the return key I have keys
labelled ; (semicolon) ' (single quote) and # (hash). When I press
them,
13 matches
Mail list logo
