Larry Rosenman wrote:
On Tue, 13 Oct 2009, Ivan Voras wrote:
As for what data is needed, it depends on what you can get - from this
discussion thread it looks like it would be enough to verify that disk
IO doesn't leave VM processes waiting (i.e. that disk IO doesn't
interfere with CPU-bound
Ivan Voras wrote:
2009/10/13 Larry Rosenman l...@lerctr.org:
note huge packet loss. It looks like it's VM fault or something like it.
It sounds like the VM is failing to execute the guest during certain
types of I/O. A bit of scheduler tracing in the host OS probably wouldn't go
amiss to
Kris Kennaway wrote:
Ivan Voras wrote:
I recall others having various weird problems in 3.5 that went away when
they upgraded to 4.0.
It would be a good idea except that apparently my installation is
unupgradeable because of unsupported boot disk (a SCSI RAID volume).
On Tue, Oct 13, 2009 at 09:58:09AM +0200, Thomas Backman wrote:
On Oct 13, 2009, at 12:35 AM, Luigi Rizzo wrote:
...
hi,
this issue (not specific to FreeBSD, and not new -- it has been
like this forever) is discussed in some detail here
As a follow-up to my original message, and I thank the couple people that
did respond with suggestions. I seem to have found the issue, which is
apparently cvsup17.FreeBSD.org and some file inconsistency.
I was using cvsup17 as it was a very close site hop/ping wise on my various
servers, in
Good afternoon,
I am having a few niggly problems setting up a VNC repeater on my
FreeBSD box and I am finding it very hard to find any information
anywhere. I freshly installed FreeBSD on the box today and updated ports
and system. I then make make build make install
Hi.
I'm running i386 on i386, single P4 cpu, 1GiB RAM.
SiI 3114 - SATA [single disk] - GELI [AES-128] - ZFS [sha256]
Straight RELENG_8 as of cvsup Oct 12 14:49:00 aka 8.0-RC1 plus.
ZFS pool is at v13, ZFS fs is at v3.
Hardware seems stable.
The only modification to config defaults is:
Happened again :) So some more notes...
Watched it this time, it jumped from about 29xMiB straight to 366MiB,
then hung and rebooted itself.
The first zpool import after reboot takes about a minute more than
the usual ten seconds to import. And uses up to maybe 125MiB instead
of maybe 40MiB.
On Wed, 14 Oct 2009 18:55, grarpamp@ wrote:
Happened again :) So some more notes...
Watched it this time, it jumped from about 29xMiB straight to 366MiB,
then hung and rebooted itself.
The first zpool import after reboot takes about a minute more than
the usual ten seconds to import. And uses
