The SDM specifies (June 2014 Vol3 11.11.5):
On a hardware reset, the P6 and more recent processors clear the
valid flags in variable-range MTRRs and clear the E flag in the
IA32_MTRR_DEF_TYPE MSR to disable all MTRRs. All other bits in the
MTRRs are undefined.
We currently do none
The ELF V2 ABI for PPC64 defines MINSIGSTKSZ as 4096 bytes whereas it was
2048 previously.
Signed-off-by: Tom Musta
---
V2: Define and use TARGET_MINSIGSTKSZ constants from the various
linux-user/$ARCH/syscall.h files (per Peter Maydell's review).
linux-user/aarch64/syscall.h|1 +
linux
There's another bugreport filed against debian qemu package,
http://bugs.debian.org/755738 . It talks about security_model=mapped-xattr
case, where file type is stored elsewhere, and all files are turned into
regular files. http://bugs.debian.org/755738#10 is the proposed patch.
Thanks,
/mjt
On Wed, Aug 13, 2014 at 8:03 PM, William Dauchy wrote:
> during qemu startup I see several queues in
> /sys/devices/virtual/net/vifA.0/queues and it quickly disappears; at
> the end I see only one rx and one tx.
> Am I wrong on something? What can I do to help debug this situation?
finally found
On Tue, 2014-08-12 at 08:09 +0200, Eric Auger wrote:
> On 08/11/2014 09:25 PM, Alex Williamson wrote:
> > On Sat, 2014-08-09 at 15:25 +0100, Eric Auger wrote:
> >> diff --git a/include/hw/vfio/vfio-common.h b/include/hw/vfio/vfio-common.h
> >> new file mode 100644
> >> index 000..4684ee5
> >> -
a number of comments -- feel free to address or ignore each as you see fit:
On 08/13/14 21:09, Alex Williamson wrote:
> The SDM specifies (June 2014 Vol3 11.11.5):
>
> On a hardware reset, the P6 and more recent processors clear the
> valid flags in variable-range MTRRs and clear the E fl
Because the old refcount structure will be leaked after having rebuilt
it, we need to recalculate the refcounts and run a leak-fixing operation
afterwards.
Signed-off-by: Max Reitz
---
block/qcow2-refcount.c | 33 +
1 file changed, 33 insertions(+)
diff --git a/b
If the qcow2 check function detects a refcount block located beyond the
image end, grow the image appropriately. This cannot break anything and
is the logical fix for such a case.
Signed-off-by: Max Reitz
---
block/qcow2-refcount.c | 50 ++
1 file
Put the code for comparing the calculated refcounts against the on-disk
refcounts during qemu-img check into an own function.
Signed-off-by: Max Reitz
---
block/qcow2-refcount.c | 91 --
1 file changed, 52 insertions(+), 39 deletions(-)
diff --git
If a referenced cluster has a refcount of 0, increasing its refcount may
result in clusters being allocated for the refcount structures. This may
overwrite the referenced cluster, therefore we cannot simply increase
the refcount then.
In such cases, we can either try to replicate all the refcount
039, 060 and 061 all create images with referenced clusters having a
refcount of 0. Because previous commits changed handling of such errors,
these tests now have a different output. Fix it.
Furthermore, 060 created a refblock with a refcount greater than one
which now results in having to rebuild
On Wed, Aug 13, 2014 at 2:32 PM, Kevin Wolf wrote:
> Am 13.08.2014 um 18:38 hat Xingbo Wu geschrieben:
>> On Wed, Aug 13, 2014 at 11:54 AM, Kevin Wolf wrote:
>> > Am 12.08.2014 um 01:38 hat 吴兴博 geschrieben:
>> >> Hello,
>> >>
>> >> The introduction in the wiki page present several advantages of
The previous commit introduced the "rebuild" variable to qcow2's
implementation of the image consistency check. Now make use of this by
adding a function which creates a completely new refcount structure
based solely on the in-memory information gathered before.
The old refcount structure will be
Put the code for calculating the reference counts during qemu-img check
into an own function.
Signed-off-by: Max Reitz
---
block/qcow2-refcount.c | 202 +
1 file changed, 122 insertions(+), 80 deletions(-)
diff --git a/block/qcow2-refcount.c b/blo
There are certain cases where repairing a qcow2 image might actually
damage it further (or rather, where repairing it has in fact damaged it
further with the old qcow2 check implementation). This should not
happen, so add a test for these cases.
Signed-off-by: Max Reitz
---
tests/qemu-iotests/10
As can be seen in the final patch of this series, there are certain
cases where the current repair implementation of qcow2 actually damages
the image further because it allocates new clusters for the refcount
structure which overlap with existing but according to the on-disk
refcounts (which are as
On 08/13/2014 03:04 PM, Xingbo Wu wrote:
>>> I read several messages from this thread: "[RFC] qed: Add QEMU
>>> Enhanced Disk format". To my understanding, if the new format can be
>>> acceptable to the community:
>>> It needs to retain all the key features provided by qcow2,
>>> especially for
This submission does not re-send patches 1-24, which are identical
to the v2 submission and have already been pulled onto
stefanha's block staging branch.
This patch series introduces a number of small fixes and tweaks to
help support an AHCI test suite that in the future I hope to expand
to a ful
This test engages the HBA functionality and initializes
values to sane defaults to allow for minimal HBA functionality.
Buffers are allocated and pointers are updated to allow minimal
I/O commands to complete as expected. Error registers and responses
are sanity checked for specification adherence
In a real AHCI device, several S/ATA registers are mirrored or shadowed
within the AHCI register set. These registers are not updated
synchronously for each read access, but rather after a Device-to-Host
Register FIS packet is received, which contains the values from these
registers on the device.
Currently, there is no qtest to test the functionality of
the AHCI functionality present within the Q35 machine type.
This patch adds a skeleton for an AHCI test suite,
and adds a simple sanity-check test case where we
identify that the AHCI device is present, then
disengage the virtual machine.
In the Intel ICH9 data sheet, the MSI capability offset
in the PCI configuration space for ICH9 AHCI devices is
specified to be 0x80.
Further, the PCI capability pointer should always point
to 0x80 in ICH9 devices, despite the fact that AHCI 1.3
specifies that it should be pointing to PMCAP (Which
This adds a test wherein we engage the PCI AHCI
device and ensure that the memory region for the
HBA functionality is now accessible.
Under Q35 environments, additional PCI configuration
is performed to ensure that the HBA functionality
will become usable.
Signed-off-by: John Snow
---
tests/ahc
Utilizing all of the bring-up code in pci_enable and hba_enable,
this test issues a simple IDENTIFY command via the HBA and retrieves
the response via the PIO receive mechanisms of the HBA.
Bugs: The DPS interrupt (Descriptor Processed Status) does not
currently get set. This will need to be adjus
Add a test routine that checks the boot-up values of the HBA
configuration memory space against the AHCI 1.3 specification
and Intel ICH9 data sheet (for Q35 machines) for adherence and
sane values.
The HBA is not yet engaged or put into the idle state.
Signed-off-by: John Snow
---
tests/ahci-t
Adds a specification adherence test for AHCI
where the boot-up values for the PCI configuration space
are compared against the AHCI 1.3 specification.
This test does not itself attempt to engage the device.
Signed-off-by: John Snow
---
tests/ahci-test.c | 305 +++
El Wed, 13 Aug 2014 18:27:40 +0100
Stefan Hajnoczi escribió:
> > +void qvring_init(const QGuestAllocator *alloc, QVirtQueue *vq,
> > uint64_t addr) +{
> > +int i;
> > +
> > +vq->desc = addr;
> > +vq->avail = vq->desc + vq->size*sizeof(QVRingDesc);
> > +vq->used = (uint64_t)((vq->av
On Wed, 2014-08-13 at 22:33 +0200, Laszlo Ersek wrote:
> a number of comments -- feel free to address or ignore each as you see fit:
>
> On 08/13/14 21:09, Alex Williamson wrote:
> > The SDM specifies (June 2014 Vol3 11.11.5):
> >
> > On a hardware reset, the P6 and more recent processors cle
On 08/14/14 00:06, Alex Williamson wrote:
> On Wed, 2014-08-13 at 22:33 +0200, Laszlo Ersek wrote:
>> a number of comments -- feel free to address or ignore each as you see fit:
>>
>> On 08/13/14 21:09, Alex Williamson wrote:
>>> mappings which are now stale after reset. The result is that OVMF
>
On 08/14/14 01:17, Laszlo Ersek wrote:
> - With KVM, the lack of loading MTRR state from KVM, combined with the
> (partial) storing of MTRR state to KVM, has two consequences:
> - migration invalidates (loses) MTRR state,
I'll concede that migration *already* loses MTRR state (on KVM), even
b
someone please reviews the patch when have time.
Thanks a lot,
Xin
On Mon, Aug 4, 2014 at 8:37 PM, Xin Tong wrote:
> Sorry for the absence. Forgot the patch in submission till then. I rebased
> the patch to the newest QEMU git repository and retook the performance
> improvement data. Please re
Hello,
I wish to propose dynamic rebase of disk image, and upload some ideas.
Can someone create me an account?
Regards,
Choonho Son
On Wed, Aug 13, 2014 at 10:27 PM, Benoît Canet wrote:
> The Wednesday 13 Aug 2014 à 18:08:47 (+0800), Ming Lei wrote :
>> This test runs dummy function with coroutine by using
>> two enter and one yield since which is a common usage.
>>
>> So we can see the cost introduced by corouting for running
Michael,
Any further comments to this revision?
Thanks
Tiejun
On 2014/8/12 17:49, Tiejun Chen wrote:
v5:
* Simplify to make sure its really inherited from the standard one in patch #3
* Then drop the original patch #3
v4:
* Rebase on latest tree
* Drop patch #2
* Regenerate patches after Mi
On Tue, Aug 12, 2014 at 9:36 PM, Andreas Färber wrote:
> Am 04.08.2014 07:08, schrieb Peter Crosthwaite:
>> If "[*]" is given as the last part of a QOM property name, treat that
>> as an array property. The added property is given the first available
>> name, replacing the * with a decimal number
On Wed, Aug 13, 2014 at 5:04 PM, Xingbo Wu wrote:
> On Wed, Aug 13, 2014 at 2:32 PM, Kevin Wolf wrote:
>> Am 13.08.2014 um 18:38 hat Xingbo Wu geschrieben:
>>> On Wed, Aug 13, 2014 at 11:54 AM, Kevin Wolf wrote:
>>> > Am 12.08.2014 um 01:38 hat 吴兴博 geschrieben:
>>> >> Hello,
>>> >>
>>> >> The
On 2014/8/13 19:25, Nikolay Nikolaev wrote:
> On Wed, Aug 13, 2014 at 12:10 PM, Nikolay Nikolaev
> wrote:
>> On Tue, Aug 12, 2014 at 6:47 PM, Nikolay Nikolaev
>> wrote:
>>>
>>> Hello,
>>>
>>>
>>> On Tue, Aug 12, 2014 at 5:41 AM, Li Liu wrote:
Hi all,
Is anyone there can tel
On Wed, Aug 13, 2014 at 01:14:23PM +0200, Markus Armbruster wrote:
> David Gibson writes:
>
> > As of qemu-2.1, spapr/pseries, has a set of versioned machine classes to
> > represent the machine type as it appeared to the guest in different qemu
> > versions. This allows for safe migration of gu
If "[*]" is given as the last part of a QOM property name, treat that
as an array property. The added property is given the first available
name, replacing the * with a decimal number counting from 0.
First add with name "foo[*]" will be "foo[0]". Second "foo[1]" and so
on.
Callers may inspect th
Obsoleted by automatic object_property_add arrayification.
Reviewed-by: Paolo Bonzini
Signed-off-by: Peter Crosthwaite
---
memory.c | 30 +-
1 file changed, 5 insertions(+), 25 deletions(-)
diff --git a/memory.c b/memory.c
index 64d7176..5272bf9 100644
--- a/memory
On 08/13/2014 10:03 PM, Walid Nouri wrote:
While looking to find some ideas for approaches to replicating block
devices I have read the paper about the Remus implementation. I think
MC can take a similar approach for local disk.
I agree.
Here are the main facts that I have understood:
L
On Wed, Aug 13, 2014 at 03:10:02PM +0200, Andreas Färber wrote:
> Hi,
>
> Am 13.08.2014 03:23, schrieb David Gibson:
> > As of qemu-2.1, spapr/pseries, has a set of versioned machine classes to
> > represent the machine type as it appeared to the guest in different qemu
> > versions. This allows
Sometimes it is necessary to test whether virtio-net can send and receive
packets
normally, just as e1000 does. This patch adds loopback for virtio-net, when the
command 'VIRTIO_NET_CTRL_LOOPBACK_SET' is sent from front-end driver(such as
virtio-net driver in linux.git), virtio-net goes into loop
Hi,
For all NICs (except virtio-net) emulated by qemu,such as e1000, rtl8139,
pcnet and ne2k_pci, Qemu can still receive packets when VM is not running.
If this happened in *migration's* last PAUSE VM stage,
The new dirty RAM related to the packets will be missed,
And this will lead serious netw
On Wed, 13 Aug 2014 10:05:51 +0400
Michael Tokarev wrote:
> BTW, I found a system here with an SSD which supports discard, and tried my
> guests against it -- everything works fine when I use sata/ahci, but it breaks
> indeed when using the default IDE interface.
Hello,
Thanks for working on th
Sometimes it is necessary to test whether virtio-net can send and receive
packets
normally, just as e1000 does. This patch adds loopback for virtio-net, when the
command 'VIRTIO_NET_CTRL_LOOPBACK_SET' is sent from front-end driver(such as
virtio-net driver in linux.git), virtio-net goes into loop
Hi,
Here is my current wip on the throttle group support.
For the user interface I implemented Stefanha's idea proposed in Stuttgart.
For the throttling algorithm I use a cooperative round robin scheduler.
Classical round robin works with a fixed HZ ticks and it's totaly incompatible
with the t
The throttle_group_incref increment the refcount of a throttle group given it's
name and return the associated throttle state.
The throttle_group_unref is the mirror function for cleaning up.
Signed-off-by: Benoit Canet
---
block/Makefile.objs | 1 +
block/throttle-groups.c
This patch transform the timer_pending call into two boolean values in the
ThrottleState structure.
This way we are sure that when multiple timers will be used only
one can be armed at a time.
Signed-off-by: Benoit Canet
---
block.c | 2 ++
include/qemu/throttle.h | 3 +++
uti
This will be needed by the group throttling patches for the algorithm to be
accurate.
Signed-off-by: Benoit Canet
---
block.c | 7 +--
include/qemu/throttle.h | 3 ++-
util/throttle.c | 12 +++-
3 files changed, 14 insertions(+), 8 deletions(-)
diff --git a
Signed-off-by: Benoit Canet
---
include/qemu/throttle.h | 4 ++--
tests/test-throttle.c | 4 ++--
util/throttle.c | 4 ++--
3 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/include/qemu/throttle.h b/include/qemu/throttle.h
index 3b9d1b8..8abd94d 100644
--- a/include/qemu/t
Hi QEMU devs,
QEMU 2.10 does not currently run Windows 7 64-bit without KVM. There have been
a few threads about this over the past few years (such as
https://bugs.launchpad.net/qemu/+bug/921208 and
http://lists.gnu.org/archive/html/qemu-devel/2012-09/msg02603.html), but the
problem was never
Group throttling will share ThrottleState between multiple bs.
As a consequence the ThrottleState will be accessed by multiple aio context.
Timers are tied to their aio context so they must go out of the ThrottleState
structure.
This commit pave the way for each bs of a common ThrottleState to h
This will be needed by the group throttling algorithm.
Signed-off-by: Benoit Canet
---
include/qemu/throttle.h | 2 ++
util/throttle.c | 11 +++
2 files changed, 13 insertions(+)
diff --git a/include/qemu/throttle.h b/include/qemu/throttle.h
index 3a16c48..3b9d1b8 100644
--- a/
Signed-off-by: Benoit Canet
---
tests/test-throttle.c | 51 +++
1 file changed, 51 insertions(+)
diff --git a/tests/test-throttle.c b/tests/test-throttle.c
index 66e4982..50e6655 100644
--- a/tests/test-throttle.c
+++ b/tests/test-throttle.c
@@ -14
The throttle group support use a cooperative round robin scheduling algorithm.
The principle of the algorithm are simple:
- Each BDS of the group is used as a token in a circular way.
- The active BDS compute if a wait must be done and arm the right timer.
- If a wait must be done the token timer
When the runstate changes back to running, we definitely need to flush
queues to get packets flowing again.
Here we implement this in the net layer:
(1) add a member 'VMChangeStateEntry *vmstate' to struct NICState,
Which will listen for VM runstate changes.
(2) Register a handler function for VMs
For all NICs(except virtio-net) emulated by qemu,
Such as e1000, rtl8139, pcnet and ne2k_pci,
Qemu can still receive packets when VM is not running.
If this happened in *migration's* last PAUSE VM stage,
The new dirty RAM related to the packets will be missed,
And this will lead serious network fa
We will check vm-running state in the generic net layer.
Also we have to flush queues in nic_vmstate_change_handler() when vm state
changes to run. The check here will prevent the flushing process, because
we will check the return value of virtio_net_can_receive in
nic_vmstate_change_handler, When
On 2014/8/13 19:50, Michael S. Tsirkin wrote:
On Wed, Aug 13, 2014 at 07:21:57PM +0800, zhanghailiang wrote:
If we configure qemu with realtime-mlock-on and memory-node-bind at the same
time,
Qemu will fail to start, and mbind() fails with message "Input/output error".
> From man page:
int mbi
From: Gonglei
two duplicate destport description.
s/destport/srcport/, s/destination/source/
Signed-off-by: Gonglei
---
qemu-options.hx | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/qemu-options.hx b/qemu-options.hx
index 96516c1..ebdffeb 100644
--- a/qemu-options.hx
+++
Applied to -trivial, thank you!
/mjt
101 - 162 of 162 matches
Mail list logo
