Public bug reported:
I don't know if it's a problem, but I did, and it bothered me for a long time.
When I use qemu-i386 and interact with the video card device,an error has
occurred:
18534 ioctl(4,DRM_IOCTL_MODE_GETENCODER,{39,0,0,0,0}) = 0 ({39,4,34,3,0})
18534 ioctl(4,DRM_IOCTL_MODE_CREATE_DU
Hi,I found some problems, but I don't know if how to solve it better(I'm
not really familiar with the source code).
When I use ioctl() and use a structure like this:
struct drm_mode_card_res {
__u64 fb_id_ptr;
__u64 crtc_id_ptr;
__u64 connector_id_ptr;
__u64 encode
Hi,I found some problems, but I don't know if how to solve it better(I'm
not really familiar with the source code).
When I use ioctl() and use a structure like this:
struct drm_mode_card_res {
__u64 fb_id_ptr;
__u64 crtc_id_ptr;
__u64 connector_id_ptr;
__u64 encode
My environment is that:
schroot + debian(bullseye-i386)
qemu: 5.1.0-rc3
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1894071
Title:
qemu-i386-static ioctl return -14 (Bad Address)
Status in QEMU:
** Attachment added: "modeset.c"
https://bugs.launchpad.net/qemu/+bug/1894071/+attachment/5407367/+files/modeset.c
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1894071
Title:
qemu-i386-static
** Attachment added: "ioctls.h"
https://bugs.launchpad.net/qemu/+bug/1894071/+attachment/5407368/+files/ioctls.h
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1894071
Title:
qemu-i386-static io
This problem has bothered me for a long time, but I'm not sure whether
it's the IOCTL () I added or the QEMU with 32 bits. I hope we can
discuss it and help our friends who have other problems.
Thank you,my friends!
--
You received this bug notification because you are a member of qemu-
devel-ml
** Attachment added: "syscall_defs.h"
https://bugs.launchpad.net/qemu/+bug/1894071/+attachment/5407369/+files/syscall_defs.h
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1894071
Title:
qemu-i3
Public bug reported:
I use qemu-i386-static on 64 bit ARM.But I don't know how to solve some
problems.
First I added some ioctl operations.
Then I tried to do some DRM operations like test.c.
This is successful when I use qemu-x86_64-static,but it failed when I use
qemu-i386-static.
I can get so
** Attachment added: "syscall_types.h"
https://bugs.launchpad.net/qemu/+bug/1894071/+attachment/5407370/+files/syscall_types.h
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1894071
Title:
qemu-
Hello！
Has your problem been solved? I also encountered a similar problem. My
ioctl() also returned an error -14(Bad address).
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1731347
Title:
VFIO
** Description changed:
Hi!I use qemu-i386-static on 64 bit machines.And memory request succeeded,
but the pointer is wrong.
This is my test program:
#include
#include
#include
#include
int main(int argc, char **argv)
{
- void *pa=0,*pb=0,*pc=0,*pd=0;
- p
Public bug reported:
Hi!I use qemu-i386-static on 64 bit machines.And memory request succeeded, but
the pointer is wrong.
This is my test program:
#include
#include
#include
#include
int main(int argc, char **argv)
{
void *pa=0,*pb=0,*pc=0,*pd=0;
pa = malloc(sizeof(uint32_t)
This is where the error occurred:
(gdb) x/30i 0x40007ff2c0
0x40007ff2c0:xor%al,%dh
0x40007ff2c2:(bad)
0x40007ff2c3:add%al,(%rax)
0x40007ff2c5:add%al,(%rax)
0x40007ff2c7:add%ch,0x0(%rbp)
0x40007ff2cd:add%al,(%rax
Now, I found something new when I use gdb:
=> 0x400523c858:ud2
0x400523c85a:pushq $0xd
0x400523c85c:mov-0x230(%rbp),%rax
0x400523c863:mov-0x240(%rbp),%rdi
0x400523c86a:mov$0x1,%esi
0x400523c86f:movq $0x0,-0x230(%rbp)
I wrote an example to load local HTML:
#include "mainwindow.h"
#include "ui_mainwindow.h"
#include
MainWindow::MainWindow(QWidget *parent) :
QMainWindow(parent),
ui(new Ui::MainWindow)
{
ui->setupUi(this);
QWebEngineView *webView = new QWebEngineView(this);
webView->load(QUr
I wrote an example to load local HTML:
#include "mainwindow.h"
#include "ui_mainwindow.h"
#include
MainWindow::MainWindow(QWidget *parent) :
QMainWindow(parent),
ui(new Ui::MainWindow)
{
ui->setupUi(this);
QWebEngineView *webView = new QWebEngineView(this);
webView->load(QU
Hi,I have add QEMU_IFLA_INFO_KIND nested type for sit.But I still can't open
Google browser.
And there are still the following errors:
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
[1661:1661:0806/074307.5
Hi,I added a patch for ioctl(), and in the system call, I found no other
errors, but it still doesn't work.And，I use the "qemu-x86_64 -d unimp
xxx" command,I found this error:
Unknown QEMU_IFLA_INFO_KIND sit
In the Qemu source code:
linux-user/fd-trans.c
/* nested */
case QEMU_IF
Hi,I have already added ioctl(), but there is one individual issue.
Like this:
ioctl(54, _IOC(_IOC_READ, 0xf5, 0x0c, 0x04)
But,despite the appearance:
15461 open("/home/tony/.config/google-chrome/Default/Web
Data",O_RDWR|O_CREAT|O_NOFOLLOW|O_CLOEXEC,0600) = 43
15461 clock_gettime(1,27507071521
Hi,Peter.
I have added the ioctl() patch for Radeon driver in Qemu.
However, there are many ioctls that only give cmd, I don't know where it comes
from.
12161 poll(275275025312,1,4294967295,1,0,67108865)
12161 futex(0x0042f898,FUTEX_PRIVATE_FLAG|FUTEX_WAKE,1,NULL,NULL,0) = 0
12161 memfd_c
$ lspci
00:00.0 PCI bridge: Cadence Design Systems, Inc. Device dc16
00:01.0 PCI bridge: Cadence Design Systems, Inc. Device dc08
00:02.0 PCI bridge: Cadence Design Systems, Inc. Device dc01
00:03.0 PCI bridge: Cadence Design Systems, Inc. Device dc16
00:04.0 PCI bridge: Cadence Design Systems, Inc
And I can get some infomation by "qemu-x86_64-static -d strace".
17344 getdents(8,274880624768,32768,115,274880624899,39) = 0
17344 close(8) = 0
17344 ioctl(7,0xc0406400,0x297330) = 0
17344 ioctl(7,0xc0406400,0x297330) = 0
17344 fstat(7,0x004001a0b660) = 0
17344 fcntl(7,F_DUPFD_CLOEXEC,3)
Hi,Alex.It can't work.And I find some thing:
$ glxinfo | grep -i open
radeon: Failed to get PCI ID, error number -38
libGL error: failed to create dri screen
libGL error: failed to load driver: radeonsi
libGL error: failed to get magic
libGL error: failed to load driver: radeonsi
OpenGL vendor st
Hi,Alex.May be you are right.I don't understand what you want to express.
I don't know what causes traps.
Is it caused by software, or qemu executes CPU-sensitive instruction simulation.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
It's fine on x86 that I use qemu-x86_64-static.But it's bad on arm.So
what is 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/1890545
Title:
(ARM64) qemu-x86_64+schroot(Debian bullseye)
Hi Peter,I use 5.1.0-rc3.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1890545
Title:
(ARM64) qemu-x86_64+schroot(Debian bullseye) can't run chrome and
can't load HTML
Status in QEMU:
New
Bu
When I run some app,like google-chrome:
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1890545
Title:
(ARM64) qemu-x86_64+schr
Hi
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1890545
Title:
(ARM64) qemu-x86_64+schroot(Debian bullseye) can't run chrome and
can't load HTML
Status in QEMU:
New
Bug description:
First
Public bug reported:
First I creat a file system that is debian(bullseye amd64)on arm64
machine，then I download google-chrome，however, when I ran Google
browser, some errors occurred.
$ google-chrome --no-sandbox
or
$ qemu-x86_64-static google-chrome --no-sandbox
qemu: uncaught target signal 5
30 matches
Mail list logo
