> This patch is actually wrong and we should rather make proper -R values the
> default instead of relying on MAP_32BIT.
I don't understand what "make proper -R values" means. Where/how we can apply
"-R"?
Regards,
chenwj
I've been trying for several days now to get my OEM copy of Windows XP to pre-activate properly in Qemu-kvm. I saw the instructions for patching the seabios here:http://lists.gnu.org/archive/html/qemu-devel/2011-03/msg03080.htmlThat seems to have worked as expected. When I boot, it shows the newl
Well the issue is not new, anyhow, following a conversation with Orit ...
Since we want the migration to finish, I believe that the "migration
speed" parameter alone cannot do the job.
I suggest using two distinct parameters:
1. Migration speed - will be used to limit the network resources util
On 2011年06月04日 03:03, Luiz Capitulino wrote:
In a recent discussion on the mailing list regarding the introduction of
the BLOCK_TRAY_OPEN and BLOCK_TRAY_CLOSE events[1], it was mentioned that
we need to fix the eject command and maybe introduce new commands first.
Here's a my proposal.
This ser
On Mon, Dec 19, 2011 at 12:02:59PM -0600, Anthony Liguori wrote:
> We really need to update SeaBIOS whenever there is a bug that we
> know requires an update. Things breakdown because of one or more of
> the following reasons:
>
> 1) User submits a patch to seabios@, Kevin applies it. But that
>
On 12/19/2011 08:46 PM, Anthony Liguori wrote:
On 12/19/2011 07:19 PM, Jan Kiszka wrote:
On 2011-12-20 02:08, Anthony Liguori wrote:
Here's how we solve this problem:
1) In the short term, advertise both devices as having the same VMstate name.
Since we don't register until the device is insta
On 12/19/2011 07:19 PM, Jan Kiszka wrote:
On 2011-12-20 02:08, Anthony Liguori wrote:
There's lot of inconsistency in qdev already today so adding a little
more isn't the end of the world. We're going to need to eventually have
this debate soon so it's up to you whether you want to just get thi
The Buildbot has detected a new failure on builder default_x86_64_fedora16
while building qemu.
Full details are available at:
http://buildbot.b1-systems.de/qemu/builders/default_x86_64_fedora16/builds/121
Buildbot URL: http://buildbot.b1-systems.de/qemu/
Buildslave for this Build: kraxel_fedor
On 2011-12-20 02:19, Jan Kiszka wrote:
> On 2011-12-20 02:08, Anthony Liguori wrote:
>> On 12/19/2011 06:37 PM, Jan Kiszka wrote:
>>> On 2011-12-20 01:32, Anthony Liguori wrote:
On 12/19/2011 05:49 PM, Jan Kiszka wrote:
> On 2011-12-19 23:24, Anthony Liguori wrote:
>> On 12/19/2011 03:
On 2011-12-20 01:53, Anthony Liguori wrote:
> On 12/19/2011 06:34 PM, Jan Kiszka wrote:
>> On 2011-12-20 01:31, Anthony Liguori wrote:
>>> On 12/19/2011 05:45 PM, Jan Kiszka wrote:
On 2011-12-19 23:21, Anthony Liguori wrote:
> On 12/15/2011 06:33 AM, Jan Kiszka wrote:
>> To enable migr
On 2011-12-20 02:08, Anthony Liguori wrote:
> On 12/19/2011 06:37 PM, Jan Kiszka wrote:
>> On 2011-12-20 01:32, Anthony Liguori wrote:
>>> On 12/19/2011 05:49 PM, Jan Kiszka wrote:
On 2011-12-19 23:24, Anthony Liguori wrote:
> On 12/19/2011 03:17 PM, Marcelo Tosatti wrote:
>>
>> An
On 12/19/2011 06:37 PM, Jan Kiszka wrote:
On 2011-12-20 01:32, Anthony Liguori wrote:
On 12/19/2011 05:49 PM, Jan Kiszka wrote:
On 2011-12-19 23:24, Anthony Liguori wrote:
On 12/19/2011 03:17 PM, Marcelo Tosatti wrote:
Anthony,
Can you please review&ACK?
You could even apply directly b
>From VNC, you access the monitor via Ctrl-Alt-2 and Ctrl-Alt-1. It
works the same.
"info mice" gives me:
* Mouse #1: QEMU USB Tablet (absolute)
Mouse #0: QEMU PS/2 Mouse
As for Windows and VESA, I'm not sure what it's doing, but I can select
all sorts of resolutions, like 1440x900. The defau
On 12/19/2011 06:34 PM, Jan Kiszka wrote:
On 2011-12-20 01:31, Anthony Liguori wrote:
On 12/19/2011 05:45 PM, Jan Kiszka wrote:
On 2011-12-19 23:21, Anthony Liguori wrote:
On 12/15/2011 06:33 AM, Jan Kiszka wrote:
To enable migration between accelerated and non-accelerated APIC
models,
we wil
On 12/19/2011 06:37 PM, Jan Kiszka wrote:
On 2011-12-20 01:32, Anthony Liguori wrote:
On 12/19/2011 05:49 PM, Jan Kiszka wrote:
On 2011-12-19 23:24, Anthony Liguori wrote:
On 12/19/2011 03:17 PM, Marcelo Tosatti wrote:
Anthony,
Can you please review&ACK?
You could even apply directly b
On 12/19/2011 06:32 PM, Jan Kiszka wrote:
On 2011-12-20 01:28, Anthony Liguori wrote:
On 12/19/2011 05:32 PM, Jan Kiszka wrote:
struct APICCommonInfo {
DeviceInfo qdev;
void (*init)(APICState *s);
void (*set_base)(APICState *s, uint64_t val);
void (*set_tpr)(APICState *s
On 2011-12-20 01:32, Anthony Liguori wrote:
> On 12/19/2011 05:49 PM, Jan Kiszka wrote:
>> On 2011-12-19 23:24, Anthony Liguori wrote:
>>> On 12/19/2011 03:17 PM, Marcelo Tosatti wrote:
Anthony,
Can you please review& ACK?
You could even apply directly but well do a
On 2011-12-20 01:31, Anthony Liguori wrote:
> On 12/19/2011 05:45 PM, Jan Kiszka wrote:
>> On 2011-12-19 23:21, Anthony Liguori wrote:
>>> On 12/15/2011 06:33 AM, Jan Kiszka wrote:
To enable migration between accelerated and non-accelerated APIC
models,
we will need to handle the tim
On 12/19/2011 05:49 PM, Jan Kiszka wrote:
On 2011-12-19 23:24, Anthony Liguori wrote:
On 12/19/2011 03:17 PM, Marcelo Tosatti wrote:
Anthony,
Can you please review& ACK?
You could even apply directly but well do a kvm-autotest run through
uq/master. Still, your review is needed.
Overall,
On 2011-12-20 01:28, Anthony Liguori wrote:
> On 12/19/2011 05:32 PM, Jan Kiszka wrote:
>>> struct APICCommonInfo {
>>> DeviceInfo qdev;
>>> void (*init)(APICState *s);
>>> void (*set_base)(APICState *s, uint64_t val);
>>> void (*set_tpr)(APICState *s, uint8_t val);
>>> voi
On 12/19/2011 05:45 PM, Jan Kiszka wrote:
On 2011-12-19 23:21, Anthony Liguori wrote:
On 12/15/2011 06:33 AM, Jan Kiszka wrote:
To enable migration between accelerated and non-accelerated APIC models,
we will need to handle the timer saving and restoring specially and can
no longer rely on the
On 12/19/2011 05:32 PM, Jan Kiszka wrote:
struct APICCommonInfo {
DeviceInfo qdev;
void (*init)(APICState *s);
void (*set_base)(APICState *s, uint64_t val);
void (*set_tpr)(APICState *s, uint8_t val);
void (*external_nmi)(APICState *s);
};
Take a look at SCSIDevice for a
On Mon, Dec 19, 2011 at 10:56:40PM +, David Woodhouse wrote:
> On Tue, 2011-12-20 at 09:31 +1100, David Gibson wrote:
> > When we're running paravirtualized under pHyp, it's impossible to
> > merge multiple PEs into one domain per se. We could fake it rather
> > nastily by replicating all map/
On 2011-12-19 23:24, Anthony Liguori wrote:
> On 12/19/2011 03:17 PM, Marcelo Tosatti wrote:
>>
>> Anthony,
>>
>> Can you please review& ACK?
>>
>> You could even apply directly but well do a kvm-autotest run through
>> uq/master. Still, your review is needed.
>
> Overall, it looks good except fo
On 2011-12-19 23:21, Anthony Liguori wrote:
> On 12/15/2011 06:33 AM, Jan Kiszka wrote:
>> To enable migration between accelerated and non-accelerated APIC models,
>> we will need to handle the timer saving and restoring specially and can
>> no longer rely on the automatics of VMSTATE_TIMER. Specif
[ Please strip your replies a bit. I always worry to miss a comment when
scrolling down dozens of pages. ]
On 2011-12-19 23:14, Anthony Liguori wrote:
>> +
>> +struct APICBackend {
>> +const char *name;
>> +void (*init)(APICState *s);
>> +void (*set_base)(APICState *s, uint64_t val);
>
On 12/19/2011 04:55 PM, Corey Bryant wrote:
diff --git a/net.c b/net.c
index f7bebf8..9296224 100644
--- a/net.c
+++ b/net.c
@@ -952,6 +952,14 @@ static const struct {
.type = QEMU_OPT_STRING,
.help = "script to shut down the interface",
}, {
+ .name = "br",
+ .type = QEMU_OPT_STRING,
+ .help
On Tue, 2011-12-20 at 09:31 +1100, David Gibson wrote:
> When we're running paravirtualized under pHyp, it's impossible to
> merge multiple PEs into one domain per se. We could fake it rather
> nastily by replicating all map/unmaps across mutiple PEs. When
> running bare metal, we could do so a b
On 12/19/2011 02:36 PM, Anthony Liguori wrote:
On 12/19/2011 07:11 AM, Corey Bryant wrote:
The most common use of -net tap is to connect a tap device to a
bridge. This
requires the use of a script and running qemu as root in order to
allocate a
tap device to pass to the script.
This model is
This does a simple test using device_add to add a block device. It uses a mix
of hmp and qmp commands because there is not yet a drive_add equivalent for
qmp.
Signed-off-by: Anthony Liguori
---
kernel-3.0.config |2 +-
tests/device-add.sh | 70 +++
On Mon, Dec 19, 2011 at 03:46:38PM +, David Woodhouse wrote:
> On Mon, 2011-12-19 at 11:11 +1100, David Gibson wrote:
> > They have no inbuilt concept
> > of domains (though we could fake in software in some circumstances).
>
> That sentence doesn't make much sense to me.
>
> Either you're
Some incremental findings:
In 'qemu-kvm' the DeviceState for the peer device of the
BlockDeviceState that gets created when a disk attached by 'virsh
attach-disk' references the 'QemuOpts' options structure that lists the
options and the device ID string (ex: as 'virtio-disk4') that will (on a
r
The peripheral[-anon] containers are initialized lazily but since they sit on
sysbus, they can not be created after realize. This was causing an abort() to
occur during hotplug if no -device option was used.
This was spotted by qemu-test::device-add.sh
Signed-off-by: Anthony Liguori
---
hw/qde
On 19.12.2011, at 23:01, Anthony Liguori wrote:
> On 12/19/2011 11:35 AM, Alexander Graf wrote:
>>
>> On 24.07.2011, at 17:55, Göran Weinholt wrote:
>>
>>> Multiboot images can specify a bss segment. The boot loader must clear
>>> the memory of the bss and ensure that no modules or structures a
>From the Qemu Monitor, try looking at "info mice"
I'm not exactly sure ho to access the Qemu Monitor from VNC. You might have
to start qemu with additional parameters: -monitor
telnet:localhost:12341,server,nowait
then use "telnet localhost 12341" to access the monitor...
On Monday 19 December
On 12/19/2011 03:17 PM, Marcelo Tosatti wrote:
Anthony,
Can you please review& ACK?
You could even apply directly but well do a kvm-autotest run through
uq/master. Still, your review is needed.
Overall, it looks good except for the backend/frontend split. This should be
done in terms of q
On 12/15/2011 06:33 AM, Jan Kiszka wrote:
To enable migration between accelerated and non-accelerated APIC models,
we will need to handle the timer saving and restoring specially and can
no longer rely on the automatics of VMSTATE_TIMER. Specifically,
accelerated model will not start any QEMUTime
On 12/19/2011 03:25 PM, Jordan Justen wrote:
On Mon, Dec 19, 2011 at 11:41, Anthony Liguori wrote:
On 12/15/2011 02:51 PM, Jordan Justen wrote:
If a pflash image is found, then it is used for the system
firmware image.
If a pflash image is not initially found, then a read-only
pflash device
On 12/15/2011 06:33 AM, Jan Kiszka wrote:
The KVM in-kernel APIC model will reuse parts of the user space model
while providing the same frontend view to guest and most management
interfaces. Introduce an APIC backend concept to encapsulate those
parts that will tell user space and KVM model apar
Add a post-load hook which invalidates the display. In particular, if we
don't do this and the display size we've just reloaded is larger than
the default then we will segfault trying to read off the end of the buffer.
Signed-off-by: Peter Maydell
---
hw/pl110.c | 11 +++
1 files chang
Implement save/load for the LAN9118.
Signed-off-by: Peter Maydell
---
Does anybody have a nicer solution to the "can't put an enum in a
VMStateDescription" problem?
hw/lan9118.c | 126 +++---
1 files changed, 103 insertions(+), 23 deletions(-
Add save/load support to the PL181.
Signed-off-by: Peter Maydell
---
This isn't terribly useful until hw/sd.c has save/load support, of
course; I have a patch cooking for that.
hw/pl181.c | 49 -
1 files changed, 40 insertions(+), 9 deletions(-)
On 12/19/2011 11:35 AM, Alexander Graf wrote:
On 24.07.2011, at 17:55, Göran Weinholt wrote:
Multiboot images can specify a bss segment. The boot loader must clear
the memory of the bss and ensure that no modules or structures are
allocated inside it. Several fields are provided in the Multibo
Anthony Liguori wrote:
On 12/19/2011 03:33 PM, Erik Rull wrote:
Hi all,
coming from qemu 0.14 the usbdevice tablet update rate gets really bad in
qemu-1.0 with the same guest.
What's the specific guest?
Regards,
Anthony Liguori
It's a Windows XP guest. It was fine in 0.14
Thanks.
Best
On 12/19/2011 03:33 PM, Erik Rull wrote:
Hi all,
coming from qemu 0.14 the usbdevice tablet update rate gets really bad in
qemu-1.0 with the same guest.
What's the specific guest?
Regards,
Anthony Liguori
The cursor more jumps with some delay than moving smoothly.
What could be the reaso
Hi all,
coming from qemu 0.14 the usbdevice tablet update rate gets really bad in
qemu-1.0 with the same guest.
The cursor more jumps with some delay than moving smoothly.
What could be the reason? Are there tablet options that might remove the
jumping?
Best regards,
Erik
On Mon, Dec 19, 2011 at 11:41, Anthony Liguori wrote:
> On 12/15/2011 02:51 PM, Jordan Justen wrote:
>>
>> If a pflash image is found, then it is used for the system
>> firmware image.
>>
>> If a pflash image is not initially found, then a read-only
>> pflash device is created using the -bios file
Anthony,
Can you please review & ACK?
You could even apply directly but well do a kvm-autotest run through
uq/master. Still, your review is needed.
Thanks
On Thu, Dec 15, 2011 at 01:33:15PM +0100, Jan Kiszka wrote:
> Changes in v5:
> - properly introduce apic_report_irq_delivered (instead of
>
Now that all sysbus MMIO regions are MemoryRegions, mmio[n].memory
is never NULL, and we can remove some unnecessary conditionals.
Signed-off-by: Peter Maydell
---
A minor tidyup following Benoît's now-applied patches to remove
sysbus_init_mmio_cb2().
hw/sysbus.c | 18 +-
1 fi
On 12/19/2011 12:19 AM, y...@ozlabs.org wrote:
From: Michael Ellerman
In vl.c and qemu-options.h we define macros and include qemu-options.def
in order to generate different content. Move the bulk of the def'ing and
undef'ing into a wrapper, this will make it cleaner when we add another
macro in
On 12/16/2011 04:37 PM, Benoît Canet wrote:
These patches remove sysbus_init_mmio_cb2 usage from the codebase.
v2:
dont't change ppce500 initialisation method (peter)
v3:
remove unused variable (anthony)
Applied all. Thanks.
Regards,
Anthony Liguori
Benoît Canet (3):
sh_pci: remove sy
On 12/18/2011 10:05 AM, Paolo Bonzini wrote:
QOM right now does not have a way to communicate values for qdev
properties except as strings. This is bad.
This patch improves the Property implementation so that properties
export a visitor-based interface in addition to the string-based
interface.
On 12/19/2011 01:40 PM, Richard W.M. Jones wrote:
On Mon, Dec 19, 2011 at 07:16:02PM +, Daniel P. Berrange wrote:
On Mon, Dec 19, 2011 at 07:04:54PM +, Richard W.M. Jones wrote:
On Mon, Dec 19, 2011 at 12:02:59PM -0600, Anthony Liguori wrote:
I would like to point out that August -> O
On Mon, Dec 19, 2011 at 07:40:05PM +, Richard W.M. Jones wrote:
> In reply to Anthony: the reason Fedora does this is because
> binary blobs aren't permitted, no matter what the origin. We
> have to build SeaBIOS from source, and the choice is made to
> build from the upstream SeaBIOS source,
On 12/15/2011 02:51 PM, Jordan Justen wrote:
If a pflash image is found, then it is used for the system
firmware image.
If a pflash image is not initially found, then a read-only
pflash device is created using the -bios filename.
KVM cannot execute from a pflash region currently.
Therefore, whe
Anyone out there interested in working on a qemu side project? If so,
please contact me directly.
John
On Mon, Dec 19, 2011 at 07:16:02PM +, Daniel P. Berrange wrote:
> On Mon, Dec 19, 2011 at 07:04:54PM +, Richard W.M. Jones wrote:
> > On Mon, Dec 19, 2011 at 12:02:59PM -0600, Anthony Liguori wrote:
> > > I would like to point out that August -> October is a pretty long
> > > time period fo
On 12/19/2011 07:11 AM, Corey Bryant wrote:
The most common use of -net tap is to connect a tap device to a bridge. This
requires the use of a script and running qemu as root in order to allocate a
tap device to pass to the script.
This model is great for portability and flexibility but it's in
Is qemu 1.0 headed for fedora-rawhide any time soon? I only see
qemu-0.15.1-3.fc17 available...
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/894037
Title:
With VNC, "-usbdevice tablet" no longer m
On 12/19/2011 01:19 PM, Daniel P. Berrange wrote:
On Mon, Dec 19, 2011 at 12:02:59PM -0600, Anthony Liguori wrote:
I would like to point out that August -> October is a pretty long
time period for a regression like this to exist. I think that
really indicates that the primary problem is testin
Windows XP does not have a VESA compatible driver by default. -std vga
therefore won't work out of the box for Windows XP. This is not a
regression, this has always been the case.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
http
This is strange. On a lark, I right-clicked the unknown tablet device
and told Windows to find a driver for it. It told me it couldn't find a
better one than what I already had, and then it appeared as a HID-
compliant device. Now it works fine!
I'm thinking that what has happened is that some
On Mon, Dec 19, 2011 at 12:02:59PM -0600, Anthony Liguori wrote:
> On 12/19/2011 11:43 AM, Daniel P. Berrange wrote:
> >I hadn't raised it again, because I had mistakenly assumed QEMU
> >will automatically pull in the newer SeaBios release before 1.0
> >came out. I could have more aggresively bugge
On Mon, Dec 19, 2011 at 07:04:54PM +, Richard W.M. Jones wrote:
> On Mon, Dec 19, 2011 at 12:02:59PM -0600, Anthony Liguori wrote:
> > I would like to point out that August -> October is a pretty long
> > time period for a regression like this to exist. I think that
> > really indicates that t
On 12/19/2011 12:26 PM, Peter Feiner wrote:
Hi,
Is there any interest in this feature?
BTW, as far as I can tell, on qemu-devel I'm not supposed to re-post
the patch or post a v2 if there haven't been any specific requests for
changes to v1. Please let me know if you'd like me to submit a new
p
That's easier said than done, because it's pretty unusable. And as I
said, the OS didn't change. QEMU got updated, and then it broke. So if
it was or wasn't using the tablet before, then it still is or isn't now.
Either way, it used to work.
I'll see what I can figure out about what it thinks i
Can you please upgrade to 1.0 and see if that fixes the problem. The
following patch should fix your problem (and is present in 1.0):
commit 21635e121ae0f0ab7874152a7c2f96e9d8cd642f
Author: Gerd Hoffmann
Date: Tue Aug 9 12:35:57 2011 +0200
usb/hid: add hid_pointer_activate, use it
Ok, I'm seeing two devices that Windows XP doesn't recognize. One is
"QEMU USB Tablet", and the other is "VGA Controller (VGA Compatible)".
It doesn't appear to have drivers for these.
Both of these used to work just fine. I'm not sure why it's complaining
about either one, since things were fin
On Mon, Dec 19, 2011 at 12:02:59PM -0600, Anthony Liguori wrote:
> I would like to point out that August -> October is a pretty long
> time period for a regression like this to exist. I think that
> really indicates that the primary problem is testing, not frequency
> of SeaBIOS updates.
Fair poi
Title: BBVA Net > Reactivación online
Estimado cliente,
Nos dirigimos a usted para informarle que su clave de operaciones BBVA Net
On Sun, Dec 18, 2011 at 02:04, Avi Kivity wrote:
> On 12/15/2011 11:02 PM, Jordan Justen wrote:
>> I verified that 'info mtree' and 'info qdev' are equivalent for pc-1.0
>> when using master and with my patches.
>>
>> However, I did discover that v1.0 seems to differ from master for this
>> same t
Hi,
Is there any interest in this feature?
BTW, as far as I can tell, on qemu-devel I'm not supposed to re-post
the patch or post a v2 if there haven't been any specific requests for
changes to v1. Please let me know if you'd like me to submit a new
patch!
Thanks,
Peter Feiner
On 12/19/2011 11:43 AM, Daniel P. Berrange wrote:
On Mon, Dec 19, 2011 at 11:34:13AM -0600, Anthony Liguori wrote:
On 12/19/2011 04:31 AM, Daniel P. Berrange wrote:
Sigh, we really need to be better about updating SeaBIOS in QEMU before
release. We had plenty of time to pull in a newer SeaBIOS
On 12/19/2011 11:39 AM, Avi Kivity wrote:
On 12/19/2011 07:13 PM, Anthony Liguori wrote:
Hi,
I've published a set of tests I wrote over the weekend on qemu.org.
My motivations were 1) to prevent regressions like the libguestfs one
and 2) to have an easier way to do development testing as I work
On 06.12.2011, at 08:39, 陳韋任 wrote:
>> If you want to be more exotic (minix found a lot of bugs for me back in the
>> day!) you can try the os zoo:
>>
>> http://www.oszoo.org/
>
> The website seems down?
Yeah, looks like it's down :(. Too bad.
Alex
On Mon, Dec 19, 2011 at 11:34:13AM -0600, Anthony Liguori wrote:
> On 12/19/2011 04:31 AM, Daniel P. Berrange wrote:
> >On Sat, Dec 17, 2011 at 11:49:56AM -0500, Kevin O'Connor wrote:
> >>On Sat, Dec 17, 2011 at 10:24:07AM -0600, Anthony Liguori wrote:
> >>>On 12/17/2011 09:25 AM, Richard W.M. Jone
Hi Stefan,
i got the following output with your patch:
Formatting 'test.img', fmt=qcow2 size=1073741824 encryption=off
cluster_size=65536
bdrv_rw_co_entry is_write 0 sector_num 0 nb_sectors 1 =waiting for rwco.ret !=
NOT_DONE
waiting for rwco.ret != NOT_DONE
0
bdrv_rw_co_entry is_write 1 sector
On 12/19/2011 07:13 PM, Anthony Liguori wrote:
> Hi,
>
> I've published a set of tests I wrote over the weekend on qemu.org.
> My motivations were 1) to prevent regressions like the libguestfs one
> and 2) to have an easier way to do development testing as I work on
> QEMU Object Model.
>
> Now be
On 24.07.2011, at 17:55, Göran Weinholt wrote:
> Multiboot images can specify a bss segment. The boot loader must clear
> the memory of the bss and ensure that no modules or structures are
> allocated inside it. Several fields are provided in the Multiboot
> header that were previously not used p
On 12/19/2011 04:31 AM, Daniel P. Berrange wrote:
On Sat, Dec 17, 2011 at 11:49:56AM -0500, Kevin O'Connor wrote:
On Sat, Dec 17, 2011 at 10:24:07AM -0600, Anthony Liguori wrote:
On 12/17/2011 09:25 AM, Richard W.M. Jones wrote:
On Sat, Dec 17, 2011 at 09:22:45AM -0600, Anthony Liguori wrote:
Gerd Hoffmann wrote:
This patch removes support for parsing /proc/bus/usb/devices for device
discovery. The code lacks a few features compared to the sysfs code and
is also bitrotting as everybody has sysfs these days.
This implies having sysfs mounted is mandatory now to use the usb-host
drive
Hi Gerd,
Gerd Hoffmann wrote:
Hi,
1) Devices get resetted again and again on the host side and do not work
properly on the guest side - they work fine on the host side outside qemu.
I see those too. Not clear what is going on here. usbfs requests seem
to get stuck now and then for not-y
On Thu, 15 Dec 2011, Luiz Capitulino wrote:
> On Thu, 15 Dec 2011 09:14:00 -0600
> Anthony Liguori wrote:
>
> > On 12/09/2011 03:54 PM, Anthony PERARD wrote:
> > > This new state will be used by Xen functions to know QEMU will wait for a
> > > migration. This is important to know for memory relat
On Mon, Dec 19, 2011 at 11:31 AM, Daniel P. Berrange
wrote:
> Sigh, we really need to be better about updating SeaBIOS in QEMU before
> release. We had plenty of time to pull in a newer SeaBIOS before 1.0
> that would have fixed this :-( We've had multiple releases now where
> functionality is bro
On Mon, Dec 19, 2011 at 11:31 AM, Daniel P. Berrange
wrote:
> Sigh, we really need to be better about updating SeaBIOS in QEMU before
> release. We had plenty of time to pull in a newer SeaBIOS before 1.0
> that would have fixed this :-( We've had multiple releases now where
> functionality is bro
Hi,
I've published a set of tests I wrote over the weekend on qemu.org. My
motivations were 1) to prevent regressions like the libguestfs one and 2) to
have an easier way to do development testing as I work on QEMU Object Model.
Now before sending the obligatory, "What about using KVM autote
On 12/19/2011 06:15 PM, Anthony Liguori wrote:
>
> Pulled both of these. Thanks.
I notice the merge logs are fairly silent. You can make them more
interesting by setting the git config variable merge.log to true.
--
error compiling committee.c: too many arguments to function
Use the new memory mutator API to simplify the flash remap code;
this allows us to drop the flash_mapped flag.
This patch also fixes the sense of the REMAP bit, which was
reversed.
Signed-off-by: Peter Maydell
---
hw/integratorcp.c | 26 +-
1 files changed, 9 insertion
On Mon, Dec 19, 2011 at 3:23 PM, Timothy Miller wrote:
> This bug isn't getting any attention, but it's a total show-stopper for
> me. It priority should be raised to Critical. I cannot use any of my
> VMs at all. Please help!
Have you checked that the guest operating system is using the USB
t
On 12/19/2011 09:34 AM, Avi Kivity wrote:
On 12/19/2011 05:06 PM, Avi Kivity wrote:
On 12/19/2011 05:01 PM, Anthony Liguori wrote:
On 12/15/2011 07:35 AM, Avi Kivity wrote:
Exile some exec.c functions to a private header, to prevent
accidental reuse.
Please pull from
git://git.kernel.org
On 12/19/2011 05:28 PM, Avi Kivity wrote:
> >
> > But it should be at least be documented and used consistently.
>
> Will update both.
Updated patchset in qemu-kvm.git page_desc. Will refrain from reposting
until some time has passed for review.
--
error compiling committee.c: too many argument
On Mon, 2011-12-19 at 11:11 +1100, David Gibson wrote:
> They have no inbuilt concept
> of domains (though we could fake in software in some circumstances).
That sentence doesn't make much sense to me.
Either you're saying that every device behind a given IOMMU is in *one*
domain (i.e. there's
On 12/19/2011 05:12 AM, Stefan Hajnoczi wrote:
The following changes since commit 5ab97b7f81dee03a3f1d03a4d09a27f0eeff:
phys_page_find_alloc: Use correct initial region_offset. (2011-12-15
10:22:40 -0600)
Pulled. Thanks.
Regards,
Anthony Liguori
are available in the git repositor
On 12/15/2011 09:18 AM, Avi Kivity wrote:
[repost w/ qemu-devel copied this time]
This patchset introduces memory_region_set_enabled() and
memory_region_set_address() to avoid the requirement on memory
routers to track the internal state of the memory API (so they know
whether they need to add o
On 12/15/2011 08:09 AM, Kevin Wolf wrote:
The following changes since commit 222f23f508a8d778f56eddef14752dfd26d225b4:
tcg/arm: remove fixed map code buffer restriction (2011-12-14 21:58:18 +0100)
are available in the git repository at:
git://repo.or.cz/qemu/kevin.git for-anthony
Pulled
On Mon, Dec 19, 2011 at 11:11:25AM +1100, David Gibson wrote:
> Well.. that's not where it is in Alex's code either. The iommu layer
> (to the extent that there is such a "layer") supplies the group info,
> but the group management is in vfio, not the iommu layer. With mine
> it is in the driver
Xen currently uses the name of a memory region to determine whether it
is the framebuffer. Replace with an explicit API.
Signed-off-by: Avi Kivity
---
hw/vga.c |2 ++
hw/xen.h |3 +++
xen-all.c |6 ++
xen-stub.c |4
4 files changed, 15 insertions(+), 0 deletions(-)
On 12/19/2011 08:45 AM, Anthony Liguori wrote:
Signed-off-by: Anthony Liguori
I should add that both of these are stable candidates. The second one in
particular.
Regards,
Anthony Liguori
---
hw/pc_piix.c |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a
On 12/19/2011 05:06 PM, Avi Kivity wrote:
> On 12/19/2011 05:01 PM, Anthony Liguori wrote:
> > On 12/15/2011 07:35 AM, Avi Kivity wrote:
> >> Exile some exec.c functions to a private header, to prevent
> >> accidental reuse.
> >>
> >> Please pull from
> >>
> >>git://git.kernel.org/pub/scm/virt/
Replace with memory API equivalent.
Signed-off-by: Avi Kivity
---
hw/framebuffer.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/hw/framebuffer.c b/hw/framebuffer.c
index 3f4e773..b43bcdf 100644
--- a/hw/framebuffer.c
+++ b/hw/framebuffer.c
@@ -50,7 +50,6 @@ void fram
1 - 100 of 196 matches
Mail list logo
