> -Original Message-
> From: qemu-devel-bounces+xudong.hao=intel@nongnu.org [mailto:qemu-
> devel-bounces+xudong.hao=intel@nongnu.org] On Behalf Of Gerd
> Hoffmann
> Sent: Tuesday, January 12, 2016 6:25 PM
> To: Hao, Xudong
> Cc: Lars Kurth ; xen-de...@lists.xensource.com; Stefano
On 13.01.2016 04:13, Jason Wang wrote:
>
>
> On 01/13/2016 10:58 AM, Jason Wang wrote:
>>
>> On 01/12/2016 07:45 PM, Cleber Rosa wrote:
>>> - Original Message -
From: "Thomas Huth"
To: "Jason Wang" , "Jan Kiszka"
, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" , avocado-
On 13/01/2016 04:13, Jason Wang wrote:
> Rethinking about this. I'm not quite sure we can remove those
> especially "-net user". Google qemu "-net user" gives about 15,900
> results (and the first link is qemu wiki). Maybe we can replace "will be
> removed in a future version." with something li
Jason Wang writes:
> On 01/13/2016 10:58 AM, Jason Wang wrote:
>>
>> On 01/12/2016 07:45 PM, Cleber Rosa wrote:
>>> - Original Message -
From: "Thomas Huth"
To: "Jason Wang" , "Jan Kiszka"
, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" ,
avocado-de...@redhat.com, "M
On Wed, Jan 13, 2016 at 03:57:00PM +1100, David Gibson wrote:
> On Wed, Jan 13, 2016 at 09:40:54AM +0530, Bharata B Rao wrote:
> > On Tue, Jan 12, 2016 at 05:06:34PM +1100, David Gibson wrote:
> > > On Fri, Jan 08, 2016 at 12:25:19PM +0530, Bharata B Rao wrote:
> > > > Remove the CPU core device by
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1490611
Title:
Using qemu >=2.2.1 to convert raw->VHD (fixed) adds extra padding to
the result
On Wed, Jan 13, 2016 at 09:40:54AM +0530, Bharata B Rao wrote:
> On Tue, Jan 12, 2016 at 05:06:34PM +1100, David Gibson wrote:
> > On Fri, Jan 08, 2016 at 12:25:19PM +0530, Bharata B Rao wrote:
> > > Remove the CPU core device by removing the underlying CPU thread devices.
> > > Support hot removal
On Tue, 01/12 18:56, Daniel P. Berrange wrote:
> +#if defined CONFIG_NETTLE
> +#include "crypto/pbkdf-nettle.c"
> +#elif defined CONFIG_GCRYPT
> +#include "crypto/pbkdf-gcrypt.c"
> +#else /* ! CONFIG_GCRYPT */
> +#include "crypto/pbkdf-stub.c"
> +#endif /* ! CONFIG_GCRYPT */
I think the convention
On Tue, Jan 12, 2016 at 12:23:03PM +0530, Bharata B Rao wrote:
> On Tue, Jan 12, 2016 at 03:16:15PM +1100, David Gibson wrote:
> > On Fri, Jan 08, 2016 at 12:25:14PM +0530, Bharata B Rao wrote:
> > > This sync API will be used by the CPU hotplug code to wait for the CPU to
> > > completely get remo
On 10/25/2015 10:30 PM, Leonid Bloch wrote:
Hello qemu-devel,
This patch series is an RFC for the new networking device emulation
we're developing for QEMU.
Thanks for the patch
/Prem
Tested By: Prem Mallappa
On Wed, Jan 13, 2016 at 10:44:07AM +1100, Alexey Kardashevskiy wrote:
> On 01/08/2016 05:55 PM, Bharata B Rao wrote:
> >CPU core device is a container of CPU thread devices. CPU hotplug is
> >performed at the granularity of CPU core device. When hotplugged, CPU core
> >creates CPU thread devices.
On Tue, Jan 12, 2016 at 05:06:34PM +1100, David Gibson wrote:
> On Fri, Jan 08, 2016 at 12:25:19PM +0530, Bharata B Rao wrote:
> > Remove the CPU core device by removing the underlying CPU thread devices.
> > Support hot removal of CPU for sPAPR guests by sending the hot unplug
> > notification to
On Wed, Jan 13, 2016 at 10:58:06AM +1100, Alexey Kardashevskiy wrote:
> On 01/08/2016 05:55 PM, Bharata B Rao wrote:
> >Support CPU hotplug via device-add command like this:
> >
> >(qemu) device_add powerpc64-cpu-core,id=core2
> >
> >In response to device_add, CPU core device will be created. CPU c
On Tue, Jan 12, 2016 at 04:58:44PM +1100, David Gibson wrote:
> On Fri, Jan 08, 2016 at 12:25:18PM +0530, Bharata B Rao wrote:
> >
> > +static int spapr_core_attach(Object *obj, void *opaque)
> > +{
> > +sPAPRMachineClass *smc = SPAPR_MACHINE_GET_CLASS(qdev_get_machine());
> > +sPAPRMachin
On 01/13/2016 10:58 AM, Jason Wang wrote:
>
> On 01/12/2016 07:45 PM, Cleber Rosa wrote:
>> - Original Message -
>>> From: "Thomas Huth"
>>> To: "Jason Wang" , "Jan Kiszka"
>>> , qemu-devel@nongnu.org
>>> Cc: "Paolo Bonzini" , avocado-de...@redhat.com,
>>> "Markus Armbruster"
>>> Sent
On 01/12/2016 07:45 PM, Cleber Rosa wrote:
>
> - Original Message -
>> From: "Thomas Huth"
>> To: "Jason Wang" , "Jan Kiszka"
>> , qemu-devel@nongnu.org
>> Cc: "Paolo Bonzini" , avocado-de...@redhat.com, "Markus
>> Armbruster"
>> Sent: Tuesday, January 12, 2016 5:26:36 AM
>> Subject:
The "pnum < nb_sectors" condition in deciding whether to actually copy
data is unnecessarily strict, and the qiov initialization is
unnecessarily for bdrv_aio_write_zeroes and bdrv_aio_discard.
Rewrite mirror_iteration to fix both flaws.
The output of iotests 109 is updated because we now report
The three lines are duplicated a number of times now, refactor a
function.
Signed-off-by: Fam Zheng
Reviewed-by: Max Reitz
---
block/mirror.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/block/mirror.c b/block/mirror.c
index 7606aea..a411e02 100
v10: Fix and simplify mirror_cow_align. [Max]
v9: Fix the one bug Max found:
"shrink *= chunk_sectors".
v8: Rebase onto master (didn't pick up Max's rev-by due to non-trivial code
change).
The conflict is around removed lines about "max_iov" and "IOV_MAX" due to
commit 3515727f3,
On Tue, 01/12 18:56, Daniel P. Berrange wrote:
> Signed-off-by: Daniel P. Berrange
> ---
> crypto/Makefile.objs| 1 +
> crypto/random.c | 50
> +
> include/crypto/random.h | 43 ++
> 3 files chan
On Tue, Jan 12, 2016 at 06:02:00PM +0100, Eric Auger wrote:
> Hi David,
> On 01/12/2016 05:28 AM, David Gibson wrote:
> > On Mon, Jan 11, 2016 at 11:35:50AM +0100, Eric Auger wrote:
> >> Hi David,
> >> On 01/11/2016 03:38 AM, David Gibson wrote:
> >>> On Wed, Jan 06, 2016 at 03:13:21PM +, Eric
On Wed, Dec 23, 2015 at 9:22 PM, Hitoshi Mitake <
mitake.hito...@lab.ntt.co.jp> wrote:
> From: Vasiliy Tolstov
>
> This patch implements a blockdriver function bdrv_snapshot_delete() in
> the sheepdog driver. With the new function, snapshots of sheepdog can
> be deleted from libvirt.
>
> Cc: Jeff
"can't boot up" means guest doesn't boot at all, guest will stop to booting
after adding vga device, detail log in attachment.
Thanks,
-Xudong
> -Original Message-
> From: qemu-devel-bounces+xudong.hao=intel@nongnu.org [mailto:qemu-
> devel-bounces+xudong.hao=intel@nongnu.org] O
On 2016/1/12 23:30, Peter Maydell wrote:
> On 12 January 2016 at 15:24, Shannon Zhao wrote:
>> > When booting VM through UEFI, UEFI takes ownership of the RTC hardware.
>> > To DTB UEFI could call libfdt api to disable the RTC device node, but to
>> > ACPI it couldn't do that. Therefore, we don'
The implicit casting from unsigned int to double changes negative values
into large positive numbers and accepts them. We should instead print
an error.
Check the number range so this case is catched and reported.
Signed-off-by: Fam Zheng
---
blockdev.c | 3 ++-
include/qemu/thro
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/051| 11 +++
tests/qemu-iotests/051.out| 21 +
tests/qemu-iotests/051.pc.out | 21 +
3 files changed, 53 insertions(+)
diff --git a/tests/qemu-iotests/051 b/tests/qemu-iotests/051
index d9
v2: Check the value range and report an appropriate error. [Berto]
Now the negative values are silently converted to a huge positive number
because we are doing implicit casting from uint64_t to double. Fix it and add a
test case (this was once fixed in 7d81c1413c9 but regressed when the block
dev
On Tue, Jan 12, 2016 at 3:53 PM, Andrew Baumann
wrote:
>> From: Peter Crosthwaite [mailto:crosthwaitepe...@gmail.com]
>> Sent: Monday, 11 January 2016 19:58
> [...]
>> > +static void write_board_setup(ARMCPU *cpu, const struct arm_boot_info
>> *info)
>>
>> This is almost identical to Highbank, I'm
On Tue, 01/12 16:00, Alberto Garcia wrote:
> On Mon 11 Jan 2016 06:42:38 AM CET, Fam Zheng wrote:
>
> > The implicit casting from unsigned int to double changes negative
> > values into large positive numbers, whereas explicitly casting to
> > signed integer first will let us catch the invalid va
On Tue, 01/12 18:59, Denis V. Lunev wrote:
> On 01/12/2016 02:33 PM, Fam Zheng wrote:
> >On Tue, 01/12 11:10, Kevin Wolf wrote:
> >>The problem is that libvirt already takes a lock, as Dan mentioned in
> >>another reply in this thread, so we can't enable locking in qemu by
> >>default. It would alw
> From: Peter Crosthwaite [mailto:crosthwaitepe...@gmail.com]
> Sent: Tuesday, 12 January 2016 15:15
> On Tue, Jan 12, 2016 at 2:56 PM, Andrew Baumann
> wrote:
> >> From: Peter Crosthwaite [mailto:crosthwaitepe...@gmail.com]
> >> Sent: Monday, 11 January 2016 19:57
> >> On Thu, Dec 31, 2015 at 04:
On Tue, 01/12 13:24, Daniel P. Berrange wrote:
> On Tue, Jan 12, 2016 at 09:17:51PM +0800, Fam Zheng wrote:
> > On Tue, 01/12 13:28, Kevin Wolf wrote:
> > > Am 12.01.2016 um 12:33 hat Fam Zheng geschrieben:
> > > > On Tue, 01/12 11:10, Kevin Wolf wrote:
> > > > >
> > > > > The problem is that libv
On 01/08/2016 05:55 PM, Bharata B Rao wrote:
Support CPU hotplug via device-add command like this:
(qemu) device_add powerpc64-cpu-core,id=core2
In response to device_add, CPU core device will be created. CPU core
device creates and realizes CPU thread devices. If the machine type
supports CPU
> From: Peter Crosthwaite [mailto:crosthwaitepe...@gmail.com]
> Sent: Monday, 11 January 2016 19:58
[...]
> > +static void write_board_setup(ARMCPU *cpu, const struct arm_boot_info
> *info)
>
> This is almost identical to Highbank, I'm guessing you are stubbing monitor
> firmware where you get awa
On 01/08/2016 05:55 PM, Bharata B Rao wrote:
CPU core device is a container of CPU thread devices. CPU hotplug is
performed at the granularity of CPU core device. When hotplugged, CPU core
creates CPU thread devices.
Signed-off-by: Bharata B Rao
---
hw/ppc/Makefile.objs | 1 +
hw/ppc/
On 01/08/2016 05:55 PM, Bharata B Rao wrote:
CPU core device is a container of CPU thread devices. CPU hotplug is
performed at the granularity of CPU core device. When hotplugged, CPU core
creates CPU thread devices.
Signed-off-by: Bharata B Rao
---
hw/ppc/Makefile.objs | 1 +
hw/ppc/
On 01/08/2016 05:55 PM, Bharata B Rao wrote:
Prevent guests from booting with CPU topologies that have partially
filled CPU cores or can result in partially filled CPU cores after
CPU hotplug like
-smp 15,sockets=1,cores=4,threads=4,maxcpus=16 or
-smp 15,sockets=1,cores=4,threads=4,maxcpus=17.
*** This bug is a duplicate of bug 1505062 ***
https://bugs.launchpad.net/bugs/1505062
** This bug has been marked a duplicate of bug 1505062
Regression: QEMU 2.4 on Linux 4.2 fails to init display with SMM enabled
--
You received this bug notification because you are a member of qemu-
de
On Tue, Jan 12, 2016 at 2:56 PM, Andrew Baumann
wrote:
> Hi Peter,
>
> Thanks again for the reviews.
>
>> From: Peter Crosthwaite [mailto:crosthwaitepe...@gmail.com]
>> Sent: Monday, 11 January 2016 19:57
>> On Thu, Dec 31, 2015 at 04:31:33PM -0800, Andrew Baumann wrote:
>> > +/* TODO: probabl
** Changed in: qemu
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/697197
Title:
Empty password allows access to VNC in libvirt
Status in libvirt:
Unknown
Hi Peter,
Thanks again for the reviews.
> From: Peter Crosthwaite [mailto:crosthwaitepe...@gmail.com]
> Sent: Monday, 11 January 2016 19:57
> On Thu, Dec 31, 2015 at 04:31:33PM -0800, Andrew Baumann wrote:
> > +/* TODO: probably shouldn't be using smp_cpus here */
>
> I agree. I have started
The Xilinx ZynqMP SoC and EP108 board supports three memory regions:
- A 2GB region starting at 0
- A 32GB region starting at 32GB
- A 256GB region starting at 768GB
This patch adds support for the first two memory regions, which is
automatically created based on the size specified by the QEMU
** Changed in: qemu
Status: New => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1406016
Title:
qemu-system-arm hangs at start on OS X
Status in QEMU:
Invalid
Bug description:
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1410288
Title:
qemu-img conversion to qcow2 hangs with blank image less than 100kiB
Status in Q
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1414222
Title:
qemu-system-i386: -vnc localhost:0,to=99,id=default: Invalid parameter
'to'
St
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1416988
Title:
Wrong signal handling in qemu-aarch64.
Status in QEMU:
Fix Released
Bug descr
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1412098
Title:
qemu crashes when ctrl-alt-u is pressed
Status in QEMU:
Fix Released
Bug desc
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1478360
Title:
Cant compile on ubuntu 14.04 x64
Status in QEMU:
Fix Released
Bug d
This does not happend anymore with the upstream git. Closing. Please
reopen if you still see this.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs
Can you try the latest upstream git version from:
https://github.com/qemu/qemu?
Also can you post your configure command line?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1486911
Title:
Error co
On Tue, Jan 12, 2016 at 2:15 PM, Peter Crosthwaite
wrote:
> On Tue, Jan 12, 2016 at 2:07 PM, Alistair Francis
> wrote:
>> On Tue, Jan 12, 2016 at 2:00 PM, Peter Crosthwaite
>> wrote:
>>> On Tue, Jan 12, 2016 at 1:59 PM, Alistair Francis
>>> wrote:
On Tue, Jan 12, 2016 at 1:01 AM, Peter May
On 11/17/2015 12:25 PM, Cole Robinson wrote:
> ---
> I assume it's fine to enable...
>
> A fedora user requested it here:
> https://bugzilla.redhat.com/show_bug.cgi?id=1280318
>
> src/config/qemu/general.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/src/config/qemu/general.h b/s
On Tue, Jan 12, 2016 at 2:07 PM, Alistair Francis
wrote:
> On Tue, Jan 12, 2016 at 2:00 PM, Peter Crosthwaite
> wrote:
>> On Tue, Jan 12, 2016 at 1:59 PM, Alistair Francis
>> wrote:
>>> On Tue, Jan 12, 2016 at 1:01 AM, Peter Maydell
>>> wrote:
On 12 January 2016 at 00:24, Alistair Francis
Fix has been committed upstream.
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1470170
Title:
Unsupported syscalls 370 and 355
Status in QEM
On Tue, Jan 12, 2016 at 2:00 PM, Peter Crosthwaite
wrote:
> On Tue, Jan 12, 2016 at 1:59 PM, Alistair Francis
> wrote:
>> On Tue, Jan 12, 2016 at 1:01 AM, Peter Maydell
>> wrote:
>>> On 12 January 2016 at 00:24, Alistair Francis
>>> wrote:
On Mon, Jan 11, 2016 at 8:04 AM, Peter Maydell
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/893208
Title:
qemu on ARM hosts can't boot i386 image
Status in QEMU:
Confirmed
Status in Linaro
On Tue, Jan 12, 2016 at 1:59 PM, Alistair Francis
wrote:
> On Tue, Jan 12, 2016 at 1:01 AM, Peter Maydell
> wrote:
>> On 12 January 2016 at 00:24, Alistair Francis
>> wrote:
>>> On Mon, Jan 11, 2016 at 8:04 AM, Peter Maydell
>>> wrote:
There are a couple of problems you're running into:
On Tue, Jan 12, 2016 at 1:01 AM, Peter Maydell wrote:
> On 12 January 2016 at 00:24, Alistair Francis
> wrote:
>> On Mon, Jan 11, 2016 at 8:04 AM, Peter Maydell
>> wrote:
>>> There are a couple of problems you're running into:
>>>
>>> (1) machine->ram_size is a ram_addr_t so might be 32 bit; yo
Can you post the `configure` command line you used when you try to
compile?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1531632
Title:
Can't compile qemu because of errors in the Xen code
Status
Hi Alex,
On Tue, Jan 12, 2016 at 12:29 PM, Alex Bennée
wrote:
>
https://github.com/stsquad/qemu/tree/mttcg/multi_tcg_v8_wip_ajb_fix_locks
>
I built this branch and ran an arm64 guest. It seems to be failing
similarly to what I reported earlier:
#0 0x72211cc9 in __GI_raise (sig=sig@ent
On 12 January 2016 at 17:36, Peter Maydell wrote:
> On 12 January 2016 at 16:35, Alex Bennée wrote:
>>
>> Peter Maydell writes:
>>
>>> The VIXL code includes some equality comparisons between signed
>>> and unsigned types. Modern gcc and clang do not complain about
>>> these, but older versions
Hi Gerd,
On Mon, 11 Jan 2016 14:10:16 +0100
Gerd Hoffmann wrote:
> Hi,
>
> For SDL2 this ...
>
> > > +static int idle_counter;
>
> ... should be store in ...
>
> > > void sdl2_poll_events(struct sdl2_console *scon)
>
> ... sdl2_console, otherwise it will not work as intended in case
On 01/07/2016 10:13 PM, Igor Mammedov wrote:
On Tue, 5 Jan 2016 02:52:02 +0800
Xiao Guangrong wrote:
This patchset is against commit 5530427f0ca (acpi: extend aml_and() to
accept target argument) on pci branch of Michael's git tree
and can be found at:
https://github.com/xiaogr/qemu.
update the nvdimm ssdt table as its acpi code has been updated
Signed-off-by: Xiao Guangrong
---
tests/acpi-test-data/pc/SSDT-NVDIMM | Bin 134 -> 403 bytes
tests/acpi-test-data/pc/SSDT-NVDIMM.bridge | Bin 134 -> 403 bytes
tests/acpi-test-data/q35/SSDT-NVDIMM| Bin 134 -> 403 by
If dsm memory is successfully patched, we let qemu fully emulate
the dsm method
This patch saves _DSM input parameters into dsm memory, tell dsm
memory address to QEMU, then fetch the result from the dsm memory
Signed-off-by: Xiao Guangrong
---
hw/acpi/nvdimm.c | 117 +++
It will be used by nvdimm acpi
Signed-off-by: Xiao Guangrong
---
hw/acpi/aml-build.c | 14 ++
include/hw/acpi/aml-build.h | 1 +
2 files changed, 15 insertions(+)
diff --git a/hw/acpi/aml-build.c b/hw/acpi/aml-build.c
index 97c9efb..421dd84 100644
--- a/hw/acpi/aml-build.c
Add nvdimm test, two tables are created which are NFIT and
SSDT
Max memory size and multiple slots are needed to enable NVDIMM which
cause the primal SSDT table is also updated
Signed-off-by: Xiao Guangrong
---
tests/acpi-test-data/pc/NFIT| Bin 0 -> 224 bytes
tests/acpi-test-da
This converts the qcow2 driver to make use of the QCryptoBlock
APIs for encrypting image content. As well as continued support
for the legacy QCow2 encryption format, the appealing benefit
is that it enables support for the LUKS format inside qcow2.
With the LUKS format it is neccessary to store t
The LUKS format specifies an anti-forensic split algorithm which
is used to artificially expand the size of the key material on
disk. This is an implementation of that algorithm.
Signed-off-by: Daniel P. Berrange
---
crypto/Makefile.objs| 1 +
crypto/afsplit.c| 194
As Igor suggested that we can report the BIOS patched operation region
so that OSPM could see that particular range is in use and be able to
notice conflicts if it happens some day
Signed-off-by: Xiao Guangrong
---
hw/acpi/nvdimm.c | 27 +++
1 file changed, 27 insertions(
32 bits IO port starting from 0x0a18 in guest is reserved for NVDIMM
ACPI emulation. The table, NVDIMM_DSM_MEM_FILE, will be patched into
NVDIMM ACPI binary code
OSPM uses this port to tell QEMU the final address of the DSM memory
and notify QEMU to emulate the DSM method
Signed-off-by: Xiao Guan
Emulate dsm method after IO VM-exit
Currently, we only introduce the framework and no function is actually
supported
Signed-off-by: Xiao Guangrong
---
hw/acpi/aml-build.c | 2 +-
hw/acpi/nvdimm.c| 44
include/hw/acpi/aml-build.h
Refuse to use images with the legacy AES-CBC encryption
format in the system emulators. They are still fully
supported in the qemu-img, qemu-io & qemu-nbd tools in
order to allow data to be liberated and for compatibility
with older QEMU versions. Continued support in these tools
is not a notable b
It will be used by nvdimm acpi
Signed-off-by: Xiao Guangrong
---
hw/acpi/aml-build.c | 13 +
include/hw/acpi/aml-build.h | 1 +
2 files changed, 14 insertions(+)
diff --git a/hw/acpi/aml-build.c b/hw/acpi/aml-build.c
index 78e1290..97c9efb 100644
--- a/hw/acpi/aml-build.c
+
The dsm memory is used to save the input parameters and store
the dsm result which is filled by QEMU.
The address of dsm memory is decided by bios and patched into
int32 object named "MEMA"
Signed-off-by: Xiao Guangrong
---
hw/acpi/nvdimm.c | 34 +-
1 file change
This converts the qcow2 driver to make use of the QCryptoBlock
APIs for encrypting image content. This is only wired up to
permit use of the legacy QCow encryption format. Users who wish
to have the strong LUKS format should switch to qcow2 instead.
With this change it is now required to use the Q
Extend aml_operation_region() to use object as offset
Signed-off-by: Xiao Guangrong
---
hw/acpi/aml-build.c | 4 ++--
hw/i386/acpi-build.c| 31 ---
include/hw/acpi/aml-build.h | 2 +-
3 files changed, 19 insertions(+), 18 deletions(-)
diff --git a/h
Add a generic framework for support different block encryption
formats. Upon instantiating a QCryptoBlock object, it will read
the encryption header and extract the encryption keys. It is
then possible to call methods to encrypt/decrypt data buffers.
There is also a mode whereby it will create/ini
Instead of requiring separate input/output buffers for
encrypting data, change encrypt_sectors() to assume
use of a single buffer, encrypting in place. One current
caller all uses the same buffer for input/output already
and the other two callers are easily converted todo so.
Signed-off-by: Daniel
Provide a block encryption implementation that follows the
LUKS/dm-crypt specification.
This supports all combinations of hash, cipher algorithm,
cipher mode and iv generator that are implemented by the
current crypto layer.
The notable missing feature is support for the 'xts'
cipher mode, which
Currently, only one SSDT with default oem-table-id can be tested,
this patch extents it to test all SSDT tables
Other tables except the default one will be named as SSDT-$oem-table-id
Signed-off-by: Xiao Guangrong
---
tests/bios-tables-test.c | 43 ---
1
Now that qcow & qcow2 are wired up to get encryption keys
via the QCryptoSecret object, nothing is relying on the
interactive prompting for passwords. All the code related
to password prompting can thus be ripped out.
Signed-off-by: Daniel P. Berrange
---
hmp.c| 31 --
Instead of requiring separate input/output buffers for
encrypting data, change qcow2_encrypt_sectors() to assume
use of a single buffer, encrypting in place. The current
callers all used the same buffer for input/output already.
Signed-off-by: Daniel P. Berrange
---
block/qcow2-cluster.c | 17 ++
This patchset is against commit 8a1be662a69 (virtio: fix error message for
number of queues) on pci branch of Michael's git tree
and can be found at:
https://github.com/xiaogr/qemu.git nvdimm-acpi-v2
Changelog:
These changes are based on Igor's comments:
- drop ssdt.rev2 support as the memo
Now that all encryption keys must be provided upfront via
the QCryptoSecret API and associated block driver properties
there is no need for any explicit encryption handling APIs
in the block layer. Encryption can be handled transparently
within the block driver. We only retain an API for querying
w
Add a block driver that is capable of supporting any full disk
encryption format. This utilizes the previously added block
encryption code, and at this time supports the LUKS format.
The driver code is capable of supporting any format supported
by the QCryptoBlock module, so it registers one block
There are a number of different algorithms that can be used
to generate initialization vectors for disk encryption. This
introduces a simple internal QCryptoBlockIV object to provide
a consistent internal API to the different algorithms. The
initially implemented algorithms are 'plain', 'plain64' a
The LUKS data format includes use of PBKDF2 (Password-Based
Key Derivation Function). The Nettle library can provide
an implementation of this, but we don't want code directly
depending on a specific crypto library backend. Introduce
a include/crypto/pbkdf.h header which defines a QEMU
API for invo
When opening an image it is useful to know whether the caller
intends to perform I/O on the image or not. In the case of
encrypted images this will allow the block driver to avoid
having to prompt for decryption keys when we merely want to
query header metadata about the image. eg qemu-img info
Si
This is a posting of the previously submitted work in progress
code:
https://lists.gnu.org/archive/html/qemu-devel/2015-11/msg04748.html
This series depends on these previously submitted
patches to the block tools:
https://lists.gnu.org/archive/html/qemu-devel/2015-12/msg04354.html
As can b
Signed-off-by: Daniel P. Berrange
---
crypto/Makefile.objs| 1 +
crypto/random.c | 50 +
include/crypto/random.h | 43 ++
3 files changed, 94 insertions(+)
create mode 100644 crypto/random.c
cre
On Tue, 2016-01-12 at 16:11 +0100, Pierre Morel wrote:
> In vfio_listener_region_add(), we try to validate that the region is
> not
> zero sized and hasn't overflowed the addresses space.
>
> But the calculation uses the size of the region instead of
> using the region's limit (size - 1).
>
> Thi
12.01.2016 06:58, Peter Crosthwaite пишет:
On Sat, Jan 09, 2016 at 08:39:53PM +0300, Dmitry Osipenko wrote:
Currently ptimer would print error message and clear enable flag for an
arming timer that has delta = load = 0. That actually could be a valid case
for some hardware, like instant IRQ trig
On 12 January 2016 at 06:08, Aneesh Kumar K.V
wrote:
> The following changes since commit a7e00e2536941a6e570b45b7ab4afec4505ff67e:
>
> petalogix-ml605: Set the MicroBlaze CPU version to 8.10.a (2016-01-07
> 14:57:26 +0100)
>
> are available in the git repository at:
>
> https://github.com/kv
On 01/12/2016 01:01 PM, Paolo Bonzini wrote:
>
>
> On 12/01/2016 18:57, John Snow wrote:
>>
>>
>> On 01/12/2016 03:46 AM, Paolo Bonzini wrote:
>>>
>>>
>>> On 12/01/2016 01:36, John Snow wrote:
Instead of relying on peeking at bs->job, we want to explicitly get
a reference to the job t
On 12/01/2016 18:57, John Snow wrote:
>
>
> On 01/12/2016 03:46 AM, Paolo Bonzini wrote:
>>
>>
>> On 12/01/2016 01:36, John Snow wrote:
>>> Instead of relying on peeking at bs->job, we want to explicitly get
>>> a reference to the job that was involved in this notifier callback.
>>>
>>> Extend
On 01/12/2016 08:50 PM, Kevin Wolf wrote:
Am 12.01.2016 um 18:40 hat Markus Armbruster geschrieben:
Kevin Wolf writes:
Am 12.01.2016 um 17:35 hat Denis V. Lunev geschrieben:
On 01/12/2016 06:47 PM, Denis V. Lunev wrote:
On 01/12/2016 06:20 PM, Kevin Wolf wrote:
Am 12.01.2016 um 15:59 hat P
On 01/12/2016 03:46 AM, Paolo Bonzini wrote:
>
>
> On 12/01/2016 01:36, John Snow wrote:
>> Instead of relying on peeking at bs->job, we want to explicitly get
>> a reference to the job that was involved in this notifier callback.
>>
>> Extend the Notifier to include a job pointer, and include
On 01/12/2016 08:40 PM, Markus Armbruster wrote:
Kevin Wolf writes:
Am 12.01.2016 um 17:35 hat Denis V. Lunev geschrieben:
On 01/12/2016 06:47 PM, Denis V. Lunev wrote:
On 01/12/2016 06:20 PM, Kevin Wolf wrote:
Am 12.01.2016 um 15:59 hat Paolo Bonzini geschrieben:
On 12/01/2016 15:16, Kevi
Am 12.01.2016 um 18:40 hat Markus Armbruster geschrieben:
> Kevin Wolf writes:
>
> > Am 12.01.2016 um 17:35 hat Denis V. Lunev geschrieben:
> >> On 01/12/2016 06:47 PM, Denis V. Lunev wrote:
> >> >On 01/12/2016 06:20 PM, Kevin Wolf wrote:
> >> >>Am 12.01.2016 um 15:59 hat Paolo Bonzini geschriebe
1 - 100 of 290 matches
Mail list logo
