** Also affects: qemu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/905095
Title:
qemu-img can't convert vmdk file: Operation not permitted
Status in QE
On Tue, Aug 9, 2016 at 9:42 AM, Peter Maydell wrote:
> On 3 August 2016 at 04:10, Alistair Francis wrote:
>> Signed-off-by: Alistair Francis
>> ---
>> As the migration framework is not included in user mode this needs to be a
>> new file.
>>
>> V6:
>> - Make the OR IRQ device a TYPE_DEVICE
>>
'-object help' prints available user creatable backends.
'-object $typename,help' prints relevant properties.
Signed-off-by: Lin Ma
---
include/qom/object_interfaces.h | 2 +
qemu-options.hx | 7 ++-
qom/object_interfaces.c | 112 ++
When kernel and device tree are specified in the QEMU commandline, then
this device tree may be modified e.g. to add virtio_mmio devices.
With a bootloader e.g. on a flash device these extra devices are not
available.
With this change, the device tree can be specified at the QEMU commandline.
The m
On 09/09/2016 11:17 PM, Thomas Huth wrote:
> get_maintainer.pl now properly recognizes that the file in
> include/hw/tricore/ belongs to TriCore.
>
> Signed-off-by: Thomas Huth
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 7196dba
On 09/10/2016 11:49 AM, Paolo Bonzini wrote:
On 10/09/2016 10:23, Maxime Coquelin wrote:
Currently, devices are plugged before features are negotiated.
If the backend doesn't support VIRTIO_F_VERSION_1, the transport
need to rewind some settings.
This is the case for CCW, for which a post_p
On 10/09/2016 10:23, Maxime Coquelin wrote:
> Currently, devices are plugged before features are negotiated.
> If the backend doesn't support VIRTIO_F_VERSION_1, the transport
> need to rewind some settings.
>
> This is the case for CCW, for which a post_plugged callback had
> been introduced, w
Currently, devices are plugged before features are negotiated.
If the backend doesn't support VIRTIO_F_VERSION_1, the transport
need to rewind some settings.
This is the case for CCW, for which a post_plugged callback had
been introduced, where max_rev field is just updated if
VIRTIO_F_VERSION_1 i
Hi,
On (Fri) 09 Sep 2016 [14:45:36], Hailiang Zhang wrote:
> ping ?
Juan will start reviewing and picking patches soon.
On (Fri) 09 Sep 2016 [10:31:20], Greg Kurz wrote:
> Except virtio-9p, all virtio-* tests are orphan. This patch tries to fix
> it, according to the following logic:
>
> - when the related subsystem has its own section in MAINTAINERS, the test
> is added there
> - otherwise it is added to the "pa
10 matches
Mail list logo
