Re: [Qemu-devel] [PATCH 2/2] configure: Make AVX2 test robust to non-ELF systems

Am 19.06.2016 um 00:05 schrieb Peter Maydell: > From: Peter Maydell > > The AVX2 optimization test assumes that the object format > is ELF and the system has the readelf utility. If this isn't > true then configure might fail or emit a warning (since in > a pipe "foo |

Re: [Qemu-devel] [PATCH 1/2] configure: Improve usermode relocation linker option probe

Am 19.06.2016 um 00:05 schrieb Peter Maydell: > From: Peter Maydell > > The probe we do to determine what flags to use to make the usermode > executables use a non-default text address has some flaws: > * we run it even if we're not building the user binaries > * we

[Qemu-devel] [Bug 1594069] [NEW] SIMD instructions translated to scalar host instructions

Public bug reported: SIMD instructions inside the guest (NEON, MMX, SSE, SSE2, AVX) are translated to scalar instructions on the host instead of SIMD instructions. It appears that there have been a few efforts to rectify this [1], and even a submitted patch series, but all discussion has

Re: [Qemu-devel] [QEMU 7/7] migration: skip free pages during live migration

On Mon, Jun 13, 2016 at 06:16:49PM +0800, Liang Li wrote: > After sending out the request for free pages, live migration > process will start without waiting for the free page bitmap is > ready. If the free page bitmap is not ready when doing the 1st > migration_bitmap_sync() after

Re: [Qemu-devel] [QEMU 6/7] kvm: Add two new arch specific functions

On Mon, Jun 13, 2016 at 06:16:48PM +0800, Liang Li wrote: > Add a new function to get the vm's max pfn and a new function > to filter out the holes to get a tight free page bitmap. > They are implemented on X86, and all the arches should implement > them for live migration optimization. > >

Re: [Qemu-devel] [QEMU 4/7] balloon: get free page info from guest

On Mon, Jun 13, 2016 at 06:16:46PM +0800, Liang Li wrote: > Add a new feature to get the free page information from guest, > the free page information is saved in a bitmap. Please note that > 'free page' only means these pages are free before the request, > some of the pages will become no free

Re: [Qemu-devel] [QEMU 2/7] virtio-balloon: add drop cache support

On Mon, Jun 13, 2016 at 06:16:44PM +0800, Liang Li wrote: > virtio-balloon can make use of the amount of free memory to determine > the amount of memory to be filled in the balloon, but the amount of > free memory will be effected by the page cache, which can be reclaimed. > Drop the cache before

Re: [Qemu-devel] [QEMU 1/7] balloon: speed up inflating & deflating process

On Mon, Jun 13, 2016 at 06:16:43PM +0800, Liang Li wrote: > The implementation of the current virtio-balloon is not very efficient, > Bellow is test result of time spends on inflating the balloon to 3GB of > a 4GB idle guest: > > a. allocating pages (6.5%, 103ms) > b. sending PFNs to host (68.3%,

Re: [Qemu-devel] [RFC 0/9] Introduce light weight PC platform pc-lite

On Fri, Jun 17, 2016 at 04:14:08AM -0400, Chao Peng wrote: > - it is FAST; Any numbers to demonstrate just how fast it is and fast at what? > -- > 1.8.3.1

Re: [Qemu-devel] [PATCH 4/5] x86: Allow physical address bits to be set

On Fri, Jun 17, 2016 at 03:38:53PM +0200, Paolo Bonzini wrote: > Making the guest's phys-bits larger than host-phys-bits would be okay if > you reserve the area in the e820 and assume the guest doesn't touch it. How would it touch it if there's no RAM there? PCI BARs is the only thing that comes

Re: [Qemu-devel] [PATCH RFC 3/4] range: Drop the previous commit's trickery

On Wed, Jun 15, 2016 at 10:41:49PM +0200, Markus Armbruster wrote: > Signed-off-by: Markus Armbruster Agree with Eric about squashing this. Reviewed-by: Michael S. Tsirkin > --- > include/qemu/range.h | 21 - > util/range.c | 1

Re: [Qemu-devel] [PATCH RFC 2/4] range: Eliminate direct Range member access

On Wed, Jun 15, 2016 at 10:41:48PM +0200, Markus Armbruster wrote: > Users of struct Range mess liberally with its members, which makes > refactoring hard. Create a set of methods, and convert all users to > call them instead of accessing members. The methods have carefully > worded contracts,

Re: [Qemu-devel] [PATCH RFC 4/4] range: Replace internal representation of Range

On Wed, Jun 15, 2016 at 10:41:50PM +0200, Markus Armbruster wrote: > Range represents a range as follows. Member @start is the inclusive > lower bound, member @end is the exclusive upper bound. Zero @end is > special: if @start is also zero, the range is empty, else @end is to > be interpreted

Re: [Qemu-devel] [PATCH RFC 1/4] log: Clean up misuse of Range for -dfilter

On Wed, Jun 15, 2016 at 10:41:47PM +0200, Markus Armbruster wrote: > Range encodes an integer interval [a,b] as { begin = a, end = b + 1 }, > where a \in [0,2^64-1] and b \in [1,2^64]. Thus, zero end is to be > interpreted as 2^64. > > The implementation of -dfilter (commit 3514552) uses Range >

[Qemu-devel] [PATCH] ppc: Improve emulation of THRM registers

The 75x and 74xx processors have some thermal monitoring SPRs that some OSes such as MacOS do use. Our current "dumb" implementation isn't good enough and will cause some versions of MacOS to hang during boot. This lifts an improved emulation from MacOnLinux and adapts it to qemu, thus fixing the

[Qemu-devel] [PATCH 4/7] This patch adds initial user-virtualization support for the DRM (type 'd') IOCTLs in linux. With it and a corresponding architecture chroot (say aarch64), I am able to success

1. It will only work with open drivers as their IOCTLs are documented. 2. i965+ is only supported. That is any haswell, ivybridge, etc. GPU will work. 3. X doesn't start yet, though this patch eliminates all the visible unsupported DRM IOCTL calls as observed by setting QEMU_STRACE=1. 4. Intel

[Qemu-devel] [PATCH 1/7] Add initial x86_64 signal handlers

Note that x86_64 systems only offer the _rt signal handler variants, so the legacy signal handlers remain unimplemented on this platform. Signed-off-by: Timothy Pearson --- linux-user/signal.c | 302 +++- 1 file

[Qemu-devel] [Bug 1591611] Re: chroot using qemu-x86_64-static fails on ppc64el

Patch series sent to mailing list here: http://lists.nongnu.org/archive/html/qemu-devel/2016-06/msg05334.html In particular, this patch handles the original signal handler problem: http://lists.nongnu.org/archive/html/qemu-devel/2016-06/msg05335.html ** Changed in: qemu Status: New => In

[Qemu-devel] [PATCH 3/7] Pass select() arguments directly to do_select() on x86 platforms

This matches the calling conventions in the Linux kernel and resolves select() hangs on i386/x86_64 guests. Signed-off-by: Timothy Pearson --- linux-user/syscall.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/linux-user/syscall.c

[Qemu-devel] [PATCH 7/7] Add ALSA ioctls

Tested with ExtremeTuxRacer in guest with HDMI audio sink on host Signed-off-by: Timothy Pearson --- linux-user/ioctls.h| 72 linux-user/syscall.c | 1 + linux-user/syscall_defs.h | 73 linux-user/syscall_types.h | 273

[Qemu-devel] [PATCH 7/7] Add ALSA ioctls

Tested with ExtremeTuxRacer in guest with HDMI audio sink on host Signed-off-by: Timothy Pearson --- linux-user/ioctls.h| 72 linux-user/syscall.c | 1 + linux-user/syscall_defs.h | 73 linux-user/syscall_types.h | 273

[Qemu-devel] [PATCH 6/7] Add radeon DRM interface ioctls

Tested on a Radeon R290X with multiple 3D applications. Signed-off-by: Timothy Pearson --- linux-user/ioctls.h| 45 +- linux-user/syscall.c | 15 linux-user/syscall_defs.h | 45 +- linux-user/syscall_types.h | 209

[Qemu-devel] [PATCH 2/7] QEMU does not currently support host pages that are larger than guest pages, likely due to glibc using fixed mmap requests.

Attempting to use host pages larger than the guest leads to alignment errors during ELF load in the best case, and an initialization failure inside NPTL in the worst case, causing all fork() requests inside the guest to fail. Warn when thread space cannot be set up, and suggest reducing host page

[Qemu-devel] [PATCH 6/7] Add radeon DRM interface ioctls

Tested on a Radeon R290X with multiple 3D applications. Signed-off-by: Timothy Pearson --- linux-user/ioctls.h| 45 +- linux-user/syscall.c | 15 linux-user/syscall_defs.h | 45 +- linux-user/syscall_types.h | 209

[Qemu-devel] RE-SEND: [PATCH 0/7] Enable multimedia applications on x86_64 guests

Note: This is a resend due to my prior messages being word-wrapped accidentally. Apologies for the duplicates! -- With increasing interest in non-x86 architectures (e.g. ARM64, POWER8), there is a growing desire to execute

[Qemu-devel] [PATCH 4/7] This patch adds initial user-virtualization support for the DRM (type 'd') IOCTLs in linux. With it and a corresponding architecture chroot (say aarch64), I am able to success

1. It will only work with open drivers as their IOCTLs are documented. 2. i965+ is only supported. That is any haswell, ivybridge, etc. GPU will work. 3. X doesn't start yet, though this patch eliminates all the visible unsupported DRM IOCTL calls as observed by setting QEMU_STRACE=1. 4. Intel

[Qemu-devel] [PATCH 5/7] TIOCGPTN and related terminal control ioctls were not converted to the guest ioctl format on x86_64 targets. Convert these ioctls to enable terminal functionality on x86_64 gu

Signed-off-by: Timothy Pearson --- linux-user/x86_64/termbits.h | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/linux-user/x86_64/termbits.h b/linux-user/x86_64/termbits.h index 1c3445c..5fc4639 100644 ---

[Qemu-devel] [PATCH 5/7] TIOCGPTN and related terminal control ioctls were not converted to the guest ioctl format on x86_64 targets. Convert these ioctls to enable terminal functionality on x86_64 gu

Signed-off-by: Timothy Pearson --- linux-user/x86_64/termbits.h | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/linux-user/x86_64/termbits.h b/linux-user/x86_64/termbits.h index 1c3445c..5fc4639 100644 ---

[Qemu-devel] [PATCH 3/7] Pass select() arguments directly to do_select() on x86 platforms

This matches the calling conventions in the Linux kernel and resolves select() hangs on i386/x86_64 guests. Signed-off-by: Timothy Pearson --- linux-user/syscall.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/linux-user/syscall.c

[Qemu-devel] [PATCH 2/7] QEMU does not currently support host pages that are larger than guest pages, likely due to glibc using fixed mmap requests.

Attempting to use host pages larger than the guest leads to alignment errors during ELF load in the best case, and an initialization failure inside NPTL in the worst case, causing all fork() requests inside the guest to fail. Warn when thread space cannot be set up, and suggest reducing host page

[Qemu-devel] [PATCH 1/7] Add initial x86_64 signal handlers

Note that x86_64 systems only offer the _rt signal handler variants, so the legacy signal handlers remain unimplemented on this platform. Signed-off-by: Timothy Pearson --- linux-user/signal.c | 302 +++- 1 file

[Qemu-devel] [PATCH 0/7] Enable multimedia applications on x86_64 guests

With increasing interest in non-x86 architectures (e.g. ARM64, POWER8), there is a growing desire to execute legacy x86 applications that cannot be recompiled on these new architectures. This series enables 3D multimedia applications (e.g. games) to function correctly on an emulated x86_64 host

Re: [Qemu-devel] [Qemu-ppc] [PATCH 01/10] ppc: Fix rfi/rfid/hrfi/... emulation

On Fri, 2016-06-17 at 16:32 +0200, Cédric Le Goater wrote: > The instruction set PPC_POWER_BR contains nearly all the deleted  > instructions from isa2. rfi is not part of it and should. Also, only  > the cpus "PowerPC 601*" make a use of it in their insns_flags. Are you sure those arent the old

Re: [Qemu-devel] [Qemu-ppc] [PATCH 01/10] ppc: Fix rfi/rfid/hrfi/... emulation

On Fri, 2016-06-17 at 13:02 +0200, Thomas Huth wrote: > According to the PPC970FX user manual that I have: > > "The 970FX does not provide support for the following optional or >  obsolete instructions (or instruction forms). >  Attempted use of these will result in an illegal instruction type >  

Re: [Qemu-devel] [Qemu-ppc] [PATCH 01/10] ppc: Fix rfi/rfid/hrfi/... emulation

<1465795496-15071-2-git-send-email-...@kaod.org> <20160616010702.gi28...@voom.fritz.box> <20160617022731.ga19...@voom.fritz.box> <57639095.5010...@kaod.org> <576392b1.6030...@kaod.org>

[Qemu-devel] [PATCH 0/2] configure: Avoid warnings on OSX

From: Peter Maydell This patchset fixes a couple of minor issues with configure tests that result in configure printing out warning messages as it runs on OSX. (The warnings don't result in configure actually failing.) Both reported by Stefan Weil. Peter Maydell (2):

[Qemu-devel] [PATCH 2/2] configure: Make AVX2 test robust to non-ELF systems

From: Peter Maydell The AVX2 optimization test assumes that the object format is ELF and the system has the readelf utility. If this isn't true then configure might fail or emit a warning (since in a pipe "foo | bar >/dev/null 2>&1" does not redirect the stderr of foo,

[Qemu-devel] [PATCH 1/2] configure: Improve usermode relocation linker option probe

From: Peter Maydell The probe we do to determine what flags to use to make the usermode executables use a non-default text address has some flaws: * we run it even if we're not building the user binaries * we don't expect "ld --verbose" to fail The combination of

[Qemu-devel] [Bug 1593605] Re: windows2008r2 boot failed with uefi

... In addition to what I said above in comment #9 (which stands), the technical problem with turning the memory allocation in question into AcpiNVS type is that it would prevent *all* OSes from reusing the area. It would prevent the Windows 7 memory manager from deallocating page #0 (thereby

Re: [Qemu-devel] OSX 10.7 build failure

On 18 June 2016 at 21:51, Peter Maydell wrote: > On 18 June 2016 at 20:09, Stefan Weil wrote: >> Here is a list of problems which I noticed: >> >> configure: >> >> readelf: Error: Not an ELF file - it has the wrong magic bytes at >> the start > >

[Qemu-devel] [PATCH] i386: pci-assign: Fix MSI-X table size

The current code creates a whole page mmio region for the MSI-X table size. However, the page containing the MSI-X table may contain other registers not related to MSI-X. Creating an mmio region for the whole page masks such registers and may break drivers in the guest OS. Since maximal number

Re: [Qemu-devel] OSX 10.7 build failure

On 18 June 2016 at 20:09, Stefan Weil wrote: > Here is a list of problems which I noticed: > > configure: > > readelf: Error: Not an ELF file - it has the wrong magic bytes at > the start We should make our configure test correctly send stderr to /dev/null, since "not an

Re: [Qemu-devel] [PATCH] gt64xxx: access right I/O port when activating byte swapping

Hi Aurélien, Le 20/05/2016 à 21:56, Aurelien Jarno a écrit : On 2016-05-20 15:05, Hervé Poussineau wrote: Incidentally, this fixes YAMON on big endian guest. Signed-off-by: Hervé Poussineau --- hw/mips/gt64xxx_pci.c | 62

Re: [Qemu-devel] [PATCH] configure: Don't run AVX optimization requirement check on Mac OS X

On 18 June 2016 at 20:49, Stefan Weil wrote: > The test currently only works with ELF and requires readelf, > but OS X does not use ELF binaries. > > Signed-off-by: Stefan Weil > --- > configure | 7 +++ > 1 file changed, 7 insertions(+) Would be neater

[Qemu-devel] [PATCH v8 08/12] target-avr: adding instruction translation

Signed-off-by: Michael Rolnik --- target-avr/translate-inst.c | 2629 +++ target-avr/translate.h | 119 ++ 2 files changed, 2748 insertions(+) create mode 100644 target-avr/translate-inst.c create mode 100644

[Qemu-devel] [PATCH v8 12/12] target-avr: adding maintainer

Signed-off-by: Michael Rolnik --- MAINTAINERS | 6 ++ 1 file changed, 6 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index fe2279e..6a4e398 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -110,6 +110,12 @@ F: disas/arm.c F: disas/arm-a64.cc F: disas/libvixl/

[Qemu-devel] [PATCH v8 05/12] target-avr: adding AVR interrupt handling

Signed-off-by: Michael Rolnik --- target-avr/helper.c | 59 - 1 file changed, 58 insertions(+), 1 deletion(-) diff --git a/target-avr/helper.c b/target-avr/helper.c index ad8f83e..f96fa27 100644 --- a/target-avr/helper.c +++

[Qemu-devel] [PATCH v8 09/12] target-avr: updating translate.c to use instructions translation

Signed-off-by: Michael Rolnik --- target-avr/Makefile.objs | 4 +- target-avr/translate.c | 137 --- 2 files changed, 61 insertions(+), 80 deletions(-) diff --git a/target-avr/Makefile.objs b/target-avr/Makefile.objs index

[Qemu-devel] [PATCH v8 10/12] target-avr: saving sreg, rampD, rampX, rampY, rampD, eind in HW representation saving cpu features

Signed-off-by: Michael Rolnik --- target-avr/cpu-qom.h | 2 +- target-avr/cpu.c | 2 +- target-avr/machine.c | 107 --- 3 files changed, 87 insertions(+), 24 deletions(-) diff --git a/target-avr/cpu-qom.h

[Qemu-devel] [PATCH v8 11/12] target-avr: decoder generator. currently not used by the build, can be used manually

Signed-off-by: Michael Rolnik --- target-avr/cpugen/CMakeLists.txt | 38 +++ target-avr/cpugen/README.md| 17 ++ target-avr/cpugen/cpu/avr.yaml | 214 ++ target-avr/cpugen/src/CMakeLists.txt | 62

[Qemu-devel] [PATCH v8 06/12] target-avr: adding helpers for IN, OUT, SLEEP, WBR & unsupported instructions

Signed-off-by: Michael Rolnik --- target-avr/helper.c | 147 target-avr/helper.h | 5 ++ 2 files changed, 142 insertions(+), 10 deletions(-) diff --git a/target-avr/helper.c b/target-avr/helper.c index f96fa27..44d8f44

[Qemu-devel] [PATCH v8 01/12] target-avr: AVR cores support is added. 1. basic CPU structure 2. registers 3. no instructions

Signed-off-by: Michael Rolnik --- arch_init.c | 2 + configure | 5 + default-configs/avr-softmmu.mak | 21 +++ include/disas/bfd.h | 6 + include/sysemu/arch_init.h | 1 + target-avr/Makefile.objs|

[Qemu-devel] [PATCH v8 02/12] target-avr: adding AVR CPU features/flavors

Signed-off-by: Michael Rolnik --- target-avr/cpu.c | 307 ++- target-avr/cpu.h | 53 ++ 2 files changed, 359 insertions(+), 1 deletion(-) diff --git a/target-avr/cpu.c b/target-avr/cpu.c index 99bd788..197f9ac

[Qemu-devel] [PATCH v8 04/12] target-avr: adding instructions encodings

Signed-off-by: Michael Rolnik --- target-avr/translate-inst.h | 762 1 file changed, 762 insertions(+) create mode 100644 target-avr/translate-inst.h diff --git a/target-avr/translate-inst.h b/target-avr/translate-inst.h new file

[Qemu-devel] [PATCH v8 07/12] target-avr: adding instruction decoder

Signed-off-by: Michael Rolnik --- target-avr/decode.c | 693 1 file changed, 693 insertions(+) create mode 100644 target-avr/decode.c diff --git a/target-avr/decode.c b/target-avr/decode.c new file mode 100644 index

[Qemu-devel] [PATCH v8 03/12] target-avr: adding a sample AVR board

Signed-off-by: Michael Rolnik --- hw/Makefile.objs | 1 + hw/avr/Makefile.objs | 21 + hw/avr/sample-io.c | 215 +++ hw/avr/sample.c | 118 4 files changed, 355 insertions(+) create

[Qemu-devel] [PATCH v8 00/12] 8bit AVR cores

This series of patches adds 8bit AVR cores to QEMU. All instruction, except BREAK/DES/SPM/SPMX, are implemented. Not fully tested yet. However I was able to execute simple code with functions. e.g fibonacci calculation. This series of patches include a non real, sample board. No fuses support

[Qemu-devel] [PATCH] configure: Don't run AVX optimization requirement check on Mac OS X

The test currently only works with ELF and requires readelf, but OS X does not use ELF binaries. Signed-off-by: Stefan Weil --- configure | 7 +++ 1 file changed, 7 insertions(+) diff --git a/configure b/configure index 10cb212..89ffd28 100755 --- a/configure +++

Re: [Qemu-devel] OSX 10.7 build failure

Am 18.06.2016 um 21:09 schrieb Stefan Weil: > The resulting binary qemu-system-x86_64 boots the BIOS with curses, > but not with cocoa which does not show any window or other output. This problem is solved: I had used a remote shell for building on the Mac and tried qemu-system-x86_64 as I do it

Re: [Qemu-devel] OSX 10.7 build failure

Am 17.06.2016 um 17:49 schrieb Peter Maydell: > QEMU 2.6 builds without any deprecation warnings being generated. > > > ** Changed in: qemu >Status: New => Fix Released The deprecation warnings from https://bugs.launchpad.net/bugs/960378 are fixed, but I get new ones with OS X 10.11.5 and

Re: [Qemu-devel] [PATCH v7 12/12] target-avr: 1. use cpu_get/set_sreg function at avr_cpu_gdb_read_register/avr_cpu_gdb_read_register 2. configuring target as little endian 3. fixing and testing gen_p

On 06/14/2016 11:09 AM, Michael Rolnik wrote: Signed-off-by: Michael Rolnik --- configure | 2 +- target-avr/gdbstub.c| 19 ++- target-avr/translate-inst.c | 45 + target-avr/translate.c

Re: [Qemu-devel] [PATCH v2] target-ppc: Fix rlwimi, rlwinm, rlwnm

Hi rth, > In 63ae0915f8ec, I arranged to use a 32-bit rotate, without > considering the effect of a mask value that wraps around to > the high bits of the word. Thanks, that passes my tests. Tested-by: Anton Blanchard Anton > Signed-off-by: Richard Henderson

[Qemu-devel] [Bug 1593605] Re: windows2008r2 boot failed with uefi

Actually I can provide you with the patch which makes win2k8 + UEFI working if you willing to accept it for mainstream QEMU. It was quite simple. We have prepared it but not sent. Parallels Server 6/Parallels Desktop have this hack around 3-5 years. I have missed you comment. Closing again. **

[Qemu-devel] [Bug 1593605] Re: windows2008r2 boot failed with uefi

sorry, I meant not QEMU but UEFI above. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1593605 Title: windows2008r2 boot failed with uefi Status in QEMU: Invalid Bug description: I want to

[Qemu-devel] [Bug 1593605] Re: windows2008r2 boot failed with uefi

** Changed in: qemu Status: Invalid => 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/1593605 Title: windows2008r2 boot failed with uefi Status in QEMU: Confirmed Bug

[Qemu-devel] [Bug 1593605] Re: windows2008r2 boot failed with uefi

Denis, thanks a lot for the reminder and the analysis here. I knew about this issue at one point -- see https://bugzilla.redhat.com/show_bug.cgi?id=1185253 -- but by now I've completely forgotten that HyperV enlightenments and UEFI SMP Win7 don't mix. Also, for your analysis in comment #7 --

Re: [Qemu-devel] [PATCH] oslib-posix: New qemu_alloc_stack() to allocate stack with correct perms

On 06/17/16 16:11, Peter Maydell wrote: > Some architectures require the stack to be executable; notably > this includes MIPS, because the kernel's floating point emulator > may try to put trampoline code on the stack to handle some cases. > (See

[Qemu-devel] [Bug 1593605] Re: windows2008r2 boot failed with uefi

Thank you very much. After disabling all HyperV feature, Win2k8 can runnig with multi-vcpus in my enviroment. Referring to your advice, I will try to runnig Win2k8 with HyperV feature. Thank you very much. -- You received this bug notification because you are a member of qemu- devel-ml, which

[Qemu-devel] [PATCH] vmxnet3: Fix reading/writing guest memory specially when behind an IOMMU

When a PCI device lives behind an IOMMU, it should use 'pci_dma_*' family of functions when any transfer from/to guest memory is required while 'cpu_physical_memory_*' family of functions completely bypass any MMU/IOMMU in the system. vmxnet3 was exclusively using 'cpu_physical_memory_*' family

Re: [Qemu-devel] 答复： Re: [PATCH] Show all of snapshot info on every block device in output of 'info snapshots'

On 17.06.2016 10:18, Lin Ma wrote: > > Max Reitz mre...@redhat.com> 2016/6/15 星期三 上午 1:43 >> > 2016/6/15 星期三 上午 1:43 >>> > .. >>I have many comments, but don't worry, it's nothing that can't be fixed. >>The overall design looks good to me. > Thank you so much

Re: [Qemu-devel] [V11 2/4] hw/i386: ACPI IVRS table

On 2016-06-18 14:32, Peter Xu wrote: > On Sat, Jun 18, 2016 at 11:18:29AM +0300, David Kiarie wrote: >> On Tue, May 24, 2016 at 10:06 AM, Valentine Sinitsyn >> wrote: >>> Hi all, >>> >>> >>> On 24.05.2016 11:54, Peter Xu wrote: On Sun, May 22, 2016 at

Re: [Qemu-devel] [V11 2/4] hw/i386: ACPI IVRS table

On Sat, Jun 18, 2016 at 11:18:29AM +0300, David Kiarie wrote: > On Tue, May 24, 2016 at 10:06 AM, Valentine Sinitsyn > wrote: > > Hi all, > > > > > > On 24.05.2016 11:54, Peter Xu wrote: > >> > >> On Sun, May 22, 2016 at 01:21:52PM +0300, David Kiarie wrote: > >>

[Qemu-devel] [Bug 1529226] Re: qemu-i386-user on 32-bit Linux: uncaught target signal 11

A simpler way to reproduce would probably be to wrap the regular, installed rustc that way and try running some compilations using cargo. That should be enough to elicit the same problem. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to

Re: [Qemu-devel] [PATCH v6 02/22] qapi: Add lock-mode in blockdev-add options

On Fri, 06/17 11:17, Kevin Wolf wrote: > Am 03.06.2016 um 10:48 hat Fam Zheng geschrieben: > > To allow overriding the default locking behavior when opening the image. > > > > Signed-off-by: Fam Zheng > > --- > > qapi/block-core.json | 19 ++- > > 1 file

[Qemu-devel] [Bug 1593605] Re: windows2008r2 boot failed with uefi

you CAN run, but you have to disable HyperV enlightments. This means that these options "hv_time,hv_relaxed,hv_spinlocks=0x2000" must NOT be set. I have not found exact patch, sorry. But something like the following should be done even to start thinking on running win2k8 with EFI if HyperV is

[Qemu-devel] [Bug 1593605] Re: windows2008r2 boot failed with uefi

Hi Denis, thank you very much. I do really be interested in it. If the patch can be found, it readlly help me. And I still have another question. I notice that Win2k8 cound runnig with UEFI normally on Xen and VMare. Is there any diffrence between them abount handling with video, especially on

Re: [Qemu-devel] [PATCH 2/2] Explicitly print out default vnc option in use

On Wed, 2016-06-08 at 16:22 +0200, Markus Armbruster wrote: > Robert Hu writes: > > > On Mon, 2016-06-06 at 09:28 +0200, Markus Armbruster wrote: > >> Robert Hu writes: > >> > >> > On Tue, 2016-05-31 at 13:17 +0200, Markus Armbruster

[Qemu-devel] [RFC PATCH v0 1/1] spapr: Support setting of compat CPU type for CPU cores

Compat CPU type is typically specified on -cpu cmdline option like: -cpu host,compat=power7 or -cpu POWER8E,compat=power7 etc. With the introduction of sPAPR CPU core devices, we need to support the same for core devices too. Support the specification of CPU compat type on device_add command for

Re: [Qemu-devel] [V11 2/4] hw/i386: ACPI IVRS table

On Tue, May 24, 2016 at 10:06 AM, Valentine Sinitsyn wrote: > Hi all, > > > On 24.05.2016 11:54, Peter Xu wrote: >> >> On Sun, May 22, 2016 at 01:21:52PM +0300, David Kiarie wrote: >> [...] >>> >>> +static void >>> +build_amd_iommu(GArray *table_data, GArray *linker)

[Qemu-devel] [Bug 1591611] Re: chroot using qemu-x86_64-static fails on ppc64el

Finally figured it out! It's the page size. qemu user mode does NOT support a host page that is greater than 4k on x86/x86_64 systems, despite some claims to the contrary on older documentation pages. I'll be updating the patch to print a clear warning on failure instead of allowing corrupt

[Qemu-devel] [PATCH v2] Change net/socket.c to use socket_*() functions

Use socket_*() functions from include/qemu/sockets.h instead of listen()/bind()/ connect()/parse_host_port(). socket_*() fucntions are QAPI based and this patch performs this api conversion since everything will be using QAPI based sockets in the future. Also add a helper function

[Qemu-devel] [Bug 1593605] Re: windows2008r2 boot failed with uefi

Win2k8 EFI has a bug under HyperV. This will never work without a specific hack in UEFI. I can dig in my archives to find a patch if you are really interested in. AFAIR some memory in video driver has to be marked not as boot services but differently and will stay permanently. -- You received

[Qemu-devel] [PATCH] build: Use $(CC) for compiling .S files

We fail to pass to AS all of the different flags that may be required for a given set of CFLAGS. Rather than figuring out the host-specific mapping, it's better to allow the compiler driver to do that. This fixes e.g. ../configure --cpu=i686, but would also be required for ppc and sparc.

Re: [Qemu-devel] [RFC] target-arm: fix semihosting ram base issue

2016-06-18 14:57 GMT+09:00 Liviu Ionescu : > > > On 18 Jun 2016, at 01:22, Tsung-Han Lin wrote: > > > > ... It seems like to me that the issue is the default address assumed by > qemu, which is 0x0. > > (since Eclipse QEMU uses the same code, I believe

Re: [Qemu-devel] [RFC] target-arm: fix semihosting ram base issue

> On 18 Jun 2016, at 01:22, Tsung-Han Lin wrote: > > ... It seems like to me that the issue is the default address assumed by > qemu, which is 0x0. > (since Eclipse QEMU uses the same code, I believe they have the same problem.) it uses the same main code, but with many