Re: [Bug 1772165] Re: arm raspi2/raspi3 emulation has no USB support
Which Beagle boards, Jetson Nano, other devices have rich support from qemu? ARM is critical going forward. On Mon, Oct 5, 2020, 10:20 AM Dims <1772...@bugs.launchpad.net> wrote: > So, is it still true, that QEMU doesn't support USB on Raspberry Pi? > > In other words I can't emulate Raspberry Pi actually? > > What about documentation and QEMU helps? They reports usb for raspi2, > for example: > > $qemu-system-arm -machine raspi2 -device help | grep usb-host > name "usb-host", bus usb-bus > > Is this incorrect information? > > Also, when I was truing to configure USB passthrough, I was getting > permission errors on /dev/usb/* probably indicating it was doing > something. > > If it doesn't support usb, then why isn't it write error message? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1772165 > > Title: > arm raspi2/raspi3 emulation has no USB support > > Status in QEMU: > Confirmed > > Bug description: > Using Qemu 2.12.0 on ArchLinux. > > Trying to emulate arm device with `qemu-system-arm` and attach usb > device for unput using > > ` -usb -device usb-host,bus=001,vendorid=0x1d6b,productid=0x0002 ` > > # lsusb returns > > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 014: ID 13d3:3487 IMC Networks > Bus 001 Device 004: ID 0457:11af Silicon Integrated Systems Corp. > Bus 001 Device 003: ID 0bda:57e6 Realtek Semiconductor Corp. > Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 > Card Reader Controller > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > # qemu returns > qemu-system-arm: -device > usb-host,bus=001,vendorid=0x1d6b,productid=0x0002: Bus '001' not found > > > Tried with connecting external usb keyboard but that didn't seem to work > either. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/qemu/+bug/1772165/+subscriptions > -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1772165 Title: arm raspi2/raspi3 emulation has no USB support Status in QEMU: Confirmed Bug description: Using Qemu 2.12.0 on ArchLinux. Trying to emulate arm device with `qemu-system-arm` and attach usb device for unput using ` -usb -device usb-host,bus=001,vendorid=0x1d6b,productid=0x0002 ` # lsusb returns Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 13d3:3487 IMC Networks Bus 001 Device 004: ID 0457:11af Silicon Integrated Systems Corp. Bus 001 Device 003: ID 0bda:57e6 Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # qemu returns qemu-system-arm: -device usb-host,bus=001,vendorid=0x1d6b,productid=0x0002: Bus '001' not found Tried with connecting external usb keyboard but that didn't seem to work either. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1772165/+subscriptions
[Bug 1860056] [NEW] mips binaries segfault
Public bug reported:
Hello World appears to segfault with qemu mips, on a Debian 10.0.0
Buster amd64 host.
Example:
$ cat mips/test/hello.cpp
#include
using std::cout;
int main() {
cout << "Hello World!\n";
return 0;
}
$ mips-linux-gnu-g++ -o hello hello.cpp && ./hello
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Note that 64-bit MIPS and little endian 32-bit MIPS qemu work fine. The
problem is limited to big endian 32-bit MIPS.
** 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/1860056
Title:
mips binaries segfault
Status in QEMU:
New
Bug description:
Hello World appears to segfault with qemu mips, on a Debian 10.0.0
Buster amd64 host.
Example:
$ cat mips/test/hello.cpp
#include
using std::cout;
int main() {
cout << "Hello World!\n";
return 0;
}
$ mips-linux-gnu-g++ -o hello hello.cpp && ./hello
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
Note that 64-bit MIPS and little endian 32-bit MIPS qemu work fine.
The problem is limited to big endian 32-bit MIPS.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1860056/+subscriptions
[Qemu-devel] [Bug 1835693] [NEW] s390x binaries segfault
Public bug reported:
Hello World appears to segfault with qemu s390x, on a Debian 10.0.0
Buster amd64 host.
$ cat hello.cpp
#include
using std::cout;
int main() {
cout << "Hello World!\n";
return 0;
}
$ s390x-linux-gnu-g++ -o hello hello.cpp
$ qemu-s390x-static hello
Segmentation fault
** 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/1835693
Title:
s390x binaries segfault
Status in QEMU:
New
Bug description:
Hello World appears to segfault with qemu s390x, on a Debian 10.0.0
Buster amd64 host.
$ cat hello.cpp
#include
using std::cout;
int main() {
cout << "Hello World!\n";
return 0;
}
$ s390x-linux-gnu-g++ -o hello hello.cpp
$ qemu-s390x-static hello
Segmentation fault
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1835693/+subscriptions
[Qemu-devel] [Bug 1822012] [NEW] powernv machine complains of missing skiboot files
Public bug reported: Hi, I want to use the powernv machine from the qemu-system-ppcle application. However, when I specify this machine, qemu complains that it can't find the skiboot files. I noticed that skiboot is available for Ubuntu, but only for the PPC[64] hosts. Well, I just need skiboot files for qemu on amd64 hosts. Hmm, looks like Debian has a package for these missing qemu files: https://packages.debian.org/sid/qemu-skiboot Could we promote these to Ubuntu repositories, and fix the qemu packages so that they automatically depend on the necessary BIOS packages? For example, openbios-ppc should also be installed when qemu-system- ppc[64[le]] are installed. ** 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/1822012 Title: powernv machine complains of missing skiboot files Status in QEMU: New Bug description: Hi, I want to use the powernv machine from the qemu-system-ppcle application. However, when I specify this machine, qemu complains that it can't find the skiboot files. I noticed that skiboot is available for Ubuntu, but only for the PPC[64] hosts. Well, I just need skiboot files for qemu on amd64 hosts. Hmm, looks like Debian has a package for these missing qemu files: https://packages.debian.org/sid/qemu-skiboot Could we promote these to Ubuntu repositories, and fix the qemu packages so that they automatically depend on the necessary BIOS packages? For example, openbios-ppc should also be installed when qemu-system-ppc[64[le]] are installed. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1822012/+subscriptions
[Qemu-devel] [Bug 1772165] Re: arm raspi2/raspi3 emulation has no USB support
Out of curiousity, does the raspi2 machine support a PCI bus? I am trying to boot Debian arm64 with qemu-system-aarch64, and am running into all manner of complaints from qemu about missing devices. Is there another machine like virt, but that offers support for boot devices? -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1772165 Title: arm raspi2/raspi3 emulation has no USB support Status in QEMU: Confirmed Bug description: Using Qemu 2.12.0 on ArchLinux. Trying to emulate arm device with `qemu-system-arm` and attach usb device for unput using ` -usb -device usb-host,bus=001,vendorid=0x1d6b,productid=0x0002 ` # lsusb returns Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 014: ID 13d3:3487 IMC Networks Bus 001 Device 004: ID 0457:11af Silicon Integrated Systems Corp. Bus 001 Device 003: ID 0bda:57e6 Realtek Semiconductor Corp. Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub # qemu returns qemu-system-arm: -device usb-host,bus=001,vendorid=0x1d6b,productid=0x0002: Bus '001' not found Tried with connecting external usb keyboard but that didn't seem to work either. To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1772165/+subscriptions
