From: Kevin McMurtrie on
In article <op.vgo3pcfrw1eelo(a)msrvcn04.belkin>,
"Chris Seidel" <cseidel(a)arcor.de> wrote:

> On Sat, 31 Jul 2010 07:11:04 +0200, Kevin McMurtrie
> <mcmurtrie(a)pixelmemory.us> wrote:
>
> >> http://communities.vmware.com/thread/215461
> >>
> >> Damned, so my Software will not run in VMWare!? :/
> >
> > This is a Solaris bug, not a VMWare bug.
>
> No.
>
> I could fix it with the following VMWare settings:
>
> monitor_control.disable_tsc_offsetting=TRUE
> monitor_control.disable_rdtscopt_bt=TRUE
>
> Now everything schedules fine, no more constant offset.

You've fixed another bug then. The one you linked to is about extremely
large jumps and it happens without VMware.
--
I won't see Google Groups replies because I must filter them as spam
From: Chris Seidel on
On Sat, 31 Jul 2010 21:14:29 +0200, Kevin McMurtrie
<mcmurtrie(a)pixelmemory.us> wrote:

>> >> http://communities.vmware.com/thread/215461

> You've fixed another bug then. The one you linked to is about extremely
> large jumps and it happens without VMware.

Die Title of the post is:

"Consecutive Java 1.6.0_13 System.nanoTime() calls report sporadic large
values then never change on Solaris 5.10 x86 on VMWare ESX"

Watch the last three words...
From: Kevin McMurtrie on
In article <op.vgp6bet9w1eelo(a)msrvcn04.belkin>,
"Chris Seidel" <cseidel(a)arcor.de> wrote:

> On Sat, 31 Jul 2010 21:14:29 +0200, Kevin McMurtrie
> <mcmurtrie(a)pixelmemory.us> wrote:
>
> >> >> http://communities.vmware.com/thread/215461
>
> > You've fixed another bug then. The one you linked to is about extremely
> > large jumps and it happens without VMware.
>
> Die Title of the post is:
>
> "Consecutive Java 1.6.0_13 System.nanoTime() calls report sporadic large
> values then never change on Solaris 5.10 x86 on VMWare ESX"
>
> Watch the last three words...

Right. Take out Java and VMWare and it still happens. It's a Solaris
kernel bug that I've had to deal with first-hand.
--
I won't see Google Groups replies because I must filter them as spam
From: Lew on
Chris Seidel wrote:
>>>>>> http://communities.vmware.com/thread/215461

Kevin McMurtrie wrote:
>>> You've fixed another bug then. The one you linked to is about extremely
>>> large jumps and it happens without VMware.

Chris Seidel wrote:
>> Die Title of the post is:
>>
>> "Consecutive Java 1.6.0_13 System.nanoTime() calls report sporadic large
>> values then never change on Solaris 5.10 x86 on VMWare ESX"
>>
>> Watch the last three words...

Kevin McMurtrie wrote:
> Right. Take out Java and VMWare and it still happens. It's a Solaris
> kernel bug that I've had to deal with first-hand.

In other words, Chris, while someone may have entitled a bug report a certain
way, that doesn't mean that when investigated the bug depended in real life on
what the person who came up with the title in their incomplete knowledge
thought was involved. When encountering a person like Kevin who has more
complete knowledge, it is frequently better for one's own advancement to
accept the additional information and extra expertise to increase one's own
understanding than to reject it because those with less information and
expertise who didn't solve the problem didn't think of it.

--
Lew