On Wed, 2010-06-23 at 15:53 -0500, Sean Bruno wrote:
> On Wed, 2010-06-23 at 15:00 -0500, Alexander Motin wrote:
> > hint.atrtc.0.clock=0
> > hint.attimer.0.clock=0
> > hint.hpet.0.legacy_route=1
>
I've noted that the system is spitting out t_delta warnings on the
console now. The VM is 100% wor
Sean Bruno wrote:
> On Wed, 2010-06-23 at 15:53 -0500, Sean Bruno wrote:
>> On Wed, 2010-06-23 at 15:00 -0500, Alexander Motin wrote:
>>> hint.atrtc.0.clock=0
>>> hint.attimer.0.clock=0
>>> hint.hpet.0.legacy_route=1
>
> I've noted that the system is spitting out t_delta warnings on the
> console
On Wed, 2010-06-23 at 15:00 -0500, Alexander Motin wrote:
> hint.atrtc.0.clock=0
> hint.attimer.0.clock=0
> hint.hpet.0.legacy_route=1
after adding those to the VM:
Copyright (c) 1992-2010 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The R
Sean Bruno wrote:
> With the large amount of churn in key parts of FreeBSD ongoing, I
> thought I'd post a dmesg from a booting FreeBSD Current instance I use
> all the time. This is under KVM/QEMU on Fedora 12.
>
> there's some interesting things relating to timers and such.
Thanks. I've noti
With the large amount of churn in key parts of FreeBSD ongoing, I
thought I'd post a dmesg from a booting FreeBSD Current instance I use
all the time. This is under KVM/QEMU on Fedora 12.
there's some interesting things relating to timers and such.
booted with boot.config set to -v
Sean
Copy