Sorry, this is the "fixed" version, but you get the idea of how I invoke it.
sasl.h is present in
/home/anisse/dev/qemu-cross/build/usr/include/sasl/sasl.h ; this path is passed
through -isystem.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscri
Here is my full invocation of the configure script:
CFLAGS=" -isystem /home/anisse/dev/qemu-cross/build/usr/include" \
LDFLAGS="-Wl,--gc-sections -Wl,-Y/home/anisse/dev/qemu-cross/build/lib
-Wl,-Y/home/anisse/dev/qemu-cross/build/usr/lib
-Wl,-rpath-link,/home/anisse/dev/qemu-cross/build/lib
-Wl
Public bug reported:
Since qemu 5.2, when building, the configure would not finish, but would
return this error instead:
qemu ../meson.build:852:2: ERROR: C header 'sasl/sasl.h' not found
This is for a cross build, and I invoke qemu with the --extra-cflags and
--extra-ldflags containing all t
The bug is still present.
** Changed in: qemu
Status: Incomplete => 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/1828608
Title:
Chardev websocket might not support pasting more than a
This is a suggestion that would really help anyone using trying to use
xhci passthrough on a platform without streams.
** Changed in: qemu
Status: Incomplete => New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.
to read or poll, so the max_size wouldn't be refreshed.
Buglink: https://bugs.launchpad.net/qemu/+bug/1828608
Signed-off-by: Anisse Astier
---
Changes since v1:
- style changes
---
chardev/char-socket.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/chardev/char-socket.c b/charde
;t be refreshed.
Buglink: https://bugs.launchpad.net/qemu/+bug/1828608
Signed-off-by: Anisse Astier
---
chardev/char-socket.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/chardev/char-socket.c b/chardev/char-socket.c
index 185fe38dda..5e093e6605 100644
--- a/chardev/char-socket.c
+++
Public bug reported:
When using USBÂ passthrough with the qemu-xhci (and nec-usb-xhci),
streams are enabled by default, but if the host xHCI controller doesn't
support them, it will trigger hard-to-debug UAS guest errors.
This should be possible to detect since the kernel returns ENOSYS (errno 38)
I wrote a websocket client to help reproduce the bug without a browser:
https://github.com/anisse/websocktty
You can install it to your $GOPATH/bin (defaults to ~/go/bin) with "go
get github.com/anisse/websocktty"
I can reproduce the bug with it by simply pasting a long-enough (5 to 20
characters
Public bug reported:
When sending more than 4-5 characters on the websocket serial console
(with pasting for example), the guest might not receive all of them, or
worse interpret the input as Magic SysRq keys.
This might be due to the io loop not checking the backend readiness
before calling the
I can confirm that this patch fixes the issue. I can now reconnect after
a client has disconnected.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1816819
Title:
Chardev websocket stops listening af
Public bug reported:
Using qemu option:
-chardev socket,id=websock0,websocket,port=13042,host=127.0.0.1,server,nowait
-serial chardev:websock0
To have a websocket listening chardev. After the first connection
disconnects (that does a full websocket handshake), subsequent
connections aren't acce
12 matches
Mail list logo
