Sometimes it is very annoying that your settings in the .vmx won't be
respected / changed back by the VI client.
A very slow, but bullet-proof method is the following:
1.) Connect directly with the VI client to the ESX
(I do not have virtual center)
2.) Stop the VM and remove it from the
On 10/15/07, Piotrek Kapczuk [EMAIL PROTECTED] wrote:
2007/10/15, Fernando Braga [EMAIL PROTECTED]:
I'm failing to use vic(4) driver on ESX 3.0.2 and OpenBSD 4.2. I've
configuredethernet0.virtualDev = vmxnet as instructed on
vic(4) man page.
dmesg follows:
OpenBSD 4.2
2007/10/16, Fernando Braga [EMAIL PROTECTED]:
On 10/15/07, Piotrek Kapczuk [EMAIL PROTECTED] wrote:
2007/10/15, Fernando Braga [EMAIL PROTECTED]:
I'm failing to use vic(4) driver on ESX 3.0.2 and OpenBSD 4.2. I've
configuredethernet0.virtualDev = vmxnet as instructed
Hi,
I'm failing to use vic(4) driver on ESX 3.0.2 and OpenBSD 4.2. I've
configuredethernet0.virtualDev = vmxnet as instructed on
vic(4) man page.
dmesg follows:
OpenBSD 4.2 (GENERIC) #1: Fri Oct 12 16:00:29 BRT 2007
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0
Hi
2007/10/15, Fernando Braga [EMAIL PROTECTED]:
Hi,
I'm failing to use vic(4) driver on ESX 3.0.2 and OpenBSD 4.2. I've
configuredethernet0.virtualDev = vmxnet as instructed on
vic(4) man page.
dmesg follows:
OpenBSD 4.2 (GENERIC) #1: Fri Oct 12 16:00:29 BRT 2007
[EMAIL
5 matches
Mail list logo