Hi Mark,
Thanks a lot for this. - it did work!
So, now im wondering how did you install the iso on disk?
would you mind sharing your command line for the install please? and hacks if
any
i am now able to install and boot, but my boot hang after this line "[
22.559491] [TTM] Initializing po
Hello,
I noted a call for NetBSD maintainers in the 2.9.0 release notes.
I'm willing to attach a NetBSD machine to CI cluster and volunteer basic
maintenance. I'm mostly interested in NetBSD as host & as guest as this
is my daily and work driver on my desktop and development machines.
If I under
On Sat, Apr 22, 2017 at 08:05:41PM +0100, Peter Maydell wrote:
> On 22 April 2017 at 19:46, Krzysztof Kozlowski wrote:
> > On Thu, Apr 20, 2017 at 02:51:00PM +0100, Peter Maydell wrote:
> >> Incidentally someday maybe we should convert this Exynos4210 code
> >> to a proper QOM SoC container object
Exynos4210 has four SD/MMC controllers supporting:
- SD Standard Host Specification Version 2.0,
- MMC Specification Version 4.3,
- SDIO Card Specification Version 2.0,
- DMA and ADMA.
Add emulation of SDHCI devices which allows accessing storage through SD
cards. Differences from real hardwar
On 22 April 2017 at 19:46, Krzysztof Kozlowski wrote:
> On Thu, Apr 20, 2017 at 02:51:00PM +0100, Peter Maydell wrote:
>> Incidentally someday maybe we should convert this Exynos4210 code
>> to a proper QOM SoC container object, but that would be a lot of
>> work.
>
> Any existing platforms which
On Thu, Apr 20, 2017 at 02:51:00PM +0100, Peter Maydell wrote:
> On 16 April 2017 at 16:16, Krzysztof Kozlowski wrote:
> > Exynos4210 has four SD/MMC controllers supporting:
> > - SD Standard Host Specification Version 2.0,
> > - MMC Specification Version 4.3,
> > - SDIO Card Specification Vers
08.03.2017 18:15, Eric Blake wrote:
> Ignore test executables when building in-tree:
> test-arm-mptimer introduced in commit 882fac3
> test-crypto-hmac introduced in commit 4fd460b
> test-aio-multithread introduced in commit 0c330a7
Applied to -trivial, thank you!
/mjt
17.03.2017 18:49, Craig Jellick wrote:
> qemu-options.hx | 2 +-
Applied to -trivial, thank you!
/mjt
22.03.2017 14:52, Marc-André Lureau wrote:
> include/io/channel.h | 2 +-
Applied to -trivial, thanks!
/mjt
On 21.04.2017 23:09, Eric Blake wrote:
> On 04/06/2017 11:40 AM, Eric Blake wrote:
>
>>> === Changes to the on-disk format ===
>>>
>>> The qcow2 on-disk format needs to change so each L2 entry has a bitmap
>>> indicating the allocation status of each subcluster. There are three
>>> possible states
24.03.2017 15:55, fred.kon...@greensocs.com wrote:
> From: KONRAD Frederic
>
> The tb_env variable is set two lines above. So just drop the double
> assignment.
Applied to -trivial, thanks!
/mjt
On 2017-04-21 17:18, BALATON Zoltan wrote:
> v7: Define default values for some variables to avoid an (invalid)
> warning from gcc 6 or 7 as suggested by Aurelien Jarno.
Thanks a lot for this new version, I confirm it now builds fine with GCC
6 or 7.
--
Aurelien Jarno
On 21.04.2017 10:01, Kevin Wolf wrote:
> It is unused.
>
> Suggestetd-by: Fam Zheng
*Suggested
And, since it now would be rude not to, with that fixed:
Reviewed-by: Max Reitz
> Signed-off-by: Kevin Wolf
> ---
> tests/qemu-iotests/common.config | 18 --
> 1 file changed, 18
Public bug reported:
Using the Tianocore OVMF UEFI firmware, a UEFI application cannot write
to the emulated fat disk (-hda fat:rw:path/here). A file will get
created or written, but will be corrupted.
** Affects: qemu
Importance: Undecided
Status: New
--
You received this bug not
On 22.04.2017 00:34, Ping Li wrote:
> Currently, qemu-img 'amend' subcommand would fail to adjust image's backing
> file
> which was moved into different path.
> For example, parent.qcow2, the backing file of leaf.qcow2, first is at
> /home/a/,
> then moved into /home/b/. Originally this command,
On 21.04.2017 17:51, Stefan Hajnoczi wrote:
> On Sat, Apr 01, 2017 at 05:57:47PM +0200, Max Reitz wrote:
>> The issues of using C are well understood and nobody likes it. Let's use
>> a better language. C++ is not a better language, Rust is. Everybody
>> loves Rust. Rust is good. Rust is hip. It wi
On 04/22/2017 12:09 PM, Stafford Horne wrote:
I discussed a bit on #qemu and Alexander Graf suggested to properly define
shutdown semantics for openrisc. Some examples were shown from ppc, s390
and arm.
Yes, properly defining this in the spec goes a long way toward fixing the
underlying proble
Stefan Weil, on ven. 21 avril 2017 21:58:18 +0200, wrote:
> Am 17.04.2017 um 00:10 schrieb FONNEMANN Mark:
> > I hadn't seen the original report on the list, sorry. There is too much
> > traffic on qemu-devel for me to manage to catch these :/
> >
> > This problem was fixed by
> > e42f869b ("slir
On Tue, Apr 18, 2017 at 11:20:55PM +0900, Stafford Horne wrote:
> On Tue, Apr 18, 2017 at 12:52:52AM -0700, Richard Henderson wrote:
> > On 04/16/2017 04:23 PM, Stafford Horne wrote:
> > > In openrisc simulators we use hooks like 'l.nop 1' to cause the
> > > simulator to exit. Implement that for q
Hello David,
this mail just for CPUMASK discussion.
On Fri, Apr 21, 2017 at 01:00:32PM +0100, Dr. David Alan Gilbert wrote:
> * Alexey Perevalov (a.pereva...@samsung.com) wrote:
> > This patch provides downtime calculation per vCPU,
> > as a summary and as a overlapped value for all vCPUs.
> >
>
Hi,
I think the bellow patch can fix your problme.
[PATCH 2/4] qmp-cont: invalidate on RUN_STATE_PRELAUNCH
https://patchwork.kernel.org/patch/9591885/
Actually, we encounter the same problem in our test, we fix it with the follow
patch:
From 0e4d6d706afd9909b5fd71536b45c58af60892f8 Mon Se
On 21/04/17 16:12, Ajallooiean Hossein wrote:
> Thanks for the files and the notes.
>
> I am attaching my config-host file for you. I'm on x86_64, running Linux 64,
> Ubuntu 16.04.2 LTS
>
> so, i can also boot like you do - this worked before as well. btw, if you try
> to install that to a dis
After one round of checkpoint, the states between PVM and SVM
become consistent, so it is unnecessary to adjust the sequence
of net packets for old connections, besides, while failover
happens, filter-rewriter needs to check if it still needs to
adjust sequence of net packets.
Cc: Jason Wang
Sign
I have seen a bunch of reports about this assertion error (on source
QEMU). [At least I recall Greg Kurz mentioning this a week or so ago on
#qemu, OFTC.]
I just noticed this crash in upstream OpenStack CI environment. This
seems to occur (only intermittently, though) during live migration
witho
Filter needs to process the event of checkpoint/failover or
other event passed by COLO frame.
Cc: Jason Wang
Signed-off-by: zhanghailiang
---
include/net/filter.h | 5 +
net/filter.c | 16
net/net.c| 28
3 files changed, 49
During the time of VM's running, PVM may dirty some pages, we will transfer
PVM's dirty pages to SVM and store them into SVM's RAM cache at next checkpoint
time. So, the content of SVM's RAM cache will always be same with PVM's memory
after checkpoint.
Instead of flushing all content of PVM's RAM
Don't need to flush all VM's ram from cache, only
flush the dirty pages since last checkpoint
Cc: Juan Quintela
Signed-off-by: Li Zhijian
Signed-off-by: Zhang Chen
Signed-off-by: zhanghailiang
---
v2:
- stop dirty log after exit from COLO state. (Dave)
---
migration/ram.c | 12
If some errors happen during VM's COLO FT stage, it's important to
notify the users of this event. Together with 'x_colo_lost_heartbeat',
Users can intervene in COLO's failover work immediately.
If users don't want to get involved in COLO's failover verdict,
it is still necessary to notify users th
Make sure master start block replication after slave's block
replication started.
Besides, we need to activate VM's blocks before goes into
COLO state.
Signed-off-by: zhanghailiang
Signed-off-by: Li Zhijian
Cc: Stefan Hajnoczi
Cc: Kevin Wolf
Cc: Max Reitz
Cc: Xie Changlong
---
migration/co
While do checkpoint, we need to flush all the unhandled packets,
By using the filter notifier mechanism, we can easily to notify
every compare object to do this process, which runs inside
of compare threads as a coroutine.
Cc: Jason Wang
Signed-off-by: zhanghailiang
Signed-off-by: Zhang Chen
--
We should not load PVM's state directly into SVM, because there maybe some
errors happen when SVM is receving data, which will break SVM.
We need to ensure receving all data before load the state into SVM. We use
an extra memory to cache these data (PVM's ram). The ram cache in secondary side
is i
Notify all net filters about the checkpoint and failover event.
Cc: Jason Wang
Signed-off-by: zhanghailiang
---
migration/colo.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/migration/colo.c b/migration/colo.c
index 66bb5b2..62f58c6 100644
--- a/migration/colo.c
+++ b/migr
We record the address of the dirty pages that received,
it will help flushing pages that cached into SVM.
Here, it is a trick, we record dirty pages by re-using migration
dirty bitmap. In the later patch, we will start the dirty log
for SVM, just like migration, in this way, we can record both
the
Hi,
(Sorry, I have misspelled Dave's email address, resend this series.)
COLO Frame, block replication and COLO net compare have been exist in qemu
for long time, it's time to integrate these three parts to make COLO really
works.
In this series, we have some optimizations for COLO frame, inclu
For COLO FT, both the PVM and SVM run at the same time,
only sync the state while it needs.
So here, let SVM runs while not doing checkpoint, change
DEFAULT_MIGRATE_X_CHECKPOINT_DELAY to 200*100.
Besides, we forgot to release colo_checkpoint_semd and
colo_delay_timer, fix them here.
Cc: Jason Wa
It's a good idea to use notifier to notify COLO frame of
inconsistent packets comparing.
Cc: Jason Wang
Signed-off-by: Zhang Chen
Signed-off-by: zhanghailiang
---
net/colo-compare.c | 32
net/colo-compare.h | 2 ++
2 files changed, 30 insertions(+), 4 deletion
It's a good idea to use notifier to notify COLO frame of
inconsistent packets comparing.
Cc: Jason Wang
Signed-off-by: Zhang Chen
Signed-off-by: zhanghailiang
---
net/colo-compare.c | 32
net/colo-compare.h | 2 ++
2 files changed, 30 insertions(+), 4 deletion
If VM is in COLO FT state, we need to do some extra works before
starting normal shutdown process.
Secondary VM will ignore the shutdown command if users issue it directly
to Secondary VM. COLO will capture shutdown command and after
shutdown request from user.
Cc: Paolo Bonzini
Signed-off-by: z
It is unnecessary to call qemu_savevm_state_begin() in every checkpoint process.
It mainly sets up devices and does the first device state pass. These data will
not change during the later checkpoint process. So, we split it out of
colo_do_checkpoint_transaction(), in this way, we can reduce these
There are several stages during loadvm/savevm process. In different stage,
migration incoming processes different types of sections.
We want to control these stages more accuracy, it will benefit COLO
performance, we don't have to save type of QEMU_VM_SECTION_START
sections everytime while do check
If some errors happen during VM's COLO FT stage, it's important to
notify the users of this event. Together with 'x_colo_lost_heartbeat',
Users can intervene in COLO's failover work immediately.
If users don't want to get involved in COLO's failover verdict,
it is still necessary to notify users th
Notify all net filters about the checkpoint and failover event.
Cc: Jason Wang
Signed-off-by: zhanghailiang
---
migration/colo.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/migration/colo.c b/migration/colo.c
index 66bb5b2..62f58c6 100644
--- a/migration/colo.c
+++ b/migr
COLO's checkpoint process is based on migration process,
everytime we do checkpoint we will repeat the process of savevm and loadvm.
So we will call qemu_loadvm_section_start_full() repeatedly, It will
add all migration sections information into loadvm_handlers list everytime,
which will lead to m
We separate the process of saving/loading ram and device state when do
checkpoint. We add new helpers for save/load ram/device. With this change,
we can directly transfer RAM from primary side to secondary side without
using channel-buffer as assistant, which also reduce the size of extra memory
wa
Filter needs to process the event of checkpoint/failover or
other event passed by COLO frame.
Cc: Jason Wang
Signed-off-by: zhanghailiang
---
include/net/filter.h | 5 +
net/filter.c | 16
net/net.c| 28
3 files changed, 49
We should not load PVM's state directly into SVM, because there maybe some
errors happen when SVM is receving data, which will break SVM.
We need to ensure receving all data before load the state into SVM. We use
an extra memory to cache these data (PVM's ram). The ram cache in secondary side
is i
If VM is in COLO FT state, we need to do some extra works before
starting normal shutdown process.
Secondary VM will ignore the shutdown command if users issue it directly
to Secondary VM. COLO will capture shutdown command and after
shutdown request from user.
Cc: Paolo Bonzini
Signed-off-by: z
We will use this notifier to help COLO to notify filter object
to do something, like do checkpoint, or process failover event.
Cc: Jason Wang
Signed-off-by: zhanghailiang
Signed-off-by: Zhang Chen
Signed-off-by: Li Zhijian
---
net/colo.c | 105 +
We will use this notifier to help COLO to notify filter object
to do something, like do checkpoint, or process failover event.
Cc: Jason Wang
Signed-off-by: zhanghailiang
Signed-off-by: Zhang Chen
Signed-off-by: Li Zhijian
---
net/colo.c | 105 +
After one round of checkpoint, the states between PVM and SVM
become consistent, so it is unnecessary to adjust the sequence
of net packets for old connections, besides, while failover
happens, filter-rewriter needs to check if it still needs to
adjust sequence of net packets.
Cc: Jason Wang
Sign
While do checkpoint, we need to flush all the unhandled packets,
By using the filter notifier mechanism, we can easily to notify
every compare object to do this process, which runs inside
of compare threads as a coroutine.
Cc: Jason Wang
Signed-off-by: zhanghailiang
Signed-off-by: Zhang Chen
--
Don't need to flush all VM's ram from cache, only
flush the dirty pages since last checkpoint
Cc: Juan Quintela
Signed-off-by: Li Zhijian
Signed-off-by: Zhang Chen
Signed-off-by: zhanghailiang
---
v2:
- stop dirty log after exit from COLO state. (Dave)
---
migration/ram.c | 12
We separate the process of saving/loading ram and device state when do
checkpoint. We add new helpers for save/load ram/device. With this change,
we can directly transfer RAM from primary side to secondary side without
using channel-buffer as assistant, which also reduce the size of extra memory
wa
Make sure master start block replication after slave's block
replication started.
Besides, we need to activate VM's blocks before goes into
COLO state.
Signed-off-by: zhanghailiang
Signed-off-by: Li Zhijian
Cc: Stefan Hajnoczi
Cc: Kevin Wolf
Cc: Max Reitz
Cc: Xie Changlong
---
migration/co
It is unnecessary to call qemu_savevm_state_begin() in every checkpoint process.
It mainly sets up devices and does the first device state pass. These data will
not change during the later checkpoint process. So, we split it out of
colo_do_checkpoint_transaction(), in this way, we can reduce these
COLO's checkpoint process is based on migration process,
everytime we do checkpoint we will repeat the process of savevm and loadvm.
So we will call qemu_loadvm_section_start_full() repeatedly, It will
add all migration sections information into loadvm_handlers list everytime,
which will lead to m
There are several stages during loadvm/savevm process. In different stage,
migration incoming processes different types of sections.
We want to control these stages more accuracy, it will benefit COLO
performance, we don't have to save type of QEMU_VM_SECTION_START
sections everytime while do check
During the time of VM's running, PVM may dirty some pages, we will transfer
PVM's dirty pages to SVM and store them into SVM's RAM cache at next checkpoint
time. So, the content of SVM's RAM cache will always be same with PVM's memory
after checkpoint.
Instead of flushing all content of PVM's RAM
Hi,
COLO Frame, block replication and COLO net compare have been exist in qemu
for long time, it's time to integrate these three parts to make COLO really
works.
In this series, we have some optimizations for COLO frame, including separating
the
process of saving ram and device state, using an
We record the address of the dirty pages that received,
it will help flushing pages that cached into SVM.
Here, it is a trick, we record dirty pages by re-using migration
dirty bitmap. In the later patch, we will start the dirty log
for SVM, just like migration, in this way, we can record both
the
For COLO FT, both the PVM and SVM run at the same time,
only sync the state while it needs.
So here, let SVM runs while not doing checkpoint, change
DEFAULT_MIGRATE_X_CHECKPOINT_DELAY to 200*100.
Besides, we forgot to release colo_checkpoint_semd and
colo_delay_timer, fix them here.
Cc: Jason Wa
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 1492845627-4384-1-git-send-email-longpe...@huawei.com
Type: series
Subject: [Qemu-devel] [PATCH v3 00/18] crypto: add afalg-backend support
=== TEST SCRIPT BEGIN ===
#!/bin/bash
BASE=bas
Hi,
This series failed automatic build test. Please find the testing commands and
their output below. If you have docker installed, you can probably reproduce it
locally.
Message-id: 1492845627-4384-1-git-send-email-longpe...@huawei.com
Type: series
Subject: [Qemu-devel] [PATCH v3 00/18] crypto:
1) makes the public APIs in hmac-nettle/gcrypt/glib static,
and rename them with "nettle/gcrypt/glib" prefix.
2) introduces hmac framework, including QCryptoHmacDriver
and new public APIs.
Signed-off-by: Longpeng(Mike)
---
crypto/hmac-gcrypt.c | 51 ---
cr
Adds afalg-backend hmac support: introduces some private APIs
firstly, and then intergrates them into qcrypto_hmac_afalg_driver.
Signed-off-by: Longpeng(Mike)
---
crypto/hash-afalg.c | 108 +++---
crypto/hmac.c | 27 -
crypto/hma
Adds afalg-backend hash support: introduces some private APIs
firstly, and then intergrates them into qcrypto_hash_afalg_driver.
Signed-off-by: Longpeng(Mike)
---
crypto/Makefile.objs | 1 +
crypto/afalgpriv.h | 1 +
crypto/hash-afalg.c | 147 ++
The AF_ALG socket family is the userspace interface for linux
crypto API, this patch adds af_alg family support and some common
functions for af_alg backend. It'll be used by afalg-backend crypto
latter.
Signed-off-by: Longpeng(Mike)
---
configure| 21 +
crypto/Makefile.objs
Now we have two qcrypto backends, libiary-backend and afalg-backend,
but which one is faster? This patch add a cipher speed benchmark, it
helps us to measure the performance by using "make check-speed" or
using "./tests/benchmark-crypto-cipher" directly.
Signed-off-by: Longpeng(Mike)
---
tests/M
Extracts qcrypto_hmac_ctx_new() from qcrypto_hmac_new() for
glib-backend impls.
Reviewed-by: Gonglei
Signed-off-by: Longpeng(Mike)
---
crypto/hmac-glib.c | 34 --
1 file changed, 24 insertions(+), 10 deletions(-)
diff --git a/crypto/hmac-glib.c b/crypto/hmac-gli
1) makes the public APIs in cipher-nettle/gcrypt/builtin static,
and rename them with "nettle/gcrypt/builtin" prefix.
2) introduces cipher framework, including QCryptoCipherDriver
and new public APIs.
Reviewed-by: Gonglei
Signed-off-by: Longpeng(Mike)
---
crypto/cipher-builtin.c | 64 +++
This patch add a hash speed benchmark, it helps us to
measure the performance by using "make check-speed" or
using "./tests/benchmark-crypto-cipher" directly.
Signed-off-by: Longpeng(Mike)
---
tests/Makefile.include| 2 ++
tests/benchmark-crypto-hash.c | 67 +
This patch add a hmac speed benchmark, it helps us to
measure the performance by using "make check-speed" or
using "./tests/benchmark-crypto-hmac" directly.
Signed-off-by: Longpeng(Mike)
---
tests/Makefile.include| 2 +
tests/benchmark-crypto-hmac.c | 96
Extracts qcrypto_hmac_ctx_new() from qcrypto_hmac_new() for
nettle-backend impls.
Reviewed-by: Gonglei
Signed-off-by: Longpeng(Mike)
---
crypto/hmac-nettle.c | 34 --
1 file changed, 24 insertions(+), 10 deletions(-)
diff --git a/crypto/hmac-nettle.c b/crypto/hm
1) makes the public APIs in hash-nettle/gcrypt/glib static,
and rename them with "nettle/gcrypt/glib" prefix.
2) introduces hash framework, including QCryptoHashDriver
and new public APIs.
Reviewed-by: Gonglei
Signed-off-by: Longpeng(Mike)
---
crypto/hash-gcrypt.c | 19 +-
Extracts qcrypto_cipher_ctx_new() from qcrypto_cipher_new() for
gcrypt-backend impls.
Reviewed-by: Gonglei
Signed-off-by: Longpeng(Mike)
---
crypto/cipher-gcrypt.c | 50 +-
1 file changed, 33 insertions(+), 17 deletions(-)
diff --git a/crypto/cip
Extracts qcrypto_cipher_ctx_new() from qcrypto_cipher_new() for
builtin-backend impls.
Reviewed-by: Gonglei
Signed-off-by: Longpeng(Mike)
---
crypto/cipher-builtin.c | 101 ++--
1 file changed, 55 insertions(+), 46 deletions(-)
diff --git a/crypto/ci
Moves crypto/hmac.h into include/crypto/, likes cipher.h and hash.h
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Gonglei
Signed-off-by: Longpeng(Mike)
---
crypto/hmac.h | 166 --
include/crypto/hmac.h | 166 +++
Adds afalg-backend cipher support: introduces some private APIs
firstly, and then intergrates them into qcrypto_cipher_afalg_driver.
Signed-off-by: Longpeng(Mike)
---
crypto/Makefile.objs | 1 +
crypto/afalgpriv.h | 9 ++
crypto/cipher-afalg.c | 229 +++
1) Fix a handle-leak problem in qcrypto_hmac_new(), doesn't free
ctx->handle if gcry_mac_setkey fails.
2) Extracts qcrypto_hmac_ctx_new() from qcrypto_hmac_new() for
gcrypt-backend impls.
Reviewed-by: Gonglei
Signed-off-by: Longpeng(Mike)
---
crypto/hmac-gcrypt.c | 35 +++
Extracts qcrypto_cipher_ctx_new() from qcrypto_cipher_new() for
nettle-backend impls.
Reviewed-by: Gonglei
Signed-off-by: Longpeng(Mike)
---
crypto/cipher-nettle.c | 41 +
1 file changed, 29 insertions(+), 12 deletions(-)
diff --git a/crypto/cipher-nettl
Refactors the qcrypto_cipher_free(), splits it into two parts. One
is gcrypt/nettle__cipher_free_ctx() to free the special context.
This makes code more clear, what's more, it would be used by the
later patch.
Reviewed-by: Gonglei
Signed-off-by: Longpeng(Mike)
---
crypto/cipher-gcrypt.c | 31 +
The AF_ALG socket family is the userspace interface for linux
crypto API, users can use it to access hardware accelerators.
This patchset adds a afalg-backend for qemu crypto subsystem. Currently
when performs encrypt/decrypt, we'll try afalg-backend first and will
back to libiary-backend if it fa
82 matches
Mail list logo
