On Wed, 10/16 11:26, Fam Zheng wrote:
This series implements feature of shared object building as described in:
http://wiki.qemu.org/Features/Modules
The main idea behind modules is to isolate dependencies on third party
libraries from qemu executables, such as libglusterfs or librbd, so
http://lists.xen.org/archives/html/xen-devel/2013-09/msg03113.html
As said above, In Xen platform, after using upstream qemu, all pci devices can
be unpluged in the windows guest.
In this situation, the windows guest may occur blue screen when VM' user click
the icon of pass-through Graphics
Il 16/10/2013 07:04, Alexey Kardashevskiy ha scritto:
Hi!
Normally on sPAPR platform the IBMVSCSI host bus adapter is used which is
SCSI. So when we want some image to appear as a DVD to the guest
(particularly SLOF - our firmware), we use -device scsi-cd. Or QEMU
extracts this
On 10/10/2013 02:50 PM, Alexey Kardashevskiy wrote:
On 10/09/2013 06:47 PM, Paolo Bonzini wrote:
Il 09/10/2013 09:15, Alexey Kardashevskiy ha scritto:
Sorry for my ignorance (I never ever touched this part of qemu) but how can
you possibly avoid block.c while doing savevm? The qcow2 driver
于 2013/10/15 18:07, mike 写道:
On 10/15/2013 04:58 PM, Kevin Wolf wrote:
Am 15.10.2013 um 05:38 hat mike geschrieben:
On 10/14/2013 10:36 PM, Markus Armbruster wrote:
Mike Qiu qiud...@linux.vnet.ibm.com writes:
Without this, output of 'info block'
scsi0-hd0: /images/f18-ppc64.qcow2 (qcow2)
this patch does solve the problem
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1216368
Title:
unsupported screen resolution crashes sdl-qemu
Status in QEMU:
New
Bug description:
if the
Currently copy_policy isn't used. Recent sheepdog supports erasure coding, which
make use of copy_policy internally, but require client explicitly passing
copy_policy from base inode to newly creately inode for snapshot related
operations.
If connected sheep daemon doesn't utilize copy_policy,
'copies' is actually uint8_t since day one, but request headers and some helper
functions parameterize it as uint32_t for unknown reasons and effectively
reserve 24 bytes for possible future use. This patch explicitly set the correct
for copies and reserve the left bytes.
This is a preparation
This patch set makes use of copy_policy in struct SheepdogInode in order to
support recently introduced erasure coding in sheepdog.
Thanks
Yuan
Wenchao Xia xiaw...@linux.vnet.ibm.com writes:
于 2013/10/15 18:07, mike 写道:
On 10/15/2013 04:58 PM, Kevin Wolf wrote:
Am 15.10.2013 um 05:38 hat mike geschrieben:
On 10/14/2013 10:36 PM, Markus Armbruster wrote:
Mike Qiu qiud...@linux.vnet.ibm.com writes:
Without this, output of 'info
On Wed, Oct 16, 2013 at 10:07:30AM +0800, Asias He wrote:
On Mon, Oct 14, 2013 at 7:14 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Wed, Jul 24, 2013 at 2:50 PM, Anthony Liguori anth...@codemonkey.ws
wrote:
I will be hosting a key signing party at this year's KVM Forum.
On 10/16/2013 05:36 PM, Paolo Bonzini wrote:
Il 16/10/2013 07:04, Alexey Kardashevskiy ha scritto:
Hi!
Normally on sPAPR platform the IBMVSCSI host bus adapter is used which is
SCSI. So when we want some image to appear as a DVD to the guest
(particularly SLOF - our firmware), we use -device
于 2013/10/16 15:47, Markus Armbruster 写道:
Wenchao Xiaxiaw...@linux.vnet.ibm.com writes:
于 2013/10/15 18:07, mike 写道:
On 10/15/2013 04:58 PM, Kevin Wolf wrote:
Am 15.10.2013 um 05:38 hat mike geschrieben:
On 10/14/2013 10:36 PM, Markus Armbruster wrote:
Mike Qiuqiud...@linux.vnet.ibm.com
* rename pci_hole_start to below_4g_mem_size to reflect what is
really passed in and move pci_hole_size calculation inside
i440fx.
* remove ram_size arg from function signature, since it could be
retrieved as below_4g_mem_size + above_4g_mem_size sum,
internally.
Signed-off-by: Igor
* simplify PCI address space mapping into system address space,
replacing code duplication in piix/q53 PCs with helper function
* add fw_cfg 'etc/pcimem64-minimum-address' to allow QEMU reserve
additional address space before 64-bit PCI hole. Which will be
need for resevinig memory hotplug
'etc/pcimem64-minimum-address' will allow QEMU to communicate to BIOS
where PCI memory address space mapping starts in high memory.
Allowing BIOS start mapping 64-bit PCI BARs at address where QEMU
placed this mapping vs. hardcoded value right after highmem RAM.
That will allow QEMU to reserve
Reduce code duplication by moving PCI address space mappings
into a common helper, and reuse code in PIIX and Q35.
Also rename variables to reflect that PCI memory region mappings
are not the same as PCI holes which are programmed by BIOS to
avoid confusion with PCI holes.
PS:
Although keep user
Signed-off-by: Igor Mammedov imamm...@redhat.com
---
hw/nvram/fw_cfg.c |4
include/hw/nvram/fw_cfg.h |7 +++
2 files changed, 7 insertions(+), 4 deletions(-)
diff --git a/hw/nvram/fw_cfg.c b/hw/nvram/fw_cfg.c
index d0820e5..6c31e24 100644
--- a/hw/nvram/fw_cfg.c
+++
On Wed, 10/16 14:26, Fam Zheng wrote:
On Wed, 10/16 11:26, Fam Zheng wrote:
This series implements feature of shared object building as described in:
http://wiki.qemu.org/Features/Modules
The main idea behind modules is to isolate dependencies on third party
libraries from qemu
On 10/16/2013 03:56 PM, Wenchao Xia wrote:
于 2013/10/16 15:47, Markus Armbruster 写道:
Wenchao Xiaxiaw...@linux.vnet.ibm.com writes:
于 2013/10/15 18:07, mike 写道:
On 10/15/2013 04:58 PM, Kevin Wolf wrote:
Am 15.10.2013 um 05:38 hat mike geschrieben:
On 10/14/2013 10:36 PM, Markus Armbruster
Il 16/10/2013 08:30, Gonglei (Arei) ha scritto:
http://lists.xen.org/archives/html/xen-devel/2013-09/msg03113.html
As said above, In Xen platform, after using upstream qemu, all pci devices can
be unpluged in the windows guest.
In this situation, the windows guest may occur blue screen when VM'
On Wed, Oct 16, 2013 at 10:49:10AM +0200, Igor Mammedov wrote:
* simplify PCI address space mapping into system address space,
replacing code duplication in piix/q53 PCs with helper function
I think this does not go far enough.
I was always wondering about PCI hole in QEMU.
Some real PCs
On Wed, 2013-10-16 at 06:30 +, Gonglei (Arei) wrote:
http://lists.xen.org/archives/html/xen-devel/2013-09/msg03113.html
As said above, In Xen platform, after using upstream qemu, all pci devices
can be unpluged in the windows guest.
In this situation, the windows guest may occur blue
On Wed, Oct 16, 2013 at 10:49:14AM +0200, Igor Mammedov wrote:
'etc/pcimem64-minimum-address' will allow QEMU to communicate to BIOS
where PCI memory address space mapping starts in high memory.
Allowing BIOS start mapping 64-bit PCI BARs at address where QEMU
placed this mapping vs.
On Wed, Oct 16, 2013 at 10:49:14AM +0200, Igor Mammedov wrote:
'etc/pcimem64-minimum-address' will allow QEMU to communicate to BIOS
where PCI memory address space mapping starts in high memory.
Allowing BIOS start mapping 64-bit PCI BARs at address where QEMU
placed this mapping vs.
Paolo Bonzini pbonz...@redhat.com writes:
Il 15/10/2013 14:43, Markus Armbruster ha scritto:
Paolo, or maybe Andreas,
To go beyond RFC with this series, I need to explain why isa-i8259 and
kvm-i8259 cannot_instantiate_with_device_add_yet, or drop that. I'd
appreciate your help.
Both
On 10/15/2013 07:00 AM, Alexey Kardashevskiy wrote:
SLOF git commit is e2e8ac901e617573ea383f9cffd136146d0675a4
The main changes are:
* fixed bug with not passing arguments from -append
* client-architecture-support hypercall
* netboot
* USB stack fixes
The full list of changes:
On 16.10.13 at 08:30, Gonglei (Arei) arei.gong...@huawei.com wrote:
--- hvmloader/acpi/Makefile 2013-10-16 11:51:53.0 +0800
+++ hvmloader_new//acpi/Makefile 2013-10-16 11:51:58.0 +0800
@@ -36,18 +36,34 @@
dsdt_anycpu_qemu_xen.asl: dsdt.asl mk_dsdt
awk 'NR 1
Andreas Färber afaer...@suse.de writes:
Hi Markus,
Am 15.10.2013 14:24, schrieb Markus Armbruster:
To go beyond RFC with this series, I need to explain why TYPE_CPU
cannot_instantiate_with_device_add_yet. Would you be so kind and help
me out with a suitable comment?
From what I remember
Andreas Färber afaer...@suse.de writes:
Am 15.10.2013 16:41, schrieb Kevin Wolf:
having two IDE controllers using the same I/O ports won't work,
obviously. So if you would allow -device or device-add for them, you'd
need options to configure the ports at least.
Or a new
Anthony Liguori anth...@codemonkey.ws writes:
On Tue, Oct 15, 2013 at 7:41 AM, Kevin Wolf kw...@redhat.com wrote:
Am 15.10.2013 um 15:31 hat Andreas Färber geschrieben:
Am 15.10.2013 15:21, schrieb Markus Armbruster:
Andreas,
To go beyond RFC with this series, I need to explain why the
On Wed, 2013-10-16 at 10:54 +0100, Jan Beulich wrote:
On 16.10.13 at 08:30, Gonglei (Arei) arei.gong...@huawei.com wrote:
--- hvmloader/acpi/Makefile 2013-10-16 11:51:53.0 +0800
+++ hvmloader_new//acpi/Makefile2013-10-16 11:51:58.0 +0800
@@ -36,18 +36,34 @@
Hi,
I synced to hkp://pgp.mit.edu.
Key ID: 81AB73C8
http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x9CA4ABB381AB73C8
I think the key servers sync to each other anyway,
so it doesn't matter much which one you pick.
cheers,
Gerd
On 10/16/2013 08:54 PM, Alexander Graf wrote:
On 10/15/2013 07:00 AM, Alexey Kardashevskiy wrote:
SLOF git commit is e2e8ac901e617573ea383f9cffd136146d0675a4
The main changes are:
* fixed bug with not passing arguments from -append
* client-architecture-support hypercall
* netboot
* USB
Ian Campbell ian.campb...@citrix.com writes:
On Wed, 2013-10-16 at 10:54 +0100, Jan Beulich wrote:
On 16.10.13 at 08:30, Gonglei (Arei) arei.gong...@huawei.com wrote:
--- hvmloader/acpi/Makefile2013-10-16 11:51:53.0 +0800
+++ hvmloader_new//acpi/Makefile 2013-10-16
On Wed, 2013-10-16 at 12:49 +0200, Markus Armbruster wrote:
Ian Campbell ian.campb...@citrix.com writes:
On Wed, 2013-10-16 at 10:54 +0100, Jan Beulich wrote:
On 16.10.13 at 08:30, Gonglei (Arei) arei.gong...@huawei.com wrote:
--- hvmloader/acpi/Makefile 2013-10-16
Am 16.10.2013 12:00, schrieb Markus Armbruster:
Anthony Liguori anth...@codemonkey.ws writes:
On Tue, Oct 15, 2013 at 7:41 AM, Kevin Wolf kw...@redhat.com wrote:
Am 15.10.2013 um 15:31 hat Andreas Färber geschrieben:
Am 15.10.2013 15:21, schrieb Markus Armbruster:
Andreas,
To go beyond
Am 16.10.2013 um 12:47 schrieb Alexey Kardashevskiy a...@ozlabs.ru:
On 10/16/2013 08:54 PM, Alexander Graf wrote:
On 10/15/2013 07:00 AM, Alexey Kardashevskiy wrote:
SLOF git commit is e2e8ac901e617573ea383f9cffd136146d0675a4
The main changes are:
* fixed bug with not passing arguments
Il 16/10/2013 11:51, Markus Armbruster ha scritto:
Let me try to elaborate, to make sure I understand.
Unlike ordinary ISA devices, the i8259 devices need additional wiring,
done by code.
For instance, board code like pc_q35_init(), pc_piix.c's pc_init1(),
mips_malta_init(), ... wire up
Ian Campbell ian.campb...@citrix.com writes:
On Wed, 2013-10-16 at 12:49 +0200, Markus Armbruster wrote:
Ian Campbell ian.campb...@citrix.com writes:
On Wed, 2013-10-16 at 10:54 +0100, Jan Beulich wrote:
On 16.10.13 at 08:30, Gonglei (Arei) arei.gong...@huawei.com
wrote:
---
On 16.10.13 at 13:10, Markus Armbruster arm...@redhat.com wrote:
Ian Campbell ian.campb...@citrix.com writes:
On Wed, 2013-10-16 at 12:49 +0200, Markus Armbruster wrote:
Ian Campbell ian.campb...@citrix.com writes:
On Wed, 2013-10-16 at 10:54 +0100, Jan Beulich wrote:
On 16.10.13 at
mohamad.ge...@polymtl.ca writes:
Running this gives me:
quote
UST events:
-
None
/quote
Before or after running qemu. What is the mechanism lttng expects to
find out all these events?
Either the user should belong the group tracing, or launch the
lttng-sessiond daemon
mohamad.ge...@gmail.com writes:
* A new format is required to generate definitions for ust tracepoints.
Files ust_events_h.py and ust_events_c.py define common macros, while
new function ust_events_h in events.py does the actual definition of
each tracepoint.
* ust.py generates the
mohamad.ge...@gmail.com writes:
Signed-off-by: Mohamad Gebai mohamad.ge...@polymtl.ca
---
configure |9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/configure b/configure
index 23dbaaf..627054c 100755
--- a/configure
+++ b/configure
@@ -3287,15 +3287,14
mohamad.ge...@gmail.com writes:
Add generation of new files for LTTng ust.
Signed-off-by: Mohamad Gebai mohamad.ge...@polymtl.ca
snip
I did run into problems with the first build which were solved with a
make clean. But I suspect making the Makefile robust to that is more
effort than it's
mohamad.ge...@gmail.com writes:
Signed-off-by: Mohamad Gebai mohamad.ge...@polymtl.ca
snip
Reviewed-by: Alex Bennée a...@bennee.com
--
Alex Bennée
On Wed, 16 Oct 2013 12:29:48 +0300
Michael S. Tsirkin m...@redhat.com wrote:
On Wed, Oct 16, 2013 at 10:49:14AM +0200, Igor Mammedov wrote:
'etc/pcimem64-minimum-address' will allow QEMU to communicate to BIOS
where PCI memory address space mapping starts in high memory.
Allowing BIOS
On Tue, 15 Oct 2013 15:46:57 -0700
Richard Henderson r...@twiddle.net wrote:
On 10/07/2013 03:47 AM, Michael Mueller wrote:
A second reason for using 2k of memory here is to fully represent the
facilities as defined
in the s390x architecture. The SIE state needs it and I want to represent
This patch adds Czech keyboard layout to available keymap files
and Makefile.
Signed-off-by: Jan Krupa jkr...@suse.com
---
Makefile |2 +-
pc-bios/keymaps/cz | 94
2 files changed, 95 insertions(+), 1 deletions(-)
create mode
This patch adds support for Unicode symbols in keymap files. This
feature was already used in some keyboard layouts in QEMU generated
from XKB (e.g. Arabic) but it wasn't implemented in QEMU source code.
There is no need for check of validity of the hex string after U character
because strtol
This patch adds all missing characters used in regional keymap
files which already exist in QEMU. I checked for the missing
characters by going through all of the keymaps and matching that
with records in vnc_keysym.h. If the key wasn't found I looked
it up in libxkbcommon library [1]. If I
I tried to create keymap for Czech keyboard for QEMU. I found out that
some of the keysyms are missing. I added those specific symbols to QEMU
VNC header files plus wrote the whole keyboard layout. I also added missing
symbols for already existing keymaps in QEMU.
Another issue I hit during
This patch adds missing Czech characters to the VNC keysym table.
Signed-off-by: Jan Krupa jkr...@suse.com
---
ui/vnc_keysym.h |8
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/ui/vnc_keysym.h b/ui/vnc_keysym.h
index 6250bec..72c01d1 100644
--- a/ui/vnc_keysym.h
+++
Il 16/10/2013 14:59, Christian Borntraeger ha scritto:
Now, newer KVMs have the ability to create subdevices of a KVM guest (e.g. an
in kernel
kvm interrupt controller) with the following ioctl:
#define KVM_CREATE_DEVICE _IOWR(KVMIO, 0xe0, struct
kvm_create_device)
qemu can
Commit 4f8a066b5fc254eeaabbbde56ba4f5b29cc68fdf (blockdev: Remove IF_*
check for read-only blockdev_init) added a usage of bdrv_is_read_only()
to sd_init(), which is called for versatilepb, versatileab and
xilinx-zynq-a9 machines among others with NULL argument by default,
causing the new qom-test
On Wed, Oct 16, 2013 at 02:19:13PM +0200, Igor Mammedov wrote:
On Wed, 16 Oct 2013 12:29:48 +0300
Michael S. Tsirkin m...@redhat.com wrote:
On Wed, Oct 16, 2013 at 10:49:14AM +0200, Igor Mammedov wrote:
'etc/pcimem64-minimum-address' will allow QEMU to communicate to BIOS
where PCI
On 10/01/2013 12:19:51 PM, Richard Henderson wrote:
On 09/25/2013 12:27 PM, Richard Henderson wrote:
Signed-off-by: Richard Henderson r...@twiddle.net
---
Since the GCC compile farm took their hppa machine off-line, I have
no way
to test this port anymore. Worse, I can't find any
The comment preceding the float64_to_uint64 routine suggests that
the implementation is broken. And this is, indeed, the case.
This patch properly implements the conversion of a 64-bit floating
point number to an unsigned, 64 bit integer.
Note that the patch does not pass scripts/checkpatch.pl
dropping valgrind devel since its subscribers only...
On 16/10/13 15:06, Paolo Bonzini wrote:
Il 16/10/2013 14:59, Christian Borntraeger ha scritto:
Now, newer KVMs have the ability to create subdevices of a KVM guest (e.g.
an in kernel
kvm interrupt controller) with the following ioctl:
On 10/16/2013 06:59 AM, Rob Landley wrote:
But there's no qemu system emulation for hppa or parisc. Bootstrapping a
system
doesn't help if qemu can't actually emulate a board to run it on. (Am I
missing
something?)
A cross-compile of qemu would have made sure that there are no
compilation
This patch series adds a significant number of system calls and mips/arm
support for bsd-user. In its current state it can emulate most
FreeBSD mips/mips64 and arm target binaries on a x86 host in a simple
chroot environment. (see https://wiki.freebsd.org/QemuUserModeHowTo for
the details.)
Update FreeBSD system call numbers in freebsd/syscall_nr.h.
Signed-off-by: Stacey Son s...@freebsd.org
---
bsd-user/freebsd/syscall_nr.h | 813 ++---
1 files changed, 445 insertions(+), 368 deletions(-)
diff --git a/bsd-user/freebsd/syscall_nr.h
This change moves host OS and arch dependent code for the sysarch system
call related to the -strace functionality into the appropriate HOST_ABI_DIR
and TARGET_ABI_DIR directories.
Signed-off-by: Stacey Son s...@freebsd.org
---
bsd-user/arm/syscall.h | 36 +++
This change moves the system call handler for sysctl(2) and sysarch(2)
from syscall.c to the OS and arch dependent directories. This
eliminates many of the #ifdef's in syscall.c. These system call
handlers are now located in the host os and target arch directories.
Signed-off-by: Stacey Son
This change adds HOST_ABI_DIR (similar to TARGET_ABI_DIR) so the various
BSD OS dependent code can be seperated into its own directories rather
than using #ifdef's.
Signed-off-by: Stacey Son s...@freebsd.org
---
Makefile.target |3 ++-
configure | 11 +++
2 files changed, 13
This change adds support or stubs for file system (except stat) related system
calls including read(2), pread(2), readv(2), write(2), pwrite(2), writev(2),
pwritev(2), open(2), openat(2), close(2), closefrom(2), revoke(2), access(2),
eaccess(2), faccessat(2), chdir(2), fchdir(2), rename(2),
This change adds support or stubs for stat, directory, and file control related
system calls including stat(2), lstat(2), fstat(2), fstatat(2), nstat(),
nfstat(),
nlstat(), getfh(2), lgetfh(2), fhopen(2), fhstat(2), fhstatfs(2), statfs(2),
fstatfs(2), getfsstat(2), getdents(2), getdirentries(2),
This change adds support or stubs for memory management related system calls
including mmap(2), munmap(2), mprotect(2), msync(2), mlock(2), munlock(2),
mlockall(2), munlockall(2), madvise(2), minherit(2), mincore(2), shm_open(2),
shm_unlink(2), shmget(2), shmctl(2), shmat(2), shmdt(2), vadvise(),
This change adds support or stubs for socket related system calls including
accept(2), bind(2), connect(2), getpeername(2), getsockname(2), getsockopt(2),
setsockopt(2), listen(2), recvfrom(2), recvmsg(2), sendmsg(2), sendto(2),
socket(2), socketpair(2), shutdown(2), setfib(2), sctp_peeloff(2),
This change adds arm-bsd-user, mips-bsd-user, mips64-bsd-user,
mips64el-bsd-user, and mipsel-bsd-user as --target-list options to configure.
Signed-off-by: Stacey Son s...@freebsd.org
---
default-configs/arm-bsd-user.mak |3 +++
default-configs/mips-bsd-user.mak |1 +
This change add support for extended attribute and Access Control List
(ACL) related system calls including extattrctl(), extattr_set_file(2),
extattr_delete_file(2), extattr_set_fd(2), extattr_get_fd(2),
extattr_delete_fd(2), extattr_get_link(2), extattr_set_link(2),
extattr_delete_link(2),
Hi Xiangyouxie,
I personally haven't tried to solve the problem as yet but I've been in contact
with Anders Fudali who was able to find the issue with the help of one of his
developers.
See below for his comments. I've love to hear from any of the devs that can
explain the issue further
Il 16/10/2013 16:23, Christian Borntraeger ha scritto:
That would work, but it would change the ioctl number of KVM_*_DEVICE_ADDR,
due to the changed size of struct kvm_device_attr. We would then need compat
handlers in the kernel.
Actually I did that on purpose :) but perhaps you're right
Il 15/10/2013 22:17, Michael S. Tsirkin ha scritto:
OK so I can interpret this in 2 ways wrt bridge hotplug:
- it's in shape for 1.7 except the migration which should use
subsections (and needs cross-version testing)
- it's not in shape for 1.7
Can you tell me which it is please?
If
s...@freebsd.org writes:
This change adds arm-bsd-user, mips-bsd-user, mips64-bsd-user,
mips64el-bsd-user, and mipsel-bsd-user as --target-list options to configure.
Signed-off-by: Stacey Son s...@freebsd.org
---
snip
new file mode 100644
index 000..46d4aa2
--- /dev/null
+++
s...@freebsd.org writes:
This patch series adds a significant number of system calls and mips/arm
support for bsd-user. In its current state it can emulate most
FreeBSD mips/mips64 and arm target binaries on a x86 host in a simple
chroot environment. (see
On Oct 16, 2013, at 10:27 AM, Alex Bennée alex.ben...@linaro.org wrote:
s...@freebsd.org writes:
This patch series adds a significant number of system calls and mips/arm
support for bsd-user. In its current state it can emulate most
FreeBSD mips/mips64 and arm target binaries on a x86
On Wed, Oct 16, 2013 at 02:59:47PM +0200, Christian Borntraeger wrote:
Folks,
from time to time I update valgrind or qemu to work reasonably well
with KVM.
Now, newer KVMs have the ability to create subdevices of a KVM guest (e.g. an
in kernel
kvm interrupt controller) with the
The arm code came from another source as noted in the cover letter. It could
use a lot more work.
-stacey.
On Oct 16, 2013, at 10:38 AM, Alex Bennée alex.ben...@linaro.org wrote:
s...@freebsd.org writes:
This change moves the cpu initialization and main loop code from
main.c to the
s...@freebsd.org writes:
This change moves the cpu initialization and main loop code from
main.c to the OS and arch dependent directories. This eliminates
many of the #ifdef's in main.c. The cpu initialization and loop
code is now located in the arch directory along with target arch
support
ui/vnc.c:vnc_display_open() and spice-server/server/reds.c:do_spice_init()
are both calling sasl_server_init(). If spice_server_set_sasl_appname()
hasn't been called, spice-server will call it with spice as an appname,
causing cyrus-sasl to try to use a /etc/sasl2/spice.conf config file rather
On Oct 16, 2013, at 10:22 AM, Alex Bennée alex.ben...@linaro.org wrote:
s...@freebsd.org writes:
This change adds arm-bsd-user, mips-bsd-user, mips64-bsd-user,
mips64el-bsd-user, and mipsel-bsd-user as --target-list options to configure.
Signed-off-by: Stacey Son s...@freebsd.org
---
Paolo Bonzini pbonz...@redhat.com writes:
Il 16/10/2013 11:51, Markus Armbruster ha scritto:
Let me try to elaborate, to make sure I understand.
Unlike ordinary ISA devices, the i8259 devices need additional wiring,
done by code.
For instance, board code like pc_q35_init(), pc_piix.c's
Il 16/10/2013 05:26, Fam Zheng ha scritto:
This series implements feature of shared object building as described in:
http://wiki.qemu.org/Features/Modules
The main idea behind modules is to isolate dependencies on third party
libraries from qemu executables, such as libglusterfs or librbd,
Il 16/10/2013 18:21, BALATON Zoltan ha scritto:
On Wed, 16 Oct 2013, Paolo Bonzini wrote:
Il 16/10/2013 11:51, Markus Armbruster ha scritto:
Let me try to elaborate, to make sure I understand.
Unlike ordinary ISA devices, the i8259 devices need additional wiring,
done by code.
For
On 16 October 2013 15:37, Stacey Son s...@freebsd.org wrote:
This change adds arm-bsd-user, mips-bsd-user, mips64-bsd-user,
mips64el-bsd-user, and mipsel-bsd-user as --target-list options to configure.
diff --git a/default-configs/arm-bsd-user.mak
b/default-configs/arm-bsd-user.mak
new file
On Wed, 16 Oct 2013, Paolo Bonzini wrote:
Il 16/10/2013 11:51, Markus Armbruster ha scritto:
Let me try to elaborate, to make sure I understand.
Unlike ordinary ISA devices, the i8259 devices need additional wiring,
done by code.
For instance, board code like pc_q35_init(), pc_piix.c's
On 16 October 2013 15:36, Stacey Son s...@freebsd.org wrote:
This patch series adds a significant number of system calls and mips/arm
support for bsd-user. In its current state it can emulate most
FreeBSD mips/mips64 and arm target binaries on a x86 host in a simple
chroot environment. (see
On 16 October 2013 16:22, Alex Bennée alex.ben...@linaro.org wrote:
Given how little is typically in the -user .mak fragments I wonder what
the point of them is. Should the build fall-back to a generic .mak
fragment if there is no special config for a given build target?
At the moment our list
On 16 October 2013 16:46, Stacey Son s...@freebsd.org wrote:
The arm code came from another source as noted in the cover letter. It could
use a lot more work.
Possibly better to leave it out of this initial patch set and submit
it separately
later then?
-- PMM
On Tue, Oct 15, 2013 at 1:17 PM, Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Oct 15, 2013 at 09:27:33AM -0700, Anthony Liguori wrote:
Paolo Bonzini pbonz...@redhat.com writes:
Il 15/10/2013 16:35, Michael S. Tsirkin ha scritto:
On Tue, Oct 15, 2013 at 04:31:31PM +0200, Paolo Bonzini
This lock does not protect anything that the BQL does not already
protect. Furthermore, with -nodefaults and no monitor, the mutex
is not initialized but monitor_protocol_event_queue is called
anyway, which causes a crash under mingw (and only works by luck.
under Linux or other POSIX OSes).
Folks,
from time to time I update valgrind or qemu to work reasonably well
with KVM.
Now, newer KVMs have the ability to create subdevices of a KVM guest (e.g. an
in kernel
kvm interrupt controller) with the following ioctl:
#define KVM_CREATE_DEVICE _IOWR(KVMIO, 0xe0, struct
On Mon, Oct 14, 2013 at 7:14 PM, Stefan Hajnoczi stefa...@gmail.com wrote:
On Wed, Jul 24, 2013 at 2:50 PM, Anthony Liguori anth...@codemonkey.ws
wrote:
I will be hosting a key signing party at this year's KVM Forum.
http://wiki.qemu.org/KeySigningParty2013
keyserver.cryptnet.net
On Wed, Oct 16, 2013 at 07:17:08PM +0200, Paolo Bonzini wrote:
This lock does not protect anything that the BQL does not already
protect. Furthermore, with -nodefaults and no monitor, the mutex
is not initialized but monitor_protocol_event_queue is called
anyway, which causes a crash under
On Wed, Oct 16, 2013 at 3:00 AM, Markus Armbruster arm...@redhat.com wrote:
Anthony Liguori anth...@codemonkey.ws writes:
On Tue, Oct 15, 2013 at 7:41 AM, Kevin Wolf kw...@redhat.com wrote:
Am 15.10.2013 um 15:31 hat Andreas Färber geschrieben:
Am 15.10.2013 15:21, schrieb Markus Armbruster:
On Wed, Oct 16, 2013 at 09:38:29AM -0700, Anthony Liguori wrote:
On Tue, Oct 15, 2013 at 1:17 PM, Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Oct 15, 2013 at 09:27:33AM -0700, Anthony Liguori wrote:
Paolo Bonzini pbonz...@redhat.com writes:
Il 15/10/2013 16:35, Michael S. Tsirkin
On Wed, Oct 16, 2013 at 11:18 AM, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, Oct 16, 2013 at 09:38:29AM -0700, Anthony Liguori wrote:
On Tue, Oct 15, 2013 at 1:17 PM, Michael S. Tsirkin m...@redhat.com wrote:
On Tue, Oct 15, 2013 at 09:27:33AM -0700, Anthony Liguori wrote:
Paolo
On Wed, Oct 16, 2013 at 11:18:42AM -0700, Anthony Liguori wrote:
On Wed, Oct 16, 2013 at 11:18 AM, Michael S. Tsirkin m...@redhat.com wrote:
On Wed, Oct 16, 2013 at 09:38:29AM -0700, Anthony Liguori wrote:
On Tue, Oct 15, 2013 at 1:17 PM, Michael S. Tsirkin m...@redhat.com
wrote:
On
On 2013-10-15 04:41, Fam Zheng wrote:
If the block job completes too fast, the test can fail. Change the
numbers so the qmp events are more stably captured by the script.
A sleep is removed for the same reason.
Signed-off-by: Fam Zheng f...@redhat.com
---
tests/qemu-iotests/030 | 11
1 - 100 of 142 matches
Mail list logo
