> From: Eduardo Habkost [mailto:ehabk...@redhat.com]
> On Mon, Dec 15, 2014 at 05:38:10PM +0100, Paolo Bonzini wrote:
> > From: Pavel Dovgalyuk
> >
> > Exception index is reset at every entry at every entry into cpu_exec()
> > function. This may cause missing the exceptions while replaying them.
>
> Am 23.12.2014 um 04:56 schrieb David Gibson :
>
>> On Tue, Dec 23, 2014 at 01:30:11AM +0100, Alexander Graf wrote:
>>
>>
>>> On 23.12.14 01:17, David Gibson wrote:
>>> The initial creation of the PAPR RTC qdev class left a wart - the rtc's
>>> offset was left in the sPAPREnvironment structu
> Am 23.12.2014 um 04:14 schrieb David Gibson :
>
>> On Tue, Dec 23, 2014 at 01:26:58AM +0100, Alexander Graf wrote:
>>
>>
>>> On 23.12.14 01:17, David Gibson wrote:
>>> On x86, the guest's RTC can be read with QMP, either from the RTC device's
>>> "date" property or via the "rtc-time" proper
When passing ancillary data through a unix socket, handle
credentials properly instead of doing a simple copy and
issuing a warning.
Signed-off-by: Alex Suykov
---
v2 fixes 80-column formatting warnings from checkpatch.
linux-user/syscall.c | 18 ++
1 file changed, 14 insertions
Tue, Dec 23, 2014 at 09:59:57AM +0800, Fam Zheng wrote:
> On Sun, 12/21 13:02, Alex Suykov wrote:
> > When passing ancillary data through a unix socket, handle
> > credentials properly instead of doing a simple copy and
> > issuing a warning.
> >
> > Signed-off-by: Alex Suykov
> > ---
...
> > -
On Mon, Dec 15, 2014 at 11:15:07AM +1100, Gavin Shan wrote:
> The emulation for EEH RTAS requests from guest isn't covered
> by QEMU yet and the patch implements them.
>
> The patch defines constants used by EEH RTAS calls and adds
> callback sPAPRPHBClass::eeh_handler, which is going to be used
>
On Mon, Dec 15, 2014 at 11:15:06AM +1100, Gavin Shan wrote:
> From: Alexey Kardashevskiy
>
> This makes find_phb()/find_dev() public and changed its names
> to spapr_pci_find_phb()/spapr_pci_find_dev() as they are going to
> be used from other parts of QEMU such as VFIO DDW (dynamic DMA window)
On Tue, Dec 23, 2014 at 01:30:11AM +0100, Alexander Graf wrote:
>
>
> On 23.12.14 01:17, David Gibson wrote:
> > The initial creation of the PAPR RTC qdev class left a wart - the rtc's
> > offset was left in the sPAPREnvironment structure, accessed via a global.
> >
> > This patch moves it into
On Tue, Dec 23, 2014 at 01:26:58AM +0100, Alexander Graf wrote:
>
>
> On 23.12.14 01:17, David Gibson wrote:
> > On x86, the guest's RTC can be read with QMP, either from the RTC device's
> > "date" property or via the "rtc-time" property on the machine (which is an
> > alias to the former). Thi
On Mon, 12/22 12:22, Peter Maydell wrote:
> On 22 December 2014 at 12:07, Peter Maydell wrote:
> > Something very odd is happening here: why are all the "r"s apparently
> > missing from those error messages?
>
> Looks like the result of using GNU sed-isms in some of the filters. On OSX:
>
> $ ec
On Fri, 12/19 09:20, Markus Armbruster wrote:
> Fam Zheng writes:
>
> > On Wed, 12/17 10:36, Markus Armbruster wrote:
> >> Fam Zheng writes:
> >>
> >> > Similar to drive-backup, but this command uses a device id as target
> >> > instead of creating/opening an image file.
> >> >
> >> > Also add
On 2014/12/22 17:33, Andrey Korolyov wrote:
>> Yes, it should depends on guest os implementation,
>> because physical memory is managed by OS, which have the full knowledge of
>> memory usage,
>> so I'm afraid that windows dose not friendly support it.
>> Could you detail the peeking techniques m
On Sun, 12/21 13:02, Alex Suykov wrote:
> When passing ancillary data through a unix socket, handle
> credentials properly instead of doing a simple copy and
> issuing a warning.
>
> Signed-off-by: Alex Suykov
> ---
> linux-user/syscall.c | 15 +++
> 1 file changed, 11 insertions(+),
On 2014/12/23 9:36, Fam Zheng wrote:
> On Mon, 12/22 20:21, Zhang Haoyu wrote:
>>
>> On 2014/12/22 20:05, Paolo Bonzini wrote:
>>>
>>>
>>> On 22/12/2014 12:40, Zhang Haoyu wrote:
On 2014/12/22 17:54, Paolo Bonzini wrote:
>
>
> On 22/12/2014 10:48, Zhang Haoyu wrote:
>> Hi,
>>>
On Mon, 12/22 20:21, Zhang Haoyu wrote:
>
> On 2014/12/22 20:05, Paolo Bonzini wrote:
> >
> >
> > On 22/12/2014 12:40, Zhang Haoyu wrote:
> >> On 2014/12/22 17:54, Paolo Bonzini wrote:
> >>>
> >>>
> >>> On 22/12/2014 10:48, Zhang Haoyu wrote:
> Hi,
>
> I cannot receive qemu-dev/kv
From: Fam Zheng
This adds three qmp commands to transactions.
Users can stop a dirty bitmap, start backup of it, and start another
dirty bitmap atomically, so that the dirty bitmap is tracked
incrementally and we don't miss any write.
Signed-off-by: Fam Zheng
Signed-off-by: John Snow
---
blo
From: Fam Zheng
This allows to put the dirty bitmap into a disabled state where no more
writes will be tracked.
It will be used before backup or writing to persistent file.
Signed-off-by: Fam Zheng
Signed-off-by: John Snow
---
block.c | 19 ++-
blockdev.c
From: Fam Zheng
Signed-off-by: Fam Zheng
Signed-off-by: John Snow
---
tests/qemu-iotests/056| 33 ++---
tests/qemu-iotests/056.out| 4 ++--
tests/qemu-iotests/iotests.py | 8
3 files changed, 40 insertions(+), 5 deletions(-)
diff --git a/test
For a synchronization bitmap that has been used for
a failed operation, we may wish to merge that bitmap
back with the bitmap we copied it from so that no
dirty bit tracking information is lost due to the
failed operation.
For this operation, I add bdrv_reclaim_dirty_bitmap,
which takes a BdrvDirt
Signed-off-by: Fam Zheng
Signed-off-by: John Snow
---
block.c | 39 +++
include/block/block.h | 4
2 files changed, 39 insertions(+), 4 deletions(-)
diff --git a/block.c b/block.c
index a1d9e88..f9e0767 100644
--- a/block.c
+++ b/block.c
@
For "dirty-bitmap" sync mode, the block job will iterate through the
given dirty bitmap to decide if a sector needs backup (backup all the
dirty clusters and skip clean ones), just as allocation conditions of
"top" sync mode.
Signed-off-by: Fam Zheng
Signed-off-by: John Snow
---
block.c
We add a bitmap merge operation to assist in error cases
where we wish to combine two bitmaps together.
This is algorithmically O(bits) provided HBITMAP_LEVELS remains
constant. For a full bitmap on a 64bit machine:
sum(bits/64^k, k, 0, HBITMAP_LEVELS) ~= 1.01587 * bits
We may be able to improve
From: Fam Zheng
Signed-off-by: Fam Zheng
Signed-off-by: John Snow
---
block.c | 1 +
qapi/block-core.json | 5 -
2 files changed, 5 insertions(+), 1 deletion(-)
diff --git a/block.c b/block.c
index 3d1337b..2466ba8 100644
--- a/block.c
+++ b/block.c
@@ -5444,6 +5444,7 @@ Bloc
From: Fam Zheng
The new command pair is added to manage user created dirty bitmap. The
dirty bitmap's name is mandatory and must be unique for the same device,
but different devices can have bitmaps with the same names.
The granularity is an optional field. If it is not specified, we will
choose
From: Vladimir Sementsov-Ogievskiy
Mirror and migration use dirty bitmaps for their purposes, and since
commit [block: per caller dirty bitmap] they use their own bitmaps, not
the global one. But they use old functions bdrv_set_dirty and
bdrv_reset_dirty, which change all dirty bitmaps.
Named di
From: Fam Zheng
This returns the granularity (in bytes) of dirty bitmap,
which matches the QMP interface and the existing query
interface.
Signed-off-by: Fam Zheng
Signed-off-by: John Snow
---
block.c | 9 +++--
include/block/block.h | 2 ++
2 files changed, 9 insertions(+),
From: Fam Zheng
This makes a deep copy of an HBitmap.
Signed-off-by: Fam Zheng
Signed-off-by: John Snow
---
include/qemu/hbitmap.h | 8
util/hbitmap.c | 20
2 files changed, 28 insertions(+)
diff --git a/include/qemu/hbitmap.h b/include/qemu/hbitmap.h
i
From: Fam Zheng
This field will be set for user created dirty bitmap. Also pass in an
error pointer to bdrv_create_dirty_bitmap, so when a name is already
taken on this BDS, it can report an error message. This is not global
check, two BDSes can have dirty bitmap with a common name.
Implemented
This is v10 of the in-memory part of the incremental backup
feature.
There are some remaining issues for which I am requesting
commentary, please see below under the "RFC" section for the
lingering questions I am aware of as of this revision, the
broad overview below, and the detailed changelog.
Fix proposed to branch: master
Review: https://review.openstack.org/143575
** Changed in: cinder
Assignee: John Griffith (john-griffith) => Tony Breeds (o-tony)
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launch
Issuing loadvm under -M mac99 would fail for two reasons: firstly an incorrect
version number for openpic would cause openpic_load() to abort, and secondly
a cut/paste error when restoring the IVPR and IDR registers caused subsequent
vmstate sections to become misaligned and abort early.
Signed-of
Make sure that we include the adb_poll_timer when saving the VM state for
client OSs that use it, e.g. Darwin.
Signed-off-by: Mark Cave-Ayland
---
hw/misc/macio/cuda.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/hw/misc/macio/cuda.c b/hw/misc/macio/cuda.c
index b4
Since env->msr has already been restored by the time cpu_post_load is called,
make sure that ppc_store_msr() is explicitly called with all msr bits marked
as invalid.
This solves the issue where MSR flags aren't set correctly when restoring a VM
snapshot, in particular the internal env->excp_prefi
Otherwise when cpu_post_load calls ppc_store_sdr1() when restoring a VM
snapshot the value is deemed unchanged and so the internal env->htab*
variables aren't set correctly.
Signed-off-by: Mark Cave-Ayland
CC: Paolo Bonzini
---
target-ppc/misc_helper.c |7 ++-
target-ppc/mmu_helper.c |
A simple copy/paste error causes savevm on -M mac99 to segfault.
Signed-off-by: Mark Cave-Ayland
---
hw/intc/openpic.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/hw/intc/openpic.c b/hw/intc/openpic.c
index 7d1f3b9..8699a4a 100644
--- a/hw/intc/openpic.c
+++ b/hw/intc/
This ensures that the macio PCI device is correctly configured when restoring
from a VM snapshot.
Signed-off-by: Mark Cave-Ayland
---
hw/misc/macio/macio.c | 24
1 file changed, 24 insertions(+)
diff --git a/hw/misc/macio/macio.c b/hw/misc/macio/macio.c
index e0f1e88.
The parent ADBDevice contains the device id on the ADB bus. Make sure that
this state is included in both its subclasses since some clients (such as
OpenBIOS) reprogram each device id after enumeration.
Signed-off-by: Mark Cave-Ayland
---
hw/input/adb.c | 21 +
1 file chang
This patchset fixes up various bugs in loadvm/savevm for -M g3beige and
-M mac99 so that it is becomes possible to save and restore image snapshots.
The focus of this patchset is on -M g3beige since this matches the majority
of my test images, but there were some easy fixes to be made to -M mac99
On 23.12.14 01:16, David Gibson wrote:
> At the moment, the PAPR RTC implementation (actually a paravirt
> firmware interface, rather than a normal device) works directly off
> host time, and so doesn't respect the options such as clock=vm which
> can be specified in the -rtc command line option.
On 23.12.14 01:17, David Gibson wrote:
> The initial creation of the PAPR RTC qdev class left a wart - the rtc's
> offset was left in the sPAPREnvironment structure, accessed via a global.
>
> This patch moves it into the RTC device's own state structure, were it
> belongs. This requires a smal
On 23.12.14 01:17, David Gibson wrote:
> On x86, the guest's RTC can be read with QMP, either from the RTC device's
> "date" property or via the "rtc-time" property on the machine (which is an
> alias to the former). This is set up in the mc146818rtc driver, and
> doesn't work on other targets.
The virtual RTC time is used in two places in the pseries machine. First
is in the RTAS get-time-of-day function which returns the RTC time to the
guest. Second is in the spapr events code which is used to timestamp
event messages from the hypervisor to the guest.
Currently both call qemu_get_ti
At present the PAPR RTC isn't a "device" as such - it's accessed only via
firmware/hypervisor calls, and is handled in the sPAPR core code. This
becomes inconvenient as we extend it in various ways.
This patch makes the PAPR RTC a separate device in the qemu device model.
For now, the only piece
The initial creation of the PAPR RTC qdev class left a wart - the rtc's
offset was left in the sPAPREnvironment structure, accessed via a global.
This patch moves it into the RTC device's own state structure, were it
belongs. This requires a small change to the migration stream format. In
order
Currently, the RTAS time of day functions only partially validate the
number of parameters they receive and return. Because of how the
parameters are used, this is unlikely to lead to a crash, but it's messy.
This patch adds the missing checks.
Signed-off-by: David Gibson
---
hw/ppc/spapr_rtc.
In the 'pseries' machine the real time clock is provided by a
paravirtualized firmware interface rather than a device per se; the RTAS
get-time-of-day and set-time-of-day calls.
Out current implementations of those work directly off host time (with
an offset), not respecting options such as clock=
At the moment the RTAS (firmware/hypervisor) time of day functions are
implemented in spapr_rtas.c along with a bunch of other things. Since
we're going to be expanding these a bit, move the RTAS RTC related code
out into new file spapr_rtc.c. Also add its own initialization function,
spapr_rtc_i
On x86, the guest's RTC can be read with QMP, either from the RTC device's
"date" property or via the "rtc-time" property on the machine (which is an
alias to the former). This is set up in the mc146818rtc driver, and
doesn't work on other targets.
This patch adds a similar "date" property to the
I have a Bay Trail Chromebook for which I would like to compile a custom
coreboot. I would like to run this custom coreboot in qemu, before burning
it into the flash. For now I simply read the content of the flash chip
(coreboot), and tried running it in qemu using the following command:
qemu-sys
The mc146818rtc driver exposes the current RTC date and time via the "date"
property in QOM (which is also aliased to the machine's "rtc-time"
property). Currently it uses a custom visitor function rtc_get_date to
do this.
This patch introduces new helpers to the QOM core to expose struct tm
valu
At the moment, the PAPR RTC implementation (actually a paravirt
firmware interface, rather than a normal device) works directly off
host time, and so doesn't respect the options such as clock=vm which
can be specified in the -rtc command line option.
Extending the PAPR RTC in this way makes it cle
On 22 December 2014 at 12:11, Paolo Bonzini wrote:
> The only change from v5 to v6 is that sysbus_mmio_map is moved to
> fw_cfg_init_mem. (And fw_cfg_init1 returns void because it's now
> simpler that way).
>
> This causes changes in patches 1, 5 and 6.
>
> I did not have the ARM firmware built,
One of the annoyances of the current migration format is the fact that
it's not self-describing. In fact, it's not properly describing at all.
Some code randomly scattered throughout QEMU elaborates roughly how to
read and write a stream of bytes.
We discussed an idea during KVM Forum 2013 to add
To support programmatic JSON assembly while keeping the code that generates it
readable, this patch introduces a simple JSON writer. It emits JSON serially
into a buffer in memory.
The nice thing about this writer is its simplicity and low memory overhead.
Unlike the QMP JSON writer, this one does
Migration is a black hole to most people. One of the biggest reasons for
this is that its protocol is a secret, undocumented sauce of code rolling
around random parts of the QEMU code base.
But what if we simply exposed the description of how the format looks like
alongside the actual migration st
For ftell we flush the output buffer to ensure that we don't have anything
lingering in our internal buffers. This is a very safe thing to do.
However, with the dynamic size measurement that the dynamic vmstate
description will bring this would turn out quite slow.
Instead, we can fast path this
This patch adds a python tool to the scripts directory that can read
a dumped migration stream if it contains the JSON description of the
device states. I constructs a human readable JSON stream out of it.
It's very simple to use:
$ qemu-system-x86_64
(qemu) migrate "exec:cat > mig"
$ ./s
I've identified the cause of "ls" not returning any output, but I don't
think we can fix it in QEMU.
This happens if the host fs is ext3 or ext4 on a 64 bit system. Here the
"d_off" entry in a linux_dirent64 is actually a hashtable hash, and so
can be a full 64 bits. Unfortunately the guest binary
From: Eric Auger
A new common module is created. It implements all functions
that have no device specificity (PCI, Platform).
This patch only consists in move (no functional changes)
Signed-off-by: Kim Phillips
Signed-off-by: Eric Auger
Signed-off-by: Alex Williamson
---
hw/vfio/Makefile.ob
From: Eric Auger
vfio_get_device now takes a VFIODevice as argument. The function is split
into 2 parts: vfio_get_device which is generic and vfio_populate_device
which is bus specific.
3 new fields are introduced in VFIODevice to store dev_info.
vfio_put_base_device is created.
Signed-off-by:
With the conversion to tracepoints, a couple previous DPRINTKs are
now quite a bit more visible and are really just informational.
Remove these and add a bit more description to another.
Signed-off-by: Alex Williamson
---
hw/vfio/common.c |2 +-
hw/vfio/pci.c|3 ---
2 files changed,
From: Eric Auger
better fit in the rest of the namespace
Signed-off-by: Eric Auger
Signed-off-by: Alex Williamson
---
hw/vfio/pci.c | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
index e965f3e..48387bc 100644
--- a/
From: Eric Auger
Signed-off-by: Eric Auger
Signed-off-by: Alex Williamson
---
hw/vfio/pci.c | 213 -
trace-events | 109 +++--
2 files changed, 116 insertions(+), 206 deletions(-)
diff --git a/hw/vfio/pci.c b/h
From: Eric Auger
Since we can potentially have both PCI and platform devices in
the same VFIO group, this latter now owns a list of VFIODevices.
A unified reset handler, vfio_reset_handler, is registered, looping
through this VFIODevice list. 2 specialized operations are introduced
(vfio_compute_
From: Eric Auger
This structure is going to be shared by VFIOPCIDevice and
VFIOPlatformDevice. VFIOBAR includes it.
vfio_eoi becomes an ops of VFIODevice specialized by parent device.
This makes possible to transform vfio_bar_write/read into generic
vfio_region_write/read that will be used by VF
From: Eric Auger
Introduce a new base VFIODevice strcut that will be used by both PCI
and Platform VFIO device. Move VFIOPCIDevice fd field there. Obviously
other fields from VFIOPCIDevice will be moved there but this patch
file is introduced to ease the review.
Also vfio_mask_single_irqindex, v
From: Eric Auger
To prepare for platform device introduction, rename vfio_mask_intx
and vfio_unmask_intx into vfio_mask_single_irqindex and respectively
unmask_single_irqindex. Also use a nex index parameter.
With that name and prototype the function will be usable for other
indexes than VFIO_PC
From: Eric Auger
This prepares for the introduction of VFIOPlatformDevice
Signed-off-by: Eric Auger
Signed-off-by: Alex Williamson
---
hw/vfio/pci.c | 210 +
1 file changed, 106 insertions(+), 104 deletions(-)
diff --git a/hw/vfio/pci.
From: Eric Auger
Add 3 new fields in the VFIODevice struct. Type is set to
VFIO_DEVICE_TYPE_PCI. The type enum value will later be used
to discriminate between VFIO PCI and platform devices. The name is
set to domain:bus:slot:function. Currently used to test whether
the device already is attached
From: Eric Auger
This patch removes all DPRINTF and replace them by trace points.
A few DPRINTF used in error cases were transformed into error_report.
Signed-off-by: Eric Auger
Signed-off-by: Alex Williamson
---
hw/misc/vfio.c | 403 +---
From: Frank Blaschka
Depending on the device, container->space->as contains the valid AddressSpace.
Using address_space_memory breaks devices sitting behind an iommu (and using
a separate address space).
Signed-off-by: Frank Blaschka
Signed-off-by: Alex Williamson
---
hw/misc/vfio.c |2 +-
The following changes since commit b574f602680d41c4cf4a9c106e3e2244bed01cdd:
Merge remote-tracking branch 'remotes/kraxel/tags/pull-vga-20141216-1' into
staging (2014-12-17 19:22:42 +)
are available in the git repository at:
git://github.com/awilliam/qemu-vfio.git tags/vfio-update-2014
Patch fixing this: https://patchwork.ozlabs.org/patch/423460/
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1404690
Title:
Qemu crashes with chrooted m68k
Status in QEMU:
New
Bug description:
On 22 December 2014 at 17:05, Ronex Dicapriyo wrote:
> [Ronex] Ok, As I can understand, QEMU is functional accurate, rather than
> cycle for fast simulation. But there must be some kind of reference clock,
> like say for example any timer device which raises an interrupt after couple
> of cycles (
Hello,
I am interested in learning the qemu emulation technology, But I don't know
where to start. I have some knowledge/experience in device modeling.
While walking through the qemu.org, I couldn't found proper documentation or
guide to start working with QEMU.
So, I am seeking some helps from
The m68k signal frame setup code which writes the signal return
trampoline code to the stack was assuming that a 'long' was 32 bits;
on 64 bit systems this meant we would end up writing the 32 bit
(2 insn) trampoline sequence to retaddr+4,retaddr+6 instead of
the intended retaddr+0,retaddr+2, resul
I have a fix for this (our code for setting up the signal return
trampoline used the wrong types and only worked on 32 bit hosts).
I notice that /bin/ls can't ls directories (it seems ok with single
files) but that's a different bug.
--
You received this bug notification because you are a member
Thanks for the explanations, I have some more doubts on the same, Kindly
clarify.
On Monday, 22 December 2014 10:10 PM, Peter Maydell
wrote:
> 1) the basic execution flow of QEMU simulation engine
> 2) Notion of time, events in QEMU
We don't have quite the same kind of view of the
On 22 December 2014 at 16:08, Ronex Dicapriyo wrote:
> I am interested in learning the qemu emulation technology, But I don't know
> where to start. I have some knowledge/experience in device modeling.
>
> While walking through the qemu.org, I couldn't found proper documentation or
> guide to star
12-20 22:04:13 +)
>
> are available in the git repository at:
>
>
> https://github.com/gongleiarei/qemu.git tags/bootdevice-next-20141222
>
> for you to fetch changes up to ddcd55316fb2851e144e719171621ad2816487dc:
>
> bo
Creates set_interrupts_fdt_node and set_regions_fdt_node
for code reusability.
Signed-off-by: Baptiste Reynal
---
hw/arm/sysbus-fdt.c | 102 +---
1 file changed, 73 insertions(+), 29 deletions(-)
diff --git a/hw/arm/sysbus-fdt.c b/hw/arm/sysbus-fd
Create a meta-device for PL330 DMA.
Add add_arm_pl330_fdt_node function, with multiple compatible string
and clocks support.
Signed-off-by: Baptiste Reynal
---
hw/arm/sysbus-fdt.c | 84
hw/vfio/Makefile.objs| 1 +
hw/vfio/pl330.c
Add VFIO_DEVICE_TYPE_AMBA.
Differentiate amba and platform devices according to compatible string.
Signed-off-by: Baptiste Reynal
---
hw/vfio/platform.c| 15 ---
include/hw/vfio/vfio-common.h | 1 +
2 files changed, 13 insertions(+), 3 deletions(-)
diff --git a/hw/vfio/
The following series add VFIO support for AMBA devices.
It introduces multiple compatible string support to deal with arm,primecell
compatible string.
The VFIOPlatformDevice now checks for this string and performs amba specific
operations if it is present (change path of the device, add clock in
Hello,
I am interested in learning the qemu emulation technology, But I don't know
where to start. I have some knowledge/experience in device modeling.
While walking through the qemu.org, I couldn't found proper documentation or
guide to start working with QEMU.
So, I am seeking some helps fr
I never have a problem when using virsh snapshot-create or delete.
Problem started with one VM when I use qemu-img snapshot. Thank you Todd
for work-around. It's helped me too. VM working again.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed
Signed-off-by: Don Slutz
---
qemu-char.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/qemu-char.c b/qemu-char.c
index ef84b53..6eec1d2 100644
--- a/qemu-char.c
+++ b/qemu-char.c
@@ -1387,6 +1387,7 @@ static CharDriverState *qemu_chr_open_pty(const char *id,
}
close(slave_fd);
+
** Changed in: qemu
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1402802
Title:
target-tricore/translate.c:3812: possible bad expression ?
Status in QEMU
On 21 December 2014 at 18:47, Bastian Koppelmann
wrote:
> The following changes since commit c4e7c17a8ecb41cdbb81374a128161c614ba1f1e:
>
> Merge remote-tracking branch 'remotes/kraxel/tags/pull-roms-20141217-1'
> into staging (2014-12-20 21:28:53 +)
>
> are available in the git repository a
Two more changes. The first is a bit of a shot in the dark, because I
cannot reproduce it, but it's obviously an improvement.
Paolo Bonzini (2):
serial: refine serial_thr_ipending_needed
pckbd: set bits 2-3-6-7 of the output port by default
hw/char/serial.c | 13 +++--
hw/input/pckb
OSes typically write 0xdd/0xdf to turn the A20 line off and on. This
has bits 2-3-6-7 on, so that the output port subsection is migrated.
Change the reset value and migration default to include those four
bits, thus avoiding that the subsection is migrated.
This strictly speaking changes guest AB
If the THR interrupt is disabled, there is no need to migrate thr_ipending
because LSR.THRE will be sampled again when the interrupt is enabled.
(This is the behavior that is not documented in the datasheet, but
relied on by Windows!)
Note that in this case IIR will never be 0x2 so, if thr_ipendin
On 19 December 2014 at 16:56, Eduardo Otubo
wrote:
> The following changes since commit b574f602680d41c4cf4a9c106e3e2244bed01cdd:
>
> Merge remote-tracking branch 'remotes/kraxel/tags/pull-vga-20141216-1' into
> staging (2014-12-17 19:22:42 +)
>
> are available in the git repository at:
>
>
Signed-off-by: Denis V. Lunev
Acked-by: Roman Kagan
---
block/parallels.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/block/parallels.c b/block/parallels.c
index bea1217..e3abf4e 100644
--- a/block/parallels.c
+++ b/block/parallels.c
@@ -2,8 +2,12 @@
* Block driver
Signed-off-by: Denis V. Lunev
Acked-by: Roman Kagan
CC: Jeff Cody
CC: Kevin Wolf
CC: Stefan Hajnoczi
---
tests/qemu-iotests/115 | 68 ++
tests/qemu-iotests/115.out | 24
tests/qemu-iotests/group | 1 +
3 files changed, 93 ins
Do not even care to create WithoutFreeSpace image, it is obsolete.
Always create WithouFreSpacExt one.
The code also does not spend a lot of efforts to fill cylinders and
heads fields, they are not used actually in a real life neither in
QEMU nor in Parallels products.
Signed-off-by: Denis V. Lun
From: Roman Kagan
Implement VFS method for get_block_status to Parallels format driver.
Signed-off-by: Roman Kagan
Signed-off-by: Denis V. Lunev
CC: Jeff Cody
CC: Kevin Wolf
CC: Stefan Hajnoczi
---
block/parallels.c | 21 +
1 file changed, 21 insertions(+)
diff --git a
From: Roman Kagan
Teach parallels_read() to do reads in coarser granularity than just a
single sector: if requested, read up to the cluster end in one go.
Signed-off-by: Roman Kagan
Signed-off-by: Denis V. Lunev
CC: Jeff Cody
CC: Kevin Wolf
CC: Stefan Hajnoczi
---
block/parallels.c | 18 ++
Support write on Parallels images. The code is almost the same as one
in the previous patch implemented scatter-gather IO for read.
Signed-off-by: Denis V. Lunev
Acked-by: Roman Kagan
CC: Jeff Cody
CC: Kevin Wolf
CC: Stefan Hajnoczi
---
block/parallels.c | 77
suggested by Jeff Cody
Signed-off-by: Denis V. Lunev
Acked-by: Roman Kagan
CC: Jeff Cody
CC: Kevin Wolf
CC: Stefan Hajnoczi
---
tests/qemu-iotests/076 | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/tests/qemu-iotests/076 b/tests/qemu-iotests/076
index ed2be35.
1 - 100 of 158 matches
Mail list logo
