[Qemu-devel] [Bug 1247478] Re: usb passthrough mass storage write data corruption

2013-11-05 Thread Sascha Krissler
it is apparently not a qemu bug, but either a libusb or (more likely) linux bug. it happens on linux 3.6 but not linux 3.4, with the difference of: (USBFS_CAP_NO_PACKET_SIZE_LIM | USBFS_CAP_BULK_SCATTER_GATHER) added to the hcd capabilities bitfield in 3.6 -- You received this bug notification be

[Qemu-devel] [Bug 1247478] [NEW] usb passthrough mass storage write data corruption

2013-11-02 Thread Sascha Krissler
Public bug reported: the windows 7 professional guest writes to usb high speed mass storage devices connected via host-libusb in bulk packages of either size 20480 or 4096 (as far as the actual file data is concerned and except for the last packet for odd-sized files). The pattern is: 3 times bu

[Qemu-devel] [Bug 1216368] Re: unsupported screen resolution crashes sdl-qemu

2013-10-16 Thread Sascha Krissler
this patch does solve 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/1216368 Title: unsupported screen resolution crashes sdl-qemu Status in QEMU: New Bug description: if the (wind

[Qemu-devel] [Bug 1216368] Re: unsupported screen resolution crashes sdl-qemu

2013-08-26 Thread Sascha Krissler
its in the first sentence. let me rephrase: the (windows) guest can select some screen resolution which SDL cannot provide. what happens is that qemu quits without giving the quest a chance to shut down. thats like having a monitor that crashes windows when it doesnt support the video mode. --

[Qemu-devel] [Bug 1216368] [NEW] unsupported screen resolution crashes sdl-qemu

2013-08-24 Thread Sascha Krissler
Public bug reported: if the (windows) guest sets a screen resolution that the SDL backend does not support, qemu does an exit(1). with this fix, the the resolution is still wrong (only part of the desktop is displayed), but qemu keeps running and the guest can auto-revert the video mode: ui/sdl

[Qemu-devel] [Bug 1196145] [NEW] usb-host: hostaddr=0XX is parsed as octal number

2013-06-29 Thread Sascha Krissler
Public bug reported: when doing device_add usb-host,hostaddr=010 taking 010 in the format of both lsusb or udev, qemu parses an octal number and assumes hostaddr=8. (i used a 2.0 device on the ehci.0 bus) at least to me that is confusing. also: when adding a non-existent usb device (bogus hos

[Qemu-devel] [Bug 1196145] Re: usb-host: hostaddr=0XX is parsed as octal number

2013-06-29 Thread Sascha Krissler
ps: when using host-libusb.c and tested on 1.5.1.tgz -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1196145 Title: usb-host: hostaddr=0XX is parsed as octal number Status in QEMU: New Bug descri