[Qemu-devel] [Bug 1130769] Re: VirtFS (virtio-9p-pci) error: Parameter 'driver' expects device type

2013-03-01 Thread Daniel Berrange
I wonder if the Gentoo build has got virtio-9p enabled at all. This kind of error message is the sort of thing QEMU often prints for a feature like this is disabled at build time -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1089006] Re: Qemu scrambles order of eth devices in vm

2012-12-12 Thread Daniel Berrange
There is really no such concept as NIC order at the hardware level in QEMU. NIC naming order is something that operating systems invent according to some policy they have. As far as libvirt QEMU are concerned, you only have control over the PCI device slot numbering. The operating system may

[Qemu-devel] [Bug 1484925] Re: Segfault with custom vnc client

2015-08-14 Thread Daniel Berrange
Can you attach GDB to your qemu-dm process and attempt to capture a full stack trace when it crashes (ie thread apply all backtrace) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1484925 Title:

[Qemu-devel] [Bug 1505041] Re: Live snapshot revert times increases linearly with snapshot age

2015-10-12 Thread Daniel Berrange
I'm unsure why clock time would affect snapshot revert, but one thing to note is that the general recommended timer settings for guest OS are different from what you have. virt-manager/oVirt/OpenStack would all set: in general for all guest OS, and if they have new

[Qemu-devel] [Bug 1589923] Re: https websockets not working in 2.5 or 2.6

2016-06-08 Thread Daniel Berrange
** Changed in: qemu Status: New => Confirmed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1589923 Title: https websockets not working in 2.5 or 2.6 Status in QEMU: Confirmed Status in

[Qemu-devel] [Bug 1589923] Re: https websockets not working in 2.5 or 2.6

2016-06-07 Thread Daniel Berrange
** Changed in: qemu Assignee: (unassigned) => Daniel Berrange (berrange) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1589923 Title: https websockets not working in 2.5 or 2.6 Sta

[Qemu-devel] [Bug 1589923] Re: https websockets not working in 2.5 or 2.6

2016-06-07 Thread Daniel Berrange
The crash in 2.6 is fixed by https://lists.gnu.org/archive/html/qemu-devel/2016-06/msg01885.html The dropped connection in 2.5 is fixed by https://lists.gnu.org/archive/html/qemu-devel/2016-06/msg01884.html -- You received this bug notification because you are a member of qemu- devel-ml,

[Qemu-devel] [Bug 1586756] Re: "-serial unix:" option of qemu-system-* is broken in qemu 2.6.0

2016-06-01 Thread Daniel Berrange
** Changed in: qemu Assignee: (unassigned) => Daniel Berrange (berrange) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1586756 Title: "-serial unix:" option of qemu-system-* is b

[Qemu-devel] [Bug 1594861] Re: QEMU crashes when slow VNC client disconnects

2016-06-24 Thread Daniel Berrange
The only place we free the mutex is in vnc_disconnect_finish() which is only ever called from vnc_client_read(), in turn called from vnc_client_io(). We're crashing in vnc_client_write() which is called from vnc_client_io(). The stack trace has optimized out the "condition" param in

[Qemu-devel] [Bug 1594861] Re: QEMU crashes when slow VNC client disconnects

2016-06-28 Thread Daniel Berrange
Potential fix posted https://lists.gnu.org/archive/html/qemu-devel/2016-06/msg07693.html If you are able to test with this patch any feedback would be welcome. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1545052] [NEW] RDMA migration will hang forever if target QEMU fails to load vmstate

2016-02-12 Thread Daniel Berrange
Public bug reported: Get a pair of machines with infiniband support. On one host run $ qemu-system-x86_64 -monitor stdio -incoming rdma:ibme: -vnc :1 -m 1000 To start an incoming migration. Now on the other host, run QEMU with an intentionally different configuration (ie different RAM

[Qemu-devel] [Bug 1545052] Re: RDMA migration will hang forever if target QEMU fails to load vmstate

2016-02-12 Thread Daniel Berrange
FYI is is tested on current GIT master commit fc1ec1acffd29d54c0c4266d30d38b2399d42f4f Merge: f163684 1834ed3 Author: Peter Maydell Date: Thu Feb 11 15:09:33 2016 + Merge remote-tracking branch 'remotes/mjt/tags/pull-trivial- patches-2016-02-11' into staging

[Qemu-devel] [Bug 1538541] Re: qcow2 rejects request to use preallocation with backing file

2016-01-27 Thread Daniel Berrange
> In order to support this, qcow2 will need to support preallocated data clusters which are explicitly marked as empty (where "empty" is not "zero"; "empty" means "fall through to the backing file"). This has been proposed before, but has not been implemented so far. This sounds like a bit of

[Qemu-devel] [Bug 1538541] Re: qcow2 rejects request to use preallocation with backing file

2016-01-28 Thread Daniel Berrange
Preallocating the understanding image file at the management layer though means that the mgmt tool has to understand the full details of the qcow2 file format. The mgmt layer knows it created a 20 GB qcow2 file, but does not know that once you have stored 20 GB of user data in it, it will actually

[Qemu-devel] [Bug 1538541] [NEW] qcow2 rejects request to use preallocation with backing file

2016-01-27 Thread Daniel Berrange
Public bug reported: The 'preallocation=full' option to qemu-img / qcow2 block driver instructs QEMU to fully allocate the host file to the maximum size needed by the logical disk size. $ qemu-img create -f qcow2 -o preallocation=full base.qcow2 200M Formatting 'base.qcow2', fmt=qcow2

[Qemu-devel] [Bug 1579565] Re: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T.

2016-05-09 Thread Daniel Berrange
If you can still see the bug after applying Stefan's patch, please attach the config.log file generated by configure -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1579565 Title: ERROR:

[Qemu-devel] [Bug 1579565] Re: ERROR: sizeof(size_t) doesn't match GLIB_SIZEOF_SIZE_T.

2016-05-09 Thread Daniel Berrange
Ok so the log message associated with the failure is this: cc -m32 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings -Wmissing-prototypes -fno-strict-aliasing -fno-common -Wendif-labels -Wmissing-include-dirs

[Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message

2016-07-27 Thread Daniel Berrange
Ok, so the problem is a difference in behaviour for virtio-console vs serial ports. For plain x86 serial ports, if there's no client connected to the backend, any data is just discarded. For virtio-console, if there's no client connected to the backend, it'll refuse to send data, hence we never

[Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message

2016-07-29 Thread Daniel Berrange
Patch at https://lists.gnu.org/archive/html/qemu- devel/2016-07/msg06708.html -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1599214 Title: virtlogd: qemu 2.6.0 doesn't log boot message Status in

[Qemu-devel] [Bug 1586756] Re: "-serial unix:" option of qemu-system-arm is broken in qemu 2.6.0

2016-07-29 Thread Daniel Berrange
Ok, now it makes more sense. You are using the socket chardev in TCP outgoing client mode, which used to be blocking by default. In 2.6 this switched to match TCP server mode, in wich the incoming client was always in non-blocking mode. IOW, this arm code was already broken in 2.5 just depending

[Qemu-devel] [Bug 1586756] Re: "-serial unix:" option of qemu-system-* is broken in qemu 2.6.0

2016-07-26 Thread Daniel Berrange
Looking at the code in 2.5.0, the qemu_chr_fe_write method would see EAGAIN too, because the tcp_chr_accept() method would always set the newly connected client to non-blocking mode. So thre's no obvious change in behaviour between 2.5 and 2.6 wrt to blocking sockets. -- You received this bug

[Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message

2016-07-26 Thread Daniel Berrange
Can you provide the full QEMU command line arguments you're using to reproduce this problem. I tested a guest with the following console config: and confirmed that the log file gets written, even when no client is connected to the UNIX domain socket. **

[Qemu-devel] [Bug 1586756] Re: "-serial unix:" option of qemu-system-* is broken in qemu 2.6.0

2016-07-26 Thread Daniel Berrange
I'm unable to reproduce the problem mentioned myself, and code inspection shows no problem for x86_64 at least. Specifically hw/char/serial.c has a serial_xmit() method which calls qemu_chr_fe_write(), and if it sees EAGAIN, it sets up a event notification to re-try the write later. Can you

[Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message

2016-07-27 Thread Daniel Berrange
Ok, relevant part of command line is -add-fd set=2,fd=33 -chardev socket,id=charconsole0,host=9.152.151.129,port=1,server,nowait,logfile=/dev/fdset/2,logappend=on -device virtconsole,chardev=charconsole0,id=console0 -chardev pty,id=charconsole1 -device

[Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message

2016-07-05 Thread Daniel Berrange
** Changed in: qemu Assignee: (unassigned) => Daniel Berrange (berrange) -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1599214 Title: virtlogd: qemu 2.6.0 doesn't log boot message Sta

[Qemu-devel] [Bug 1586756] Re: "-serial unix:" option of qemu-system-arm is broken in qemu 2.6.0

2016-08-05 Thread Daniel Berrange
Fix posted https://lists.gnu.org/archive/html/qemu- devel/2016-08/msg00684.html -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1586756 Title: "-serial unix:" option of qemu-system-arm is broken in

[Qemu-devel] [Bug 1578192] Re: GTK+ interface doesn't translate keycodes properly with Wayland backend

2017-01-16 Thread Daniel Berrange
This issue was fixed already in git master with: commit a8ffb372a2202c65f42fdb69891ea68a2f274b55 Author: Daniel P. Berrange Date: Thu Dec 1 09:41:17 2016 + ui: use evdev keymap when running under wayland Wayland always uses evdev as its input source, so

[Qemu-devel] [Bug 1668273] Re: DoS possible on - a QEMU process using userspace SLIRP?

2017-02-27 Thread Daniel Berrange
Unless I'm mis-understanding what you're saying you have an app which opens 100's of TCP conenctions in the guest, and this causes QEMU to have 100's of file descriptors open in the host. If so, this is normal behaviour of SLIRP - it opens a socket for every connection it has to proxy across from

[Qemu-devel] [Bug 1668273] Re: DoS possible on - a QEMU process using userspace SLIRP?

2017-02-27 Thread Daniel Berrange
IIUC, a socket staying around in FIN_WAIT2 state means that a socket has been closed in one direction, but not the other direction. Assuming SLIRP is just mirroring what the guest OS has done with the socket shutdown process, this would be expected. -- You received this bug notification because

[Qemu-devel] [Bug 1589923] Re: https websockets not working in 2.5 or 2.6

2016-09-14 Thread Daniel Berrange
Fixed in stable-2.6 branch in commit 510531ea442a02048b1837fcf574d03559b38c9e Author: Daniel P. Berrange Date: Tue Jun 7 12:27:51 2016 +0100 io: remove mistaken call to object_ref on QTask The QTask struct is just a standalone struct, not a QOM Object, so

[Qemu-devel] [Bug 1599214] Re: virtlogd: qemu 2.6.0 doesn't log boot message

2016-09-14 Thread Daniel Berrange
Fix in 2.7.0 release thanks to commit bce6261eb2d879625126485d4ddd28cacb93152e Author: Daniel P. Berrange Date: Wed Aug 3 17:22:36 2016 +0100 virtio-console: set frontend open permanently for console devs The virtio-console.c file handles both serial consoles

[Qemu-devel] [Bug 1640525] Re: -net socket, connect/listen does not work in 2.7.0

2016-11-09 Thread Daniel Berrange
The patch for this issue is here: https://lists.gnu.org/archive/html/qemu-devel/2016-11/msg00811.html -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1640525 Title: -net socket,connect/listen does

[Qemu-devel] [Bug 1637447] Re: VNC/RFB: QEMU reports incorrect name (length)

2016-10-28 Thread Daniel Berrange
The right fix here is to switch to use g_strdup_printf and avoid a fixed length stack buffer entirely. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1637447 Title: VNC/RFB: QEMU reports incorrect

[Qemu-devel] [Bug 1455912] Re: vnc websocket option not properly parsed when running on commandline

2017-01-05 Thread Daniel Berrange
https://lists.gnu.org/archive/html/qemu-devel/2017-01/msg00583.html ** Changed in: qemu Status: Confirmed => In Progress -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1455912 Title: vnc

[Qemu-devel] [Bug 1455912] Re: vnc websocket option not properly parsed when running on commandline

2017-01-04 Thread Daniel Berrange
signee: (unassigned) => Daniel Berrange (berrange) ** Changed in: qemu Status: New => Confirmed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1455912 Title: vnc websocket option not properly

[Qemu-devel] [Bug 1583420] Re: Please support "-soundhw none"

2017-08-11 Thread Daniel Berrange
Pulseaudio is a sound *backend*. This is independent of the choice of guest hardware frontend. You can disable pulseaudio using an env variable QEMU_AUDIO_DRV=none -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1670377] Re: VNC: short read for zlre data/RDR EndOfStream

2017-04-27 Thread Daniel Berrange
It isn't 100% clear from the info provided, but this is almost certainly fixed in 2.9.0 by commit 537848ee62195fc06c328b1cd64f4218f404a7f1 Author: Michael Tokarev Date: Fri Feb 3 12:52:29 2017 +0300 vnc: do not disconnect on EAGAIN When qemu vnc server is trying

[Qemu-devel] [Bug 1686390] Re: vnc server closed socket after arrow "down" keyevent

2017-04-27 Thread Daniel Berrange
> Wrote wire 0x5579e6bd2c60 51480 -> -2 That is QIO_CHANNEL_ERR_BLOCK, aka EAGAIN. This is fixed in the 2.9.0 release with commit 537848ee62195fc06c328b1cd64f4218f404a7f1 Author: Michael Tokarev Date: Fri Feb 3 12:52:29 2017 +0300 vnc: do not disconnect on EAGAIN

[Qemu-devel] [Bug 1064631] Re: Feature request: tls for chardev socket (telnet, tcp, udp)

2017-04-27 Thread Daniel Berrange
This support was introduced in QEMU 2.6 last year. Some info here: https://www.berrange.com/posts/2016/08/16/improving-qemu-security-part-6 -tls-support-for-character-devices/ ** Changed in: qemu Status: New => Fix Released -- You received this bug notification because you are a member

[Qemu-devel] [Bug 1686980] Re: qemu is very slow when adding 16, 384 virtio-scsi drives

2017-04-28 Thread Daniel Berrange
The first place where it ages an insane amount of time is simply processing -drive options. The stack trace I see is this (gdb) bt #0 0x5583b596719a in drive_get (type=type@entry=IF_NONE, bus=bus@entry=0, unit=unit@entry=2313) at blockdev.c:223 #1 0x5583b59679bd in drive_new

[Qemu-devel] [Bug 1686980] Re: qemu is very slow when adding 16, 384 virtio-scsi drives

2017-04-28 Thread Daniel Berrange
I instrumented drive_new to time how long 1000 creations took with current code: 1000 drive_new() in 0 secs 1000 drive_new() in 2 secs 1000 drive_new() in 18 secs 1000 drive_new() in 61 secs As a quick hack you can just disable the drive_get() calls when if=none. They're mostly just used to fill

[Qemu-devel] [Bug 1686980] Re: qemu is very slow when adding 16, 384 virtio-scsi drives

2017-04-28 Thread Daniel Berrange
I added further instrumentation and got this profile of where the remaining time goes 1000x drive_new 18.347secs -> 1000x blockdev_init 18.328secs -> 1000x monitor_add_blk 4.515secs -> 1000x blk_by_name 1.545secs -> 1000x bdrv_find_node 2.968secs -> 1000x blk_new_open 13.786secs

[Qemu-devel] [Bug 778032] Re: qemu spinning on serial port writes

2017-05-05 Thread Daniel Berrange
I'm confident this has been solved a while ago. When this bug was reported, the code was indeed broken wrt EAGAIN handling. The chardev code has long since been re-written though, and the send_all method replaced by io_channel_send_all() which will handle EAGAIN by returning instead of spinning

[Qemu-devel] [Bug 1721788] Re: Failed to get shared "write" lock with 'qemu-img info'

2017-10-06 Thread Daniel Berrange
The QEMU process that has the disk image open may be doing I/O that causes qcow2 metadata to be changed. Such changes could confuse the 'qemu-img' process it is was reading the metadata at the same time it was being changed, causing bad data to be printed or worse. So requiring a write lock is the

[Qemu-devel] [Bug 1721788] Re: Failed to get shared "write" lock with 'qemu-img info'

2017-10-06 Thread Daniel Berrange
I've just noticed, however, that '--force-share' appears totally undocumented in both CLI help output and the man page. So that's certainly something that should be fixed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1718964] Re: Memory leak when using websocket over a low speed network

2017-10-10 Thread Daniel Berrange
In the modern code this needs fixing in the io/channel-websock.c impl - it is checking the output buffer limit against the wrong buffer - it uses 'rawoutput' instead of 'encoutput', so this fix is easy enough there. The code is in fact broken all the way back to day1 of the introduction of

[Qemu-devel] [Bug 1718964] Re: Memory leak when using websocket over a low speed network

2017-10-17 Thread Daniel Berrange
** Changed in: qemu Status: New => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1718964 Title: Memory leak when using websocket over a low speed network Status in QEMU:

[Qemu-devel] [Bug 1718964] Re: Memory leak when using websocket over a low speed network

2017-10-12 Thread Daniel Berrange
This has been assigned CVE-2017-15268 http://www.openwall.com/lists/oss-security/2017/10/12/4 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15268 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1716028] Re: qemu 2.10 locks images with no feature flag

2017-09-11 Thread Daniel Berrange
Having a single QEMU process open the same qcow2 file twice is just as dangerous as having two separate QEMU processes open the same qcow2 file concurrently. In both cases you have qcow2 state cached in a BlockDriverState and nothing is able to invalidate the cache in the other BlockDriverState.

[Qemu-devel] [Bug 1715700] Re: Windows 7 guest won't boot on qemu 2.10 (works on 2.9)

2017-09-11 Thread Daniel Berrange
The newer GCC compilers are more fussy - just add '--disable-werror' when running 'configure' to make it ignore the warning -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1715700 Title: Windows 7

[Qemu-devel] [Bug 1715186] Re: websockets: Improve error messages

2017-09-05 Thread Daniel Berrange
At very least we should also use 404 if given a invalid path -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1715186 Title: websockets: Improve error messages Status in QEMU: New Bug

[Qemu-devel] [Bug 1583784] Re: qio_task_free segfault websocket

2017-09-28 Thread Daniel Berrange
*** This bug is a duplicate of bug 1589923 *** https://bugs.launchpad.net/bugs/1589923 ** This bug has been marked a duplicate of bug 1589923 https websockets not working in 2.5 or 2.6 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed

[Qemu-devel] [Bug 1327608] Re: monitor socked path is cut a 105 characters

2017-10-03 Thread Daniel Berrange
There's actually two bugs here. First QEMU was truncating the UNIX, but because it used 'snprintf', QEMU truncated it at 107 characters and then added a trailing NUL, instead of truncating at 108 characters and not having a NUL (which is perfectly fine for AF_UNIX) Second though if you look at

[Qemu-devel] [Bug 1724477] Re: Build-in websocket broken since v2.9.0-rc0

2017-10-18 Thread Daniel Berrange
Note that we tightened up the websocket server impl to validate HTTP requests more strictly. One key change is that the websockets path is required to be empty, while noVNC will default to appending a path - so make sure you change noVNC to have an empty path. Also until GIT master yesterday,

[Qemu-devel] [Bug 1718964] Re: Memory leak when using websocket over a low speed network

2017-10-17 Thread Daniel Berrange
commit a7b20a8efa28e5f22c26c06cd06c2f12bc863493 Author: Daniel P. Berrange Date: Mon Oct 9 14:43:42 2017 +0100 io: monitor encoutput buffer size from websocket GSource The websocket GSource is monitoring the size of the rawoutput buffer to determine if the

[Qemu-devel] [Bug 1724570] Re: qemu-system-x86_64 generates ACPI tables with broken endianess when run on big-endian hosts

2017-10-18 Thread Daniel Berrange
** Attachment added: "AML for APIC generated on ppc64 host" https://bugs.launchpad.net/qemu/+bug/1724570/+attachment/4974806/+files/aml-APIC.ppc64 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1724570] Re: qemu-system-x86_64 generates ACPI tables with broken endianess when run on big-endian hosts

2017-10-18 Thread Daniel Berrange
** Attachment added: "AML for HPET generated on x86_64 host" https://bugs.launchpad.net/qemu/+bug/1724570/+attachment/4974811/+files/aml-HPET.x86_64 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1724570] Re: qemu-system-x86_64 generates ACPI tables with broken endianess when run on big-endian hosts

2017-10-18 Thread Daniel Berrange
** Attachment added: "AML for HPET generated on ppc64 host" https://bugs.launchpad.net/qemu/+bug/1724570/+attachment/4974810/+files/aml-HPET.ppc64 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1724570] Re: qemu-system-x86_64 generates ACPI tables with broken endianess when run on big-endian hosts

2017-10-18 Thread Daniel Berrange
** Attachment added: "AML for DSDT generated on ppc64 host" https://bugs.launchpad.net/qemu/+bug/1724570/+attachment/4974808/+files/aml-DSDT.ppc64 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1724570] Re: qemu-system-x86_64 generates ACPI tables with broken endianess when run on big-endian hosts

2017-10-18 Thread Daniel Berrange
** Attachment added: "AML for APIC generated on x86_64 host" https://bugs.launchpad.net/qemu/+bug/1724570/+attachment/4974807/+files/aml-APIC.x86_64 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1724570] [NEW] qemu-system-x86_64 generates ACPI tables with broken endianess when run on big-endian hosts

2017-10-18 Thread Daniel Berrange
Public bug reported: The bios-tables-test always fails when run on a big-endian host, which has iasl installed. When it calls iasl to dumps the AML files into ASL files, iasl complains Intel ACPI Component Architecture ASL+ Optimizing Compiler/Disassembler version 20170831 Copyright (c) 2000 -

[Qemu-devel] [Bug 1724570] Re: qemu-system-x86_64 generates ACPI tables with broken endianess when run on big-endian hosts

2017-10-18 Thread Daniel Berrange
** Attachment added: "AML for DSDT generated on x86_64 host" https://bugs.launchpad.net/qemu/+bug/1724570/+attachment/4974809/+files/aml-DSDT.x86_64 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Qemu-devel] [Bug 1725707] Re: QEMU sends excess VNC data to websockify even when network is poor

2017-10-23 Thread Daniel Berrange
This is nothing specific to websockets AFAIK. Even using regular VNC QEMU doesn't try to dynamically throttle data / quality settings. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1725707 Title:

[Qemu-devel] [Bug 1725707] Re: QEMU sends excess VNC data to websockify even when network is poor

2017-10-23 Thread Daniel Berrange
NB, if websockify crashes, then that is a serious flaw in websockify - it shouldn't read an unbounded amount of data from QEMU, if it is unable to send it onto the client. If websockify stopped reading data from QEMU, then QEMU would in turn stop sending it once the TCP buffer was full -- You

[Qemu-devel] [Bug 1726910] Re: UI request: add a function key toolbar (f1-f12)

2017-11-09 Thread Daniel Berrange
Adding a toolbar with function keys consumes alot of screen real estate for something that is going to be rarely used in practice. The more usual approach to this problem is for the application to grab the keyboard and block all local window system accelerators, so that Fn goes straight to the

[Qemu-devel] [Bug 1732671] Re: vnc websocket compatibility issue

2017-11-16 Thread Daniel Berrange
Which version of QEMU did you test this against ? It should be fixed in current GIT master AFAIK -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1732671 Title: vnc websocket compatibility issue

[Qemu-devel] [Bug 1732671] Re: vnc websocket compatibility issue

2017-11-16 Thread Daniel Berrange
No problem, it is a valid bug report, since we've not actually released the fix yet, so changing status. ** Changed in: qemu Status: Invalid => Fix Committed -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.