** Changed in: qemu
Status: Confirmed => Fix Committed
** Changed in: qemu
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1248854
Title:
The gues
kvm.git + qemu.git: ede58222_5c5432e7
test on Romley_EP, Ivytown_EP, create guest with parameter "-no-acpi", the
guest boot up fine.
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
GlusterFS supports creation of zero-filled file on GlusterFS volume
by means of an API called glfs_zerofill(). Use this API from QEMU to
create an image that is filled with zeroes by using the preallocation
option of qemu-img.
qemu-img create gluster://server/volume/image -o preallocation=full 10G
Support .bdrv_co_write_zeroes() from gluster driver by using GlusterFS API
glfs_zerofill() that off-loads the writing of zeroes to GlusterFS server.
Signed-off-by: Bharata B Rao
---
block/gluster.c | 101
configure | 8 +
2 fil
Convert the read, write, flush and discard implementations from aio-based
ones to coroutine based ones.
Signed-off-by: Bharata B Rao
---
block/gluster.c | 168 +---
1 file changed, 63 insertions(+), 105 deletions(-)
diff --git a/block/gluster.
Hi,
This series is about converting all the bdrv_aio* implementations in gluster
driver to coroutine based implementations. Read, write, flush and discard
routines are converted.
This also adds support for .bdrv_co_write_zeroes() in gluster and provides
a new preallocation option with qemu-img (-
于 2013/11/19 19:29, Kevin Wolf 写道:
Am 10.11.2013 um 23:03 hat Wenchao Xia geschrieben:
Signed-off-by: Wenchao Xia
---
tests/qemu-iotests/058 | 102
tests/qemu-iotests/058.out | 32 ++
tests/qemu-iotests/check |1 +
tests
Am 22.11.2013 07:39, schrieb Fam Zheng:
> Signed-off-by: Fam Zheng
> ---
> .gitignore | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/.gitignore b/.gitignore
> index 5584b5f..1c9d63d 100644
> --- a/.gitignore
> +++ b/.gitignore
> @@ -3,6 +3,7 @@ config-all-devices.*
> config-all-disas.*
Am 21.11.2013 09:40, schrieb Stefan Hajnoczi:
> Excellent, thanks! The latest buildbot has compiled successfully:
> http://buildbot.b1-systems.de/qemu/builders/default_mingw32/builds/784
>
> It's now hitting a make check failure unrelated to VSS.
>
> Thanks,
> Stefan
'make check' for MinGW cross
Signed-off-by: Fam Zheng
---
.gitignore | 1 +
1 file changed, 1 insertion(+)
diff --git a/.gitignore b/.gitignore
index 5584b5f..1c9d63d 100644
--- a/.gitignore
+++ b/.gitignore
@@ -3,6 +3,7 @@ config-all-devices.*
config-all-disas.*
config-host.*
config-target.*
+config.status
trace/genera
On 2013年11月20日 10:32, Ian Main wrote:
On Thu, Oct 17, 2013 at 01:36:41PM +0800, Fam Zheng wrote:
This series adds for point-in-time snapshot NBD exporting based on
blockdev-backup (variant of drive-backup with existing device as target).
In general this seems to work great. I did a bunch of t
Signed-off-by: Fam Zheng
---
block.c | 37 -
include/block/block_int.h | 3 +++
2 files changed, 35 insertions(+), 5 deletions(-)
diff --git a/block.c b/block.c
index 3bf4c8a..a5da656 100644
--- a/block.c
+++ b/block.c
@@ -1166,11 +1166,33 @
Drive backup is a read only operation on source bs. We want to allow
this specific case to enable image-fleecing. Note that when
image-fleecing job starts, the job still add its blocker to source bs,
and any other operation on it will be blocked by that.
Signed-off-by: Fam Zheng
---
block.c | 2
Before operate on a BlockDriverState, respective types are checked
against bs->op_blockers and it will error out if there's a blocker.
Signed-off-by: Fam Zheng
---
blockdev-nbd.c | 4
blockdev.c | 25 +
2 files changed, 29 insertions(+)
diff --git a/blockdev-nb
Similar to drive-backup, but this command uses a device id as target
instead of creating/opening an image file.
Also add blocker on target bs, since the target is also a named device
now.
Signed-off-by: Fam Zheng
---
block/backup.c | 22 ++
blockdev.c | 46 ++
This drops BlockDriverState.in_use with op_blockers:
- Call bdrv_op_block_all in place of bdrv_set_in_use(bs, 1).
- Call bdrv_op_unblock_all in place of bdrv_set_in_use(bs, 0).
- Check bdrv_op_is_blocked() in place of bdrv_in_use(bs).
The specific types are used, e.g. in place of startin
BlockDriverState.op_blockers is an array of list with BLOCK_OP_TYPE_MAX
elements. Each list is a list of blockers of an operation type
(BlockOpType), that marks this BDS is currently blocked for certain type
of operation with reason errors stored in the list. The rule of usage
is:
* BDS user who
This series adds for point-in-time snapshot NBD exporting based on
blockdev-backup (variant of drive-backup with existing device as target).
We get a thin point-in-time snapshot by COW mechanism of drive-backup, and
export it through built in NBD server. The steps are as below:
1. (SHELL) qemu-i
This adds the enum of all the operations that can be taken on a block
device.
Signed-off-by: Fam Zheng
---
qapi-schema.json | 25 +
1 file changed, 25 insertions(+)
diff --git a/qapi-schema.json b/qapi-schema.json
index 83fa485..4656e8c 100644
--- a/qapi-schema.json
+++
libnuma choosed 128 for MAX_NODES, so we follow libnuma here.
Signed-off-by: Wanlong Gao
---
include/sysemu/sysemu.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/sysemu/sysemu.h b/include/sysemu/sysemu.h
index 291aa6a..807619e 100644
--- a/include/sysemu/sysemu.h
+
Set the guest numa nodes memory policies using the mbind(2)
system call node by node.
After this patch, we are able to set guest nodes memory policies
through the QEMU options, this arms to solve the guest cross
nodes memory access performance issue.
And as you all know, if PCI-passthrough is used,
Signed-off-by: Wanlong Gao
---
hw/i386/pc.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/hw/i386/pc.c b/hw/i386/pc.c
index 50ed4cc..74c1f16 100644
--- a/hw/i386/pc.c
+++ b/hw/i386/pc.c
@@ -1072,8 +1072,12 @@ PcGuestInfo *pc_guest_info_init(ram_addr_t
below_4g_mem_s
Signed-off-by: Wanlong Gao
---
Makefile.target | 2 +-
cpus.c | 14
include/sysemu/cpus.h | 1 -
include/sysemu/sysemu.h | 3 +
numa.c | 182
vl.c| 139 +---
Reviewed-by: Luiz Capitulino
Signed-off-by: Wanlong Gao
---
hmp.c | 57 +
hmp.h | 1 +
monitor.c | 21 +
3 files changed, 59 insertions(+), 20 deletions(-)
diff --git a/hmp.c b/hmp.c
index 32ee285..d6dedd2 1006
Sorry, please ignore this patch.
Thanks,
Wanlong Gao
> Signed-off-by: Wanlong Gao
> ---
> hw/i386/pc.c | 8 ++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/hw/i386/pc.c b/hw/i386/pc.c
> index 50ed4cc..74c1f16 100644
> --- a/hw/i386/pc.c
> +++ b/hw/i386/pc.c
> @@ -10
If the total number of the assigned numa nodes memory is not
equal to the assigned ram size, it will write the wrong data
to ACPI talb, then the guest will ignore the wrong ACPI table
and recognize all memory to one node. It's buggy, we should
check it to ensure that we write the right data to ACPI
Add qmp command query-numa to show guest NUMA information.
Reviewed-by: Luiz Capitulino
Signed-off-by: Wanlong Gao
---
numa.c | 66
qapi-schema.json | 36 +++
qmp-commands.hx | 49 +++
Signed-off-by: Wanlong Gao
---
include/sysemu/sysemu.h | 3 +-
numa.c | 148 +++-
qapi-schema.json| 30 ++
vl.c| 11 +++-
4 files changed, 114 insertions(+), 78 deletions(-)
diff --git a/include/
Add the numa_info structure to contain the numa nodes memory,
VCPUs information and the future added numa nodes host memory
policies.
Reviewed-by: Eduardo Habkost
Signed-off-by: Andre Przywara
Signed-off-by: Wanlong Gao
---
hw/i386/pc.c| 12
include/sysemu/sysemu.h |
Add "-numa mem," option like following as Paolo suggested:
-numa mem,nodeid=0,size=1G
This new option will make later coming memory hotplug better.
We will use the new options to specify nodes memory info,
and just remain "-numa node,mem=xx" as legacy.
Reviewed-by: Laszlo Ersek
Signed-off-
As you know, QEMU can't direct it's memory allocation now, this may cause
guest cross node access performance regression.
And, the worse thing is that if PCI-passthrough is used,
direct-attached-device uses DMA transfer between device and qemu process.
All pages of the guest will be pinned by get_u
Signed-off-by: Wanlong Gao
---
qapi-schema.json | 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/qapi-schema.json b/qapi-schema.json
index db539b6..1043e57 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -4223,7 +4223,8 @@
##
{ 'union': 'NumaOption
The memory policy setting format is like:
policy={default|membind|interleave|preferred}[,relative=true],host-nodes=N-N
And we are adding this setting as a suboption of "-numa mem,",
the memory policy then can be set like following:
-numa node,nodeid=0,cpus=0 \
-numa node,nodeid=1,cpus=1
When a link change occurs on a backend (like tap), we currently do
not propage such change to the nic. As a result, when someone turns
off a link on a tap device, for instance, then a guest doesn't see
that change and continues to try to send traffic or run DHCP even
though the lower-layer is disc
于 2013/11/13 9:44, Wenchao Xia 写道:
> This series add support for tag/keyword 'event' in qapi-schema.
> The implemention doesn't generate a struture and visit function
> in the background for every event, so it doesn't support nested
> structure in the define to avoid trouble.
>
> It is on top of s
于 2013/11/19 19:26, Kevin Wolf 写道:
Am 10.11.2013 um 23:03 hat Wenchao Xia geschrieben:
Now it is possible to directly export an internal snapshot, which
can be used to probe the snapshot's contents without qemu-img
convert.
Signed-off-by: Wenchao Xia
---
block/snapshot.c | 18 +
于 2013/11/19 19:20, Kevin Wolf 写道:
Am 10.11.2013 um 23:03 hat Wenchao Xia geschrieben:
Since later this function will be used so improve it. The only caller of it
now is qemu-img, and it is not impacted by introduce function
bdrv_snapshot_load_tmp_by_id_or_name() that call bdrv_snapshot_load_tmp
于 2013/11/21 19:02, Zhanghailiang 写道:
Hi,
Now qemu ram live snapshot feature has some problems, it is based on
‘ram live migration’.
The time of snapshot depends on completion time of migration, which is
not measurable. Also It may can’t achieve migrate in some situation.
I have seen discussio
Igor Mammedov wrote:
On Thu, 21 Nov 2013 16:32:27 +0800
Li Guang wrote:
Michael S. Tsirkin wrote:
On Thu, Nov 21, 2013 at 04:18:45PM +0800, Li Guang wrote:
Hu Tao wrote:
On Thu, Nov 21, 2013 at 09:14:18AM +0200, Michael S. Tsirkin wrote:
On Thu, N
Michael S. Tsirkin wrote:
On Thu, Nov 21, 2013 at 04:32:27PM +0800, Li Guang wrote:
Michael S. Tsirkin wrote:
On Thu, Nov 21, 2013 at 04:18:45PM +0800, Li Guang wrote:
Hu Tao wrote:
On Thu, Nov 21, 2013 at 09:14:18AM +0200, Michael S. Tsirkin wrote:
On
From: Peter Maydell
Fix build failures with clang when KVM is not enabled by
providing a stub version of kvm_arch_get_supported_cpuid().
We retain the compile time check that this function isn't
called when CONFIG_KVM is not set by guarding the stub with
ifndef __OPTIMIZE__ (we assume that an opt
We were relying on msix_unset_vector_notifiers() to release all the
vectors when we disable MSI-X, but this only happens when MSI-X is
still enabled on the device. Perform further cleanup by releasing
any remaining vectors listed as in-use after this call. This caused
a leak of IRQ routes on hotp
On 11/21/13 23:26, Eric Blake wrote:
> On 11/21/2013 03:21 PM, Laszlo Ersek wrote:
>> This patch allows the user to usefully specify
>>
>> -drive file=img_1,if=pflash,format=raw,readonly \
>> -drive file=img_2,if=pflash,format=raw
>>
>> on the command line. The flash images will be mapped under
On 11/21/2013 03:21 PM, Laszlo Ersek wrote:
> This patch allows the user to usefully specify
>
> -drive file=img_1,if=pflash,format=raw,readonly \
> -drive file=img_2,if=pflash,format=raw
>
> on the command line. The flash images will be mapped under 4G in their
> reverse unit order -- that i
On Mon, Nov 18, 2013 at 04:32:34PM -0700, Alex Williamson wrote:
> On Mon, 2013-11-18 at 17:55 -0500, Vlad Yasevich wrote:
> > On 11/18/2013 05:40 PM, Alex Williamson wrote:
> > > On Mon, 2013-11-18 at 17:07 -0500, Vlad Yasevich wrote:
> > >> On 11/18/2013 04:33 PM, Alex Williamson wrote:
> > >>> O
Split the variable store off to a separate file when SPLIT_VARSTORE is
defined.
Even in this case, the preexistent PCDs' values don't change. Qemu must
take care of contiguously mapping NVVARSTORE.fd + OVMF.fd so that when
concatenated they end exactly at 4GB.
Contributed-under: TianoCore Contrib
This patch allows the user to usefully specify
-drive file=img_1,if=pflash,format=raw,readonly \
-drive file=img_2,if=pflash,format=raw
on the command line. The flash images will be mapped under 4G in their
reverse unit order -- that is, with their base addresses progressing
downwards, in inc
On Thu, 21 Nov 2013 16:32:27 +0800
Li Guang wrote:
> Michael S. Tsirkin wrote:
> > On Thu, Nov 21, 2013 at 04:18:45PM +0800, Li Guang wrote:
> >
> >> Hu Tao wrote:
> >>
> >>> On Thu, Nov 21, 2013 at 09:14:18AM +0200, Michael S. Tsirkin wrote:
> >>>
> On Thu, Nov 21, 2013 at
On Thu, Nov 21, 2013 at 02:39:10PM +0100, Igor Mammedov wrote:
> On Thu, 21 Nov 2013 08:20:56 +0200
> "Michael S. Tsirkin" wrote:
>
> > On Thu, Nov 21, 2013 at 03:38:21AM +0100, Igor Mammedov wrote:
> > > ---
> > > What's new since v6:
> > >
> > > * DIMM device is split to backend and frontend.
On 11/21/2013 01:04 PM, Vlad Yasevich wrote:
> rtl8139 hardware requires 9346 config register to be set into
> write mode before mac address can be changed even though it is
> not documented. Every driver inspected so far appears to do
> this along with comments that this is an undocumented requir
Added qemu-devel, since that is where this stuff belongs now. Everyone
else, sorry for the dupe...
On Thu, Nov 21, 2013 at 07:14:27PM +0100, Paolo Bonzini wrote:
> Can you remind us about your DSDT modifications? It should be possible
> to patch the HPET and applesmc bits appropriately from QEMU
Marcel Apfelbaum wrote:
On Thu, 2013-11-21 at 22:20 +0100, Erik Rull wrote:
Marcel Apfelbaum wrote:
Added 2 tests:
1. Basic check of FACS table (missed on prev submission)
2. Compare DSDT and SSDT tables against expected values
Test 2:
- runs only if iasl is installed on the host mach
On Thu, 2013-11-21 at 22:20 +0100, Erik Rull wrote:
> Marcel Apfelbaum wrote:
> > Added 2 tests:
> > 1. Basic check of FACS table (missed on prev submission)
> > 2. Compare DSDT and SSDT tables against expected values
> >
> > Test 2:
> > - runs only if iasl is installed on the host machine.
>
From: Peter Maydell
Our rules.mak adds '-rR' to MAKEFLAGS to indicate that we will be
explicitly specifying everything and not relying on any default
variables or rules. However we were accidentally relying on the
default ARFLAGS ("rv"). This went unnoticed because of a bug in
GNU Make 3.82 and e
From: Peter Maydell
clang defines __ATOMIC_SEQ_CST but its implementation of the
__atomic_exchange() builtin differs from that of gcc. Move the
__clang__ branch of the ifdef ladder to the top and fix its
implementation (there is no such builtin as __sync_exchange),
so we can compile with clang ag
Marcel Apfelbaum wrote:
Added 2 tests:
1. Basic check of FACS table (missed on prev submission)
2. Compare DSDT and SSDT tables against expected values
Test 2:
- runs only if iasl is installed on the host machine.
- the test plan:
1. Dumps the ACPI tables as AML on the disk.
2. R
Public bug reported:
Running a script like
while [ 1 ]
do
date
sleep 1
done
on the VM will result in the (correct) date being displayed, but it is
displayed only every two (!) seconds. We have also noticed that if we
connect to the VM's console using VNC, and move the mouse pointer
constant
On 11/21/2013 01:04 PM, Vlad Yasevich wrote:
> e1000 provides a E1000_RAH_AV bit on every complete write
> to the Receive Address Register. We can use this bit
> 2 ways:
> 1) To trigger HMP notifications. When the bit is set the
> mac address is fully set and we can update the HMP.
>
> 2)
On 11/21/2013 01:51 AM, Peter Lieven wrote:
> vnc_update_client currently scans the dirty bitmap of each client
> bitwise which is a very costly operation if only few bits are dirty.
> vnc_refresh_server_surface does almost the same.
> this patch optimizes both by utilizing the heavily optimized
>
rtl8139 hardware requires 9346 config register to be set into
write mode before mac address can be changed even though it is
not documented. Every driver inspected so far appears to do
this along with comments that this is an undocumented requirement.
We can use this to help us identify when the
Am 21.11.2013 14:28, schrieb Gleb Natapov:
> The following changes since commit fc8ead74674b7129e8f31c2595c76658e5622197:
>
> Merge remote-tracking branch 'qemu-kvm/uq/master' into staging (2013-10-18
> 10:03:24 -0700)
>
> are available in the git repository at:
>
>
> git://git.kernel.org/pub/
Il 21/11/2013 13:17, Michael S. Tsirkin ha scritto:
> g_string_vprintf was only introduced in 2.24 so switch to vsnprintf
> instead. A bit uglier but name size is fixed at 4 bytes here so it's
> easy.
>
> Reported-by: Richard Henderson
> Signed-off-by: Michael S. Tsirkin
> ---
> hw/i386/acpi-b
From: Jan Kiszka
This feature was already deprecated back then in qemu-kvm, ie. before
pci-assign went upstream. assigned_dev_ioport_rw will never be invoked
with resource_fd < 0.
Signed-off-by: Jan Kiszka
Acked-by: Alex Williamson
Signed-off-by: Gleb Natapov
---
hw/i386/kvm/pci-assign.c | 5
The following changes since commit fc8ead74674b7129e8f31c2595c76658e5622197:
Merge remote-tracking branch 'qemu-kvm/uq/master' into staging (2013-10-18
10:03:24 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git uq/master
for you to fetch cha
On Wed, Nov 20, 2013 at 03:44:11PM +0800, Fam Zheng wrote:
> This series adds cache mode option in the iotests framework. Test cases are
> updated to make use of cache mode and mask supported modes.
>
> v3: Change _unsupported_qemu_io_options to _supported_cache_modes.
> Change default mode to
On Thu, 21 Nov 2013 16:28:40 +0800
Hu Tao wrote:
> On Thu, Nov 21, 2013 at 10:26:36AM +0200, Michael S. Tsirkin wrote:
> > On Thu, Nov 21, 2013 at 04:12:22PM +0800, Hu Tao wrote:
> > > On Thu, Nov 21, 2013 at 09:14:18AM +0200, Michael S. Tsirkin wrote:
> > > > On Thu, Nov 21, 2013 at 03:38:37AM +
pc-bios/s390-zipl.rom is a flat image so it's expected that
loading it as elf will fail.
It should fall back on loading a flat file, but doesn't
on 32 bit systems, instead it fails printing:
qemu: hardware error: could not load bootloader 's390-zipl.rom'
The result is boot failure.
The reason
pc-bios/s390-zipl.rom is a flat image so it's expected that
loading it as elf will fail.
It should fall back on loading a flat file, but doesn't
on 32 bit systems, instead it fails printing:
qemu: hardware error: could not load bootloader 's390-zipl.rom'
The result is boot failure.
The reason
Il 21/11/2013 13:17, Michael S. Tsirkin ha scritto:
> g_array_get_element_size was only added in glib 2.14.
> Fortunately we don't use it for any arrays where
> element size is > 1, so just add an assert.
>
> Reported-by: Richard Henderson
> Signed-off-by: Michael S. Tsirkin
> ---
> hw/i386/acp
Signed-off-by: Hans de Goede
---
hw/usb/host-libusb.c | 50 ++
1 file changed, 50 insertions(+)
diff --git a/hw/usb/host-libusb.c b/hw/usb/host-libusb.c
index 0dd60b2..894875b 100644
--- a/hw/usb/host-libusb.c
+++ b/hw/usb/host-libusb.c
@@ -1280,6
On 2013年11月21日 20:41, Stefan Hajnoczi wrote:
On Wed, Nov 20, 2013 at 03:44:16PM +0800, Fam Zheng wrote:
The "raw" doesn't always work on certain file systems (e.g. tmpfs). Use
qcow2 to make the allocation status explicit.
Signed-off-by: Fam Zheng
---
tests/qemu-iotests/048 | 8 +++-
1 f
On 21.11.2013, at 13:24, Cornelia Huck wrote:
> On Thu, 21 Nov 2013 14:08:22 +0200
> "Michael S. Tsirkin" wrote:
>
>> pc-bios/s390-zipl.rom is a flat image so it's expected that
>> loading it as elf will fail.
>> It should fall back on loading a flat file, but doesn't
>> on 32 bit systems, ins
On Thu, 21 Nov 2013 08:20:56 +0200
"Michael S. Tsirkin" wrote:
> On Thu, Nov 21, 2013 at 03:38:21AM +0100, Igor Mammedov wrote:
> > ---
> > What's new since v6:
> >
> > * DIMM device is split to backend and frontend. Therefore following
> > command/options were added for supporting it:
> >
>
On Thu, Nov 21, 2013 at 01:24:13PM +0100, Cornelia Huck wrote:
> On Thu, 21 Nov 2013 14:08:22 +0200
> "Michael S. Tsirkin" wrote:
>
> > pc-bios/s390-zipl.rom is a flat image so it's expected that
> > loading it as elf will fail.
> > It should fall back on loading a flat file, but doesn't
> > on 3
From: Paolo Bonzini
Only the first item of the array was ever looked at. No
practical effect, but still worth fixing.
Signed-off-by: Paolo Bonzini
Signed-off-by: Gleb Natapov
---
target-i386/kvm.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/target-i386/kvm.c b/tar
On Wed, Nov 20, 2013 at 03:44:16PM +0800, Fam Zheng wrote:
> The "raw" doesn't always work on certain file systems (e.g. tmpfs). Use
> qcow2 to make the allocation status explicit.
>
> Signed-off-by: Fam Zheng
> ---
> tests/qemu-iotests/048 | 8 +++-
> 1 file changed, 7 insertions(+), 1 dele
This test will run only if iasl is installed on the host machine.
The test plan:
1. Dumps the ACPI tables as AML on the disk.
2. Runs iasl to disassembly the tables into ASL files.
3. Compares them with expected offline ASL files.
The test runs for both default machine and q35.
In case the test
Hu Tao wrote:
On Thu, Nov 21, 2013 at 09:06:43AM +0100, Erik Rull wrote:
Hi all,
when doing a git clone on the latest master, it fails compiling:
CCx86_64-softmmu/memory_mapping.o
CCx86_64-softmmu/dump.o
CCx86_64-softmmu/xen-stub.o
CCx86_64-softmmu/hw/i386/multiboot
e1000 provides a E1000_RAH_AV bit on every complete write
to the Receive Address Register. We can use this bit
2 ways:
1) To trigger HMP notifications. When the bit is set the
mac address is fully set and we can update the HMP.
2) We can turn off he bit on the write to low order bits of
Recent threads regarding e1000/rtl8139 and mac address change notifications
prompted some research into the respecitive hw data sheets as well as
available drivers. What I found is that each hw has a mechanism that
can be used by our emulation layer to determine when the mac address
change has com
Il 21/11/2013 20:47, Vlad Yasevich ha scritto:
> On 11/11/2013 02:50 AM, Paolo Bonzini wrote:
>> Il 11/11/2013 06:18, Jason Wang ha scritto:
>>> On 11/08/2013 10:13 AM, Vlad Yasevich wrote:
It is currently possible to specify things like:
-device e1000,netdev=foo,vlan=1
With this
Am 21.11.2013 um 15:33 hat Stefan Hajnoczi geschrieben:
> On Tue, Nov 19, 2013 at 04:37:27PM +0100, Kevin Wolf wrote:
> > @@ -1114,6 +1093,24 @@ int bdrv_open(BlockDriverState *bs, const char
> > *filename, QDict *options,
> > goto fail;
> > }
> >
> > +/* Prepare a
From: Stefan Weil
gcc 4.8.2 reports this warning when extra warnings are enabled (-Wextra):
CCqga/commands.o
qga/commands.c: In function ‘slog’:
qga/commands.c:28:5: error:
function might be possible candidate for ‘gnu_printf’ format attribute
[-Werror=suggest-attribute=format]
g_lo
From: Mark Cave-Ayland
Upstream OpenBIOS now implements SBus probing in order to determine the
contents of a physical bus slot, which is required to allow OpenBIOS to
identify the framebuffer without help from the fw_cfg interface.
SBus probing works by detecting the presence of an FCode program
On 11/11/2013 02:50 AM, Paolo Bonzini wrote:
> Il 11/11/2013 06:18, Jason Wang ha scritto:
>> On 11/08/2013 10:13 AM, Vlad Yasevich wrote:
>>> It is currently possible to specify things like:
>>> -device e1000,netdev=foo,vlan=1
>>> With this usage, whichever argument was specified last (vlan or
The kill() syscall is triggered with the following command:
# qemu -sandbox on -monitor stdio \
-device intel-hda -device hda-duplex -vnc :0
The resulting syslog/audit message:
# ausearch -m SECCOMP
time->Wed Nov 20 09:52:08 2013
type=SECCOMP msg=audit(1384912328.482:6656): aui
Ensure configure will set-up links for the files
if the build is created in other directory.
Signed-off-by: Marcel Apfelbaum
---
configure | 4
1 file changed, 4 insertions(+)
diff --git a/configure b/configure
index 9addff1..127e287 100755
--- a/configure
+++ b/configure
@@ -4665,6 +4665,
FACS table does not have a checksum, so we can
check at least the signature (existence).
Signed-off-by: Marcel Apfelbaum
---
tests/acpi-test.c | 18 ++
1 file changed, 18 insertions(+)
diff --git a/tests/acpi-test.c b/tests/acpi-test.c
index d6ff66f..43775cd 100644
--- a/tests/a
Added 2 tests:
1. Basic check of FACS table (missed on prev submission)
2. Compare DSDT and SSDT tables against expected values
Test 2:
- runs only if iasl is installed on the host machine.
- the test plan:
1. Dumps the ACPI tables as AML on the disk.
2. Runs iasl to disassembly the tabl
Ensure more then one instance of test_data may exist
at a given time. It will help to compare different
acpi table versions.
Signed-off-by: Marcel Apfelbaum
---
tests/acpi-test.c | 55 ---
1 file changed, 32 insertions(+), 23 deletions(-)
diff
This function basically parses command-line options given as a QDict
replacing a config file.
For instance, the QDict {"section.opt1": 42, "section.opt2": 23}
corresponds to the config file:
[section]
opt1 = 42
opt2 = 23
It is possible to specify multiple sections and also multiple sections
of t
If the filename is not prefixed by "blkverify:" in
blkverify_parse_filename(), the blkverify driver was not selected
through that protocol prefix, but by an explicit command line option
(like file.driver=blkverify). Contrary to the current reaction, this is
not really a problem; the whole filename
Currently, the configuration of blkdebug and blkverify is done through
the "filename" alone. There is now way of manually choosing blkdebug or
blkverify as a driver and using a normal image filename.
In the case of blkdebug, the filename starts with the protocol prefix,
follows up with the name of
Sorry for the delays around this release. I finally have proper
internet access at home.
I've updated the wiki and compressed the schedule for 1.7.0 should go
out on Wednesday. I went through patches this morning and believe I
have everything committed that was targeted for 1.7 (minus Paolo's
pu
The following changes since commit 394cfa39ba24dd838ace1308ae24961243947fb8:
Merge remote-tracking branch 'quintela/migration.next' into staging
(2013-11-19 13:03:06 -0800)
are available in the git repository at:
git://github.com/bonzini/qemu.git tags/for-anthony
for you to fetch changes
On Thu, 21 Nov 2013 15:13:12 +0100
Andreas Färber wrote:
> Am 21.11.2013 06:48, schrieb Li Guang:
> > Hi, Igor
> >
> > Igor Mammedov wrote:
> >> Add DimmBus for memory hotplug below 4Gb or above 4Gb depending
> >> on initial memory size and hotplug memory size.
> >>
> > ...
> >> +static
> >>
You have been subscribed to a public bug by Amos Kong (amoskong):
1. create listen socket
# cat /dev/random | nc -l localhost 1024
2. start vm with rng-egd backend
./x86_64-softmmu/qemu-system-x86_64 --enable-kvm -mon
chardev=qmp,mode=control,pretty=on -chardev
socket,id=qmp,host=localhost,po
Signed-off-by: Peter Lieven
---
vl.c | 34 --
1 file changed, 20 insertions(+), 14 deletions(-)
diff --git a/vl.c b/vl.c
index 8d5d874..dc0b41a 100644
--- a/vl.c
+++ b/vl.c
@@ -1385,35 +1385,41 @@ static QemuOptsList qemu_smp_opts = {
static void smp_parse(Qemu
On Tue, Nov 19, 2013 at 04:37:27PM +0100, Kevin Wolf wrote:
> @@ -1114,6 +1093,24 @@ int bdrv_open(BlockDriverState *bs, const char
> *filename, QDict *options,
> goto fail;
> }
>
> +/* Prepare a new options QDict for the temporary file, where user
> + * opt
On 20/11/13 4:15 AM, Stefan Hajnoczi wrote:
Sorry I forgot to CC qemu-devel on this:
On Wed, Nov 20, 2013 at 10:06 AM, Stefan Hajnoczi wrote:
Hi Brad,
The QEMU buildbot is failing on brad_openbsd_current as follows:
Building optionrom/multiboot.img
ld: multiboot.o: relocation R_X86_64_16 c
1 - 100 of 230 matches
Mail list logo
