Hi guys,

Thanks for the feedback.

I have seen the "caclru: runtime went backwards from xxx usec to yyy usec for 
pid zzzz" off an on but I have not seen any visible system impact because of 
that. It could be because the clock is virtualized and the system is taking 
some time to adjust to it. We can file this as a bug in our database and work 
on resolving it.

The "Status: Degraded (Integration services upgrade required)" issue is benign.

The "Heartbeat shows as 'OK (No Application Data)" is benign too.

Let us know if you guys are seeing some other issues.
From: Karl Pielorz <kpielorz_...@tdx.co.uk>
Sent: Wednesday, September 11, 2013 6:15 AM
To: Pavel Timofeev; Abhishek Gupta (LIS)
Cc: freebsd-virtualization@freebsd.org
Subject: Re: Hyper-V driver development status

--On 11 September 2013 16:43 +0400 Pavel Timofeev <tim...@gmail.com> wrote:

> I've just checked out and built projects/hyperv and everything looks good.

I just did that as well this morning...

"FreeBSD  10.0-CURRENT FreeBSD 10.0-CURRENT #6 r255470: Wed Sep 11 10:29:25
UTC 2013   root@:/usr/obj/src/sys/GENERIC  amd64"

I'm running under Windows Hyper V Server 2012 - the only things I've
noticed so far (not been testing long):

 - I get a myriad of "caclru: runtime went backwards from xxx usec to yyy
usec for pid zzzz" on the console every now and again.

 - On the Hyper-V Manager, under Networking it says:

     "Status: Degraded (Integration services upgrade required)"

   [I have just the 'Network Adapter' present in the VM - not the Legacy

Heartbeat shows as 'OK (No Application Data)' - which I'm guessing is
probably cosmetic?


freebsd-virtualization@freebsd.org mailing list
To unsubscribe, send any mail to 

Reply via email to