[Bug 1876568] [NEW] "semtimedop" implementation missing in qemu?

2020-05-03 Thread Manuel Reimer
Public bug reported:

I was trying to do an ARMv6 cross compile with qemu-user-static when I
ran into this:

https://travis-ci.com/github/VDR4Arch/vdr4arch/jobs/326884620#L1596

I was close to giving up when I found the following:

https://github.com/osrf/multiarch-docker-image-generation/issues/36

Most important comment may be this one:

https://github.com/osrf/multiarch-docker-image-
generation/issues/36#issuecomment-610626796

> The "correct" way to fix this does seem to be to implement semtimedop
in qemu.

I don't know how much involved the people, discussing there, are in the
qemu development but I thought it may be a good idea to bring this to
your attention. If this is already fixed (I haven't found any bug about
"semtimedop"), then please just close this one and tell me in which
version the fix will be included.

** Affects: qemu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1876568

Title:
  "semtimedop" implementation missing in qemu?

Status in QEMU:
  New

Bug description:
  I was trying to do an ARMv6 cross compile with qemu-user-static when I
  ran into this:

  https://travis-ci.com/github/VDR4Arch/vdr4arch/jobs/326884620#L1596

  I was close to giving up when I found the following:

  https://github.com/osrf/multiarch-docker-image-generation/issues/36

  Most important comment may be this one:

  https://github.com/osrf/multiarch-docker-image-
  generation/issues/36#issuecomment-610626796

  > The "correct" way to fix this does seem to be to implement
  semtimedop in qemu.

  I don't know how much involved the people, discussing there, are in
  the qemu development but I thought it may be a good idea to bring this
  to your attention. If this is already fixed (I haven't found any bug
  about "semtimedop"), then please just close this one and tell me in
  which version the fix will be included.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1876568/+subscriptions



[Bug 1869782] Re: qemu-arm-static crashes "segmentation fault" when running "svn checkout"

2020-03-31 Thread Manuel Reimer
Managed to get a coredump. Coredumps usually tell me nothing but maybe
someone here can find something useful in there...

** Attachment added: "core.1001.13055.1585661762.bz2"
   
https://bugs.launchpad.net/qemu/+bug/1869782/+attachment/5343797/+files/core.1001.13055.1585661762.bz2

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1869782

Title:
  qemu-arm-static crashes "segmentation fault" when running "svn
  checkout"

Status in QEMU:
  New

Bug description:
  I'm not actually sure how far I can help as I so far failed to
  reproduce the issue on my local VM but I get it on Travis CI every
  time. I even went through the hassle of hacking a Debian repository
  into their Ubuntu Bionic VM to get qemu 4.2 as I hoped a new version
  could fix this.

  This build runs in an armv6h chroot. I don't get the segfault if I do
  the same on an armv7h chroot for some reason.

  Here is where the error occured: https://travis-
  ci.com/github/VDR4Arch/vdr4arch/jobs/309106220#L5420

  Maybe now I'll just try to remove all uses of svn in my build
  scripts...

  Is it actually a viable solution to cross-build with qemu? I'm
  starting to doubt it...

  Would it help if I manage to get this core dump out of Travis somehow
  (maybe make Travis push it to some GIT or upload it to my webserver)?

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1869782/+subscriptions



[Bug 1869782] Re: qemu-arm-static crashes "segmentation fault" when running "svn checkout"

2020-03-31 Thread Manuel Reimer
This is a "Ubuntu Bionic" thing.

I've tried again on a VM with up-to-date Ubuntu Bionic and get the same
segfault.

For comparison I've placed the Debian build of qemu-user-static version
4.2 to my Arch Linux VM and have no crash there.

So either the kernel version or some kernel configuration. Now I'm
trying to get a coredump on my VM.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1869782

Title:
  qemu-arm-static crashes "segmentation fault" when running "svn
  checkout"

Status in QEMU:
  New

Bug description:
  I'm not actually sure how far I can help as I so far failed to
  reproduce the issue on my local VM but I get it on Travis CI every
  time. I even went through the hassle of hacking a Debian repository
  into their Ubuntu Bionic VM to get qemu 4.2 as I hoped a new version
  could fix this.

  This build runs in an armv6h chroot. I don't get the segfault if I do
  the same on an armv7h chroot for some reason.

  Here is where the error occured: https://travis-
  ci.com/github/VDR4Arch/vdr4arch/jobs/309106220#L5420

  Maybe now I'll just try to remove all uses of svn in my build
  scripts...

  Is it actually a viable solution to cross-build with qemu? I'm
  starting to doubt it...

  Would it help if I manage to get this core dump out of Travis somehow
  (maybe make Travis push it to some GIT or upload it to my webserver)?

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1869782/+subscriptions



[Bug 1869782] Re: qemu-arm-static crashes "segmentation fault" when running "svn checkout"

2020-03-30 Thread Manuel Reimer
Here we go:
https://travis-ci.com/github/VDR4Arch/vdr4arch/jobs/309187889#L332

Created with this commit:
https://github.com/VDR4Arch/vdr4arch/commit/29ec2197483bf15102c889eef2749bb0cffc0839

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1869782

Title:
  qemu-arm-static crashes "segmentation fault" when running "svn
  checkout"

Status in QEMU:
  New

Bug description:
  I'm not actually sure how far I can help as I so far failed to
  reproduce the issue on my local VM but I get it on Travis CI every
  time. I even went through the hassle of hacking a Debian repository
  into their Ubuntu Bionic VM to get qemu 4.2 as I hoped a new version
  could fix this.

  This build runs in an armv6h chroot. I don't get the segfault if I do
  the same on an armv7h chroot for some reason.

  Here is where the error occured: https://travis-
  ci.com/github/VDR4Arch/vdr4arch/jobs/309106220#L5420

  Maybe now I'll just try to remove all uses of svn in my build
  scripts...

  Is it actually a viable solution to cross-build with qemu? I'm
  starting to doubt it...

  Would it help if I manage to get this core dump out of Travis somehow
  (maybe make Travis push it to some GIT or upload it to my webserver)?

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1869782/+subscriptions



[Bug 1869782] Re: qemu-arm-static crashes "segmentation fault" when running "svn checkout"

2020-03-30 Thread Manuel Reimer
I could run an "qemu... --version" in the chroot to get it into log.

But I'm close to 100% sure it is version 4.2 as the VM is set up from
scratch for every build and the chroot is also set up from scratch.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1869782

Title:
  qemu-arm-static crashes "segmentation fault" when running "svn
  checkout"

Status in QEMU:
  New

Bug description:
  I'm not actually sure how far I can help as I so far failed to
  reproduce the issue on my local VM but I get it on Travis CI every
  time. I even went through the hassle of hacking a Debian repository
  into their Ubuntu Bionic VM to get qemu 4.2 as I hoped a new version
  could fix this.

  This build runs in an armv6h chroot. I don't get the segfault if I do
  the same on an armv7h chroot for some reason.

  Here is where the error occured: https://travis-
  ci.com/github/VDR4Arch/vdr4arch/jobs/309106220#L5420

  Maybe now I'll just try to remove all uses of svn in my build
  scripts...

  Is it actually a viable solution to cross-build with qemu? I'm
  starting to doubt it...

  Would it help if I manage to get this core dump out of Travis somehow
  (maybe make Travis push it to some GIT or upload it to my webserver)?

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1869782/+subscriptions



[Bug 1869782] Re: qemu-arm-static crashes "segmentation fault" when running "svn checkout"

2020-03-30 Thread Manuel Reimer
** Description changed:

  I'm not actually sure how far I can help as I so far failed to reproduce
  the issue on my local VM but I get it on Travis CI every time. I even
  went through the hassle of hacking a Debian repository into their Ubuntu
  Bionic VM to get qemu 4.2 as I hoped a new version could fix this.
  
+ This build runs in an armv6h chroot. I don't get the segfault if I do
+ the same on an armv7h chroot for some reason.
+ 
  Here is where the error occured: https://travis-
  ci.com/github/VDR4Arch/vdr4arch/jobs/309106220#L5420
- 
- I don't get this error with an armv7h chroot.
  
  Maybe now I'll just try to remove all uses of svn in my build scripts...
  
  Is it actually a viable solution to cross-build with qemu? I'm starting
  to doubt it...
  
  Would it help if I manage to get this core dump out of Travis somehow
  (maybe make Travis push it to some GIT or upload it to my webserver)?

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1869782

Title:
  qemu-arm-static crashes "segmentation fault" when running "svn
  checkout"

Status in QEMU:
  New

Bug description:
  I'm not actually sure how far I can help as I so far failed to
  reproduce the issue on my local VM but I get it on Travis CI every
  time. I even went through the hassle of hacking a Debian repository
  into their Ubuntu Bionic VM to get qemu 4.2 as I hoped a new version
  could fix this.

  This build runs in an armv6h chroot. I don't get the segfault if I do
  the same on an armv7h chroot for some reason.

  Here is where the error occured: https://travis-
  ci.com/github/VDR4Arch/vdr4arch/jobs/309106220#L5420

  Maybe now I'll just try to remove all uses of svn in my build
  scripts...

  Is it actually a viable solution to cross-build with qemu? I'm
  starting to doubt it...

  Would it help if I manage to get this core dump out of Travis somehow
  (maybe make Travis push it to some GIT or upload it to my webserver)?

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1869782/+subscriptions



[Bug 1869782] [NEW] qemu-arm-static crashes "segmentation fault" when running "svn checkout"

2020-03-30 Thread Manuel Reimer
Public bug reported:

I'm not actually sure how far I can help as I so far failed to reproduce
the issue on my local VM but I get it on Travis CI every time. I even
went through the hassle of hacking a Debian repository into their Ubuntu
Bionic VM to get qemu 4.2 as I hoped a new version could fix this.

This build runs in an armv6h chroot. I don't get the segfault if I do
the same on an armv7h chroot for some reason.

Here is where the error occured: https://travis-
ci.com/github/VDR4Arch/vdr4arch/jobs/309106220#L5420

Maybe now I'll just try to remove all uses of svn in my build scripts...

Is it actually a viable solution to cross-build with qemu? I'm starting
to doubt it...

Would it help if I manage to get this core dump out of Travis somehow
(maybe make Travis push it to some GIT or upload it to my webserver)?

** Affects: qemu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1869782

Title:
  qemu-arm-static crashes "segmentation fault" when running "svn
  checkout"

Status in QEMU:
  New

Bug description:
  I'm not actually sure how far I can help as I so far failed to
  reproduce the issue on my local VM but I get it on Travis CI every
  time. I even went through the hassle of hacking a Debian repository
  into their Ubuntu Bionic VM to get qemu 4.2 as I hoped a new version
  could fix this.

  This build runs in an armv6h chroot. I don't get the segfault if I do
  the same on an armv7h chroot for some reason.

  Here is where the error occured: https://travis-
  ci.com/github/VDR4Arch/vdr4arch/jobs/309106220#L5420

  Maybe now I'll just try to remove all uses of svn in my build
  scripts...

  Is it actually a viable solution to cross-build with qemu? I'm
  starting to doubt it...

  Would it help if I manage to get this core dump out of Travis somehow
  (maybe make Travis push it to some GIT or upload it to my webserver)?

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1869782/+subscriptions



[Bug 1805913] Re: readdir() returns NULL (errno=EOVERFLOW) for 32-bit user-static qemu on 64-bit host

2020-03-27 Thread Manuel Reimer
I seem to have found another workaround. Knowing now what causes this my
guess was: If I make the qemu-arm-static on the host a 32 bit binary and
get "multilib" running to make my 64 bit Linux installation run this,
then in theory this incompatibility should not happen. If it would, then
32 bit x86 applications whould run into the same problem.

And at least according to my tries, I did so far, this seems to be the
case. I was able to reproduce this with svn (no checkout possible from
32 bit armv7h). If the qemu-arm-static binary is a 32 bit x86
application, then SVN checkouts work well now.

So until there is a better solution it seems to be a good idea to make
the emulation layer run through multilib for 32 bit target
architectures, so the host kernel can switch to its 32 bit backwards
compatibility mode.

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1805913

Title:
  readdir() returns NULL (errno=EOVERFLOW) for 32-bit user-static qemu
  on 64-bit host

Status in QEMU:
  Confirmed

Bug description:
  This can be simply reproduced by compiling and running the attached C
  code (readdir-bug.c) under 32-bit user-static qemu, such as qemu-arm-
  static:

  # Setup docker for user-static binfmt
  docker run --rm --privileged multiarch/qemu-user-static:register --reset
  # Compile the code and run (readdir for / is fine, so create a new directory 
/test).
  docker run -v /path/to/qemu-arm-static:/usr/bin/qemu-arm-static -v 
/path/to/readdir-bug.c:/tmp/readdir-bug.c -it --rm arm32v7/ubuntu:18.10 bash -c 
'{ apt update && apt install -y gcc; } >&/dev/null && mkdir -p /test && cd 
/test && gcc /tmp/readdir-bug.c && ./a.out'
  dir=0xff5b4150
  readdir(dir)=(nil)
  errno=75: Value too large for defined data type

  Do remember to replace the /path/to/qemu-arm-static and /path/to
  /readdir-bug.c to the actual paths of the files.

  The root cause is in glibc:
  
https://sourceware.org/git/?p=glibc.git;a=blob;f=sysdeps/unix/sysv/linux/getdents.c;h=6d09a5be7057e2792be9150d3a2c7b293cf6fc34;hb=a5275ba5378c9256d18e582572b4315e8edfcbfb#l87

  By C standard, the return type of readdir() is DIR*, in which the
  inode number and offset are 32-bit integers, therefore, glibc calls
  getdents64() and check if the inode number and offset fits the 32-bit
  range, and reports EOVERFLOW if not.

  The problem here is for 32-bit user-static qemu running on 64-bit
  host, getdents64 simply passing through the inode number and offset
  from underlying getdents64 syscall (from 64-bit kernel), which is very
  likely to not fit into 32-bit range. On real hardware, the 32-bit
  kernel creates 32-bit inode numbers, therefore works properly.

  The glibc code makes sense to do the check to be conformant with C
  standard, therefore ideally it should be a fix on qemu side. I admit
  this is difficult because qemu has to maintain a mapping between
  underlying 64-bit inode numbers and 32-bit inode numbers, which would
  severely hurt the performance. I don't expect this could be fix
  anytime soon (or even there would be a fix), but it would be
  worthwhile to surface this issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1805913/+subscriptions



[Bug 1869241] [NEW] svn checkout fails with E000075 "Value too large for defined data type"

2020-03-26 Thread Manuel Reimer
Public bug reported:

I try to autobuild for ARM7 with qemu-arm-static. Part of this is
downloading source via SVN.

Whenever I try to download a SVN repository I get the following output:

svn: E75: Can't read directory '...': Value too large for
defined data type

This is the repository I'm trying to check out:
https://svn.baycom.de/repos/vdr-mcli-plugin/

qemu-arm-static version is 4.2.0

I've also tried older versions without change.

Platform I try to emulate is armv7h (Arch Linux ARM for Raspberry Pi 2)

Host system is AMD64

This can be reproduced 100% of the time. Here I have the issue happening
on Travis CI:

https://travis-ci.com/github/VDR4Arch/vdr4arch/jobs/304839747#L9944

** Affects: qemu
 Importance: Undecided
 Status: New

** Description changed:

  I try to autobuild for ARM7 with qemu-arm-static. Part of this is
  downloading source via SVN.
  
  Whenever I try to download a SVN repository I get the following output:
  
- svn: E75: Can't read directory '...': Value too large for
+ svn: E75: Can't read directory '...': Value too large for
  defined data type
  
  qemu-arm-static version is 4.2.0
  
  I've also tried older versions without change.
  
  Platform I try to emulate is armv7h (Arch Linux ARM for Raspberry Pi 2)
  
  Host system is AMD64
  
  This can be reproduced 100% of the time. Here I have the issue happening
  on Travis CI:
  
- https://travis-ci.com/github/VDR4Arch/vdr4arch/jobs/304839747#L7228
+ https://travis-ci.com/github/VDR4Arch/vdr4arch/jobs/304839747#L9944

** Description changed:

  I try to autobuild for ARM7 with qemu-arm-static. Part of this is
  downloading source via SVN.
  
  Whenever I try to download a SVN repository I get the following output:
  
  svn: E75: Can't read directory '...': Value too large for
  defined data type
+ 
+ This is the repository I'm trying to check out:
+ https://svn.baycom.de/repos/vdr-mcli-plugin/
  
  qemu-arm-static version is 4.2.0
  
  I've also tried older versions without change.
  
  Platform I try to emulate is armv7h (Arch Linux ARM for Raspberry Pi 2)
  
  Host system is AMD64
  
  This can be reproduced 100% of the time. Here I have the issue happening
  on Travis CI:
  
  https://travis-ci.com/github/VDR4Arch/vdr4arch/jobs/304839747#L9944

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1869241

Title:
  svn checkout fails with E75 "Value too large for defined data
  type"

Status in QEMU:
  New

Bug description:
  I try to autobuild for ARM7 with qemu-arm-static. Part of this is
  downloading source via SVN.

  Whenever I try to download a SVN repository I get the following
  output:

  svn: E75: Can't read directory '...': Value too large for
  defined data type

  This is the repository I'm trying to check out:
  https://svn.baycom.de/repos/vdr-mcli-plugin/

  qemu-arm-static version is 4.2.0

  I've also tried older versions without change.

  Platform I try to emulate is armv7h (Arch Linux ARM for Raspberry Pi
  2)

  Host system is AMD64

  This can be reproduced 100% of the time. Here I have the issue
  happening on Travis CI:

  https://travis-ci.com/github/VDR4Arch/vdr4arch/jobs/304839747#L9944

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1869241/+subscriptions



[Bug 1869073] Re: qemu-arm-static crashes "segmentation fault" when running "git clone -s"

2020-03-26 Thread Manuel Reimer
Actually this one magically went good. I'm testing in Virtual Box as my
ARM64 host. Maybe something went wrong there. After rebooting the whole
machine today "git" works well.

Will reopen if it happens again...

** Changed in: qemu
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1869073

Title:
  qemu-arm-static crashes "segmentation fault" when running "git clone
  -s"

Status in QEMU:
  Incomplete

Bug description:
  I want to use qemu-arm-static to cross-compile software. The compiler
  itself is a native cross-compiler connected via "distcc".

  The problem is that a script tries to do some stuff with "git" and
  with a "git clone -s" command the whole story reproducibly stops with
  a "segmentation fault".

  I don't know how to properly debug the issue but it happens 100% of
  the time that I get the "crash" or git just hangs forever with 100%
  CPU usage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1869073/+subscriptions



[Bug 1869073] [NEW] qemu-arm-static crashes "segmentation fault" when running "git clone -s"

2020-03-25 Thread Manuel Reimer
Public bug reported:

I want to use qemu-arm-static to cross-compile software. The compiler
itself is a native cross-compiler connected via "distcc".

The problem is that a script tries to do some stuff with "git" and with
a "git clone -s" command the whole story reproducibly stops with a
"segmentation fault".

I don't know how to properly debug the issue but it happens 100% of the
time that I get the "crash" or git just hangs forever with 100% CPU
usage.

** Affects: qemu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1869073

Title:
  qemu-arm-static crashes "segmentation fault" when running "git clone
  -s"

Status in QEMU:
  New

Bug description:
  I want to use qemu-arm-static to cross-compile software. The compiler
  itself is a native cross-compiler connected via "distcc".

  The problem is that a script tries to do some stuff with "git" and
  with a "git clone -s" command the whole story reproducibly stops with
  a "segmentation fault".

  I don't know how to properly debug the issue but it happens 100% of
  the time that I get the "crash" or git just hangs forever with 100%
  CPU usage.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1869073/+subscriptions



[Qemu-devel] [Bug 1687270] [NEW] Can't write to 9p shared folder with qemu 2.9.0

2017-04-30 Thread Manuel Reimer
Public bug reported:

When running a virtual machine with qemu 2.9.0 with this parameter for
sharing a folder:

-virtfs local,id=fsdev1,path=$HOME/git,security_model=none,mount_tag=git

then the folder is shared to the VM but in some subfolders I can't
delete files. The guest system then reports that the file, I want to
delete, is "no file or folder".

I've downgraded to 2.8.0 now, which re-enables deleting my files.

Is this a known bug which will be fixed with a future version?

** Affects: qemu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1687270

Title:
  Can't write to 9p shared folder with qemu 2.9.0

Status in QEMU:
  New

Bug description:
  When running a virtual machine with qemu 2.9.0 with this parameter for
  sharing a folder:

  -virtfs
  local,id=fsdev1,path=$HOME/git,security_model=none,mount_tag=git

  then the folder is shared to the VM but in some subfolders I can't
  delete files. The guest system then reports that the file, I want to
  delete, is "no file or folder".

  I've downgraded to 2.8.0 now, which re-enables deleting my files.

  Is this a known bug which will be fixed with a future version?

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1687270/+subscriptions



[Qemu-devel] Can someone give me a hint about parallel port support?

2005-06-03 Thread Manuel Reimer

Hello,

I'm *very* interested in parallel port support.

I've found several patches in this mailing list. Can someone tell me 
if one of those patches has made into the current stable version?


I want to install Win98 SE under qemu to get my old mustek scanner 
(doesn't work with sane :-( ) running without having to reboot into 
windows.


I'm also interested in trying to write some software to get the 
scanner remote controlled from host OS (perhaps a GIMP-Plugin and a 
Server application for the Guest OS)


I have the parport kernel module loaded. What would I have to do to 
forward the parallel port to the guest OS?


Has anybody ever had success with getting parallel port devices 
running with qemu? There are some questions in the forum, but no 
answers. What about scanners?


BTW: My system is an 667 MHz Pentium III System. I also have an old 
Win95 license if Win98 is too heavy. If this also doesn't work then 
my scanner also has an Win3.1 driver ;-)


Thank you very much for any answer!

CU

Manuel


___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel