The kernel allows a NULL msg in recvfrom so that he size of the next
message may be queried before allocating a correctly sized buffer. This
change allows the syscall translator to pass along the NULL msg pointer
instead of returning early with EFAULT.
Signed-off-by: Zach Reizner
---
v2
The kernel allows a NULL msg in recvfrom so that he size of the next
message may be queried before allocating a correctly sized buffer. This
change allows the syscall translator to pass along the NULL msg pointer
instead of returning early with EFAULT.
Signed-off-by: Zach Reizner
---
linux-user
I wrote up a quick example to show that this should work specifically for
/proc/self/exe:
#define _GNU_SOURCE
#include
#include
#include
#include
int main(int argc, char** argv) {
int fd = open("/proc/self/exe", O_NOFOLLOW | O_PATH);
system("ls -la /proc/$PPID/fd/"
in the process of link resolution via the readlink() loop, we end up
with the same path as our candidate, we can return true. This avoids the
need to rely on any libc implementation of realpath(), since we're just
relying on the host kernel.
*Zach Riggle*
On Fri, Nov 10, 2017 at 5:44 PM, L
Day 17 Ping :)
*Zach Riggle*
On Tue, Nov 7, 2017 at 2:06 PM, Riku Voipio wrote:
> Hi,
>
> On Mon, Nov 06, 2017 at 08:17:44PM +0000, Zach Riggle wrote:
> > Ping! What needs to be done to move this forward? My current
> implementation
> > is compatible with musl.
&g
Ping! What needs to be done to move this forward? My current implementation
is compatible with musl.
On Thu, Nov 2, 2017 at 12:36 PM Peter Maydell
wrote:
> On 28 October 2017 at 06:14, Eric Blake wrote:
> > By definition, in linux-user, we ARE using glibc; therefore, you are
> > free to use all
Ping. What changes do I need to make to land this?
On Sat, Oct 28, 2017 at 12:49 AM Eric Blake wrote:
> On 10/27/2017 09:07 PM, Zach Riggle wrote:
> > Another case that may be more relevant for general QEMU use, is that the
> > current code fails if the software under test has poo
canonicalization issues and could be resolved with e.g.
canonicalize_file_name, but I'm not sure if QEMU allows GNU extensions --
and realpath() is portable.
*Zach Riggle*
On Fri, Oct 27, 2017 at 12:05 PM, Zach Riggle wrote:
> The symlink was just an easy test case. Doing cd pro
ly, this
will return the memory layout of QEMU, not the emulated memory layout of
the software under test.
*Zach Riggle*
On Fri, Oct 27, 2017 at 4:36 AM, Riku Voipio wrote:
> On Thu, Oct 26, 2017 at 04:06:22PM -0500, Zach Riggle wrote:
> > Friendly ping :)
> >
> > I'
Friendly ping :)
I've updated the patch with v2 which addresses the style issue
*Zach Riggle*
On Tue, Oct 24, 2017 at 10:34 PM, Zach Riggle wrote:
> Previously, it was possible to get a handle to the "real" /proc/self/mem
> by creating a symlink to it and opening the sy
602bc000 r-xp fc:01 270375
/usr/bin/qemu-arm-static
604bc000-6050f000 rw-p 002bc000 fc:01 270375
/usr/bin/qemu-arm-static
...
Signed-off-by: Zach Riggle
---
linux-user/syscall.c | 47 ---
1
From: Zach Riggle
Previously, it was possible to get a handle to the "real" /proc/self/mem
by creating a symlink to it and opening the symlink, or opening e.g.
"./mem" after chdir'ing to "/proc/self".
$ ln -s /proc/self self
$ cat self/maps
60
Seems to work when using virt-install to do a manual uefi install
** Project changed: qemu => virt-manager
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1637693
Title:
QEMU not able to create vm w
Public bug reported:
Running Fedora 24 with the virt-preview repo on QEMU Version 2.7.0 and
libvirt version 2.2.0. Tried to install a windows 10 vm with the OVMF
bios and this error happens every time, it didnt happen when using the
stable version of qemu for fedora 24.
libvirtError: internal err
Public bug reported:
When using the "-no-reboot" qemu option with kvm, qemu does nothing and
immediately exits with no output or error message. If I add the --no-
kvm option to the command line, it works as expected.
It works fine in 11.0 and 11.1, but I tested all versions of 12.X, and
they al
Hi-
The serial routines do not set the proper termios flags for the serial
port so that data can pass unmolested from the emulated environment to
the host serial device. This simple patch fixes that. Tested on a
FreeBSD 6.2 host with Windows XP as the emulated OS.
--- Zach
--- /usr/ports
No more kernel messages on FreeBSD. I'll send a note to the port
maintainer to have it updated. Thanks!
--- Zach
On 6/23/06, Fabrice Bellard <[EMAIL PROTECTED]> wrote:
I put online kqemu version 1.3.0pre9 which should solve the issue. Maybe
it helps for the Windows XP hosts too
Let me know if you need any testing. I have both 6.1-RELEASE and
5.3-RELEASE machines on which to test.
Thanks, and this is a truly great bit of software!
--- Zach
On 6/21/06, Fabrice Bellard <[EMAIL PROTECTED]> wrote:
There is a bug in the FPU virtualization in kqemu which is only visi
t get these messages. In both
cases, Windows appears to work fine.
This thread:
http://tinyurl.com/mbm5l
appears to have some information on why this happens. Has a patch been
released to fix this bug?
--- Zach
___
Qemu-devel mailing list
Qemu-devel@nong
19 matches
Mail list logo
