Maquina Virtual Vmware

[Helen Drewski]

Zabbixvmware collector processes collect virtual machine data - the processes obtain necessary information from VMware web services over the SOAP protocol, pre-process it, and store it in Zabbix server shared memory.

If Zabbix server is compiled from sources, it must be compiled with the --with-libcurl --with-libxml2 configuration options to enable virtual machine monitoring. Zabbix packages are compiled with these options already enabled.

It is recommended to enable more collectors than the number of monitored VMware services; otherwise, the retrieval of VMware performance counter statistics might be delayed by the retrieval of VMware configuration data (which takes a while for large installations).

Generally, the value of StartVMwareCollectors should not dip below 2 and should not exceed twice the amount of monitored VMware services: Amount of services

Note that the required number of collectors also depends on the scope of the VMware environment, and the VMwareFrequency and VMwarePerfFrequency configuration parameters.

Zabbix can use low-level discovery rules (for example, vmware.hv.discovery[$VMWARE.URL]) to automatically discover VMware hypervisors and virtual machines. Moreover, Zabbix can use host prototypes to automatically generate real hosts for the discovered entities. For more information, see Host prototypes.

Zabbix includes a range of ready-to-use templates designed for monitoring VMware vCenter or ESXi hypervisors. These templates contain pre-configured low-level discovery rules, along with various built-in checks for monitoring virtual installations.

For the correct functioning of the VMware FQDN template, each monitored virtual machine should have a unique OS name adhering to FQDN rules. Additionally, VMware Tools/Open Virtual Machine tools must be installed on every machine. If these prerequisites are met, using the VMware FQDN template is recommended. The VMware FQDN template has been available since Zabbix 5.2 with the introduction of the ability to create hosts with custom interfaces.

A classic VMware template is also available and can be used if FQDN requirements are unmet. However, the VMware template has a known issue. Hosts for discovered virtual machines are created with names that are saved in vCenter (for example, "VM1", "VM2", etc.). If Zabbix agent is installed on these hosts, and active Zabbix agent autoregistration is enabled, the autoregistration process will read host names as they were registered during launch (for example, "vm1.example.com", "vm2.example.com", etc.). This can lead to the creation of new hosts for existing virtual machines (since no name matches have been found), resulting in duplicate hosts with different names.

The data collected by the vmware collector processes can be logged for detailed debugging using debug level 5. The debug level can be configured in the server and proxy configuration files or using the runtime control option -R log_level_increase="vmware collector,N", where "N" is the process number.

Hi, I have quartus web edition running on my linux machine using a window xp virtual machine. The VM that I am using is VirtualBox. I was able to get the usbblaster to "bridge" and be recognized enough by windows to request and install the usb blaster drivers. However when I try to do an auto detect on my cyclone 3 starter board I just get a messagebox window with "Unable to scan device chain. Can't scan JTAG chain". Quartus on the VM does seem to find the USB blaster, but seems unable to use it. Does anyone have any insight? Maybe I could just build sof files on the virtual machine and download to the cyclone 3 with some linux utility ? Any insight appreciated.

yes, you can use the command-line programmer under linux without a quartus license. I'm using this to do the reverse of you, running the nios II IDE in a linux guest on a vista host. USB connection is working fine for me inside virtualbox. (in fact if windows sees and installs the driver, it's most probably your quartus settings that are off)

at the moment i'm having the same problem running the quartus II 8.0 programmer in a windows XP virtualbox guest-OS. in an other VM which runs a ubuntu 7.10 (yeah i konw, pretty old) the USB bridge works well. therefor i think it's more likely that winXP resp. quartus II has a problem with the bridged usb-interface.

The virtualbox USB driver definately does suck, but I've never had windows/quartus detect the Blaster but not be able to use it. The problem's always that the USB Blaster somehow disappears (I think the screensaver sets this off) and then i have to disconnect inside VB, disconnect the cable, reconnect the cable, and reconnect inside VB. Ugh. I should switch to vmware but VB is so damn good otherwise...

I find it much easier to use the standalone programmer on a physical host. And connect from the Quartus virtual machine to the jtag server using TCP/IP. Like this you don't install any USB drivers on the virtual machine at all.

i agree with you alex! VB is indeed a pretty good tool ;) but what does the procedure you explained do? are you able to use the usb blaster after this procedure? @vjAlter: thats a quite a good idea, is there any tutorial available which shows how to setup a standalone programmer with JTAG-server in linux?

Yes, I'm able to use it again. If I don't follow this procedure, if I just try to disconnect/reconnect the USB Blaster inside VirtualBox's Devices menu to try to get the VM to detect it again it doesn't work and VB throws some sort of error dialog related to USB. After that, I must restart the whole computer to get it to stop throwing that dialog. This is on a 32bit Vista SP1 host. On Vista 64bit I get a BSOD when I try USB.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

3a8082e126