Re: vic(4) on ESX 3.0.2
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 inventory. (right click on the vm in the left pannel, then Remove from the Inventory) 3.) Change the .vmx file, i.e., append something like (if you want to use the em driver and have 3 interfaces) ethernet0.virtualDev = e1000 ethernet1.virtualDev = e1000 ethernet2.virtualDev = e1000 or (if you want to use use the vic driver) ethernet0.virtualDev = vmxnet ethernet1.virtualDev = vmxnet ethernet2.virtualDev = vmxnet 4.) Add the VM again to the repository. (With the VI client, go to the global Configuration Tab, click on Storage (SCSI, SAN and NFS), then right-click on the storage (i.e., typically storage1) and choose Browse Datastore Search for the .vmx file and then via right-click Add to Inventory.)
Re: vic(4) on ESX 3.0.2
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 (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 ? 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. Thanks!
Re: vic(4) on ESX 3.0.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 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
vic(4) on ESX 3.0.2
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: Intel(R) Xeon(R) CPU E5310 @ 1.60GHz (GenuineIntel 686-class) 1.60 GHz cpu0: FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,SSE3,DS-CPL,CX16 real mem = 1073246208 (1023MB) avail mem = 1030144000 (982MB) mainbus0 at root bios0 at mainbus0: AT/286+ BIOS, date 04/17/06, BIOS32 rev. 0 @ 0xfd880, SMBIOS rev. 2.31 @ 0xe0010 (45 entries) bios0: vendor Phoenix Technologies LTD version 6.00 date 04/17/2006 bios0: VMware, Inc. VMware Virtual Platform apm0 at bios0: Power Management spec V1.2 apm0: AC on, battery charge unknown apm0: flags 30102 dobusy 0 doidle 1 pcibios0 at bios0: rev 2.1 @ 0xfd880/0x780 pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdf30/176 (9 entries) pcibios0: PCI Interrupt Router at 000:07:0 (Intel 82371FB ISA rev 0x00) pcibios0: PCI bus #1 is the last bus bios0: ROM list: 0xc/0x8000 0xc8000/0x1a00! 0xca000/0x1000 0xcb000/0x1000 0xdc000/0x4000! 0xe/0x4000! cpu0 at mainbus0 pci0 at mainbus0 bus 0: configuration mode 1 (no bios) pchb0 at pci0 dev 0 function 0 Intel 82443BX AGP rev 0x01 ppb0 at pci0 dev 1 function 0 Intel 82443BX AGP rev 0x01 pci1 at ppb0 bus 1 piixpcib0 at pci0 dev 7 function 0 Intel 82371AB PIIX4 ISA rev 0x08 pciide0 at pci0 dev 7 function 1 Intel 82371AB IDE rev 0x01: DMA, channel 0 configured to compatibility, channel 1 configured to c ompatibility atapiscsi0 at pciide0 channel 0 drive 0 scsibus0 at atapiscsi0: 2 targets cd0 at scsibus0 targ 0 lun 0: NECVMWar, VMware IDE CDR00, 1.00 SCSI0 5/cdrom removable cd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 2 pciide0: channel 1 ignored (disabled) piixpm0 at pci0 dev 7 function 3 Intel 82371AB Power rev 0x08: SMBus disabled vga1 at pci0 dev 15 function 0 VMware Virtual SVGA II rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) mpi0 at pci0 dev 16 function 0 Symbios Logic 53c1030 rev 0x01: irq 9 scsibus1 at mpi0: 16 targets sd0 at scsibus1 targ 0 lun 0: VMware, Virtual disk, 1.0 SCSI2 0/direct fixed sd0: 10240MB, 1305 cyl, 255 head, 63 sec, 512 bytes/sec, 20971520 sec total sd1 at scsibus1 targ 1 lun 0: VMware, Virtual disk, 1.0 SCSI2 0/direct fixed sd1: 20480MB, 2610 cyl, 255 head, 63 sec, 512 bytes/sec, 41943040 sec total mpi0: target 0 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1 mpi0: target 1 Sync at 160MHz width 16bit offset 127 QAS 1 DT 1 IU 1 pcn0 at pci0 dev 17 function 0 AMD 79c970 PCnet-PCI rev 0x10, Am79c970A, rev 0: irq 11, address 00:50:56:91:57:b6 pcn1 at pci0 dev 18 function 0 AMD 79c970 PCnet-PCI rev 0x10, Am79c970A, rev 0: irq 10, address 00:50:56:91:16:e8 isa0 at piixpcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 pmsi0 at pckbc0 (aux slot) pckbc0: using irq 12 for aux slot wsmouse0 at pmsi0 mux 0 pcppi0 at isa0 port 0x61 midi0 at pcppi0: PC speaker spkr0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 biomask e365 netmask ef65 ttymask ffe7 pctr: 686-class user-level performance counters enabled mtrr: CPU supports MTRRs but not enabled dkcsum: sd0 matches BIOS drive 0x80 dkcsum: sd1 matches BIOS drive 0x81 root on sd0a swap on sd0b dump on sd0b -- Fernando M. Braga +55 82 8802-9559
Re: vic(4) on ESX 3.0.2
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 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 Regards Piotrek
