On 05/28/10 17:44, Gleb Natapov wrote:
> On Fri, May 28, 2010 at 05:24:47PM +0200, Jes Sorensen wrote:
>> I guess the Socket Designation in particular might have been done for a
>> reason?
>>
> It was part of commit cf2affa6de. And was a result of moving to
> snprintf() instead of direct string man
On 05/29/10 14:49, Sebastian Herbszt wrote:
> Jes Sorensen wrote:
>> We were looking at the dmidecode output from qemu-kvm pre-seabios and
>> current qemu-kvm and noticed some of the strings have changed.
>>
>> The main problem with this is that certain OSes are quite sensitive to
>> system changes
On 05/30/10 13:22, Michael S. Tsirkin wrote:
> On Fri, May 28, 2010 at 11:56:54AM +0200, Jes Sorensen wrote:
>> It looks pretty good to me, however one thing I have been thinking of
>> while reading through it:
>>
>> Rather than storing a pointer within the ring struct, pointing into a
>> position
Blue Swirl wrote:
> On Sun, May 30, 2010 at 12:24 PM, Jan Kiszka wrote:
>> Blue Swirl wrote:
Linux don't use RTC as time source and I don't know about BSD, so no
Linux or BSD test case for you, sorry. Run WindowXP standard HAL and put
heavy load on the host. You can run video inside
On Thu, 27 May 2010 05:20:35 am Michael S. Tsirkin wrote:
> Here's a rewrite of the original patch with a new layout.
> I haven't tested it yet so no idea how this performs, but
> I think this addresses the cache bounce issue raised by Avi.
> Posting for early flames/comments.
Sorry, not without s
On Mon, May 31, 2010 at 09:32:08AM +0200, Jes Sorensen wrote:
> On 05/28/10 17:44, Gleb Natapov wrote:
> > On Fri, May 28, 2010 at 05:24:47PM +0200, Jes Sorensen wrote:
> >> I guess the Socket Designation in particular might have been done for a
> >> reason?
> >>
> > It was part of commit cf2affa6d
[cc: kraxel]
Avi Kivity writes:
> On 05/29/2010 11:01 AM, Markus Armbruster wrote:
>> Jan Kiszka writes:
>>
>>
>>> From: Jan Kiszka
>>>
>>> As the user may specify ambiguous device IDs, let's search for their
>>> official names first before considering the user-supplied identifiers.
>>>
>>>
On 05/28/10 16:21, Paul Brook wrote:
Try to pci hotplug a vga card, watch qemu die with hw_error().
This patch fixes it.
I think this is wrong. There's no reason why VGA adapters shouldn't be
hotplugged. You should fix the underlying problems that prevent hotplugging
The qemu code base simpl
Jan Kiszka writes:
> Avi Kivity wrote:
>> On 05/29/2010 11:14 AM, Jan Kiszka wrote:
Currently breaks down when IDs contain '/', but permitting that is a
bug. There may be more problems; the path lookup code is way too
clever.
>>> Indeed. Less can sometimes be more. My i
Markus Armbruster wrote:
> Jan Kiszka writes:
>
>> Avi Kivity wrote:
>>> On 05/29/2010 11:14 AM, Jan Kiszka wrote:
> Currently breaks down when IDs contain '/', but permitting that is a
> bug. There may be more problems; the path lookup code is way too
> clever.
>
Inde
On 05/28/10 15:38, Markus Armbruster wrote:
I'm working on cleanly separating block device host and guest parts.
I'd like to route all this work through Kevin's block tree. This is
just preliminaries.
Markus Armbruster (14):
blockdev: Belatedly remove MAX_DRIVES
blockdev: Belatedly remove
Now, I’m working with Qemu source study, but I have some difficulties. Could
someday give me some help or advice.
At the beginning of cpu_exec, there is a function call env_to_regs, but I
cannot understand the behavior of env_to_regs. In my understanding, env_to_regs
stores environment conte
On 05/28/10 17:03, Markus Armbruster wrote:
Signed-off-by: Markus Armbruster
Nice catch.
Acked-by: Gerd Hoffmann
cheers,
Gerd
Implement TMKNOD as part of 2000.L Work
Synopsis
size[4] Tmknod tag[2] fid[4] name[s] mode[4] dev[4] gid[4]
size[4] Rmknod tag[2] qid[13]
Description
mknod asks the file server to create a device node with given device
type, mode and gid. The qid for the new device node is retu
Jan Kiszka writes:
> Markus Armbruster wrote:
>> Jan Kiszka writes:
>>
>>> From: Jan Kiszka
>>>
>>> Extend qbus_find_dev to allow addressing of devices without an unique id
>>> via an optional per-bus instance number. The new formats are
>>> 'driver.instance' and 'alias.instance'.
>>>
>>> Sign
On 29.05.2010, at 15:31, Andreas Färber wrote:
> Am 28.05.2010 um 21:00 schrieb Thomas Monjalon:
>
>> From: Thomas Monjalon
>>
>> This line was a bit clear.
>> The next lines set or reset this bit (LE) depending of another bit (ILE).
>> So the first line is useless.
>>
>> Signed-off-by: Thoma
On 05/29/10 09:38, Markus Armbruster wrote:
[cc: kraxel]
Jan Kiszka writes:
From: Jan Kiszka
As long as we allow /dev.1 as shortcut for /dev1/bus1, we also have to
make sure that /dev1/dev2 works for /dev1/bus1/dev2/bus2 - as long as
there is only one child bus per device.
We auto-root a p
Hi,
Also it's worth mentioning that I am still running C: on QEMU IDE
emulation, as I could not quite figure out how to boot for a megasas LD
with option-rom. What QEMU CLI ops where requried to make this work
again..?
-option-rom $file
or
-device megasas,romfile=$file
cheers,
Gerd
On 05/31/10 03:42, Nicholas A. Bellinger wrote:
From: Nicholas Bellinger
Greetings Gerd, Kevin and Co,
Attached are two patches to add the necesary CDB parsing to determine
SCSIRequest->cmd.xfer
(length) and SCSIRequest->cmd.mode (direction) for Persistent Reservation IN/OUT
CDBs and for Maint
pci_add nic -net use either the ID or option "name" of qemu_net_opts.
And there's our hole. Reproducible with "-net user -net nic,id=foo
-device lsi,id=foo".
Oh. Well. Yes, better plug that.
@@ -242,6 +243,10 @@ DeviceState *qdev_device_add(QemuOpts *opts)
qdev = qdev_create_from_info
Am 29.05.2010 21:55, schrieb Miguel Di Ciurcio Filho:
> Both bdrv_can_snapshot() and bdrv_has_snapshot() does not work as advertized.
>
> First issue: Their names implies different porpouses, but they do the same
> thing
> and have exactly the same code. Maybe copied and pasted and forgotten?
> b
Dear Researcher
Please excuse us for contacting you directly. We are offering an efficient
service to help you and your colleagues ensure that your academic and
professional work is written in perfect English. We will check the grammar
and style of your work and return it to you to meet your
Avi Kivity writes:
> On 05/28/2010 09:21 PM, Markus Armbruster wrote:
>
>
>
>> Summary of the host / guest split:
>>
>> -drive options host or guest?
>> bus, unit, if, index, addr guest, already covered by qdev
>> cyls, heads, secs, transguest, new qdev
Avi Kivity writes:
> On 05/28/2010 10:24 PM, Luiz Capitulino wrote:
>>
>>> If a password is needed, we should throw an error and let the QMP client
>>> set the password and try again.
>>>
>> It's what we do today, a password should be set with block_passwd before
>> issuing the change com
Jan Kiszka writes:
> Markus Armbruster wrote:
>> Jan Kiszka writes:
>>
>>> Avi Kivity wrote:
On 05/29/2010 11:14 AM, Jan Kiszka wrote:
>> Currently breaks down when IDs contain '/', but permitting that is a
>> bug. There may be more problems; the path lookup code is way too
>>
Markus Armbruster wrote:
> Jan Kiszka writes:
>
>> Markus Armbruster wrote:
>>> Jan Kiszka writes:
>>>
Avi Kivity wrote:
> On 05/29/2010 11:14 AM, Jan Kiszka wrote:
>>> Currently breaks down when IDs contain '/', but permitting that is a
>>> bug. There may be more problems; the
Gerd Hoffmann writes:
>> pci_add nic -net use either the ID or option "name" of qemu_net_opts.
>> And there's our hole. Reproducible with "-net user -net nic,id=foo
>> -device lsi,id=foo".
>
> Oh. Well. Yes, better plug that.
>
>> @@ -242,6 +243,10 @@ DeviceState *qdev_device_add(QemuOpts *opt
On 05/31/2010 01:54 PM, Markus Armbruster wrote:
We expose some of the cache property to the guest. IMO we need the
cache property to be both guest and host, with qemu bridging the
impedance mismatch if needed.
Yes.
How should the device properties look like?
write_cache=enabled|
Avi Kivity writes:
> On 05/31/2010 01:54 PM, Markus Armbruster wrote:
>>
>>> We expose some of the cache property to the guest. IMO we need the
>>> cache property to be both guest and host, with qemu bridging the
>>> impedance mismatch if needed.
>>>
>> Yes.
>>
>> How should the device pro
Forgot to mention that I'm also getting constantly the error message:
BUG: kvm_dirty_pages_log_enable_slot: invalid parameters
BUG: kvm_dirty_pages_log_disable_slot: invalid parameters
BUG: kvm_dirty_pages_log_enable_slot: invalid parameters
BUG: kvm_dirty_pages_log_disable_slot: invalid parameter
I'm using qemu-kvm 0.12.3 with "-vga std" and with res like 1680x1050,
1440x900 and a few other it crashes/quits immediately with message
"Could not open SDL display". It happens for me both when switching with
ctrl-alt-f or with cmd line option -full-screen. With 1024x768 for
example it does not h
On Mon, May 31, 2010 at 05:16:42PM +0930, Rusty Russell wrote:
> On Thu, 27 May 2010 05:20:35 am Michael S. Tsirkin wrote:
> > Here's a rewrite of the original patch with a new layout.
> > I haven't tested it yet so no idea how this performs, but
> > I think this addresses the cache bounce issue ra
On Mon, May 31, 2010 at 6:59 AM, Kevin Wolf wrote:
>> int bdrv_snapshot_create(BlockDriverState *bs,
>> QEMUSnapshotInfo *sn_info)
>> {
>> BlockDriver *drv = bs->drv;
>> - if (!drv)
>> - return -ENOMEDIUM;
>> - if (!drv->bdrv_snapshot_create)
>> -
Hello,
This patch series adds support to specify some descriptive help text
to qdev device parameters. This series adds some help text to the
virtserialport and net family of devices as an example, and the new
output is shown in the respective commits.
This series also adds a new '-device help' o
Add a 'description' along with each qdev property to document the input
each qdev property takes.
Signed-off-by: Amit Shah
---
block_int.h | 10 +++---
hw/a9mpcore.c |2 +-
hw/acpi_piix4.c |2 +-
hw/arm11mpcore.c |4 +-
hw/arm_sysctl.c |4 +-
Document the parameters for the virtserialport and virtioconsole
devices.
Example:
$ ./x86_64-softmmu/qemu-system-x86_64 -device virtserialport,?
virtserialport.nr=uint32, The 'number' for the port for \
predictable port numbers. Use this to spawn ports if you \
plan to migrate the guest.
virtse
Instead of printing out the device properties help messages from
qdev_device_help(), split it off into a new function. This way, we have
two separate function calls for device help and device properties help.
This will be later used to show all the devices and all the properties
associated with th
On 05/30/2010 08:19 PM, Blue Swirl wrote:
We have PRI*64 just for this purpose, so let's use them. The
discussion about that was earlier.
How does mingw matter for vhost-net specific code?
Paolo
The new '-device help' option shows all the devices that are registered
with qdev and prints out all the properties each device has, along with
the description for each property.
This is useful in creating automatic documentation for all the options
that we have and support.
Signed-off-by: Amit S
This results in an output like:
$ ./x86_64-softmmu/qemu-system-x86_64 -device virtio-net-pci,?
...
virtio-net-pci.mac=macaddr, The MAC address for the NIC.
virtio-net-pci.vlan=vlan, The VLAN to associate the NIC with.
virtio-net-pci.netdev=netdev, The peer net device to associate with this
virt
Alexander Graf wrote:
> Thomas, have you verified that it still boots a ppc64 guest?
No, but I don't see any specific link between ppc64 and this change.
This is the current (pseudo)code:
LE = 0
if ILE == 1
LE = 1
else
LE = 0
In all cases, LE will be overwritten after
On Mon, May 31, 2010 at 09:36:00AM +0200, Jes Sorensen wrote:
> On 05/30/10 13:22, Michael S. Tsirkin wrote:
> > On Fri, May 28, 2010 at 11:56:54AM +0200, Jes Sorensen wrote:
> >> It looks pretty good to me, however one thing I have been thinking of
> >> while reading through it:
> >>
> >> Rather t
On Mon, May 31, 2010 at 02:51:26PM +0200, Paolo Bonzini wrote:
> On 05/30/2010 08:19 PM, Blue Swirl wrote:
>> We have PRI*64 just for this purpose, so let's use them. The
>> discussion about that was earlier.
>
> How does mingw matter for vhost-net specific code?
>
> Paolo
Good point. That code is
On Mon, 31 May 2010 13:05:37 +0200
Markus Armbruster wrote:
> Avi Kivity writes:
>
> > On 05/28/2010 10:24 PM, Luiz Capitulino wrote:
> >>
> >>> If a password is needed, we should throw an error and let the QMP client
> >>> set the password and try again.
> >>>
> >> It's what we do toda
On Sat, 29 May 2010 10:50:55 +0200
Jan Kiszka wrote:
> Luiz Capitulino wrote:
> > This new version moves the documentation to qemu-monitor.hx and now
> > QMP/qmp-commands.txt is generated from there (thanks Jan!).
> >
> > I hope I've addressed all review comments in this version and now it shoul
Am 31.05.2010 15:48, schrieb Luiz Capitulino:
> On Mon, 31 May 2010 13:05:37 +0200
> Markus Armbruster wrote:
>
>> Avi Kivity writes:
>>
>>> On 05/28/2010 10:24 PM, Luiz Capitulino wrote:
> If a password is needed, we should throw an error and let the QMP client
> set the password a
We need Device IDs to be unique and not contain '/' so device tree
nodes can always be unambigously referenced by tree path.
We already have some protection against duplicate IDs, but it got
holes:
* We don't assign IDs to default devices.
* -device and device_add use the ID of a qemu_device_opt
For all i, ports_map[i] is used in and only in the i-th iteration.
Replace the dynamic array by a scalar variable.
Signed-off-by: Markus Armbruster
---
hw/virtio-serial-bus.c | 12 +++-
1 files changed, 3 insertions(+), 9 deletions(-)
diff --git a/hw/virtio-serial-bus.c b/hw/virtio-se
On Sat, May 29, 2010 at 4:31 AM, Aurelien Jarno wrote:
> Please find my comments below. Note that I don't feel very comfortable
> with PCI code, so a review from someone know this part of QEMU would be
> nice.
>
> On Wed, May 19, 2010 at 10:26:32PM +0800, Huacai Chen wrote:
>> Signed-off-by: Huaca
On Sat, May 29, 2010 at 4:56 AM, Aurelien Jarno wrote:
> Please find my comments below.
>
> On Wed, May 19, 2010 at 10:28:36PM +0800, Huacai Chen wrote:
>> Signed-off-by: Huacai Chen
>> ---
>> Makefile.target | 2 +-
>> hw/mips_fulong2e.c | 421
>>
Am 28.05.2010 15:38, schrieb Markus Armbruster:
> Commit 428c149b added IDEState member conf to let commit 0009baf1 find
> the BlockConf from there. It exists only for qdev drives, created via
> ide_drive_initfn(), not for drives created via ide_init2().
>
> But for a qdev drive, we can just as w
Thomas Monjalon wrote:
> Alexander Graf wrote:
>
>> Thomas, have you verified that it still boots a ppc64 guest?
>>
>
> No, but I don't see any specific link between ppc64 and this change.
>
> This is the current (pseudo)code:
> LE = 0
> if ILE == 1
> LE = 1
> else
>
Thomas Monjalon wrote:
> From: Thomas Monjalon
>
> Since commit 2ada0ed, "Return From Interrupt" is broken for PPC processors
> because some interrupt specifics bits of SRR1 are copied to MSR.
>
> SRR1 is a save of MSR during interrupt.
> During RFI, MSR must be restored from SRR1.
> But some bits
Kevin Wolf writes:
> Am 28.05.2010 15:38, schrieb Markus Armbruster:
>> Commit 428c149b added IDEState member conf to let commit 0009baf1 find
>> the BlockConf from there. It exists only for qdev drives, created via
>> ide_drive_initfn(), not for drives created via ide_init2().
>>
>> But for a
Signed-off-by: cmchao
---
Makefile.target |2 +-
hw/omap.h |2 +
hw/omap2.c| 462 --
hw/omap_gptimer.c | 484 +
4 files changed, 487 insertions(+), 463 deletions(-)
cr
Signed-off-by: cmchao
---
Makefile.target |2 +-
hw/omap.h |2 +
hw/omap2.c | 396
hw/omap_gpmc.c | 419 +++
4 files changed, 422 insertions(+), 397 deletions(-)
create
Signed-off-by: cmchao
---
Makefile.target |2 +-
hw/omap.h |1 +
hw/omap1.c | 181 -
hw/omap_gpio.c | 202 +++
4 files changed, 204 insertions(+), 182 deletions(-)
create mo
Signed-off-by: cmchao
---
Makefile.target |2 +-
hw/omap.h | 11 +++---
hw/omap2.c | 72 +-
hw/omap_synctimer.c | 96 +++
4 files changed, 104 insertions(+), 77 deletions(-)
crea
Signed-off-by: cmchao
---
hw/omap.h | 36
hw/omap1.c | 12 ++--
hw/omap2.c |6 +++---
3 files changed, 9 insertions(+), 45 deletions(-)
diff --git a/hw/omap.h b/hw/omap.h
index 34443b4..18eb72b 100644
--- a/hw/omap.h
+++ b/hw/omap.h
@@ -108,
Signed-off-by: cmchao
---
hw/omap.h |3 +
hw/omap2.c | 523
hw/omap_gpio.c | 523
3 files changed, 526 insertions(+), 523 deletions(-)
diff --git a/hw/omap.h b/hw/oma
The following changes since commit aa6f63fff62faf2fe9ffba5a789675d49293614d
Blue Swirl:
mc146818rtc: improve debugging
Add a separate flag for debugging coalesced interrupts.
The patches almostly base on http://meego.gitorious.org/qemu-maemo/qemu work
and
act as preparatory wo
Signed-off-by: cmchao
---
Makefile.target |3 +-
hw/omap1.c | 170
hw/omap_uart.c | 194 +++
3 files changed, 196 insertions(+), 171 deletions(-)
create mode 100644 hw/omap_uart.c
d
Signed-off-by: cmchao
---
Makefile.target |2 +-
hw/omap.h |2 +
hw/omap2.c | 323 ---
hw/omap_spi.c | 346 +++
4 files changed, 349 insertions(+), 324 deletions(-)
create
Signed-off-by: cmchao
---
Makefile.target |3 +-
hw/omap.h | 37 ++--
hw/omap2.c | 269 ++-
hw/omap_l4.c| 271 +++
4 files changed, 307 insertions(+), 273 deletions(
Signed-off-by: cmchao
---
Makefile.target |2 +-
hw/omap.h |2 +
hw/omap1.c | 576 +
hw/omap_intc.c | 598 +++
4 files changed, 603 insertions(+), 575 deletions(-)
creat
Signed-off-by: cmchao
---
Makefile.target |2 +-
hw/omap2.c | 90
hw/omap_tap.c | 112 +++
3 files changed, 113 insertions(+), 91 deletions(-)
create mode 100644 hw/omap_tap.c
diff --
Signed-off-by: cmchao
---
Makefile.target |2 +-
hw/omap.h |2 +
hw/omap2.c | 144
hw/omap_sdrc.c | 165 +++
4 files changed, 168 insertions(+), 145 deletions(-)
create mod
Le mardi 25 mai 2010 00:27:29, Bruce Rogers a écrit :
> >>> On 5/24/2010 at 05:43 AM, Laurent Léonard
wrote:
> > The problem has already been reported on the list here :
> > http://lists.nongnu.org/archive/html/qemu-devel/2010-03/msg01725.html
> >
> > Any information on what can be done to solve
On Mon, May 31, 2010 at 10:35:03PM +0800, chen huacai wrote:
> On Sat, May 29, 2010 at 4:56 AM, Aurelien Jarno wrote:
> > Please find my comments below.
> >
> > On Wed, May 19, 2010 at 10:28:36PM +0800, Huacai Chen wrote:
> >> Signed-off-by: Huacai Chen
> >> ---
> >> Makefile.target
From: Jan Kiszka
Push the doc fragments for the info command to the end of
qemu-monitor.hx. This helps to establish a proper layout in the upcoming
QMP documentation.
Signed-off-by: Jan Kiszka
---
qemu-monitor.hx | 186 --
1 files changed, 9
Rebase.. Let's try to merge this ASAP, please.
changelog
-
v3 -> v4
- Rebased
- Minor commit log clarification
v2 -> v3
- Rebased
- Addressed review comments
- Move contents to qemu-monitor.hx (Jan)
v1 -> v2
- Rebased
- Addressed Markus's comments
- Changed
From: Jan Kiszka
One of the most important missing feature in QMP today is its
supported commands documentation.
The plan is to make it part of self-description support, however
self-description is a big task we have been postponing for a
long time now and still don't know when it's going to be
Previous commit added QMP documentation to the qemu-monitor.hx
file, it's is a copy of this information.
While it's good to keep it near code, maintaining two copies of
the same information is too hard and has little benefit as we
don't expect client writers to consult the code to find how to
use
Public bug reported:
I use eucalyptus software (1.6.2) on debian squeeze with kvm
0.12.4+dfsg-1. Kernel 2.6.32-3-amd64. After a few days machines crash.
There are no logs in host system. Guest is the same kernel and OS as
host. The kvm process use 100% of cpu time. I can not even ping the
guest. H
On Mon, May 31, 2010 at 1:35 PM, Michael S. Tsirkin wrote:
> On Mon, May 31, 2010 at 02:51:26PM +0200, Paolo Bonzini wrote:
>> On 05/30/2010 08:19 PM, Blue Swirl wrote:
>>> We have PRI*64 just for this purpose, so let's use them. The
>>> discussion about that was earlier.
>>
>> How does mingw matt
On Fri, May 28, 2010 at 09:07:32PM +0200, Thomas Monjalon wrote:
> From: Thomas Monjalon
>
> Since commit 2ada0ed, "Return From Interrupt" is broken for PPC processors
> because some interrupt specifics bits of SRR1 are copied to MSR.
>
> SRR1 is a save of MSR during interrupt.
> During RFI, MSR
On Sat, May 08, 2010 at 10:43:35PM +0200, Lars Munch wrote:
> Booting an arm kernel has been broken a while when booting from non zero start
> address. This is due to the order of events: board init loads the kernel and
> sets register 15 to the start address and then qemu_system_reset reset the cp
Aurelien Jarno wrote:
> On Tue, May 11, 2010 at 05:38:17PM +0200, Alexander Graf wrote:
>
>> Commit 213acd2e introduced leul_to_cpu with a special code path for big
>> endian
>> hosts. Unfortunately that code used preprocessor magic that didn't work.
>>
>> This patch replaces the explicit ##s b
On Tue, May 11, 2010 at 05:38:17PM +0200, Alexander Graf wrote:
> Commit 213acd2e introduced leul_to_cpu with a special code path for big endian
> hosts. Unfortunately that code used preprocessor magic that didn't work.
>
> This patch replaces the explicit ##s by glue() which is proven to work
>
On Fri, May 28, 2010 at 09:00:45PM +0200, Thomas Monjalon wrote:
> From: Thomas Monjalon
>
> This line was a bit clear.
> The next lines set or reset this bit (LE) depending of another bit (ILE).
> So the first line is useless.
Thanks, applied.
> Signed-off-by: Thomas Monjalon
> ---
> target-
Alexander Graf wrote:
> Commit 213acd2e introduced leul_to_cpu with a special code path for big endian
> hosts. Unfortunately that code used preprocessor magic that didn't work.
>
> This patch replaces the explicit ##s by glue() which is proven to work
> reliably,
> enabling me to compile qemu on
OK, I dropped the vhost change for now: I still think
we should not bother about mingw for linux-only code,
but at this point it's not important for me.
The following changes since commit aa6f63fff62faf2fe9ffba5a789675d49293614d:
mc146818rtc: improve debugging (2010-05-30 19:20:07 +)
are a
On 05/31/10 16:13, Markus Armbruster wrote:
We need Device IDs to be unique and not contain '/' so device tree
nodes can always be unambigously referenced by tree path.
We already have some protection against duplicate IDs, but it got
holes:
* We don't assign IDs to default devices.
* -device
On Mon, May 31, 2010 at 08:44:55PM +0200, Alexander Graf wrote:
> Aurelien Jarno wrote:
> > On Tue, May 11, 2010 at 05:38:17PM +0200, Alexander Graf wrote:
> >
> >> Commit 213acd2e introduced leul_to_cpu with a special code path for big
> >> endian
> >> hosts. Unfortunately that code used prepr
Am 31.05.2010 um 11:52 schrieb Gerd Hoffmann :
Hi,
Also it's worth mentioning that I am still running C: on QEMU IDE
emulation, as I could not quite figure out how to boot for a
megasas LD
with option-rom. What QEMU CLI ops where requried to make this work
again..?
-option-rom $file
o
Hi Kevin,
here is an updated patch for the ceph/rbd driver. I hope that everything
is fine now.
Regards,
Christian
This is a block driver for the distributed file system Ceph
(http://ceph.newdream.net/). This driver uses librados (which
is part of the Ceph server) for direct access to the Ceph
** Changed in: qemu
Status: In Progress => Fix Committed
--
SMC91C111 failed when booting Linux/ARM(Mainstone) since 0.10.0
https://bugs.launchpad.net/bugs/586424
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: Fi
Fixed in e03c22a98cf5deffd0dec2f9ff88a600aa330bc4
** Changed in: qemu
Status: New => Fix Committed
--
Linux on ARM/Mainstone machine fails at bootstrap
https://bugs.launchpad.net/bugs/586221
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed
Drop not used board_ahci constants.
Signed-off-by: Sebastian Herbszt
diff --git a/hw/ahci.c b/hw/ahci.c
index 3476cea..4090def 100644
--- a/hw/ahci.c
+++ b/hw/ahci.c
@@ -65,12 +65,6 @@ do { fprintf(stderr,"ahci: " fmt , ## __VA_ARGS__); } while
(0)
#define RX_FIS_SDB0x58 /* off
On 31.05.2010, at 22:12, Sebastian Herbszt wrote:
> Drop not used board_ahci constants.
>
> Signed-off-by: Sebastian Herbszt
>
> diff --git a/hw/ahci.c b/hw/ahci.c
> index 3476cea..4090def 100644
> --- a/hw/ahci.c
> +++ b/hw/ahci.c
> @@ -65,12 +65,6 @@ do { fprintf(stderr,"ahci: " fmt , ## __V
Alexander Graf wrote:
On 31.05.2010, at 22:12, Sebastian Herbszt wrote:
Drop not used board_ahci constants.
Signed-off-by: Sebastian Herbszt
diff --git a/hw/ahci.c b/hw/ahci.c
index 3476cea..4090def 100644
--- a/hw/ahci.c
+++ b/hw/ahci.c
@@ -65,12 +65,6 @@ do { fprintf(stderr,"ahci: " fmt , #
On Mon, May 31, 2010 at 6:43 PM, Luiz Capitulino wrote:
Hi Luiz,
I'm interested in QMP, have left some feedback. As I get up to speed
with QMP my questions and suggestions will hopefully be useful.
Apologies in advance if any of my thoughts here are old news and have
been discussed elsewhere :).
Gleb Natapov wrote:
I don't care much as long as we will not have "CPU :". It looks like something
that can change after BIOS upgrade, so it is hard to believe Windows
will stop working because of this change.
Maybe it could trigger the Windows activation process?
Sebastian
Drop not used ATAPI_CMD constants.
Signed-off-by: Sebastian Herbszt
diff --git a/hw/ahci.c b/hw/ahci.c
index 9987459..a024706 100644
--- a/hw/ahci.c
+++ b/hw/ahci.c
@@ -179,21 +179,6 @@ do { fprintf(stderr,"ahci: " fmt , ## __VA_ARGS__); }
while (0)
#define ATA_CMD_WRITE_EXT 0x34/* Wr
On 31.05.2010, at 22:56, Sebastian Herbszt wrote:
> Drop not used ATAPI_CMD constants.
I'd postpone that. We should get rid of _all_ ATA and ATAPI commands in ahci.c,
but that'll be part of a bigger cleanup. IMHO we should reuse the IDE core for
those.
Alex
The commit 8e65b7c04965c8355e4ce43211582b6b83054e3d introduced
expire_time of UHCIState.
But expire_time is not in vmstate, the second uhci_frame_timer will
not be fired immediately after loadvm.
Signed-off-by: TeLeMan
---
hw/usb-uhci.c |3 ++-
1 files changed,[PATCH] usb-uhci: fix commit
8e
setenv() is not implemented on MinGW, so we have to use putenv().
Signed-off-by: TeLeMan
---
sdl.c |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/sdl.c b/sdl.c
index add1148..eac898a 100644
--- a/sdl.c
+++ b/sdl.c
@@ -850,7 +850,14 @@ void sdl_display_init(Display
The commit 8e65b7c04965c8355e4ce43211582b6b83054e3d introduced
expire_time of UHCIState. But expire_time is not in vmstate, the
second uhci_frame_timer will not be fired immediately after loadvm.
Signed-off-by: TeLeMan
---
hw/usb-uhci.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-
Public bug reported:
Tested on qemu v0.11.0 and v0.12.3:
>qemu-kvm -cpu core2duo,+sse4.1,+sse4.2
CPU feature sse4.1 not found
CPU feature sse4.2 not found
>egrep "model name|flags" /proc/cpuinfo | sort -r | uniq
model name : Intel(R) Xeon(R) CPU X5570 @ 2.93GHz
flags :
Please send in any agenda items you are interested in covering.
If we have a lack of agenda items I'll cancel the week's call.
thanks,
-chris
1 - 100 of 107 matches
Mail list logo
