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 > > > configured ethernet0.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 > > > > [...] > > > pcn0 at pci0 dev 17 function 0 "AMD 79c970 PCnet-PCI" rev 0x10, > > > pcn1 at pci0 dev 18 function 0 "AMD 79c970 PCnet-PCI" rev 0x10, > > [...] > > > > pcn (!!) > > > > Vmware still starts your VM with AMD NIC. > > I wrote a quick solution to this. > > http://communities.vmware.com/thread/31256 > > Bulls eye! > > But... Does it mean VirtualCenter never will be able to start this VM > without changing back to vlance ?
No. > I've shutdown the VM while connected to ESX server, and then started > again with VIC conected back to VI3, and vmxnet has remained. > > I hope it stays like this. It will. This happens because VI server does some weird caching. When you edit manually .vmx file and start VM VI server compares it with repository and does sync. So you have to do that trick to override VI smartness trying to be bullet proof. Regards Piotr
