Dear all
I have set two directory for QEMU.
One of my qemu-ifup is as follow(the other ip address is different)
*#!/bin/sh*
*sudo modprobe tun*
*sudo /sbin/ifconfig $1 up 192.168.2.52 netmask 255.255.255.0 broadcast
192.168.2.255*
* *
*# IP masquerade*
*sudo echo "1" > /proc/sys/net/ipv4/ip_forw
On Thu, Nov 18, 2010 at 09:05:30AM +0200, Michael S. Tsirkin wrote:
> On Wed, Nov 17, 2010 at 01:50:27PM +0900, Isaku Yamahata wrote:
> > Emulates secondary bus reset when secondary bus reset bit
> > is written from 0 to 1.
> >
> > Signed-off-by: Isaku Yamahata
> > Signed-off-by: Anthony Liguori
On Thu, Nov 18, 2010 at 09:15:19AM +0200, Michael S. Tsirkin wrote:
> On Thu, Nov 18, 2010 at 04:09:34PM +0900, Isaku Yamahata wrote:
> > On Thu, Nov 18, 2010 at 08:46:43AM +0200, Michael S. Tsirkin wrote:
> > > > What is missing for multiple pci buses is
> > > > - a new PC machine description whic
On Thu, Nov 18, 2010 at 04:09:34PM +0900, Isaku Yamahata wrote:
> On Thu, Nov 18, 2010 at 08:46:43AM +0200, Michael S. Tsirkin wrote:
> > > What is missing for multiple pci buses is
> > > - a new PC machine description which has multiple pci buses
> > > My Q35 chipset patch will provide this.
> >
On Thu, Nov 18, 2010 at 08:46:43AM +0200, Michael S. Tsirkin wrote:
> > What is missing for multiple pci buses is
> > - a new PC machine description which has multiple pci buses
> > My Q35 chipset patch will provide this.
>
> IMHO, what we really need is a way to specify bridges
> through qdev.
On Wed, Nov 17, 2010 at 01:50:27PM +0900, Isaku Yamahata wrote:
> Emulates secondary bus reset when secondary bus reset bit
> is written from 0 to 1.
>
> Signed-off-by: Isaku Yamahata
> Signed-off-by: Anthony Liguori
> ---
> hw/pci_bridge.c | 12 +++-
> 1 files changed, 11 insertions(
On Wed, Nov 17, 2010 at 01:50:25PM +0900, Isaku Yamahata wrote:
> Signed-off-by: Isaku Yamahata
> Signed-off-by: Anthony Liguori
> ---
> hw/pci.c | 38 ++
> hw/pci.h |3 +++
> 2 files changed, 37 insertions(+), 4 deletions(-)
>
> diff --git a/hw/pci.c b
On Thu, Nov 18, 2010 at 12:09:18PM +0900, Isaku Yamahata wrote:
> Right now, qemu is internally ready to handle pci-to-pci bridge emulators
> and it's quite easy to add a new simple p2p bridge emulator.
> Just a single function to initialize vid/did and a single PCIDevinceInfo.
>
> But it's diffic
On Thu, Nov 18, 2010 at 11:08:40AM +0900, Isaku Yamahata wrote:
> On Wed, Nov 17, 2010 at 02:02:00PM +0200, Michael S. Tsirkin wrote:
> > > > Another bug is that migrating from qemu where a bit is writeable to one
> > > > where it's RO creates a situation where a RW bit becomes RO, or the
> > > > r
On Wed, Nov 17, 2010 at 09:41:03PM -0800, Wei Xu wrote:
> Could you explain more on irq routing in dsdt and related code in qemu? I
> encountered a problem: emulated user networking (-net nic -net user) cannot
> work in my qemu-kvm+q35+pcie code. Your original q35 (pure qemu) works fine.
The relat
Isaku,
Could you explain more on irq routing in dsdt and related code in qemu? I
encountered a problem: emulated user networking (-net nic -net user) cannot
work in my qemu-kvm+q35+pcie code. Your original q35 (pure qemu) works fine.
Thanks!
Wei
On 11/17/10 7:09 PM, "Isaku Yamahata" wrote:
>
http://download1.ideco-software.ru/ics/IdecoICS_405_121.iso
http://download2.ideco-software.ru/ics/IdecoICS_405_121.iso
--
KVM segmentation fault, using SCSI+writeback and linux 2.4 guest
https://bugs.launchpad.net/bugs/595438
You received this bug notification because you are a member of qemu-
d
Now that we have the function split out, we have to reindent it.
In order to increase the readability of the actual functional change,
this is split out.
Signed-off-by: Alexander Graf
---
hw/ide/core.c | 734
1 files changed, 367 insertio
Tried to reproduce this so as to be able to verify the fix in lucid-proposed,
but a 2.4 based livecd is apparently hard to come by! Can someone who
reproduces this point me to a livecd i can use?
--
KVM segmentation fault, using SCSI+writeback and linux 2.4 guest
https://bugs.launchpad.net/bugs/
This patch adds the storage sata class id.
Signed-off-by: Alexander Graf
---
hw/pci_ids.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/hw/pci_ids.h b/hw/pci_ids.h
index 82cba7e..ea3418c 100644
--- a/hw/pci_ids.h
+++ b/hw/pci_ids.h
@@ -15,6 +15,7 @@
#define PCI_CLAS
From: Roland Elek
We need to hook into some of the core IDE functionality for AHCI. To
do that, the easiest way is to make explicit functions calls be implicit
through a function call struct.
Signed-off-by: Roland Elek
Signed-off-by: Alexander Graf
---
v1 -> v2:
- rename IDEExtender to ID
When we add a device using -drive to the guest, we also need to create a
new SATA bus to handle the device. This patch does it the same way SCSI
does it today.
Signed-off-by: Alexander Graf
---
hw/pc.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/hw/pc.c b/hw/pc.c
This patch adds an emulation layer for an ICH-7M AHCI controller. For now
this controller does not do IDE legacy emulation. It is a pure AHCI controller.
Signed-off-by: Alexander Graf
---
v1 -> v2:
- rename IDEExtender to IDEBusOps and make a pointer (kraxel)
- make dma hooks explicit by p
The ATA command interpretation code can be used for PATA and SATA
interfaces alike. So let's split it out into a separate function.
Signed-off-by: Alexander Graf
---
hw/ide/core.c | 20 ++--
hw/ide/internal.h |2 ++
2 files changed, 16 insertions(+), 6 deletions(-)
dif
This patch adds support for AHCI emulation. I have tested and verified it works
in Linux, OpenBSD, Windows Vista and Windows 7. This AHCI emulation supports
NCQ, so multiple read or write requests can be outstanding at the same time.
The code is however not fully optimized yet. I'm fairly sure tha
From: Roland Elek
I modified ide_identify() to include the zero-based queue length
value in word 75, and set bit 8 in word 76 to signal NCQ support
in the identify data for AHCI SATA drives.
Signed-off-by: Roland Elek
---
hw/ide/core.c |7 +++
hw/ide/internal.h |2 ++
2 files c
For DMA operations, we need to hook into even more IDE functionality.
This patch adds the respective hooking points, allowing us to handle
SG lists ourselves in the AHCI code.
Signed-off-by: Roland Elek
Signed-off-by: Alexander Graf
---
v1 -> v2:
- make dma hooks explicit by putting them i
We need to be able to spawn new AHCI drives, so let's add AHCI support
to the -drive option.
Signed-off-by: Alexander Graf
---
blockdev.c|6 +-
blockdev.h|1 +
qemu-common.h |2 +-
3 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/blockdev.c b/blockdev.c
inde
We need a PCI ID for our new AHCI adapter. I just picked an ICH-7M
because that's the one built into the first Macbooks.
This patch adds a PCI ID define for an ICH-7M AHCI adapter.
Signed-off-by: Alexander Graf
---
hw/pci.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git
Right now, qemu is internally ready to handle pci-to-pci bridge emulators
and it's quite easy to add a new simple p2p bridge emulator.
Just a single function to initialize vid/did and a single PCIDevinceInfo.
But it's difficult to use multi pci buses at the moment
because other part isn't ready. I
When the total sent page size is larger than max_factor
times of the size of guest OS's memory, stop the
iteration.
The default value of max_factor is 3.
This is similar to XEN.
Signed-off-by: Wen Congyang
---
arch_init.c | 13 -
1 files changed, 12 insertions(+), 1 deletions(-)
On Tue, Nov 16, 2010 at 09:31:28PM -0800, Etienne Martineau wrote:
>
> On Wed, 17 Nov 2010, Isaku Yamahata wrote:
>
> > > Because of such it seems like the only way to maintain consistency
> > > between
> > > the assigned device and it's corresponding driver is to perform the error
> > > detec
On Wed, Nov 17, 2010 at 02:02:00PM +0200, Michael S. Tsirkin wrote:
> > > Another bug is that migrating from qemu where a bit is writeable to one
> > > where it's RO creates a situation where a RW bit becomes RO, or the
> > > reverse, which might confuse guests. So we will need a compatibility
> >
Uh, but capslock works for me! In the stock 0.12.5 maverick qemu-kvm
package.
(I hadn't noticed before, because I generally keep capslock set as an
additional control).
So this bug is, in fact fix committed. It sounds like you have a differnet bug
relating
to your keyboard layout. Please do o
Capslock turning on:
sdl_process_key({type=0x2,which=0x0,state=0x1,keysym={scancode=0x42,sym=0x12d,mod=0x2000,unicode=0x0}})
keycode = 0x3a
kbd_put_keycode(0x3a)
kbd_put_keycode(0xba)
capslock turning off:
sdl_process_key({type=0x3,which=0x0,state=0x0,keysym={scancode=0x42,sym=0x12d,mod=0x0,unic
Add an option to specify the host IP to send multicast packets from when
using a multicast socket for networking. The option takes an IP address
and sets the IP_MULTICAST_IF socket option, which causes the packets to
use that IP's interface as an egress.
This is useful if the host machine has seve
This patch introduce a fallback mechanism for old systems that do not
support utimensat(). This fix build failure with following warnings:
hw/virtio-9p-local.c: In function 'local_utimensat':
hw/virtio-9p-local.c:479: warning: implicit declaration of function 'utimensat'
hw/virtio-9p-local.c:479:
I modified qemu-kvm to show what keys it receives (patch attached). I am
using the German NEO layout and I get one press and one release event.
Here's the output, if I first press 'caps lock' and then '#':
sdl_process_key({type=0x2,which=0x0,state=0x1,keysym={scancode=0x42,sym=0x139,mod=0x0,unicod
I am reopening the bug for qemu-kvm, because the patch was dropped in
0.12.4+noroms-0ubuntu1.
** Changed in: qemu-kvm (Ubuntu)
Status: Fix Released => New
--
does not pass pressed caps lock to client
https://bugs.launchpad.net/bugs/427612
You received this bug notification because you are
On 11/17/2010 05:35 AM, Daniel P. Berrange wrote:
On Tue, Nov 16, 2010 at 09:46:20AM -0600, Anthony Liguori wrote:
On 11/08/2010 01:33 PM, Daniel P. Berrange wrote:
This introduces a new tracing backend that targets the SystemTAP
implementation of DTrace userspace tracing. The core fu
On 11/17/2010 04:39 PM, Paolo Bonzini wrote:
On 11/17/2010 09:08 PM, Blue Swirl wrote:
It's not simplification but to unify the build system. Some people
make changes to Makefiles and then test their changes without an
object directory, these may then break the build for those who use it.
This h
On 11/18/2010 12:05 AM, Peter Maydell wrote:
> It may be unified but it's pretty much unlike every other
> build system I've ever seen.
If you want another approach you could do what glibc does (IIRC),
which is to just give an error message if you invoke configure in
the source directory sugge
On 11/16/2010 03:24 PM, Alex Williamson wrote:
On Tue, 2010-11-16 at 08:58 -0600, Anthony Liguori wrote:
On 11/01/2010 10:14 AM, Alex Williamson wrote:
Register the actual VM RAM using the new API
Signed-off-by: Alex Williamson
---
hw/pc.c | 12 ++--
1 files changed,
> On 12 November 2010 10:00, Paolo Bonzini wrote:
>> On 08/09/2010 01:51 AM, adq wrote:
>>>
>>> Figured out what the problem is - READ DVD STRUCTURE has its xfer
>>> length in an unexpected place, so hw/scsi-bus.c retrieves completely
>>> the wrong value for the transfer length. Attached nasty hac
On 17 November 2010 22:39, Paolo Bonzini wrote:
> On 11/17/2010 09:08 PM, Blue Swirl wrote:
>> It's not simplification but to unify the build system. Some people
>> make changes to Makefiles and then test their changes without an
>> object directory, these may then break the build for those who us
I'll have a go at resurrecting it; I wasn't sure if there was any
interest before.
On 12 November 2010 10:00, Paolo Bonzini wrote:
> On 08/09/2010 01:51 AM, adq wrote:
>>
>> Figured out what the problem is - READ DVD STRUCTURE has its xfer
>> length in an unexpected place, so hw/scsi-bus.c retrie
On 11/17/2010 09:08 PM, Blue Swirl wrote:
It's not simplification but to unify the build system. Some people
make changes to Makefiles and then test their changes without an
object directory, these may then break the build for those who use it.
This has happened several times already. Hopefully w
2010/11/16 Gleb Natapov :
> On Tue, Nov 16, 2010 at 06:30:19PM +, Blue Swirl wrote:
>> >> Perhaps the FW path should use device class names if no name is specified.
>> > What do you mean by "device class name". We can do something like this:
>> > if (dev->child_bus.lh_first)
>> > return
On 11/16/2010 05:17 PM, Anthony Liguori wrote:
Except, in virtproxy, the fact that Alice cannot talk to Joe blocks Mary
from talking to Bob which creates a dead lock.
To be honest, there's no simple solution. This is a classic queuing
problem. You need some form of congestion control to fix this
Here is another update for the ceph storage driver. It includes changes
for the annotations Stefan made last week and a bit more things Sage
discovered while looking over the driver again.
I really hope that this time we are not only close, but have reached
a quality that everyone is satisfied wit
On Wed, Nov 17, 2010 at 8:49 PM, Michael S. Tsirkin wrote:
> On Wed, Nov 17, 2010 at 08:38:25PM +, Stefan Hajnoczi wrote:
>> On Wed, Nov 17, 2010 at 6:01 PM, Michael S. Tsirkin wrote:
>> > On Wed, Nov 17, 2010 at 04:19:25PM +, Stefan Hajnoczi wrote:
>> >> The v4 version includes:
>> >> *
On Wed, Nov 17, 2010 at 08:38:25PM +, Stefan Hajnoczi wrote:
> On Wed, Nov 17, 2010 at 6:01 PM, Michael S. Tsirkin wrote:
> > On Wed, Nov 17, 2010 at 04:19:25PM +, Stefan Hajnoczi wrote:
> >> The v4 version includes:
> >> * Simpler start/stop ioeventfd mechanism using bool ioeventfd_start
On Wed, Nov 17, 2010 at 6:01 PM, Michael S. Tsirkin wrote:
> On Wed, Nov 17, 2010 at 04:19:25PM +, Stefan Hajnoczi wrote:
>> The v4 version includes:
>> * Simpler start/stop ioeventfd mechanism using bool ioeventfd_started state
>> * Support for migration
>> * Handle deassign race condition
On 11/17/2010 08:15 PM, Blue Swirl wrote:
If the user attempts to run 'configure' in the source tree,
create an object directory and configure that instead.
Rename topmost Makefile to Makefile.top. Add a new Makefile, which
is only used when user attempts to run 'make' in the source tree.
Inte
On Wed, Nov 17, 2010 at 8:00 PM, Paolo Bonzini wrote:
> On 11/17/2010 08:15 PM, Blue Swirl wrote:
>>
>> If the user attempts to run 'configure' in the source tree,
>> create an object directory and configure that instead.
>>
>> Rename topmost Makefile to Makefile.top. Add a new Makefile, which
>>
On Tue, Nov 16, 2010 at 10:37 PM, Peter Maydell
wrote:
> On 16 November 2010 21:59, Blue Swirl wrote:
>> If the user attempts to run 'configure' in the source tree,
>> create an object directory and configure that instead.
>>
>> Rename topmost Makefile to Makefile.top. Add a new Makefile, which
>
On Wed, Nov 17, 2010 at 04:19:25PM +, Stefan Hajnoczi wrote:
> The v4 version includes:
> * Simpler start/stop ioeventfd mechanism using bool ioeventfd_started state
> * Support for migration
> * Handle deassign race condition to avoid dropping a virtqueue kick
> * Add missing kvm_enabled()
On Wed, Nov 17, 2010 at 06:02:39PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> Better don't try ...
> >>>
> >>>Better prevent it then?
> >>
> >>How can I do that?
>
> Question still stands: Is there some way to disable hotplug for
> certain pci devices?
Not sure. It's really a work-around bug,
Hi Peter,
Is this what you had in mind?
--
ARM semihosting SYS_GET_CMDLINE does not return arguments
https://bugs.launchpad.net/bugs/673613
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
Status in QEMU: New
Bug description:
I have do
On 17.11.2010, at 18:07, Stefan Weil wrote:
> Am 17.11.2010 13:01, schrieb Alexander Graf:
>> The s390 target doesn't compile out of the box anymore. This patch fixes all
>> the obvious glitches that got introduced in the last few weeks.
>>
>> Signed-off-by: Alexander Graf
>> ---
>> hw/s390-vir
Hi,
Better don't try ...
Better prevent it then?
How can I do that?
Question still stands: Is there some way to disable hotplug for certain
pci devices?
How does this work btw? Only
one vga adapter can drive the legacy vga ports, right? Is there
some way to enable/disable this p
Am 17.11.2010 13:01, schrieb Alexander Graf:
The s390 target doesn't compile out of the box anymore. This patch
fixes all
the obvious glitches that got introduced in the last few weeks.
Signed-off-by: Alexander Graf
---
hw/s390-virtio-bus.h | 2 ++
hw/s390-virtio.c | 1 +
target-s390x/kvm.c | 2
Signed-off-by: Gleb Natapov
---
hw/fw_cfg.c | 14 ++
sysemu.h|1 +
vl.c| 48
3 files changed, 63 insertions(+), 0 deletions(-)
diff --git a/hw/fw_cfg.c b/hw/fw_cfg.c
index 7b9434f..20a816f 100644
--- a/hw/fw_cfg.c
Extend -option-rom command to have additional parameter ,bootindex=.
Signed-off-by: Gleb Natapov
---
hw/loader.c| 16 +++-
hw/loader.h|8
hw/multiboot.c |3 ++-
hw/ne2000.c|2 +-
hw/nseries.c |4 ++--
hw/palm.c |6 +++---
hw/pc.c
Store all io ports used by device in ISADevice structure.
Signed-off-by: Gleb Natapov
---
hw/cs4231a.c |1 +
hw/fdc.c |3 +++
hw/gus.c |4
hw/ide/isa.c |2 ++
hw/isa-bus.c | 25 +
hw/isa.h |4
hw/m48t59.c
Signed-off-by: Gleb Natapov
---
hw/ide/cmd646.c |4 ++--
hw/ide/internal.h |3 ++-
hw/ide/isa.c |2 +-
hw/ide/piix.c |4 ++--
hw/ide/qdev.c |3 ++-
hw/ide/via.c |4 ++--
6 files changed, 11 insertions(+), 9 deletions(-)
diff --git a/hw/ide/cmd646.c b/
If bootindex is specified on command line a string that describes device
in firmware readable way is added into sorted list. Later this list will
be passed into firmware to control boot order.
Signed-off-by: Gleb Natapov
---
block_int.h |4 +++-
hw/e1000.c |4
hw/eepro100.c
Signed-off-by: Gleb Natapov
---
hw/scsi-bus.c | 23 +++
1 files changed, 23 insertions(+), 0 deletions(-)
diff --git a/hw/scsi-bus.c b/hw/scsi-bus.c
index 5a3fd4b..db7482a 100644
--- a/hw/scsi-bus.c
+++ b/hw/scsi-bus.c
@@ -5,9 +5,12 @@
#include "qdev.h"
#include "blockde
Action that depends on fully initialized device model should register
with this notifier chain.
Signed-off-by: Gleb Natapov
---
sysemu.h |2 ++
vl.c | 15 +++
2 files changed, 17 insertions(+), 0 deletions(-)
diff --git a/sysemu.h b/sysemu.h
index 48f8eee..c42f33a 100644
-
Signed-off-by: Gleb Natapov
---
hw/ide/qdev.c | 13 +
1 files changed, 13 insertions(+), 0 deletions(-)
diff --git a/hw/ide/qdev.c b/hw/ide/qdev.c
index 88ff657..01a181b 100644
--- a/hw/ide/qdev.c
+++ b/hw/ide/qdev.c
@@ -24,9 +24,12 @@
/* - */
Change fw_cfg_add_file() to get full file path as a parameter instead
of building one internally. Two reasons for that. First caller may need
to know how file is named. Second this moves policy of file naming out
from fw_cfg. Platform may want to use more then two levels of
directories for instance
Signed-off-by: Gleb Natapov
---
hw/pci.c | 108 -
1 files changed, 85 insertions(+), 23 deletions(-)
diff --git a/hw/pci.c b/hw/pci.c
index 438c0d1..8514e15 100644
--- a/hw/pci.c
+++ b/hw/pci.c
@@ -43,12 +43,14 @@
static void pcibu
Prints out mmio or pio used to access child device.
Signed-off-by: Gleb Natapov
---
hw/pci_host.c |2 ++
hw/sysbus.c | 30 ++
hw/sysbus.h |4
3 files changed, 36 insertions(+), 0 deletions(-)
diff --git a/hw/pci_host.c b/hw/pci_host.c
index bc5b771
Signed-off-by: Gleb Natapov
---
hw/usb-bus.c | 42 ++
1 files changed, 42 insertions(+), 0 deletions(-)
diff --git a/hw/usb-bus.c b/hw/usb-bus.c
index 256b881..8b4583c 100644
--- a/hw/usb-bus.c
+++ b/hw/usb-bus.c
@@ -5,11 +5,13 @@
#include "monitor.h"
Ports on root hub will have NULL here. This is needed to reconstruct
path from device to its root hub to build device path.
Signed-off-by: Gleb Natapov
---
hw/usb-bus.c |3 ++-
hw/usb-hub.c |2 +-
hw/usb-musb.c |2 +-
hw/usb-ohci.c |2 +-
hw/usb-uhci.c |2 +-
hw/usb.h
New get_fw_dev_path callback will be used for build device path usable
by firmware in contrast to qdev qemu internal device path.
Signed-off-by: Gleb Natapov
---
hw/qdev.h |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/hw/qdev.h b/hw/qdev.h
index 9f90efe..dc669b3 10064
Add "fw_name" to DeviceInfo to use in device path building. In
contrast to "name" "fw_name" should refer to functionality device
provides instead of particular device model like "name" does.
Signed-off-by: Gleb Natapov
---
hw/fdc.c|1 +
hw/ide/isa.c|1 +
hw/ide/qdev.c |
Use device ioports to create unique device path.
Signed-off-by: Gleb Natapov
---
hw/isa-bus.c | 16
1 files changed, 16 insertions(+), 0 deletions(-)
diff --git a/hw/isa-bus.c b/hw/isa-bus.c
index c0ac7e9..c423c1b 100644
--- a/hw/isa-bus.c
+++ b/hw/isa-bus.c
@@ -31,11 +31,13
I am using open firmware naming scheme to specify device path names.
In this version: added SCSI bus support. Pass boot order list as file
to firmware.
Names look like this on pci machine:
/p...@i0cf8/i...@1,1/dr...@1/d...@0
/p...@i0cf8/i...@1/f...@03f1/flo...@1
/p...@i0cf8/i...@1/f...@03f1/flo...
On Wed, Nov 17, 2010 at 04:20:45PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> +qxl0 = qxl;
> >>>
> >>>What happens when this device is then removed?
> >>
> >>Better don't try ...
> >
> >Better prevent it then?
>
> How can I do that?
>
> >>The primary vga can't be hot-unplugged in qemu.
On Wed, Nov 17, 2010 at 05:12:12PM +0100, Bernhard Kohl wrote:
> I will fix the guest and inform you after testing.
> Then we can skip this patch.
OK, that's best,
On Wed, Nov 17, 2010 at 1:41 PM, Kevin Wolf wrote:
> Am 17.11.2010 13:43, schrieb Stefan Hajnoczi:
>>> A typical sequence in qcow2 (simple cluster allocation) looks like this:
>>>
>>> 1. Update refcount table
>>> 2. bdrv_flush
>>> 3. Update L2 entry
>>>
>>> If we delay the operation and get three
On Wed, Nov 17, 2010 at 1:41 PM, Kevin Wolf wrote:
> Am 17.11.2010 13:43, schrieb Stefan Hajnoczi:
>>> A typical sequence in qcow2 (simple cluster allocation) looks like this:
>>>
>>> 1. Update refcount table
>>> 2. bdrv_flush
>>> 3. Update L2 entry
>>>
>>> If we delay the operation and get three
On Tue, Nov 16, 2010 at 09:22:45AM +0200, Gleb Natapov wrote:
> On Mon, Nov 15, 2010 at 09:52:19PM -0500, Kevin O'Connor wrote:
> > I also have an ulterior motive here. If the boot order is exposed as
> > a newline separated list via an entry in QEMU_CFG_FILE_DIR, then this
> > becomes free for co
On 11/05/2010 07:44 PM, Marcelo Tosatti wrote:
The following changes since commit d33ea50a958b2e050d2b28e5f17e3b55e91c6d74:
scsi-disk: Fix immediate failure of bdrv_aio_* (2010-11-04 13:54:37 +0100)
Pulled. Thanks.
Regards,
Anthony Liguori
are available in the git repository at:
The VirtIOPCIProxy bugs field is currently used to enable workarounds
for older guests. Rename it to flags so that other per-device behavior
can be tracked.
A later patch uses the flags field to remember whether ioeventfd should
be used for virtqueue host notification.
Signed-off-by: Stefan Hajn
Signed-off-by: Stefan Hajnoczi
---
docs/qdev-device-use.txt |9 +++--
1 files changed, 7 insertions(+), 2 deletions(-)
diff --git a/docs/qdev-device-use.txt b/docs/qdev-device-use.txt
index f252c8e..85feda7 100644
--- a/docs/qdev-device-use.txt
+++ b/docs/qdev-device-use.txt
@@ -97,15 +9
There used to be a limit of 6 KVM io bus devices inside the kernel. On
such a kernel, don't use ioeventfd for virtqueue host notification since
the limit is reached too easily. This ensures that existing vhost-net
setups (which always use ioeventfd) have ioeventfds available so they
can continue
Virtqueue notify is currently handled synchronously in userspace virtio. This
prevents the vcpu from executing guest code while hardware emulation code
handles the notify.
On systems that support KVM, the ioeventfd mechanism can be used to make
virtqueue notify a lightweight exit by deferring har
The v4 version includes:
* Simpler start/stop ioeventfd mechanism using bool ioeventfd_started state
* Support for migration
* Handle deassign race condition to avoid dropping a virtqueue kick
* Add missing kvm_enabled() check to kvm_has_many_ioeventfds()
* Documentation updates for qdev -devi
Am 17.11.2010 15:12, schrieb ext Michael S. Tsirkin:
On Tue, Nov 16, 2010 at 05:43:06PM +0100, Bernhard Kohl wrote:
Am 16.11.2010 14:14, schrieb m...@redhat.com:
Although explicitly disallowed by the PCI spec, some guests read a
single byte or word from mmio. Likely a guest OS bug, b
diff --git a/arm-semi.c b/arm-semi.c
index 0687b03..53b40e4 100644
--- a/arm-semi.c
+++ b/arm-semi.c
@@ -373,45 +373,48 @@ uint32_t do_arm_semihosting(CPUState *env)
#ifdef CONFIG_USER_ONLY
/* Build a commandline from the original argv. */
{
-char **arg = ts->info->
Hi,
+qxl0 = qxl;
What happens when this device is then removed?
Better don't try ...
Better prevent it then?
How can I do that?
The primary vga can't be hot-unplugged in qemu. Not only because
the qxl0 pointer would point into nowhere in this case, but also
because you can't
On Tue, Nov 16, 2010 at 05:26:04PM +0900, Isaku Yamahata wrote:
> Now v9 of pcie aer patch series.
> I dropped qmp patch to inject aer error because it will depends
> on Gleb's openfirmware path patches.
> Once his patches are merged, the glue patch will be respined.
>
> Patch description:
> The p
On Tue, Nov 16, 2010 at 05:43:06PM +0100, Bernhard Kohl wrote:
> Am 16.11.2010 14:14, schrieb m...@redhat.com:
> >Although explicitly disallowed by the PCI spec, some guests read a
> >single byte or word from mmio. Likely a guest OS bug, but I have an OS
> >which reads single bytes and it works fi
On Tue, Nov 16, 2010 at 05:43:06PM +0100, Bernhard Kohl wrote:
> Am 16.11.2010 14:14, schrieb m...@redhat.com:
> >Although explicitly disallowed by the PCI spec, some guests read a
> >single byte or word from mmio. Likely a guest OS bug, but I have an OS
> >which reads single bytes and it works fi
Open-code functions created in the previous patch,
to make code more compact and clear.
Detcted and documented what looks like a bug in code
that becomes apparent from this refactoring.
Signed-off-by: Michael S. Tsirkin
---
hw/pcie_aer.c | 80 +++
Added some TODOs: they are trivial but omitted here
to make the patch logic as transparent as possible.
Signed-off-by: Michael S. Tsirkin
---
hw/pcie_aer.c | 48 +++-
1 files changed, 31 insertions(+), 17 deletions(-)
diff --git a/hw/pcie_aer.c b/hw
On Tue, Nov 16, 2010 at 05:26:09PM +0900, Isaku Yamahata wrote:
> This patch implements helper functions for pcie aer capability
> which will be used later.
>
> Signed-off-by: Isaku Yamahata
OK, I applied this and tried to get rid of recursion,
and clean up some whitespace and english mistakes.
On Wed, Nov 17, 2010 at 02:28:21PM +0100, Gerd Hoffmann wrote:
> On 11/16/10 18:43, Michael S. Tsirkin wrote:
> >On Tue, Nov 02, 2010 at 02:34:58PM +0100, Gerd Hoffmann wrote:
> >>+if (ram_size< 32 * 1024 * 1024)
> >>+ram_size = 32 * 1024 * 1024;
> >>+vga_common_init(vg
Hi,
Hmm, no bus registered anywhere. Dunno whenever it makes sense to
register ide bus(es) here or whenever we should create a new sata
bus.
I'm not sure I understand this comment :).
The ahci controller should register one or more busses where you can
hook up devices to via -device. Ri
Am 17.11.2010 13:43, schrieb Stefan Hajnoczi:
> On Fri, Nov 5, 2010 at 6:38 PM, Kevin Wolf wrote:
>> Instead of directly executing writes and fsyncs, queue them and execute them
>> asynchronously. What makes this interesting is that we can delay syncs and if
>> multiple syncs occur, we can merge t
On 11/16/10 18:43, Michael S. Tsirkin wrote:
On Tue, Nov 02, 2010 at 02:34:58PM +0100, Gerd Hoffmann wrote:
+if (ram_size< 32 * 1024 * 1024)
+ram_size = 32 * 1024 * 1024;
+vga_common_init(vga, ram_size);
+vga_init(vga);
+register_ioport_write(0x3c0, 1
In which qmp-shell will exclusively use the HMP passthrough feature,
this is useful for testing.
Example:
# ./qmp-shell -H qmp-sock
Welcome to the HMP shell!
Connected to QEMU 0.13.50
(QEMU) info network
VLAN 0 devices:
user.0: net=10.0.2.0, restricted=n
e1000.0
This driver handles in-memory chardev operations. That's, all writes
to this driver are stored in an internal buffer and it doesn't talk
to the external world in any way.
Right now it's very simple: it supports only writes. But it can be
easily extended to support more operations.
This is going t
1 - 100 of 138 matches
Mail list logo
