On Sat, Jan 30, 2010 at 3:44 AM, Anthony Liguori wrote:
> Hi,
>
> I've been (slowly) working to convert qemu.org to a wiki in order to allow
> more community participation in the website. I've finally got a site setup
> and to my liking with all of the www.qemu.org content migrated.
>
> Before do
s documentation only change updates the instructions to:
* Remove use of '--enable-mingw32' in the configure example
* Correct the 'sdl-config' script name
* Remove references to i386-mingw32msvc.tar.gz which no longer exists in
recent SDL releases
* Document the zlib dependen
On Mon, Dec 28, 2009 at 4:34 AM, Aurelien Jarno wrote:
> Most of the patches I commit without posting them first to the list are
> to fix bugs on non i386 targets, as they are broken too often by people
> who don't care about them.
>
> I don't like leaving the tree broken too long so I prefer to f
On Tue, Dec 22, 2009 at 11:05 PM, Anthony Liguori wrote:
> On 12/22/2009 02:52 AM, Aurelien Jarno wrote:
>>
>> In version 0.12.1, using -usbdevice with an inexistent device exits
>> without any error message, thus confusing the user:
>
> Would be good to file in launchpad since I think a lot of fo
When an non-existent USB device is specified on the command line,
print "qemu: could not add USB device 'X'".
Likewise for the usb_{add,del} monitor commands.
Signed-off-by: Scott Tsai
---
vl.c | 17 ++---
1 files changed, 14 insertions(+), 3 deletions(-)
diff
On Fri, Dec 4, 2009 at 8:55 AM, Christoffer Dall wrote:
> I tried to verify if the bug existed with Realview, but I just can't get the
> guest to mount an sd-card, which I created with qemu-img and copied a roots
> onto there and the guest kernel cannot be configured with PCI/SCSI support
> for th
On Wed, Dec 2, 2009 at 7:26 PM, Kevin Wolf wrote:
> v3 even. Anthony, I hope this doesn't confuse your scripts?
Kevin, I see use of fopen, fdopen, popen, eventfd in qemu without the
equivalent of CLOEXEC set.
Do you want to handle those in this patch series as well?
209,6 @@ if test "$target" = "arm-linux-user" -o "$target" =
> "armeb-linux-user" -o "$targ
> mkdir -p $target_dir/nwfpe
> fi
>
> -if test ! -f $target_dir/config-devices.mak ; then
> - cp $source_path/default-configs/${target}.mak
&g
On Sat, Nov 21, 2009 at 7:29 AM, Aurelien Jarno wrote:
> On Thu, Nov 19, 2009 at 05:48:02PM -0500, Christoffer Dall wrote:
>> Hi.
>>
>> I am experiencing problems with bridged networking to ARM guests. I have
>> experimented with various kernel versions, distributions and host
>> machines and I ex
On Fri, Nov 20, 2009 at 6:48 AM, Christoffer Dall wrote:
> When I copy files into the guest using SCP, after an undeterministic number
> of megabytes have been copied, the network crashes. At this point not even
> pings to localhost works inside the guest.
I cannot reproduce this with v0.11.0 emu
On Fri, Nov 13, 2009 at 11:17 PM, Kevin Wolf wrote:
> We're leaking file descriptors to child processes. Set FD_CLOEXEC on file
> descriptors that don't need to be passed to children to stop this
> misbehaviour.
Since qemu is a multi threaded program, how about opening those file
descriptors wit
On Thu, Nov 12, 2009 at 2:09 AM, Michael S. Tsirkin wrote:
>> I do have a newbie question, when exactly would vrtio have to handle
>> concurrent access from multiple threads?
>> My current reading of the code suggests:
>> 1. when CONFIG_IOTHREAD is true
>> 2. when CONFIG_KVM is true and the guest
On Wed, Nov 11, 2009 at 10:08 PM, Michael S. Tsirkin wrote:
> On Wed, Nov 11, 2009 at 01:45:35PM +, Paul Brook wrote:
>> If you don't need real barriers, then why does the kvm code have them?
>
> We need real barriers but AFAIK kvm does not have them :(
> IOW: virtio is currently broken with k
On Wed, Nov 11, 2009 at 8:09 AM, Anthony Liguori wrote:
> That said, if we position this as an example device, I think that makes
> sense. But that suggests that we should document the heck out of it and
> make it a learning experience for QEMU too. It could be an example of how
> to write a sim
On Wed, Nov 11, 2009 at 8:57 AM, Greg KH wrote:
>
> What code? Where is it at?
http://patchwork.ozlabs.org/patch/38118/
This code emulates a Vernier Go!Temp device in qemu.
I wrote this to enable people to follow your driver tutorial without
buying the gadget.
(I implemented functionality not e
Adds documentation for the '-usbdevice thermometer' option.
Signed-off-by: Scott Tsai
---
qemu-options.hx |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/qemu-options.hx b/qemu-options.hx
index b65fd74..c2e3b6c 100644
--- a/qemu-options.hx
+++ b/qemu-
r',
the temperature would increment on each report but is bound between 25C
~ 40C.
Added new monitor commands:
info thermometers
therm_set INDEX
therm_temp TEMPERATURE
modeled after 'info mice', 'mouse_set' and 'mouse_move'
Move USB HID request constants from hw/usb-hid.c to hw/usb.h
to allow other modules to use them.
Signed-off-by: Scott Tsai
---
hw/usb-hid.c | 20 ++--
hw/usb.h |8
2 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/hw/usb-hid.c b/hw/usb-hid.c
I reworked the second patch in this series to add generic monitor commands
to change the temperature reported from thermometers.
Thermometer devices can now include "sensor.h" and call
'qemu_add_therm_temp_handler'
to register themselves.
I went with separate 'therm_set DEVICE_INDEX' and 'therm_
or',
the temperature would increment on each report but is bound between 25C
~ 40C.
Added new monitor commands:
info thermometers
therm_set DEVICE_INDEX
therm_temp TEMPERATURE
modeled after 'info mice', 'mouse_set' and 'mouse_move'.
S
On Wed, Nov 11, 2009 at 1:06 AM, Luiz Capitulino wrote:
>>
>> I'd certainly like to make this code useful for something other than
>> developer training.
>> How about a new monitor command "thermometer_set" that works like
>> "mouse_move"?
>> "thermometer_set" would just set the temperature of th
On Tue, Nov 10, 2009 at 11:39 PM, Juan Quintela wrote:
> Change them in the middle of one interval?
> once then arrived same limit, 40° or so go back to 20°?
I can do this.
On Tue, Nov 10, 2009 at 11:33 PM, Alexander Graf wrote:
> How about having a monitor command to change the temperature, leveraging a
> "common interface"?
> That way in the future real host temperature measurements could maybe get
> forwarded there too. At least for battery I've had several people
>> + s->temperature++;
>>
> You're going to overheat very quickly.
> Apart from making the driver work, is this actually useful?
I wanted the temperature to change with time to give a sense of
"something is happening" ^_^
The main user I had in mind was someone new to USB and Linux driver deve
Adds documentation for the '-usbdevice thermometer' option.
Signed-off-by: Scott Tsai
---
qemu-options.hx |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/qemu-options.hx b/qemu-options.hx
index b65fd74..c2e3b6c 100644
--- a/qemu-options.hx
+++ b/qemu-
ernel 'ldusb' module under Linux.
No testing have yet been done with the vendor's fancier Windows software.
Signed-off-by: Scott Tsai
---
Makefile|2 +-
hw/usb-gotemp.c | 710 +++
2 files changed, 711 insertions(+), 1 dele
Move USB HID request constants from hw/usb-hid.c to hw/usb.h
to allow other modules to use them.
Signed-off-by: Scott Tsai
---
hw/usb-hid.c | 20 ++--
hw/usb.h |8
2 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/hw/usb-hid.c b/hw/usb-hid.c
Rebased on top of the master branch of git://git.savannah.nongnu.org/qemu.git
since
last posting. Any advice on how to get these reviewed and merged or rejected
greatly
appreciated!
Greg Kroah-Hartman has been giving a talk titled "Write a Real, Working, Linux
Driver"
for the past four years at
2009/11/7 m9807418 :
> When I used qemu-system-arm and the -smp option.
> I key -smp 2.
> It have a message ""Number of SMP cpus requested (2), exceeds max cpus
> supported by machine `Versatile' (1) "
> which files of the qemu source code can i change?
> And the change can let me emulator arm's m
On Fri, Nov 6, 2009 at 12:43 PM, Scott Tsai wrote:
> Michael,
> You might want to read these two threads:
> "RE: [Qemu-devel] Support for new target emulator":
> http://lists.gnu.org/archive/html/qemu-devel/2009-10/msg02131.html
> "[Qemu-devel] [PATCH 00/12] S/390 s
Michael,
You might want to read these two threads:
"RE: [Qemu-devel] Support for new target emulator":
http://lists.gnu.org/archive/html/qemu-devel/2009-10/msg02131.html
"[Qemu-devel] [PATCH 00/12] S/390 support"
http://lists.gnu.org/archive/html/qemu-devel/2009-10/msg01857.html
Document the '-usbdevice thermometer' option.
---
qemu-options.hx |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/qemu-options.hx b/qemu-options.hx
index d78b738..6748875 100644
--- a/qemu-options.hx
+++ b/qemu-options.hx
@@ -396,6 +396,9 @@ or fake device.
@item net:@v
ernel 'ldusb' module under Linux.
No testing have yet been done with the vendor's fancier Windows software.
Signed-off-by: Scott Tsai
---
Makefile|2 +-
hw/usb-gotemp.c | 709 +++
vl.c|3 +
3 files chan
Move USB HID request constants from hw/usb-hid.c to hw/usb.h
to allow other modules to use them.
Signed-off-by: Scott Tsai
---
hw/usb-hid.c | 20 ++--
hw/usb.h |8
2 files changed, 14 insertions(+), 14 deletions(-)
diff --git a/hw/usb-hid.c b/hw/usb-hid.c
Greg Kroah-Hartman has been giving a talk titled "Write a Real, Working, Linux
Driver"
for the past four years at various conferences. This patch series enables qemu
to emulate
the Vernier Go!Temp USB thermometer used in that talk.
This was motivated by experience from the FreedomHEC Taipei 200
Hi, Dustin,
What's the easiest way to see the patches to qemu that Canonical
carries for the different Ubuntu releases?
(I think http://patches.ubuntu.com/ only diffs against Debian for the
last stable Ubuntu release?)
Also, is there a way for an outside developer to get email
notifications when a
> Hmm - 0x930 doesn't seem right. Is that 930 decimal, 0x3a2 hex?
yup. printf format string typo.
input descriptors.
BTW, I can also reproduce this running Dustin's image inside Fedora 11's
qemu-0.10.6-9.fc11.x86_64.
The patch I posted earlier actually only applies to the 0.10 branch, here's a
patch that compiles for 0.11:
>From 06aa7db0705cf747c35cbcbd09d0e37713f16fe4 Mon S
virtio-net
to call exit(1).
>From d48af0377f359983bff67eb9296ba040def401ec Mon Sep 17 00:00:00 2001
From: Scott Tsai
Date: Thu, 29 Oct 2009 10:56:12 +0800
Subject: [PATCH] virtio-net: drop large packets when no mergable_rx_bufs
see: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/458521
---
hw/virtio-net.c |
> Scott, Sven, if you could test the tap-drain-queue branch from
> my tree, that would be great:
> http://repo.or.cz/w/qemu/markmc.git
>
> Thanks,
> Mark.
Mark,
I've tested http://repo.or.cz/w/qemu/markmc.git and it indeed works for my test
case
(NFS through emulated smc91c111 NIC on
p.txt after encountering this
problem and currently find the code
called from "tap_send()" ex: qemu_send_packet_async,
qemu_deliver_packet and the semantics of their return values pretty
confusing.
I'm sure my patch should be refined to both make both NFS root and the
originally i
41 matches
Mail list logo
