Hello.
As far as I can tell, this is still an issue with the latest available
ubuntu, 18.04.2, which has: version 2.11.1(Debian 1:2.11+dfsg-
1ubuntu7.15)
Anyone know where I could get a newer version that would be compatible
with Ubuntu?
--
You received this bug notification because you are a m
On 12/21/10 11:39, Olivier Galibert wrote:
> On Tue, Dec 21, 2010 at 09:18:08AM -0700, David S. Ahern wrote:
>>
>>
>> On 12/21/10 08:16, Olivier Galibert wrote:
>>>
>>> Hi all,
>>>
>>> Google sees patches to hw/usb-ehci.c from ti
On 12/21/10 08:16, Olivier Galibert wrote:
>
> Hi all,
>
> Google sees patches to hw/usb-ehci.c from time to time, in
> http://www.mail-archive.com/qemu-devel@nongnu.org/msg37741.html for
> instance. Where is that code hiding, since I just can't find it in
> the git tree?
git://git.kiszka.o
On 12/09/10 06:05, Gerd Hoffmann wrote:
>
> Hi,
>
>> New features developed for the kernel are done in a separate git trees.
>> When a feature is ready for inclusion into the main kernel tree, a pull
>> request is sent. That workflow maintains a complete change history for
>> the feature. Tak
On 12/08/10 01:32, Jan Kiszka wrote:
> Am 08.12.2010 09:26, Gerd Hoffmann wrote:
>> Hi,
>>
>>> It appears that the import of the ehci code to spice has completely lost
>>> the development history and code contributions - from the original
>>> version by Mark Burkley through the work I've done o
On 12/04/10 02:05, Jan Kiszka wrote:
> Am 04.12.2010 01:18, Gerd Hoffmann wrote:
>> Hi,
>>
>>> as you may know, there is an experimental git repository at
>>>
>>> git://git.kiszka.org/qemu.git ehci
>>
>> Looking into this right now as I'm busy with various usb issues anyway.
>> Current stat
On 11/11/10 14:17, Stefan Weil wrote:
> Am 11.11.2010 21:37, schrieb Russell Morris:
>> Hi,
>>
>> Thanks for the pointer! I tried this, but I get an error message, as
>> follows ...
>> *chardev: opening backent "stdio" failed*
>> *qemu: could not open serial device 'stdio': Inappropriate ioctl fo
ppropriate ioctl for
> device.*
qemu command line?
David
>
>
>
> Thoughts?
>
>
>
> Thanks again!
>
>
>
> On Thu, Nov 11, 2010 11:22 AM, "David S. Ahern" wrote:
>
> On 11/11/10 09:57, Mulyadi Santosa wrote:
> > On Thu,
On 11/11/10 09:57, Mulyadi Santosa wrote:
> On Thu, Nov 11, 2010 at 12:50, wrote:
>> Hi,
>>
>> Is there a way to log / copy the console output (like the Linux boot info,
>> if booting QEMU to Linux) to a file?
>
> I think you could consider booting Linux in serial console...then
> start Qemu
On 08/04/10 11:34, Avi Kivity wrote:
>> And it's awesome for fast prototyping. Of course, once that fast
>> becomes dog slow, it's not useful anymore.
>
> For the Nth time, it's only slow with 100MB initrds.
100MB is really not that large for an initrd.
Consider the deployment of stateless no
On 08/03/10 12:43, Avi Kivity wrote:
> libguestfs does not depend on an x86 architectural feature.
> qemu-system-x86_64 emulates a PC, and PCs don't have -kernel. We should
> discourage people from depending on this interface for production use.
That is a feature of qemu - and an important one
ping. This patch request was first submitted to the list 3 weeks ago. If
there are no objections, please apply.
On 07/26/10 07:50, David Ahern wrote:
> Create USB buses and devices based on USB version. This addresses
> addresses a number of FIXME's by assigning USB devices to a specific bus.
> t
How do I get X86_FEATURE_ARCH_PERFMON enabled for a guest?
I've tried "-cpu host,+perfmon" and "-cpu host,+arch_perfmon", but both
get rejected with an error: CPU feature perfmon not found
Host processor:
model name : Intel(R) Xeon(R) CPU E5540 @ 2.53GHz
stepping: 5
...
On 07/20/10 08:45, Chris Wright wrote:
> 0.13
> - rc RSN (hopefully this week, top priority for anthony)
Can Cam's inter-vm shared memory device get committed for 0.13? It's
been stagnant on the list for a while now waiting for inclusion (or NAK
comments).
David
On 07/20/10 10:09, jes.soren...@redhat.com wrote:
> From: Jes Sorensen
>
> O_DIRECT (cache=none) requires sector alignment, however the physical
> sector size of CDROM/DVD drives is 2048, as opposed to most disk
> devices which use 512. QEMU is hard coding 512 all over the place, so
> allowing
On 07/20/10 10:02, Jes Sorensen wrote:
> On 07/20/10 17:40, Anthony Liguori wrote:
>> On 07/20/2010 10:17 AM, jes.soren...@redhat.com wrote:
>>> From: Jes Sorensen
>>>
>>> O_DIRECT (cache=none) requires sector alignment, however the physical
>>> sector size of CDROM/DVD drives is 2048, as opposed
On 07/14/10 11:56, David Ahern wrote:
> Create USB buses and devices based on USB version.
>
> Signed-off-by: David Ahern
ping.
Relative to current code this addresses a number of FIXME's by assigning
USB devices to a specific bus. It is also groundwork for adding ehci.
David
> ---
> hw/usb-
On 07/10/10 00:02, Jan Kiszka wrote:
> They improve disk pass-through for me as well. I'm now also able to boot
> from some external USB disk. However, applying more heavy load, the disk
> stops working at some point and even disconnects after a while.
I saw that as well. On the TO-DO list.
> T
On 07/08/10 15:08, Cam Macdonell wrote:
> Resent (again): Some lines were over 80 characters and debugging is now off.
>
> Support an inter-vm shared memory device that maps a shared-memory object as a
> PCI device in the guest. This patch also supports interrupts between guest by
> communicatin
On 07/08/10 08:42, Jan Kiszka wrote:
> David S. Ahern wrote:
>>
>> On 07/08/10 01:49, Jan Kiszka wrote:
>>> David Ahern wrote:
>>>> Per the EHCI specification a USB 2.0 host controller is comprised of one
>>>> high-speed controller and 0 to N U
On 07/08/10 01:49, Jan Kiszka wrote:
> David Ahern wrote:
>> Per the EHCI specification a USB 2.0 host controller is comprised of one
>> high-speed controller and 0 to N USB 1.1 companion host controllers (UHCI or
>> OHCI) for low- and full-speed devices. Port routing and control logic
>> dete
On 06/23/10 22:45, TJ wrote:
>
>> -- Forwarded message --
>> From: Timothy Jones
>> Date: Wed, Jun 23, 2010 at 9:07 PM
>> Subject: Guest OS hangs on usb_add
>> To: qemu-devel@nongnu.org
>>
>>
>> With some digging around I found out that the qemu hangs in
>> usb_host_claim_interf
On 06/10/10 12:26, Natalia Portillo wrote:
> Hi David,
>
>> Attempting to try out your patches, but it's failing with the following:
>>
>> usb-uvc: Init called
>> usb-uvc: Trying to open /dev/video0
>> .usb-uvc: Device opened correctly.
>> usb-uvc: Querying capabilities.
>> usb-uvc: Device drive
On 06/08/10 09:34, Natalia Portillo wrote:
> Hi,
>
> This currently adds an emulated USB webcam compliant with USB Video Class
> Specification 1.0a.
>
> It only works on Linux guests and feeds the emulated device using a
> Video4Linux 2 host device, as long as it supports 320x240 MJPEG format
On 06/07/10 12:46, Avi Kivity wrote:
> On 06/07/2010 07:31 PM, David S. Ahern wrote:
>>
>> On 06/07/10 09:26, Avi Kivity wrote:
>>
>>
>>> The original motivation for moving the PIC and IOAPIC into the kernel
>>> was performance, especially
On 06/07/10 09:26, Avi Kivity wrote:
> The original motivation for moving the PIC and IOAPIC into the kernel
> was performance, especially for assigned devices. Both devices are high
> interaction since they deal with interrupts; practically after every
> interrupt there is either a PIC ioport
On 06/03/10 09:41, Nico Prenzel wrote:
> Hello Anthony,
>
> which qemu-kvm version do you expect to work with serial usb devices?
>
> After you've changed this ticket status and I've checked it again with
> qemu-kvm version 0.12.4. The reported error message is gone away and the
> device is p
On 05/26/2010 07:23 AM, Kevin Wolf wrote:
> Am 26.05.2010 15:06, schrieb David S. Ahern:
>>
>>
>> On 05/26/2010 06:48 AM, Gerd Hoffmann wrote:
>>>
>>> Hi,
>>>
>>>>> USB devices can support both 1.1 and 2.0, right? Who decides whic
On 05/26/2010 06:48 AM, Gerd Hoffmann wrote:
>
> Hi,
>
>>> USB devices can support both 1.1 and 2.0, right? Who decides which
>>> protocol is used then? I think the OS can speak 1.1 to the device even
>>> in case a ehci controller is present (but unused by the OS), right?
>>
>> AFAIK the OS
USB 2.0 leverages companion UHCI or OHCI host controllers for full and
low speed devices. I do not see an appropriate means for doing that bus
transition and could use some suggestions.
I've read through the code for the "legacy" path in handling USB devices
(-usbdevice CLI arg and usb_add monito
On 05/21/2010 10:10 AM, Adnan Khaleel wrote:
> So do you have any idea whats causing the problem? Is there any other
> way I can mount a dvd in Qemu?
>
> Adnan
have you tried ejecting the cd in the guest before changing the file in
the monitor?
David
> On 05/21/2010 1:33 AM, Markus Armbruster wrote:
> Note: usbdevice_init() is not for general initialization, just for
> dealing with the legacy -usbdevice command line.
Perhaps the comment before usbdevice_create is misleading or has some
conversion not completed? Right now even devices entered t
On 05/20/2010 03:48 PM, Adnan Khaleel wrote:
> Thanks for your response.
>
>
> Does it work if the guest uses ide based CD's:
> rmmod ide-scsi
> modprobe ide-cd
>
> There isn't an ide-scsi but there is a scsi_mod and when I try to remove
> that it gives
> ERROR: Module scsi_mod is
On 05/20/2010 02:29 PM, Adnan Khaleel wrote:
> I cannot change DVD roms during execution using the monitor. I can only
> mount a cdrom/dvdrom if I specify the iso file in the command line
> x86_64-softmmu/qemu-system-x86_64 -hda ../../OSImages/sles11.qcow2
> -cdrom ../../ISOz/mydvd.iso -m 2048
>
On 05/19/2010 12:10 PM, Shahar Havivi wrote:
> When closig Vm or removing usb on guest via usb_del monitor command,
> qemu does not return the control to the host, the user have to
> unplug and plug the device in order to use it on the host.
>
> v2:
> added empty methods to usb-bsd and usb-stub.
On 05/09/2010 08:32 PM, Vincent Palatin wrote:
> Dear developers,
>
> While using the EHCI patchset, I have found 2 minor issues.
> So, I send in this email thread 2 fix proposals.
Changes look good to me.
Are you looking at any particular device or EHCI in general?
David
>
> Those patches
Hi Jan:
The attached addresses the spinning with the usb net device. Now I can
enable the device and ethtool shows a link:
# ifconfig usb0 up
# ethtool usb0
Settings for usb0:
Current message level: 0x0007 (7)
Link detected: yes
Though dhclient still can't get an address. Aft
On 04/13/2010 07:20 PM, Alexander Graf wrote:
It still needs a lot of love, but definitely an improvement from the
last version. The biggest difference for the performance boost and
stability is discovering that the usbfs in linux limits transactions to
16k versus the EHCI spe
On 04/13/2010 05:35 PM, Jan Kiszka wrote:
> David S. Ahern wrote:
>> After a month of code refactoring and clean ups, etc, I thought I would
>> send along an update. The attached patch is relative to your ehci
>> branch; I also attached the full usb-ehci.c file for easier
On 03/10/2010 02:45 AM, Arnaud Patard (Rtp) wrote:
>
> The usb-msd device emulation needs some small tweaks in the requests
> emulations. For instance, the reset/maxlun requests are class/interface
> specific so requests for them with the type class and recipient interface
> bits sets have to b
On 03/07/2010 04:32 AM, Jan Kiszka wrote:
> Kevin Wolf wrote:
>> Am Freitag, 5. März 2010 04:17 schrieb David S. Ahern:
>>> Jan:
>>>
>>> I spent some more time on the EHCI support today. With the attached
>>> patch (delta to the patch from yest
Jan:
I spent some more time on the EHCI support today. With the attached
patch (delta to the patch from yesterday) a USB key is recognized within
the guest (FC-12):
scsi 2:0:0:0: Direct-Access Kingston DT HyperXPMAP PQ: 0
ANSI: 0 CCS
sd 2:0:0:0: Attached scsi generic sg1 type 0
sd 2:0
On 03/03/2010 04:47 PM, Jan Kiszka wrote:
>
> Thanks for your work, David and Niels! I assume that David based this on
> Niels' patch, so there is nothing to be merged? David's version built
> for me, so I pushed
>
> git://git.kiszka.org/qemu.git ehci
>
> So far it's supposed to be a refer
On 02/27/2010 01:41 AM, Shahar Havivi wrote:
> On Fri, Feb 26, 2010 at 03:19:19PM -0700, David S. Ahern wrote:
>> Date: Fri, 26 Feb 2010 15:19:19 -0700
>> From: "David S. Ahern"
>> To: Shahar Havivi
>> CC: qemu-devel@nongnu.org, Dor Laor
>> Subject
On 02/26/2010 01:04 PM, Shahar Havivi wrote:
> Fix codding style
> ---
> qemu-char.c |9 +
> 1 files changed, 9 insertions(+), 0 deletions(-)
>
> diff --git a/qemu-char.c b/qemu-char.c
> index 4169492..4533887 100644
> --- a/qemu-char.c
> +++ b/qemu-char.c
> @@ -1002,6 +1002,7 @@
David Ahern
On 02/22/2010 12:32 AM, Taimoor Mirza wrote:
> Hi all,
>
> I've few questions about QEMU:
>
> 1) I read in QEMU's official documentation that in case of using host
> system devices "USB devices requiring real time streaming (i.e. USB
> Video Cameras) are not supported yet". Also
On 02/20/2010 12:42 PM, Shahar Havivi wrote:
> On Sat, Feb 20, 2010 at 11:03:41AM -0600, Anthony Liguori wrote:
>> Date: Sat, 20 Feb 2010 11:03:41 -0600
>> From: Anthony Liguori
>> To: "David S. Ahern"
>> Cc: Dor Laor , Shahar Havivi ,
>> qemu-d
On 02/20/2010 10:03 AM, Anthony Liguori wrote:
> On 02/20/2010 09:18 AM, David S. Ahern wrote:
>> On 02/20/2010 01:30 AM, Shahar Havivi wrote:
>>
>>> when exiting qemu that run with "-monitor /dev/tty", the launching
>>> terminal get weird behavi
On 02/20/2010 01:30 AM, Shahar Havivi wrote:
> when exiting qemu that run with "-monitor /dev/tty", the launching
> terminal get weird behaviour because no restore terminals action has
> taken.
> added chr_close and register atexit() code for tty devices (like stdio
> does)
>
> Signed-off-by: Sha
I have not seen a follow up. I believe the comments regarding whitespace
and coding style have been addressed.
Thanks,
David Ahern
On 02/10/2010 06:27 PM, David Ahern wrote:
> v1 -> v2 coding style changes
>
> Add a tty close callback. Right now if a guest device that is connected
> to a tty-b
I have not seen a response to this. If there are no objections please apply.
Thanks,
David Ahern
On 02/03/2010 08:49 AM, David S. Ahern wrote:
>
> I have streaming audio devices working within qemu-kvm. This is a port
> of the changes to qemu.
>
> Streaming audio genera
I have not seen response to this. If there are no objections please apply.
Thanks,
David Ahern
On 02/03/2010 09:18 AM, David S. Ahern wrote:
> Add a tty close callback. Right now if a guest device that is connected
> to a tty-based chardev in the host is removed, the tty is not closed.
I have not seen response to this. If there are no objections please apply.
Thanks,
David Ahern
On 02/03/2010 09:00 AM, David S. Ahern wrote:
> This fixes a segfault due to buffer overrun in the usb-serial device.
> The memcpy was incrementing the start location by recv_used ye
Add a tty close callback. Right now if a guest device that is connected
to a tty-based chardev in the host is removed, the tty is not closed.
With this patch it is closed.
Example use case is connecting an emulated USB serial cable in the guest
to tty0 of the host using the monitor command:
usb_a
This fixes a segfault due to buffer overrun in the usb-serial device.
The memcpy was incrementing the start location by recv_used yet, the
computation of first_size (how much to write at the end of the buffer
before wrapping to the front) was not accounting for it. This causes the
next element afte
I have streaming audio devices working within qemu-kvm. This is a port
of the changes to qemu.
Streaming audio generates a series of isochronous requests that are
repetitive and time sensitive. The URBs need to be submitted in
consecutive USB frames and responses need to be handled in a timely ma
On 02/02/2010 06:42 AM, Michael Buesch wrote:
> Hi,
>
> I've got a buggy device that needs a special workaround to be usable under
> host-usb access. The device really doesn't like being reset via
> USBDEVFS_RESET. It
> immediatenly locks up the device firmware or whatever. It won't respond
> p
On 01/03/2010 11:19 AM, David S. Ahern wrote:
>
> After weeks of fruitless effort I could use some help getting a USB
> audio device to work. I have instrumented the hell out of the guest
> driver and uhci code, qemu's linux and uhci code, and the host side usb
> code. Nea
After weeks of fruitless effort I could use some help getting a USB
audio device to work. I have instrumented the hell out of the guest
driver and uhci code, qemu's linux and uhci code, and the host side usb
code. Near as I can tell data from the device makes its way into qemu
(async_complete show
On 12/21/2009 06:51 AM, Michael S. Tsirkin wrote:
> On Mon, Dec 21, 2009 at 06:45:22AM -0700, David S. Ahern wrote:
>>
>> On 12/21/2009 05:05 AM, Avi Kivity wrote:
>>> On 12/21/2009 01:45 PM, Alexander Graf wrote:
>>>>
>>>> Well, we have two gro
On 12/21/2009 05:05 AM, Avi Kivity wrote:
> On 12/21/2009 01:45 PM, Alexander Graf wrote:
>>
>> Well, we have two groups:
>>
>> 1) Casual user w/o management app
>> 2) Enterprise user w/ management app
>>
>> So I clearly belong to the first group.
>>
>
> 3) Developer/power user who knows what
et it. Hopefully by the end of the week I can get make to
reproducing the abort and capturing a core.
David Ahern
On 12/14/2009 09:04 AM, Luiz Capitulino wrote:
> On Sat, 12 Dec 2009 11:09:38 -0700
> "David S. Ahern" wrote:
>
>> Thanks for the responses. I had forgotten that SIG
, Stefan Weil wrote:
> David S. Ahern schrieb:
>> I realize this is a rather generic question, but what are typical
>> reasons Qemu would be killed by a SIGABRT? I am seeing this on a
>> somewhat regular (though not repeatable on demand) basis. I do not have
>> a core file, t
I realize this is a rather generic question, but what are typical
reasons Qemu would be killed by a SIGABRT? I am seeing this on a
somewhat regular (though not repeatable on demand) basis. I do not have
a core file, though I hope to capture one if I can get it repeat again.
Thanks,
--
David Ahern
64 matches
Mail list logo
