qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: wj193102  <wj193102@163.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu3.0.0: Linux on non x86 CPUs run Wine
Date: Tue, 30 Oct 2018 20:10:02 +0800 (CST)	[thread overview]
Message-ID: <1e1a8483.155c9.166c4e17888.Coremail.wj193102@163.com> (raw)
In-Reply-To: <CAFEAcA-r=71qgPByUWuKsSAwiRA2S7qidtrrWyRuHvrckAvxSQ@mail.gmail.com>

Thanks for your reply.

At 2018-10-30 16:33:15, "Peter Maydell" <peter.maydell@linaro.org> wrote:
>On 30 October 2018 at 02:16, wj193102 <wj193102@163.com> wrote:
>> Hi, everyone.
>>     When I have installed the QEMU3.0.0 in the Linux on non X86 CPUS, I want to use user space emulator to run Wine. I can get the source code for Wine and the RPM file for Wine from the WineHQ web page.
>> I used to compile Wine in the X86-based Linux system and used it to run most Win32 programs. Now I want to  use it on the non X86 CPUS by QEMU. But I can't get the function to install and use the Wine. Please give me some advice
>> or some functions to finish it. Thanks a lot.
>
>I'm afraid you will need to provide more detail for us to
>help here. What exactly are you doing? Which commands are you
>running? What is the exact error message or failure you see?



I have installed the Wine in Linux(fedora) on the X86 CPUs from the source code. Can I copy the related file of Wine from the Linux on X86 CPUs to the Linux on the non X86 CPUS for running the command "wine" or "winecfg".


>>    Meanwhile, I use the command "qemu-i386/qemu-x86_64 *.sh" to
>> run the application from the X86 CPUS on non X86 CPUS, I get the
>> error information:"Invalid ELF image for this architecture". Why
>> the error is comming? What can I do to resolve this problem?
>
>This is probably because you are trying to run a shell script.
>(I'm guessing this from the '.sh' extension). This won't work.
>QEMU only runs actual executables (ELF files).

That is my fault. I don't run the *.sh file. I copy the file "/bin/ls" from the Linux on x86 CPUs to the Linux on non X86 CPUs. I put the file in the new created directory, such as "/home/admin/user/test/".
Then I run the executable file,using "qemu-i386 ./ls", I get the following error: "./ls: error while loading shared libraries: libselinux.so.1: cannot open shared object file: No such file or directory."
How can I resolve this  problem? 


>Usually the setup is that the host Linux system is set up
>with binfmt-misc, so that if it encounters a guest-architecture
>binary it will automatically run it under QEMU. Usually
>this is done to allow running guest binaries inside a chroot.
>
>thanks

>-- PMM


Thanks a lot.
--WangJi




  reply	other threads:[~2018-10-30 12:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-30  2:16 [Qemu-devel] qemu3.0.0: Linux on non x86 CPUs run Wine wj193102
2018-10-30  9:33 ` Peter Maydell
2018-10-30 12:10   ` wj193102 [this message]
2018-10-30 12:43     ` Peter Maydell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1e1a8483.155c9.166c4e17888.Coremail.wj193102@163.com \
    --to=wj193102@163.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).