Just a couple of minor comments to help note where allocated
buffers are freed, and a typo fix.
Signed-off-by: Jeff Cody jc...@redhat.com
---
block/vhdx.c | 6 --
block/vhdx.h | 6 +++---
2 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/block/vhdx.c b/block/vhdx.c
index
Allow tracking of first file write in the VHDX image, as well as
the ability to update the GUID in the header. This is in preparation
for log support.
Signed-off-by: Jeff Cody jc...@redhat.com
---
block/vhdx.c | 30 --
block/vhdx.h | 6 ++
2 files changed, 30
In preparation for VHDX log support, move these structures to the
header.
Signed-off-by: Jeff Cody jc...@redhat.com
---
block/vhdx.c | 52
block/vhdx.h | 48
2 files changed, 48 insertions(+),
This adds some magic number defines, and internal structure definitions
for VHDX log replay support. The struct VHDXLogEntries does not reflect
an on-disk data structure, and thus does not need to be packed.
Some minor code style fixes are applied as well.
Signed-off-by: Jeff Cody
This adds support for VHDX v0 logs, as specified in Microsoft's
VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
The following support is added:
* Log parsing, and validation - validate that an existing log
is correct.
* Log search - search
This adds support for writing to the VHDX log.
For spec details, see VHDX Specification Format v1.00:
https://www.microsoft.com/en-us/download/details.aspx?id=34750
There are a few limitations to this log support:
1.) There is no caching yet
2.) The log is flushed after each entry
The primary
This moves the endian translation functions out from the vhdx.c source,
into a separate source file. In addition to the previously defined
endian functions, new endian translation functions for log support are
added as well.
Signed-off-by: Jeff Cody jc...@redhat.com
---
block/Makefile.objs | 2
This is preperation for vhdx_create(). The ability to write headers,
and calculate the number of BAT entries will be needed within the
create() functions, so move this relevant code into helper functions.
Signed-off-by: Jeff Cody jc...@redhat.com
---
block/vhdx.c | 121
This adds support for VHDX image creation, for images of type Fixed
and Dynamic. Differencing types (i.e., VHDX images with backing
files) are currently not supported.
Options for image creation include:
* log size:
The size of the journaling log for VHDX. Minimum is 1MB,
On Wed, Oct 30, 2013 at 12:29:16PM -0200, Eduardo Habkost wrote:
On Wed, Oct 30, 2013 at 04:18:16PM +0200, Michael S. Tsirkin wrote:
On Wed, Oct 30, 2013 at 01:56:40PM +0100, arm...@redhat.com wrote:
From: Markus Armbruster arm...@redhat.com
Currently, we get SeaBIOS defaults:
In preparation for vhdx_create(), move more endian translation
functions out to vhdx-endian.c.
Signed-off-by: Jeff Cody jc...@redhat.com
---
block/vhdx-endian.c | 75 +
block/vhdx.c| 20 +++---
block/vhdx.h| 9 ++-
This tests the replay of a data sector in a VHDX image file.
The image file is a 10G dynamic image, with 4MB block size. The
image was created with qemu-img, and the log left unplayed by
modification of the vhdx image format driver.
It was verified under both QEMU and Hyper-V that the image
Bit shifting can be fun, but in this case it was unnecessary. The
upper 44 bits of the 64-bit BAT entry is specifies the File Offset,
so we shifted the bits to get access to the value.
However, per the spec the value is in MB. So we dutifully shifted back
to the left by 20 bits, to convert to a
Marcel Apfelbaum marce...@redhat.com writes:
On Wed, 2013-10-30 at 13:15 +0100, Markus Armbruster wrote:
Marcel Apfelbaum marce...@redhat.com writes:
On Tue, 2013-10-29 at 17:08 +0100, arm...@redhat.com wrote:
From: Markus Armbruster arm...@redhat.com
Such devices have always been
This removes the IMGFMT_GENERIC blocker for read-only, so existing
iotests run read/write tests for vhdx images created by qemu-img (e.g.
tests 001, 002, 003).
In addition, this updates the sample image test for the Hyper-V
created image, to verify we can write it as well.
Signed-off-by: Jeff
VHDXPage83Data and VHDXParentLocatorHeader both incorrectly had their
MSGUID fields set as arrays of 16. This is incorrect (it stems from
an early version where those fields were uint_8 arrays). Those fields
were, up to this patch, unused.
Also, there were a couple of typos and incorrect
The non-global option output is suppresed in _make_test_img() for
output verification in the 0?? tests. This adds suppression for
the vhdx-unique options as well. This allows check -vhdx to run
successfully.
Signed-off-by: Jeff Cody jc...@redhat.com
---
tests/qemu-iotests/common.rc | 5 -
Michael S. Tsirkin m...@redhat.com writes:
On Wed, Oct 30, 2013 at 01:56:40PM +0100, arm...@redhat.com wrote:
From: Markus Armbruster arm...@redhat.com
Currently, we get SeaBIOS defaults: manufacturer Bochs, product Bochs,
no version. Best SeaBIOS can do, but we can provide better
This adds support for writing to VHDX image files, using coroutines.
Writes into the BAT table goes through the VHDX log. Currently, BAT
table writes occur when expanding a dynamic VHDX file, and allocating a
new BAT entry.
Signed-off-by: Jeff Cody jc...@redhat.com
---
block/vhdx.c | 212
I came across this little tests/Makefile annoyance:
If you modify QEMU code and then run make check it will not rebuild QEMU.
This can be confusing during development when you expect changing the
code and rerunning the tests to pass :).
I played with tests/Makefile but was unable to add the
Michael S. Tsirkin m...@redhat.com writes:
On Wed, Oct 30, 2013 at 12:29:16PM -0200, Eduardo Habkost wrote:
On Wed, Oct 30, 2013 at 04:18:16PM +0200, Michael S. Tsirkin wrote:
On Wed, Oct 30, 2013 at 01:56:40PM +0100, arm...@redhat.com wrote:
From: Markus Armbruster arm...@redhat.com
Regions in the image file cannot overlap - the log, region tables,
and metdata must all be unique and non-overlapping.
This adds region checking by means of a QLIST; there can be a variable
number of regions and metadata (there may be metadata or region tables
that we do not recognize / know
Signed-off-by: Jeff Cody jc...@redhat.com
---
block/vhdx.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/block/vhdx.c b/block/vhdx.c
index 241703a..3f06ce3 100644
--- a/block/vhdx.c
+++ b/block/vhdx.c
@@ -778,6 +778,17 @@ exit:
}
+static void
On Wed, 30 Oct 2013 15:33:35 +0100
Gerd Hoffmann kra...@redhat.com wrote:
Hi,
I don't think we can predict the future.
It seems just as likely that BIOS will need to drive the
new hardware so it will not be enough to have start pci here.
In particular, non-contiguous hotpluggable
Am 30.10.2013 14:54, schrieb Stefan Hajnoczi:
v3:
* I lost track of this patch, now I'm pushing it again
Part of this series is in a pending qom-next pull of mine (on a
different base), which Anthony didn't merge due to some questions or
problems, and during Hackathon he disappeared and so far
Il 30/10/2013 16:07, Stefan Hajnoczi ha scritto:
I came across this little tests/Makefile annoyance:
If you modify QEMU code and then run make check it will not rebuild QEMU.
This can be confusing during development when you expect changing the
code and rerunning the tests to pass :).
I
Am 30.10.2013 16:07, schrieb Stefan Hajnoczi:
I came across this little tests/Makefile annoyance:
If you modify QEMU code and then run make check it will not rebuild QEMU.
This can be confusing during development when you expect changing the
code and rerunning the tests to pass :).
I
From: Markus Armbruster arm...@redhat.com
In an ideal world, machines can be built by wiring devices together
with configuration, not code. Unfortunately, that's not the world we
live in right now. We still have quite a few devices that need to be
wired up by code. If you try to device_add
From: Markus Armbruster arm...@redhat.com
Signed-off-by: Markus Armbruster arm...@redhat.com
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
---
qom/cpu.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/qom/cpu.c b/qom/cpu.c
index 09c15e6..6e0d54e 100644
---
From: Markus Armbruster arm...@redhat.com
device_add plugs devices into suitable bus. For real buses, that
actually connects the device. For sysbus, the connections need to be
made separately, and device_add can't do that. The device would be
left unconnected, and could not possibly work.
From: Markus Armbruster arm...@redhat.com
In an ideal world, machines can be built by wiring devices together
with configuration, not code. Unfortunately, that's not the world we
live in right now. We still have quite a few devices that need to be
wired up by code. If you try to device_add
From: Markus Armbruster arm...@redhat.com
Signed-off-by: Markus Armbruster arm...@redhat.com
Reviewed-by: Peter Maydell peter.mayd...@linaro.org
---
hw/intc/apic_common.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/hw/intc/apic_common.c b/hw/intc/apic_common.c
index
From: Markus Armbruster arm...@redhat.com
Many PCI host bridges consist of a sysbus device and a PCI device.
You need both for the thing to work. Arguably, these bridges should
be modelled as a single, composite devices instead of pairs of
seemingly independent devices you can only use together,
From: Markus Armbruster arm...@redhat.com
An ICH9 southbridge contains several PCI devices, some of them with
multiple functions. We model each function as a separate qdev. Two
of them need some special wiring set up in pc_q35_init() to work: the
LPC controller at 00:1f.0, and the SMBus
From: Markus Armbruster arm...@redhat.com
Such devices have always been unavailable and omitted from the list of
available devices shown by device_add help. Until commit 18b6dad
silently broke the former, setting up nasty traps for unwary users,
like this one:
$ qemu-system-x86_64
From: Markus Armbruster arm...@redhat.com
A VT82C686B southbridge has multiple functions. We model each
function as a separate qdev. One of them need some special wiring set
up in mips_fulong2e_init() to work: the ISA bridge at 05.0.
The IDE controller at 05.1 (via-ide) has always had
From: Markus Armbruster arm...@redhat.com
A PIIX3/PIIX4 southbridge has multiple functions. We model each
function as a separate qdev. Two of them need some special wiring set
up in pc_init1() or mips_malta_init() to work: the ISA bridge at 01.0,
and the SMBus controller at 01.3.
The IDE
From: Markus Armbruster arm...@redhat.com
Drop it when there's no obvious reason why device_add could not work.
Else keep and document why.
* isa-fdc: drop
* i8042: drop, even though its I/O base is hardcoded (because you
could conceivably still add one to a board that has none), and even
Il 30/10/2013 15:40, Giridhar Maruthy ha scritto:
Hi All,
I tried to measure the network performance of guest (mach-virt) with
virtio-net on an ARM host platform (Samsung exynos). The qemu version
is 1.6.50.
I found that with 1GbE NIC on the host, the host iperf gave a speed of
On Tue, 29 Oct 2013 19:38:44 -0200
Marcelo Tosatti mtosa...@redhat.com wrote:
On Tue, Oct 29, 2013 at 07:18:49PM +0100, Igor Mammedov wrote:
Otherwise 1GB TLBs cannot be cached for the range.
This fails to back non-1GB-aligned gpas, but 2MB aligned, with 2MB large
pages.
With current
Il 25/10/2013 15:53, jacek burghardt ha scritto:
Is there a patch for qemu git master that pre init e1000 so I can get
rid off unpluged network cable message ? I know there is patch but is is
for older version of qemu and it seeem that it no longer functions and
does not apply fully as code
Il 29/10/2013 19:30, Kevin Wolf ha scritto:
Am 28.10.2013 um 17:43 hat Paolo Bonzini geschrieben:
Hi all,
this is some cleanup to the IDE code that I started long ago
and picked up again on my flight back from KVM Forum...
The patches clean up the callbacks to prepare for implementing
Am 18.10.2013 um 05:12 hat Fam Zheng geschrieben:
Implement .bdrv_get_specific_info to return the extent information.
Signed-off-by: Fam Zheng f...@redhat.com
---
block/vmdk.c | 64
+-
qapi-schema.json | 24
On 30 October 2013 16:52, Paolo Bonzini pbonz...@redhat.com wrote:
Il 25/10/2013 15:53, jacek burghardt ha scritto:
Is there a patch for qemu git master that pre init e1000 so I can get
rid off unpluged network cable message ? I know there is patch but is is
for older version of qemu and it
The function of this patch is initialize emulated network card and pass
data just like Mac firmware
On 10/29/2013 12:04 PM, Sebastian Macke wrote:
The carry and overflag and the instructions l.addc and l.addic
are never used in the toolchain. Linux and gcc compiled software
don't need them.
Really? That's quite surprising.
To speed up the emulation a cpu was added which
neglects the
Quoting Joe Doe (joe.doe.launch...@mailinator.com):
Public bug reported:
sudo apt-get install kvm virt-manager removed postgresql-9.2 from my system.
Could you please show your OS release and from where and how you
installed postgresql-9.2? I'd like to try and reproduce, but
don't see any
Public bug reported:
I'm trying to run the following:
qemu-system-mips64el --machine magnum [...]
The qemu binaries from (k)ubuntu work fine. info version shows
1.5.0 (Debian 1.5.0+dfsg-3ubuntu5)
When I try qemu 1.6.1 (compiled from source .tar.bz2), however, qemu
only shows a black screen when
Public bug reported:
sudo apt-get install kvm virt-manager removed postgresql-9.2 from my system.
Furthermore, it seem impossible for me to run postgresql and qemu at the same
time.
Starting one, kills the other.
** Affects: qemu
Importance: Undecided
Status: New
** Tags: kvm
You have been subscribed to a public bug:
On booting the cloud image using qemu/kvm fails with the following
error:
Cloud-init v. 0.7.3 running 'init' at Thu, 03 Oct 2013 16:45:21 +. Up
360.78 seconds.
ci-info: +Net device info+
ci-info:
** Summary changed:
- [cloud-init][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
+ [KVM/QEMU][ARM][SAUCY] fails to boot cloud-image due to host kvm fail
** Project changed: cloud-init = qemu
--
You received this bug notification because you are a member of qemu-
devel-ml, which is
Ubuntu kernels use CONFIG_STRICT_MEM which prevents access to physical
mem other than BIOS and PCI region so that X or dmidecode tools can read
this info. On a native ARM system since there is no BIOS (yet) this
causes mmap() of /dev/mem to return a -1. But with KVM/QEMU emulating
ARM (mach virt)
On 10/29/2013 12:04 PM, Sebastian Macke wrote:
{
int lab = gen_new_label();
-dc-btaken = tcg_temp_local_new();
-tcg_gen_movi_tl(jmp_pc, dc-pc+8);
-tcg_gen_movi_tl(dc-btaken, 0);
+tcg_gen_movi_tl(jmp_pc, 0);
Il 30/10/2013 18:29, Peter Maydell ha scritto:
This looks odd -- you seem to be modifying val but then not
using the modified value before we reach the end of the function.
}
static void
@@ -445,8 +450,9 @@ set_mdic(E1000State *s, int index, uint32_t val)
} else {
On Wed, Oct 30, 2013 at 10:48:13AM +0200, Gleb Natapov wrote:
On Tue, Oct 29, 2013 at 07:21:59PM -0200, Marcelo Tosatti wrote:
Could add a warning to memory API: if memory region is larger than 1GB
and RAM is 1GB backed, and not properly aligned, warn.
Perhaps it would be better do
On Wed, Oct 30, 2013 at 05:49:49PM +0100, Igor Mammedov wrote:
On Tue, 29 Oct 2013 19:38:44 -0200
Marcelo Tosatti mtosa...@redhat.com wrote:
On Tue, Oct 29, 2013 at 07:18:49PM +0100, Igor Mammedov wrote:
Otherwise 1GB TLBs cannot be cached for the range.
This fails to back
On Wed, Oct 30, 2013 at 04:51:29PM -0200, Marcelo Tosatti wrote:
On Wed, Oct 30, 2013 at 05:49:49PM +0100, Igor Mammedov wrote:
On Tue, 29 Oct 2013 19:38:44 -0200
Marcelo Tosatti mtosa...@redhat.com wrote:
On Tue, Oct 29, 2013 at 07:18:49PM +0100, Igor Mammedov wrote:
Otherwise 1GB
On 30/10/2013 11:33 AM, Richard Henderson wrote:
On 10/29/2013 12:04 PM, Sebastian Macke wrote:
{
int lab = gen_new_label();
-dc-btaken = tcg_temp_local_new();
-tcg_gen_movi_tl(jmp_pc, dc-pc+8);
-tcg_gen_movi_tl(dc-btaken, 0);
+
On Wed, Oct 30, 2013 at 03:48:55PM +0100, Markus Armbruster wrote:
Michael S. Tsirkin m...@redhat.com writes:
On Wed, Oct 30, 2013 at 01:56:40PM +0100, arm...@redhat.com wrote:
From: Markus Armbruster arm...@redhat.com
Currently, we get SeaBIOS defaults: manufacturer Bochs, product
On Wed, Oct 30, 2013 at 04:18:37PM +0100, Markus Armbruster wrote:
Michael S. Tsirkin m...@redhat.com writes:
On Wed, Oct 30, 2013 at 12:29:16PM -0200, Eduardo Habkost wrote:
On Wed, Oct 30, 2013 at 04:18:16PM +0200, Michael S. Tsirkin wrote:
On Wed, Oct 30, 2013 at 01:56:40PM +0100,
On 30/10/2013 11:14 AM, Richard Henderson wrote:
On 10/29/2013 12:04 PM, Sebastian Macke wrote:
The carry and overflag and the instructions l.addc and l.addic
are never used in the toolchain. Linux and gcc compiled software
don't need them.
Really? That's quite surprising.
Yes, Really. :)
On 10/30/2013 07:49 AM, Markus Armbruster wrote:
The first proposal is to add another parameter, say id. Users can
then refer either to an arbitrary BDS by id, or (for backward
compatibility) to the root BDS by device. When the code sees
device, it'll look up the BB, then fetch its root
On Wed, Oct 30, 2013 at 05:49:49PM +0100, Igor Mammedov wrote:
On Tue, 29 Oct 2013 19:38:44 -0200
Marcelo Tosatti mtosa...@redhat.com wrote:
On Tue, Oct 29, 2013 at 07:18:49PM +0100, Igor Mammedov wrote:
Otherwise 1GB TLBs cannot be cached for the range.
This fails to back
On 10/30/2013 12:22 PM, Sebastian Macke wrote:
I would like to implement lazy flags or at least change the big bunch of code
which is there right now.
But for this patchset I want to keep it that way and change the whole flag
handling in one of the next patches.
If you don't want to modernize
On 10/30/2013 12:07 PM, Sebastian Macke wrote:
Correct. The movcond function can be used here. I will change that.
But I didn't know that it exists because it is not written in the document
http://wiki.qemu.org/Documentation/TCG/frontend-ops
I had no idea that existed.
The canonical
At Tue, 29 Oct 2013 16:25:52 +0800,
Liu Yuan wrote:
Sheepdog support two kinds of redundancy, full replication and erasure coding.
# create a fully replicated vdi with x copies
-o redundancy=x (1 = x = SD_MAX_COPIES)
# create a erasure coded vdi with x data strips and y parity strips
On 10/30/2013 12:07 PM, Sebastian Macke wrote:
case JUMP_BRANCH:
{
int l1 = gen_new_label();
-tcg_gen_brcondi_tl(TCG_COND_NE, dc-btaken, 0, l1);
+tcg_gen_brcondi_tl(TCG_COND_NE, jmp_pc, 0, l1);
gen_goto_tb(dc, 1, dc-pc);
On Wed, 30 Oct 2013 16:51:29 -0200
Marcelo Tosatti mtosa...@redhat.com wrote:
On Wed, Oct 30, 2013 at 05:49:49PM +0100, Igor Mammedov wrote:
On Tue, 29 Oct 2013 19:38:44 -0200
Marcelo Tosatti mtosa...@redhat.com wrote:
On Tue, Oct 29, 2013 at 07:18:49PM +0100, Igor Mammedov wrote:
Michael S. Tsirkin m...@redhat.com writes:
On Wed, Oct 30, 2013 at 04:18:37PM +0100, Markus Armbruster wrote:
Michael S. Tsirkin m...@redhat.com writes:
On Wed, Oct 30, 2013 at 12:29:16PM -0200, Eduardo Habkost wrote:
On Wed, Oct 30, 2013 at 04:18:16PM +0200, Michael S. Tsirkin wrote:
Il 30/10/2013 20:31, Marcelo Tosatti ha scritto:
I do not believe that unability to deal with memory aliases on the
future ability to create machine from configuration is strong enough
reason to justify pushing mixed 1GB and 2MB pages size to the user (1GB
pages are allocated on the host
On 30/10/2013 12:47 PM, Richard Henderson wrote:
On 10/30/2013 12:07 PM, Sebastian Macke wrote:
case JUMP_BRANCH:
{
int l1 = gen_new_label();
-tcg_gen_brcondi_tl(TCG_COND_NE, dc-btaken, 0, l1);
+tcg_gen_brcondi_tl(TCG_COND_NE, jmp_pc, 0,
Hi Stefan, please have a Look at v7 of this series. Hopefully the final one.
Thx,
Am 30.10.2013 um 09:28 schrieb Stefan Hajnoczi stefa...@redhat.com:
On Fri, Oct 18, 2013 at 09:10:43PM +0200, Peter Lieven wrote:
Am 18.10.2013 um 15:50 schrieb Paolo Bonzini pbonz...@redhat.com:
Il
Some targets use a stat64 structure for the stat64 syscall while others
use a stat structure. SPARC64 used the wrong kind.
Instead of extending the conditional compilation in syscall.c, now a
macro TARGET_HAS_STRUCT_STAT64 is defined whenever a target has a
target_stat64.
Signed-off-by: Stefan
Did some testing: if one pauses the vms that run windows before suspending
ubuntu no high cpu usage is there once the host and windows vms are resumed.
for me it's workable then in ubuntu by using a suspend / resume script with
power manaager. I put this in /etc/pm/sleep.d (and make it
On 10/30/2013 02:08 PM, Sebastian Macke wrote:
Do you have a publicly accessible tree with all your patches applied?
I'd like to re-read the logic in the proper context.
After you are the second who demanded it:
https://github.com/s-macke/qemu/tree/or32-optimize
Ok, the logic as written is
On Wed, Oct 30, 2013 at 09:22:38PM +0100, Markus Armbruster wrote:
Michael S. Tsirkin m...@redhat.com writes:
On Wed, Oct 30, 2013 at 04:18:37PM +0100, Markus Armbruster wrote:
Michael S. Tsirkin m...@redhat.com writes:
On Wed, Oct 30, 2013 at 12:29:16PM -0200, Eduardo Habkost wrote:
On Wed, Oct 16, 2013 at 10:03:37PM +0300, Michael S. Tsirkin wrote:
This simply imports kvm-unittest git into qemu source tree.
We can next work on making make check run it
automatically.
Squashed 'kvm-unittest/' content from commit 2bc0e29
git-subtree-dir: kvm-unittest
On Wed, Oct 30, 2013 at 08:56:17PM +0100, Igor Mammedov wrote:
On Wed, 30 Oct 2013 16:51:29 -0200
Marcelo Tosatti mtosa...@redhat.com wrote:
On Wed, Oct 30, 2013 at 05:49:49PM +0100, Igor Mammedov wrote:
On Tue, 29 Oct 2013 19:38:44 -0200
Marcelo Tosatti mtosa...@redhat.com wrote:
I wonder if anyone can post reworked patch to latest qemu
On Fri, Oct 25, 2013 at 8:27 AM, jacek burghardt
jaceksburgha...@gmail.comwrote:
https://github.com/saucelabs/mac-osx-on-kvm/blob/master/e1000-mac-hacks.patch
-} else
-s-phy_reg[addr] = data;
+} else {
Il 31/10/2013 00:54, jacek burghardt ha scritto:
I wonder if anyone can post reworked patch to latest qemu
That's what I did 5 hours ago, though what I did was actually to look at
the bits affected by the patch and reimplement them based on the e1000
hardware spec. Can you test the second
I am in process of recompiling qemu right now
I came up with this patch is this correct
diff -Naur qemu/hw/net/e1000.c qemu-a/hw/net/e1000.c
--- qemu/hw/net/e1000.c 2013-10-27 15:36:05.496526538 -0600
+++ qemu-a/hw/net/e1000.c 2013-10-30 18:09:03.101711694 -0600
@@ -203,6 +203,12 @@
i got this error
hw/net/e1000.c: In function 'set_phy_ctrl':
hw/net/e1000.c:209:10: warning: implicit declaration of function 'set_ics'
[-Wimplicit-function-declaration]
set_ics(s, 0, E1000_ICR_LSC);
^
hw/net/e1000.c:209:10: warning: nested extern declaration of 'set_ics'
Il 31/10/2013 01:21, jacek burghardt ha scritto:
I am in process of recompiling qemu right now
I came up with this patch is this correct
diff -Naur qemu/hw/net/e1000.c qemu-a/hw/net/e1000.c
--- qemu/hw/net/e1000.c 2013-10-27 15:36:05.496526538 -0600
+++ qemu-a/hw/net/e1000.c 2013-10-30
On 27.09.2013, at 11:25, Richard Henderson r...@twiddle.net wrote:
On 09/26/2013 05:48 PM, Alexander Graf wrote:
This patch adds emulation support for the orr instruction.
Signed-off-by: Alexander Graf ag...@suse.de
---
target-arm/helper-a64.c| 28 +++
target-arm/helper-a64.h
On 30/10/2013 3:02 PM, Richard Henderson wrote:
On 10/30/2013 02:08 PM, Sebastian Macke wrote:
Do you have a publicly accessible tree with all your patches applied?
I'd like to re-read the logic in the proper context.
After you are the second who demanded it:
I will try that the original patch:
--- qemu-kvm-0.12.5/hw/e1000.c.vanilla 2011-02-19 12:28:38.0 +
+++ qemu-kvm-0.12.5/hw/e1000.c 2011-02-21 14:11:33.0 +
@@ -199,6 +202,8 @@
{
/* RST is self clearing */
s-mac_reg[CTRL] = val ~E1000_CTRL_RST;
+if (val
I got this error
hw/net/e1000.c: In function 'set_phy_ctrl':
hw/net/e1000.c:209:10: warning: implicit declaration of function 'set_ics'
[-Wimplicit-function-declaration]
set_ics(s, 0, E1000_ICR_LSC);
^
hw/net/e1000.c:209:10: warning: nested extern declaration of 'set_ics'
On Wed, 10/30 18:27, Kevin Wolf wrote:
Am 18.10.2013 um 05:12 hat Fam Zheng geschrieben:
Implement .bdrv_get_specific_info to return the extent information.
Signed-off-by: Fam Zheng f...@redhat.com
---
block/vmdk.c | 64
+-
On 31 October 2013 00:29, Alexander Graf ag...@suse.de wrote:
On 27.09.2013, at 11:25, Richard Henderson r...@twiddle.net wrote:
Why are you not using the same split apart bits as A32?
There is an architecturally defined register that specifies
what pstate looks like and IIRC that includes
Reviewed-by: Eric Blake ebl...@redhat.com
Signed-off-by: Fam Zheng f...@redhat.com
---
qapi-schema.json | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/qapi-schema.json b/qapi-schema.json
index 60f3fd1..add97e2 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -256,6
The new information looks like:
image: /tmp/foo.vmdk
file format: vmdk
virtual size: 100G (107374182400 bytes)
disk size: 4.0K
Format specific information:
cid: 0
create_type: twoGbMaxExtentFlat
parent cid: 0
extents:
[0]:
Implement .bdrv_get_specific_info to return the extent information.
Signed-off-by: Fam Zheng f...@redhat.com
---
v5: Changed 3 lines:
- Save cid in vmdk_open. (Kevin)
- Report parent_cid in vmdk_get_specific_info.
- Rename create_type to create-type in qapi-schema.json.
This patch suspends the test image IO before starting block stream job
so that it doesn't complete before we could check the status.
Signed-off-by: Fam Zheng f...@redhat.com
---
tests/qemu-iotests/030| 10 ++
tests/qemu-iotests/iotests.py | 5 -
2 files changed, 10
On Thu, Oct 31, 2013 at 04:41:05AM +0900, MORITA Kazutaka wrote:
At Tue, 29 Oct 2013 16:25:52 +0800,
Liu Yuan wrote:
Sheepdog support two kinds of redundancy, full replication and erasure
coding.
# create a fully replicated vdi with x copies
-o redundancy=x (1 = x =
On 30 October 2013 22:12, Paolo Bonzini pbonz...@redhat.com wrote:
Il 30/10/2013 15:40, Giridhar Maruthy ha scritto:
Hi All,
I tried to measure the network performance of guest (mach-virt) with
virtio-net on an ARM host platform (Samsung exynos). The qemu version
is 1.6.50.
I found that
v3:
- rework is_numeric
v2:
- fix a typo in comment and commit log
This patch set add one sheepdog specific option for qemu-img to control
redundancy.
This patch set is on top of Kevin's block tree.
Liu Yuan (2):
sheepdog: refactor do_sd_create()
sheepdog: support user-defined
We can actually use BDRVSheepdogState *s to pass most of the parameters.
Cc: Kevin Wolf kw...@redhat.com
Cc: Stefan Hajnoczi stefa...@redhat.com
Reviewed-by: Benoit Canet ben...@irqsave.net
Signed-off-by: Liu Yuan namei.u...@gmail.com
---
block/sheepdog.c | 37
Sheepdog support two kinds of redundancy, full replication and erasure coding.
# create a fully replicated vdi with x copies
-o redundancy=x (1 = x = SD_MAX_COPIES)
# create a erasure coded vdi with x data strips and y parity strips
-o redundancy=x:y (x must be one of {2,4,8,16} and 1 = y
Hi,
Does QEMU support MIPS smp 2 malta board?
$ qemu-system-mipsel -M malta -kernel vmlinux -initrd ramfs.cpio.gz \
-append console=ttyS0 root=/dev/ram0 maxcpus=2 -nographic -s \
-smp 2
Linux version 3.11.0-rc6 (yrtan@localhost.localdomain) (gcc version
4.7.2 (Sourcery CodeBench Lite
101 - 200 of 208 matches
Mail list logo
