On Thu, 2017-10-12 at 16:25 -0400, hanji unit wrote:
> Hello, is it possible to run (or rebuild modifying build flags) QEMU
> without support for X11 window system integration?
./configure --disable-gtk --disable-sdl --disable-opengl
cheers,
Gerd
> From: Auger Eric [mailto:eric.au...@redhat.com]
> Sent: Thursday, October 12, 2017 6:10 PM
>
> Hi Peter,
>
> On 12/10/2017 11:54, Peter Maydell wrote:
> > On 11 October 2017 at 17:08, Auger Eric wrote:
> >> Hi Peter,
> >>
> >> On 11/10/2017 16:56, Peter Maydell wrote:
> >>> On 19 September 201
On Thu, 12 Oct 2017 17:48:19 +0200
Igor Mammedov wrote:
> follow up commit that registers host-spapr-cpu-core type unconditionally
> "ppc: spapr: register 'host' core type along with the rest of core types"
>
> makes 'non' machine crash
> ppc64-softmmu/qemu-system-ppc64 -M none -device host-s
Hi Kevin,
On 13/10/2017 09:01, Tian, Kevin wrote:
>> From: Auger Eric [mailto:eric.au...@redhat.com]
>> Sent: Thursday, October 12, 2017 6:10 PM
>>
>> Hi Peter,
>>
>> On 12/10/2017 11:54, Peter Maydell wrote:
>>> On 11 October 2017 at 17:08, Auger Eric wrote:
Hi Peter,
On 11/10/201
Richard Henderson writes:
> On 10/02/2017 10:43 AM, Alex Bennée wrote:
>>> +mkdir -p capstone
>>
>> Having a mkdir -p here seems a little out of place. Shouldn't the build
>> directory creation be handled by the make recipe?
>
> *shrug* We do this for the other directories at configure time.
On 10/12/17 17:45 +0200, Paolo Bonzini wrote:
> On 12/10/2017 14:45, Haozhong Zhang wrote:
> > Basically, QEMU builds two ROMs for guest, /rom@etc/acpi/tables and
> > /rom@etc/table-loader. The former is unstructured to guest, and
> > contains all data of guest ACPI. The latter is a BIOSLinkerLoade
13.10.2017 01:39, Eric Blake wrote:
On 10/12/2017 04:53 AM, Vladimir Sementsov-Ogievskiy wrote:
Minimally implement nbd structured read extension.
v3:
clone: tag up-nbd-minimal-structured-read-v3 from
https://src.openvz.org/scm/~vsementsov/qemu.git
online:
https://src.openvz.org/users/vsemen
On 10/12/17 13:39 -0400, Konrad Rzeszutek Wilk wrote:
> On Thu, Oct 12, 2017 at 08:45:44PM +0800, Haozhong Zhang wrote:
> > On 10/10/17 12:05 -0400, Konrad Rzeszutek Wilk wrote:
> > > On Tue, Sep 12, 2017 at 11:15:09AM +0800, Haozhong Zhang wrote:
> > > > On 09/11/17 11:52 -0700, Stefano Stabellini
On 13.10.2017 01:54, Anatol Pomozov wrote:
> * clang 3.8 enables SSE even for 32bit code. Generate code for pentium
>CPU to make sure no new instructions are used.
> * add memset() implementation. Clang implements array zeroing in
>print_num() via memset() function call.
> ---
> tests/mu
On 13.10.2017 03:24, Fam Zheng wrote:
> Signed-off-by: Fam Zheng
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 772ac209e1..da3c78df47 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -982,7 +982,7 @@ S: Supported
On 13.10.2017 03:24, Fam Zheng wrote:
> Signed-off-by: Fam Zheng
> ---
> MAINTAINERS | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index da3c78df47..731c5c7ec2 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -778,7 +778,6 @@ F: pc-bios/openbios-sparc64
>
From: "Daniel P. Berrange"
When building the tarball to pass into the docker/vm test image,
the code relies on the git submodules being checked out in the
main checkout.
ie if the developer has not run 'git submodule update --init dtc'
many of the docker tests will fail due to the libfdt package
From: "Daniel P. Berrange"
Currently if DTC is required by configure and not available in the host
OS install, we exit with an error message telling the user to checkout a
git submodule or install the library.
This introduces automatic handling of the git submodule checkout process
and enables i
From: "Daniel P. Berrange"
All public code should use qemu_input_event_send_key* functions
instead of creating an event directly.
Signed-off-by: Daniel P. Berrange
Message-id: 20170929101201.21039-7-berra...@redhat.com
Signed-off-by: Gerd Hoffmann
---
include/ui/input.h | 1 -
ui/input.c
Update files where I think I've figured the correct xkb maps.
TODO: nl-be sl sv
Signed-off-by: Gerd Hoffmann
Message-id: 20171005153330.19210-3-kra...@redhat.com
---
pc-bios/keymaps/Makefile | 56
1 file changed, 56 insertions(+)
create mode 1006
From: "Daniel P. Berrange"
Always use QKeyCode in the InputKeyEvent struct, by converting key
numbers to QKeyCode at the time the event is created. This allows
the code processing / consuming key events to assume QKeyCode is
used. The only place we accept a key number in the InputKeyEvent
struct
qemu-keymap generates qemu reverse keymaps from xkb keymaps,
which can be used with the qemu "-k" command line switch.
Signed-off-by: Gerd Hoffmann
Message-id: 20171005153330.19210-2-kra...@redhat.com
---
configure | 23 ++
Makefile | 5 ++
qemu-keymap.c | 258 +++
From: Anthony PERARD
vte_terminal_copy_clipboard() is deprecated in VTE 0.50.
Signed-off-by: Anthony PERARD
Reviewed-by: Daniel P. Berrange
Signed-off-by: Gerd Hoffmann
---
ui/gtk.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/ui/gtk.c b/ui/gtk.c
index 5bd87c265a..342e96fbe9 1006
From: Anthoine Bourgeois
The gd_gl_area_scanout_texture must destroy framebuffer if there is
no texture id instead of no framebuffer id.
The effect was a black screen with "-vga virtio -display gtk,gl=on"
options.
The bug was introduce by a4f113fd "gtk: use framebuffer helper functions."
Signed-
From: "Daniel P. Berrange"
The https://gitlab.com/keycodemap/keycodemapdb/ repo contains a
data file mapping between all the different scancode/keycode/keysym
sets that are known, and a tool to auto-generate lookup tables for
different combinations.
It is used by GTK-VNC, SPICE-GTK and libvirt f
The following changes since commit bac960832015bf4c4c1b873011612e2675e4464c:
Merge remote-tracking branch 'remotes/elmarco/tags/vus-pull-request' into
staging (2017-10-11 13:10:36 +0100)
are available in the git repository at:
git://git.kraxel.org/qemu tags/ui-20171013-pull-re
On Wed, 2017-10-11 at 15:37 +0100, Peter Maydell wrote:
> On 11 October 2017 at 09:35, Gerd Hoffmann wrote:
> > The following changes since commit
> > 567d0a19c7998fa366598b83d5a6e5f0759d3ea9:
> >
> > Merge remote-tracking branch 'remotes/ehabkost/tags/x86-and-
> > machine-pull-request' into st
On Fri, 10/13 10:04, Thomas Huth wrote:
> On 13.10.2017 03:24, Fam Zheng wrote:
> > Signed-off-by: Fam Zheng
> > ---
> > MAINTAINERS | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 772ac209e1..da3c78df47 100644
> > --- a/MAINTAIN
From: "Daniel P. Berrange"
Replace the number_to_qcode, qcode_to_number and linux_to_qcode
tables with automatically generated tables.
Missing entries in linux_to_qcode now fixed:
KEY_LINEFEED -> Q_KEY_CODE_LF
KEY_KPEQUAL -> Q_KEY_CODE_KP_EQUALS
KEY_COMPOSE -> Q_KEY_CODE_COMPOSE
KEY_AGA
On Fri, Oct 13, 2017 at 10:08 AM, Thomas Huth wrote:
> On 13.10.2017 03:24, Fam Zheng wrote:
>> Signed-off-by: Fam Zheng
>> ---
>> MAINTAINERS | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index da3c78df47..731c5c7ec2 100644
>> --- a/MAINTAINERS
>> +++ b
On 13.10.2017 10:20, Fam Zheng wrote:
> On Fri, 10/13 10:04, Thomas Huth wrote:
>> On 13.10.2017 03:24, Fam Zheng wrote:
>>> Signed-off-by: Fam Zheng
>>> ---
>>> MAINTAINERS | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index 772ac209
If a CPU selected with the "cpu" command is hot-unplugged then "info cpus"
causes QEMU to exit:
(qemu) device_del cpu1
(qemu) info cpus
qemu:qemu_cpu_kick_thread: No such process
I could verify that this happens with x86 and ppc, but I guess s390x is
also impacted.
This series tries to fix t
The current code assumes that only the CPU core object holds a
reference on each individual CPU object, and happily frees their
allocated memory when the core is unrealized. This is dangerous
as some other code can legitimely keep a pointer to a CPU if it
calls object_ref(), but it would end up wit
If a CPU selected with the "cpu" command is hot-unplugged then "info cpus"
causes QEMU to exit:
(qemu) device_del cpu1
(qemu) info cpus
qemu:qemu_cpu_kick_thread: No such process
This happens because "cpu" stores the pointer to the selected CPU into
the monitor structure. When the CPU is hot-unpl
On 10/09/2017 05:01 PM, Ian Jackson wrote:
We need to restrict *all* the control fds that qemu opens. Looking in
/proc/PID/fd shows there are many; their allocation seems scattered
throughout Xen support code in qemu.
We must postpone the restrict call until roughly the same time as qemu
change
On Fri, 13 Oct 2017 15:53:26 +0800
Haozhong Zhang wrote:
> On 10/12/17 17:45 +0200, Paolo Bonzini wrote:
> > On 12/10/2017 14:45, Haozhong Zhang wrote:
> > > Basically, QEMU builds two ROMs for guest, /rom@etc/acpi/tables and
> > > /rom@etc/table-loader. The former is unstructured to guest, and
On Fri, 10/13 10:30, Thomas Huth wrote:
> On 13.10.2017 10:20, Fam Zheng wrote:
> > On Fri, 10/13 10:04, Thomas Huth wrote:
> >> On 13.10.2017 03:24, Fam Zheng wrote:
> >>> Signed-off-by: Fam Zheng
> >>> ---
> >>> MAINTAINERS | 2 +-
> >>> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>>
> >>>
On Fri, 13 Oct 2017 10:35:06 +0200
Greg Kurz wrote:
> If a CPU selected with the "cpu" command is hot-unplugged then "info cpus"
> causes QEMU to exit:
>
> (qemu) device_del cpu1
> (qemu) info cpus
> qemu:qemu_cpu_kick_thread: No such process
>
> I could verify that this happens with x86 an
v2: Adopt Thomas' suggestions.
Fam Zheng (3):
MAINTAINERS: Clean up SCSI device section
MAINTAINERS: Fix Sun4v file
MAINTAINERS: Track default-configs/pci.mak
MAINTAINERS | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
--
2.13.5
Suggested-by: Thomas Huth
Signed-off-by: Fam Zheng
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 18ddaf4070..3938ccbf8a 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -778,7 +778,7 @@ F: pc-bios/openbios-sparc64
Sun4v
M: Arty
Suggested-by: Thomas Huth
Signed-off-by: Fam Zheng
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 3938ccbf8a..7cb237babc 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -934,6 +934,7 @@ F: hw/pci/*
F: hw/pci-bridge/*
F: docs/pci*
F: docs/spec
1. Remove nonexistent file util/scsi*.
2. Drop useless section for LSI53C895A.
3. Leave include/scsi to "Block SCSI subsystem" section.
Suggested-by: Thomas Huth
Signed-off-by: Fam Zheng
---
MAINTAINERS | 6 --
1 file changed, 6 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 772
On Thu, 12 Oct 2017 17:07:28 -0700
Alistair Francis wrote:
> The BCM2836 uses a Cortex-A7 not a Cortex-A15. Update the device to use
> the correct CPU.
> https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2836/QA7_rev3.4.pdf
>
> Signed-off-by: Alistair Francis
> ---
> V2:
> - Fi
On 13.10.2017 10:53, Fam Zheng wrote:
> 1. Remove nonexistent file util/scsi*.
> 2. Drop useless section for LSI53C895A.
> 3. Leave include/scsi to "Block SCSI subsystem" section.
>
> Suggested-by: Thomas Huth
> Signed-off-by: Fam Zheng
> ---
> MAINTAINERS | 6 --
> 1 file changed, 6 deleti
On Thu, 12 Oct 2017 17:07:23 -0700
Alistair Francis wrote:
> There are numorous QEMU machines that only have a single or a handful of
> valid CPU options. To simplyfy the management of specificying which CPU
> is/isn't valid let's create a property that can be set in the machine
> init. We can th
On 13.10.2017 10:53, Fam Zheng wrote:
> Suggested-by: Thomas Huth
> Signed-off-by: Fam Zheng
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 18ddaf4070..3938ccbf8a 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@
On Thu, 12 Oct 2017 17:07:25 -0700
Alistair Francis wrote:
> List all possible valid CPU options.
>
> Although the board only ever has a Cortex-M3 we mark the Cortex-M4 as
> supported because the Netduino2 Plus supports the Cortex-M4 and the
> Netduino2 Plus is similar to the Netduino2.
>
> Sig
On 13/10/2017 09:37, Ross Lagerwall wrote:
> On 10/09/2017 05:01 PM, Ian Jackson wrote:
>> We need to restrict *all* the control fds that qemu opens. Looking in
>> /proc/PID/fd shows there are many; their allocation seems scattered
>> throughout Xen support code in qemu.
>>
>> We must postpone the
On 13.10.2017 10:53, Fam Zheng wrote:
> Suggested-by: Thomas Huth
> Signed-off-by: Fam Zheng
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 3938ccbf8a..7cb237babc 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -934,6 +934,7 @@
> -Original Message-
> From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of
> Andrew Cooper
> Sent: 13 October 2017 10:00
> To: Ross Lagerwall ; Ian Jackson
> ; qemu-devel@nongnu.org
> Cc: Anthony Perard ; Juergen Gross
> ; Stefano Stabellini ; xen-
> de...@lists.xenproject
Hi,
the German Bundesamt für Sicherheit in der Informationstechnik
(Federal Office for Information Security) published a study on
the security of KVM and QEMU:
https://www.bsi.bund.de/DE/Publikationen/Studien/Sicherheitsanalyse_KVM/sicherheitsanalyse_kvm.html
(article only available in German)
Hi William,
David's fine (I'm from Red Hat)
OK, so it is the pflash; if you get some debug, please add it to this
bug, I'll ask some colleagues on the block side if they have any ideas.
Dave
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed
On Fri, Oct 13, 2017 at 10:58 AM, Thomas Huth wrote:
> On 13.10.2017 10:53, Fam Zheng wrote:
>> Suggested-by: Thomas Huth
>> Signed-off-by: Fam Zheng
>> ---
>> MAINTAINERS | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 18ddaf4070..
On Fri, 13 Oct 2017 10:46:22 +0200
Cornelia Huck wrote:
> On Fri, 13 Oct 2017 10:35:06 +0200
> Greg Kurz wrote:
>
> > If a CPU selected with the "cpu" command is hot-unplugged then "info cpus"
> > causes QEMU to exit:
> >
> > (qemu) device_del cpu1
> > (qemu) info cpus
> > qemu:qemu_cpu_ki
On Fri, 13 Oct 2017 10:35:19 +0200
Greg Kurz wrote:
> The current code assumes that only the CPU core object holds a
> reference on each individual CPU object, and happily frees their
> allocated memory when the core is unrealized. This is dangerous
> as some other code can legitimely keep a poin
On Fri, 13 Oct 2017 10:35:31 +0200
Greg Kurz wrote:
> If a CPU selected with the "cpu" command is hot-unplugged then "info cpus"
> causes QEMU to exit:
>
> (qemu) device_del cpu1
> (qemu) info cpus
> qemu:qemu_cpu_kick_thread: No such process
>
> This happens because "cpu" stores the pointer to
Fam Zheng writes:
> The existence of tty in the container seems to urge gcc into colorize
> the output, but the escape chars will clutter the report once turned
> into email replies on patchew. Move -t to debug mode.
>
> Reported-by: Eric Blake
> Signed-off-by: Fam Zheng
I certainly improves
On Fri, 13 Oct 2017 11:10:05 +0200
Stefan Weil wrote:
> Hi,
>
> the German Bundesamt für Sicherheit in der Informationstechnik
> (Federal Office for Information Security) published a study on
> the security of KVM and QEMU:
>
> https://www.bsi.bund.de/DE/Publikationen/Studien/Sicherheitsanalyse
On Fri, 13 Oct 2017 11:21:20 +0200
Igor Mammedov wrote:
> On Fri, 13 Oct 2017 10:35:19 +0200
> Greg Kurz wrote:
>
> > The current code assumes that only the CPU core object holds a
> > reference on each individual CPU object, and happily frees their
> > allocated memory when the core is unreali
On Fri, Oct 13, 2017 at 11:37:08AM +0200, Cornelia Huck wrote:
> On Fri, 13 Oct 2017 11:10:05 +0200
> Stefan Weil wrote:
>
> > Hi,
> >
> > the German Bundesamt für Sicherheit in der Informationstechnik
> > (Federal Office for Information Security) published a study on
> > the security of KVM and
On Thu, Oct 12, 2017 at 09:20:26PM +0530, Pankaj Gupta wrote:
> This patch adds virtio-pmem driver for KVM guest.
> Guest reads the persistent memory range information
> over virtio bus from Qemu and reserves the range
> as persistent memory. Guest also allocates a block
> device correspo
On Fri, 10/13 10:35, Alex Bennée wrote:
>
> Fam Zheng writes:
>
> > The existence of tty in the container seems to urge gcc into colorize
> > the output, but the escape chars will clutter the report once turned
> > into email replies on patchew. Move -t to debug mode.
> >
> > Reported-by: Eric B
On Fri, 13 Oct 2017 10:44:00 +0100
"Daniel P. Berrange" wrote:
> On Fri, Oct 13, 2017 at 11:37:08AM +0200, Cornelia Huck wrote:
> > On Fri, 13 Oct 2017 11:10:05 +0200
> > Stefan Weil wrote:
> >
> > > Hi,
> > >
> > > the German Bundesamt für Sicherheit in der Informationstechnik
> > > (Federa
gt; are available in the git repository at:
>
> git://git.kraxel.org/qemu tags/ui-20171013-pull-request
>
> for you to fetch changes up to 942a35335b2efa2f2997d51eb5142fc9903efe43:
>
> gtk: fix wrong id between texture
On Fri, 13 Oct 2017 11:24:59 +0200
Igor Mammedov wrote:
> On Fri, 13 Oct 2017 10:35:31 +0200
> Greg Kurz wrote:
>
> > If a CPU selected with the "cpu" command is hot-unplugged then "info cpus"
> > causes QEMU to exit:
> >
> > (qemu) device_del cpu1
> > (qemu) info cpus
> > qemu:qemu_cpu_kick_t
Hi William,
Just to confirm: are both src and dest on the same host, using the same
command line options? Then I'm confused why you need block migration
because they share the same image files (for OVMF pflash and ${HDRIVE}).
--
You received this bug notification because you are a member of qemu
The system compiler in OpenBSD is gcc 4.2.1 which is too
old for our needs. If doing 'pkg_add gcc' you can get a
much newer version (4.9.4 in OpenBSD 6.1) which works with
QEMU. This installs binaries with two naming schemes:
$ pkg_info -L gcc | grep bin
/usr/local/bin/ecpp
/usr/local/bin/e
Am 13.10.2017 um 11:37 schrieb Cornelia Huck:
> On Fri, 13 Oct 2017 11:10:05 +0200
> Stefan Weil wrote:
>
>> Hi,
>>
>> the German Bundesamt für Sicherheit in der Informationstechnik
>> (Federal Office for Information Security) published a study on
>> the security of KVM and QEMU:
>>
>> https://www
Ross Lagerwall writes ("Re: [PATCH 3/8] xen: defer call to xen_restrict until
just before os_setup_post"):
> This works for normally starting a VM but doesn't seem to work when
> resuming/migrating.
>
> Here is the order of selected operations when starting a VM normally:
> VNC server runni
>
> On Thu, Oct 12, 2017 at 09:20:26PM +0530, Pankaj Gupta wrote:
> > This patch adds virtio-pmem driver for KVM guest.
> > Guest reads the persistent memory range information
> > over virtio bus from Qemu and reserves the range
> > as persistent memory. Guest also allocates a block
> >
I can reproduce this:
./x86_64-softmmu/qemu-system-x86_64 -nographic -M q35 -drive
id=d,file=/home/vmimages/dummy1,if=none,readonly -device virtio-
blk,id=vb1,drive=d -drive
if=pflash,format=raw,unit=0,file=/usr/share/edk2/ovmf/OVMF_CODE.secboot.fd,readonly
-drive if=pflash,format=raw,unit=1,file=
On 13.10.2017 12:28, Daniel P. Berrange wrote:
> The system compiler in OpenBSD is gcc 4.2.1 which is too
> old for our needs. If doing 'pkg_add gcc' you can get a
> much newer version (4.9.4 in OpenBSD 6.1) which works with
> QEMU. This installs binaries with two naming schemes:
>
> $ pkg_info
On 13.10.2017 12:52, Thomas Huth wrote:
> On 13.10.2017 12:28, Daniel P. Berrange wrote:
>> The system compiler in OpenBSD is gcc 4.2.1 which is too
>> old for our needs. If doing 'pkg_add gcc' you can get a
>> much newer version (4.9.4 in OpenBSD 6.1) which works with
>> QEMU. This installs binari
On 10/11/2017 03:47 PM, Stefan Berger wrote:
EBADMSG was only added to OpenBSD very recently. To make QEMU compilable
on older OpenBSD versions use EMSGSIZE instead when a mismatch between
number of received bytes and message size indicated in the header was
found.
Return -EMSGSIZE and convert a
On 10/13/17 10:44 +0200, Igor Mammedov wrote:
> On Fri, 13 Oct 2017 15:53:26 +0800
> Haozhong Zhang wrote:
>
> > On 10/12/17 17:45 +0200, Paolo Bonzini wrote:
> > > On 12/10/2017 14:45, Haozhong Zhang wrote:
> > > > Basically, QEMU builds two ROMs for guest, /rom@etc/acpi/tables and
> > > > /ro
Hi
On Wed, Oct 11, 2017 at 9:47 PM, Stefan Berger
wrote:
> EBADMSG was only added to OpenBSD very recently. To make QEMU compilable
> on older OpenBSD versions use EMSGSIZE instead when a mismatch between
> number of received bytes and message size indicated in the header was
> found.
>
> Return
i added some debug, and I'm seeing:
blk_pwrite failed for pflash1 0 @ 0 cluster_size=1048576 ret=-5
so that's an EIO.
The EIO is coming from blk_check_byte_request because it's trying to
write a 1MB cluster size chunk, yet the var file is only ~128k
--
You received this bug notification becau
The current code assumes that only the CPU core object holds a
reference on each individual CPU object, and happily frees their
allocated memory when the core is unrealized. This is dangerous
as some other code can legitimely keep a pointer to a CPU if it
calls object_ref(), but it would end up wit
On Fri, Oct 13, 2017 at 12:52:26PM +0200, Thomas Huth wrote:
> On 13.10.2017 12:28, Daniel P. Berrange wrote:
> > The system compiler in OpenBSD is gcc 4.2.1 which is too
> > old for our needs. If doing 'pkg_add gcc' you can get a
> > much newer version (4.9.4 in OpenBSD 6.1) which works with
> > Q
On Fri, Oct 13, 2017 at 12:55:40PM +0200, Thomas Huth wrote:
> On 13.10.2017 12:52, Thomas Huth wrote:
> > On 13.10.2017 12:28, Daniel P. Berrange wrote:
> >> The system compiler in OpenBSD is gcc 4.2.1 which is too
> >> old for our needs. If doing 'pkg_add gcc' you can get a
> >> much newer versio
EBADMSG was only added to OpenBSD very recently. To make QEMU compilable
on older OpenBSD versions use EMSGSIZE instead when a mismatch between
number of received bytes and message size indicated in the header was
found.
Return -EMSGSIZE and convert all other errnos in the same functions to
return
The following changes since commit f90ea7ba7c5ae7010ee0ce062207ae42530f57d6:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20171012'
into staging (2017-10-12 17:06:50 +0100)
are available in the git repository at:
git://github.com/stefanberger/qemu-tpm.git tags/pull-tp
From: Amarnath Valluri
TPMDriverOps inside TPMBackend is not required, as it is supposed to be a class
member. The only possible reason for keeping in TPMBackend was, to get the
backend type in tpm.c where dedicated backend api, tpm_backend_get_type() is
present.
Signed-off-by: Amarnath Valluri
From: Amarnath Valluri
Signed-off-by: Amarnath Valluri
Reviewed-by: Stefan Berger
Reviewed-by: Marc-André Lureau
Signed-off-by: Stefan Berger
---
hw/tpm/tpm_passthrough.c | 64
hw/tpm/tpm_util.c| 25 +++
hw/tpm/tpm_util
From: Amarnath Valluri
This change introduces a new TPM backend driver that can communicate with
swtpm(software TPM emulator) using unix domain socket interface. QEMU talks to
the TPM emulator using QEMU's socket-based chardev backend device.
Swtpm uses two Unix sockets for communications, one f
From: Amarnath Valluri
As Emulator TPM backend uses chardev, tpm cleanup should happen before chardev
similar to other vhost-users.
Signed-off-by: Amarnath Valluri
Reviewed-by: Stefan Berger
Signed-off-by: Stefan Berger
---
tpm.c | 1 -
vl.c | 1 +
2 files changed, 1 insertion(+), 1 deletio
From: Amarnath Valluri
Initialize and free TPMBackend data members in it's own instance_init() and
instance_finalize methods.
Took the opportunity to remove unneeded destroy() method from TpmDriverOps
interface as TPMBackend is a Qemu Object, we can use object_unref() inplace of
tpm_backend_dest
From: Amarnath Valluri
TPM configuration options are backend implementation details and shall not be
part of base TPMBackend object, and these shall not be accessed directly outside
of the class, hence added a new interface method, get_tpm_options() to
TPMDriverOps., which shall be implemented by
From: Amarnath Valluri
buffer reallocation is very unlikely to be backend specific. Hence move inside
the tis.
Signed-off-by: Amarnath Valluri
Reviewed-by: Stefan Berger
Reviewed-by: Marc-André Lureau
Signed-off-by: Stefan Berger
---
backends/tpm.c | 9 -
hw/tpm/tpm_p
From: Amarnath Valluri
This allows backend implementations left optional interface methods.
For mandatory methods assertion checks added.
Took the opportunity to remove unused methods:
- tpm_backend_get_desc()
- TPMDriverOps->handle_startup_error
Signed-off-by: Amarnath Valluri
Reviewed-by:
This patch adds a description of the current TPM support in QEMU
to the specs.
Several public specs are referenced via their landing page on the
trustedcomputinggroup.org website.
Signed-off-by: Stefan Berger
Reviewed-by: Laszlo Ersek
---
docs/specs/tpm.txt | 123 ++
On 13.10.2017 13:38, Daniel P. Berrange wrote:
> On Fri, Oct 13, 2017 at 12:55:40PM +0200, Thomas Huth wrote:
>> On 13.10.2017 12:52, Thomas Huth wrote:
[...]
>> By the way, looks like OpenBSD is also switching to clang by default soon:
>>
>> https://www.phoronix.com/scan.php?page=news_item&px=Open
If a CPU selected with the "cpu" command is hot-unplugged then "info cpus"
causes QEMU to exit:
(qemu) device_del cpu1
(qemu) info cpus
qemu:qemu_cpu_kick_thread: No such process
This happens because "cpu" stores the pointer to the selected CPU into
the monitor structure. When the CPU is hot-unpl
From: Amarnath Valluri
Move thread handling inside TPMBackend, this way backend implementations need
not to maintain their own thread life cycle, instead they needs to implement
'handle_request()' class method that always been called from a thread.
This change made tpm_backend_int.h kind of usel
>>> On 13.10.17 at 13:13, wrote:
> To Jan, Andrew, Stefano and Anthony,
>
> what do you think about allowing QEMU to build the entire guest ACPI
> and letting SeaBIOS to load it? ACPI builder code in hvmloader is
> still there and just bypassed in this case.
Well, if that can be made work in a n
On Sat, Sep 23, 2017 at 02:14:08PM +0300, Manos Pitsidianakis wrote:
> This patch series renames bdrv_co_drain to bdrv_co_drain_begin and adds a new
> bdrv_co_drain_end callback to match bdrv_drained_begin/end and
> drained_begin/end of BdrvChild. This is needed because the throttle driver
> (bl
Hello,
I'm student at Slovak University of Technology in Bratislava and I'm
working on tracing process's memory access. I found out Qemu is good tool
for task such as mine. I would like to generate trace file from process
with two informations: type of access to memory and memory address
accessed.
Hi Ard, Leif,
the current physical memory map of the "virt" machine type doesn't leave
much room for ECAM / MMCONFIG, which limits the number of PCI Express
root ports and downstream ports (each port takes a separate bus number,
and each bus number eats up a chunk of the ECAM area). Also, each por
On Thu, Oct 12, 2017 at 04:05:32PM +0300, Alberto Garcia wrote:
> @@ -522,8 +522,8 @@ int qcow2_get_cluster_offset(BlockDriverState *bs,
> uint64_t offset,
> {
> BDRVQcow2State *s = bs->opaque;
> unsigned int l2_index;
> -uint64_t l1_index, l2_offset, *l2_table;
> -int l1_bits,
This code appears to be unused since its introduction. We need to keep
the state_vmstate field byte in VMState for compatibility reasons.
Signed-off-by: Marc-André Lureau
---
hw/usb/dev-smartcard-reader.c | 23 +--
1 file changed, 1 insertion(+), 22 deletions(-)
diff --git a
[adding qemu-block]
On 10/13/2017 02:37 AM, Vladimir Sementsov-Ogievskiy wrote:
> 077 is unrelated to backup, it's already broken test:
>
> i=1; while check -nbd 077; do echo $((i++)) - OK; done; echo $i - FAIL
>
> failed on 3rd try for me on master
>
>> 077 - output mismatch (see 077.
On 13 October 2017 at 13:51, Laszlo Ersek wrote:
> Hi Ard, Leif,
>
> the current physical memory map of the "virt" machine type doesn't leave
> much room for ECAM / MMCONFIG, which limits the number of PCI Express
> root ports and downstream ports (each port takes a separate bus number,
> and each
Many projects these days are recording progress wrt CII best practices
for FLOOS projects. I filled out a record for QEMU:
https://bestpractices.coreinfrastructure.org/projects/1309
I only looked at the 'Passing' criteria, not considered the 'Silver' and
'Gold' criteria. So if anyone else wants
On Fri, 13 Oct 2017 13:47:51 +0200
Greg Kurz wrote:
> If a CPU selected with the "cpu" command is hot-unplugged then "info cpus"
> causes QEMU to exit:
>
> (qemu) device_del cpu1
> (qemu) info cpus
> qemu:qemu_cpu_kick_thread: No such process
>
> This happens because "cpu" stores the pointer to
On Thu, Oct 12, 2017 at 11:54:56AM +0800, Wei Wang wrote:
> > But I think flushing is very fragile. You will easily run into races
> > if one of the actors gets out of sync and keeps adding data.
> > I think adding an ID in the free vq stream is a more robust
> > approach.
> >
>
> Adding ID to th
1 - 100 of 213 matches
Mail list logo
