2009/3/12 :
> I discovered a severe performance problem, wherein an OpenBSD guest would
> run fine for some period of hours, and then become horribly bogged down
> during disk operations, to the point of unusability. This was true even
> when the guest was nearly idle and the VM host had abundan
On Wed, Mar 11, 2009 at 4:02 PM, wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Josh Archambault wrote:
>
>> I'm fairly confident that using anything other than the default "e1000"
>> network device with 64-bit guests is discouraged by VMWare.
>
> It would appear that you're correct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Josh Archambault wrote:
I'm fairly confident that using anything other than the default "e1000"
network device with 64-bit guests is discouraged by VMWare.
It would appear that you're correct. Though the documentation does not
make that clear, I
I see that the vic(4) driver is still not in amd64/conf/GENERIC. Has
anyone any recent experience with this driver+platform, or know whether
its absence reflects a known problem or just lack of testing?
For the record, it works fine for me on an i386 guest on ESXi 3.5 U3,
with adaptor type "flexi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Salutations --
I see that the vic(4) driver is still not in amd64/conf/GENERIC. Has
anyone any recent experience with this driver+platform, or know whether
its absence reflects a known problem or just lack of testing?
For the record, it works fi
5 matches
Mail list logo
