On 06/28/2017 10:00 PM, Dr. David Alan Gilbert (git) wrote:
From: "Dr. David Alan Gilbert"
Clear the area and turn off THP.
Signed-off-by: Dr. David Alan Gilbert
---
contrib/libvhost-user/libvhost-user.c | 32 ++--
1
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/779151
Title:
qemu-nbd
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/816860
Title:
Guest
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/796480
Title:
Addresses
VHDX uses uint64_t types for most offsets, following the VHDX spec.
However, bdrv_truncate() takes an int64_t value for the truncating
offset. Check for overflow before calling bdrv_truncate().
N.B.: For a compliant image this is not an issue, as the maximum VHDX
image size is defined per the
Calls to bdrv_getlength() were not checking for error. In vhdx.c, this
can lead to truncating an image file, so it is a definite bug. In
vhdx-log.c, the path for improper behavior is less clear, but it is best
to check in any case.
Reported-by: Markus Armbruster
Two VHDX items cleaned up:
1. Check for error when calling bdrv_getlength() [Markus]
2. Check for overflow in offset prior to calling bdrv_truncate().
Jeff Cody (2):
block/vhdx: check error return of bdrv_getlength()
block/vhdx: check for offset overflow to bdrv_truncate()
On Sat, 08/05 16:11, Eduardo Habkost wrote:
> On Sat, Aug 05, 2017 at 10:56:20PM +0800, Fam Zheng wrote:
> > On Fri, 08/04 18:36, Eduardo Habkost wrote:
> > > This series adds the ability to run QMP commands
> > > non-interactively to qmp-shell, and deletes scripts/qmp/qmp.
> >
> > Hmm, not so
On 04/08/2017 19:48, Dr. David Alan Gilbert wrote:
>>
>> (I don't know if there have in fact been any changes between
>> 2.9 and 2.10 that would be compatibility issues.)
> I think there's two sub questions:
> a) The virt-2.9 needs to pick up HW_COMPAT_2_9 if anything
> in it is relevant for
On 05/08/2017 09:39, Thomas Huth wrote:
>> +CONFIG_VHOST_USER_SCSI=$(and $(CONFIG_VHOST_USER),$(CONFIG_LINUX))
> I have to say that I don't really like using $(and ...) in our makefiles
> like this. You rely on the fact that the config variables are either set
> to "y" or not set at all ... but if
On 04/08/2017 23:47, Alexander Bezzubikov wrote:
2017-08-04 23:28 GMT+03:00 Laszlo Ersek :
On 08/04/17 20:59, Alexander Bezzubikov wrote:
2017-08-01 20:28 GMT+03:00 Alexander Bezzubikov :
2017-08-01 16:38 GMT+03:00 Marcel Apfelbaum :
Am 06.08.2017 um 13:25 schrieb Shantanu Agarwal:
> Hello all,
> I was reading about qemu, trying to understand the source code. I found
> that vl.c is considered the main file of qemu source code from where all
> the execution starts. So I flipped some values, i even put a exit(0) just
> after the
Hello all,
I was reading about qemu, trying to understand the source code. I found
that vl.c is considered the main file of qemu source code from where all
the execution starts. So I flipped some values, i even put a exit(0) just
after the int main starts, but nothing is changed. Qemu is fully
On 08/06/17 09:38, Dhiru Kholia wrote:
> On Sat, Aug 05, 2017 at 10:05:09PM +0200, Laszlo Ersek wrote:
>> On 08/05/17 13:46, Dhiru Kholia wrote:
>>> On Sat, Aug 5, 2017 at 2:00 PM, Dhiru Kholia wrote:
I ran git bisect on OVMF repository [5] to find the commit that
On Sat, Aug 05, 2017 at 10:05:09PM +0200, Laszlo Ersek wrote:
> On 08/05/17 13:46, Dhiru Kholia wrote:
> > On Sat, Aug 5, 2017 at 2:00 PM, Dhiru Kholia wrote:
> >> I ran git bisect on OVMF repository [5] to find the commit that broke
> >> booting of macOS + Clover
15 matches
Mail list logo