Just out of interest tried how far the timeout hackery can go working
around the issue. Well, looks like it goes quite far: having previously
reproduced the hang in 4-5 runs and in under a minute, now have had this
running without a hang for an hour. I will also test the patch under OBS
worker(s) a
Some kind of semi-workaround patch attached. It seems to leave this kind
of race window for me (for select which is worse):
0x6004bf98 <+136>: xor%r8d,%r8d
0x6004bf9b <+139>: test %eax,%eax
0x6004bf9d <+141>: jne0x6004c2b7
0x6004bfa3 <+1
LK: Ok, good catch, that might be more suitable option. Thanks,
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/955379
Title:
cmake hangs with qemu-arm-static
Status in QEMU:
Confirmed
Status in L
Peter, I have qemu chrootable test case under which you could fire one
command to hit the bug reliably. Only issue is, are you willing to take
a peek at 100M extractable tarball? If not, I'll try to create a smaller
one.
--
You received this bug notification because you are a member of qemu-
deve
Ok, test case attached (80M tar). This hugely stripped one is not 100%
reproducer, but do few loops and you will hit it. Instructions for using:
- extract, chroot
- cd /home/abuild/rpmbuild
- su abuild
- export RPM_BUILD_ROOT=$PWD
- rpmbuild -ba SOURCES/libshortcut.spec
** Attachment added: "Tiz
Mind you, when you hit the bug it just hangs and cmake test errors are
just to speed up the process of hitting the bug (if cmake just fails you
did not hit the bug). Feel free to try with any qemu variant, they all
hang similarly when bug is hit. I think that root had some suse 1.2 one
inside.
--
If that is the case for you (for me it reproduces it every 4-5 runs or so),
there are two options:
1) put while(true) loop around the rpmbuild and you will hit it always, or
2) I can wrap up a bit bigger cmake usecase that systematically hits it. Warn
you though, size will jump to 200M.
--
You
> this blocks forever, because the thing that would wake it up is the
signal handler writing to the pipe we're selecting on, but we will never
run the signal handler until select exits
Duh, makes sense, have to think about this. Thank you for great analysis
:)
Apparently have to dig into qemu's c
So I guess 'raciness' of my proposed patch would only depend on how
small I could squeeze the section between 'sigpending' flag comparison
and actual syscall entering?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launc
And what would break if we make poll timeout instantly in case there are
signals pending and restart the given syscall after handlers run?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/955379
Title:
Moreover, is there even a need to restart anything, just make it async
call in case signals were pending?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/955379
Title:
cmake hangs with qemu-arm-stati
Never mind, async/zero timeout call would suffer from same (albeit now
tiny) race. It would make this far less invasive as a change though.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/955379
Title:
Luke Kim: quite unlikely that above patch would cause the issue you
see.. are you sure something else did not break in your environment?
Can you execute that same make manually?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https:/
From: Janne Karhunen
Replace hardcoded vmdk description file hardware version flag with
a user definable version.
Signed-off-by: Janne Karhunen
---
block/vmdk.c | 20 ++--
include/block/block_int.h | 3 +--
qemu-doc.texi | 4 ++--
3 files changed, 13
On Wed, Apr 20, 2016 at 7:22 PM, Fam Zheng wrote:
>> Replace hardcoded vmdk description file hardware version flag with
>> a user definable version.
>
> Hi Janne,
>
> Since this is a new feature, please explain why this change is desired (i.e.
> the necessity.)
See here what it controls for vmwa
On Wed, Apr 20, 2016 at 7:22 PM, Fam Zheng wrote:
> For backward compatibility reason, we shouldn't remove a pre-existing option
> without solid justification and probably a grace period. I suggest adding the
> hwversion option in addition, and document and check it as exclusive with the
> compat
On Wed, Apr 20, 2016 at 8:26 PM, Fam Zheng wrote:
>> In other words, without the patch not a single qemu-img generated vmdk
>> is 'good' for the system I'm using.
>
> Thanks for the explanation, please add this information into the commit
> message
> in next submission and also fix the option co
From: Janne Karhunen
Vmdk images have metadata to indicate the vmware virtual
hardware version image was created/tested to run with.
Allow users to specify that version via new 'hwversion'
option.
Signed-off-by: Janne Karhunen
---
block/vmdk.c
On Wed, Apr 20, 2016 at 9:44 PM, Fam Zheng wrote:
>> That's certainly doable and kind of makes sense, but I'm not entirely
>> sure that compat6 flag makes any sense to begin with. Does it?
>
> I don't know VMware products well enough to tell, but it has been available
> since forever, therefore m
On Fri, Apr 29, 2016 at 12:41 AM, Fam Zheng wrote:
>> Signed-off-by: Janne Karhunen
>
> Sorry for the late reply, I was distracted..
Like wise, was traveling..
>> if (qemu_opt_get_bool_del(opts, BLOCK_OPT_COMPAT6, false)) {
>> -flags |= BLOCK_FLAG_CO
From: Janne Karhunen
Vmdk images have metadata to indicate the vmware virtual
hardware version image was created/tested to run with.
Allow users to specify that version via new 'hwversion'
option.
Signed-off-by: Janne Karhunen
---
block/vmdk.c
On Mon, May 2, 2016 at 5:49 PM, Fam Zheng wrote:
> Yes.
>
> But you get:
Fair enough, sent another one.
Thanks,
--
Janne
Fam,
Any objections to this one?
--
Janne
On Tue, May 3, 2016 at 12:43 PM, Janne Karhunen
wrote:
> From: Janne Karhunen
>
> Vmdk images have metadata to indicate the vmware virtual
> hardware version image was created/tested to run with.
> Allow users to specify that
On Fri, May 6, 2016 at 2:05 PM, Kevin Wolf wrote:
>>
>> Reviewed-by: Fam Zheng
>
> Thanks, applied to block-next.
Great, thanks everyone!
--
Janne
Hi,
I have created an experimental setup for Linux where all the virtio
data structures and traffic can be allocated by the guest from a ram
blob outside of the guest default ram space. That ram blob can be
hotplugged to the guest or defined via the guests device tree.This is
done as some hypervis
25 matches
Mail list logo
