Why You Need Log Files? Log files are keys to resolving problems in any IT system, why?! You are unable to troubleshooting without having log files. Any enterprise system must have logging system and logging is very important to IT administrators. Log location is very important for IT administrators even very importantly. Oracle VM Server log files locations are listed in the following table: Log File Directory Description xend.log /var/log/xen/ Contains a log of all the actions of the Oracle VM Server daemon. Actions are normal or error conditions. This log contains the same information as output using the xm log command. xend-debug.log /var/log/xen/ Contains more detailed logs of the actions of the Oracle VM Server daemon. xen-hotplug.log /var/log/xen/ Contains a log of hotplug events. Hotplug events are logged if a device or network script does not start up or become available. qemu-dm.pid.log /var/log/xen/ Contains a log for each hardware virtualized guest. This log is created by the quemu-dm process. Use the ps command to find the pid (process identifier) and replace this in the file name. ovs-agent.log /var/log/ Contains a log for Oracle VM Agent. osc.log /var/log/ Contains a log for Oracle VM Storage Connect plug-ins. ovm-consoled.log /var/log/ Contains...
Oracle VM Server installer using the below algorithm to set default memory size for dom0: dom0 Memory = 502 (MB) + (Physical Memory (MB) * 0.0205) As an example, your physical server has 256 GB memory, dom0 needs to 5.7 GB memory. If you didn’t assign enough memory to dom0, you will face with serious performance issues. So calculating dom0 memory is very important for preventing performance issues on your virtual machines. Also you can change dom0 memory size by the below instruction: Edit your grub configuration on the Oracle VM Server to adjust the value for the dom0_mem parameter. If you are using UEFI boot, the grub configuration file is located at /boot/efi/EFI/redhat/grub.cfg, otherwise the grub configuration file is located at /boot/grub2/grub.cfg. Edit the line starting with multiboot2 /xen.gz and append the required boot parameters. For example, to change the memory allocation to 1024 MB, edit the file to contain: multiboot2 /xen.gz dom0_mem=max:1024M placeholder ${xen_rm_opts}
You will need to a backup solution in virtual environments same as physical environments. There is many backup solutions for VMware vSphere, Nakivo or Veeam are third-party solutions. Also Veeam is best third-party solution Hyper-V platform. But if you are implementing Oracle VM, you need to know, what is best backup and restore solution for this platform. Below are some partners with currently supported data protection solutions: Acronis with Acronis Backup Advanced Actifio with Actifio Sky. Actifio Sky for Oracle Cloud is available in Oracle Cloud Marketplace Asigra with Asigra Cloud backup Zmanda, a Carbonite company with Amanda Enterprise Arcserve with two backup products: Arcserve Backup and Arcserve Unified Data Protection Barracuda Networks with Barracuda Backup CloudBerrry Lab with CloudBerry Backup. CloudBerry Explorer provides a user interface to Oracle cloud storage Commvault with Commvault Software (formerly Simpana) Dell with Rapid Recovery and NetVault EMC with its Data Protection Suite (DPS), with Avamar and NetWorker as key components FalconStor Optimized backup (VTL & NAS) Hewlett Packard Enterprise’s Data Protector; StoreOnce R1Soft with Server backup Manager SEP with Sesam Storware with vProtect Storix System Backup Administrator Veritas Technologies with Backup Exec and NetBackup, available in the Oracle Cloud Marketplace
it seems, there is incompatibility issue between Windows Server 2008 R2 and VMware Ballooning driver and it’s cause of stop error on Windows: Stop A: 0xA As Microsoft describe in its KB, the issue is happening when ballooning activated on virtual machines that use NUMA. So, we know that NUMA can improve our machines performance by grant local access to memory. You can read my post about NUMA for more information: NUMA and vNUMA: Back to the Basics for Better Performance Microsoft has released a hotfix for fixing this issue on Windows Server 2008 R2. It’s strongly recommended to download and install the hotfix on all your virtual machine that those have Windows Server 2008 R2 as guest OS. You can download the hotfx from the below link: Hotfx Download
Which server brand do you use? HPE, Dell, Fujitsu or any other. It doesn’t matter, you should check your server compatibility with new vSphere version before planning for migration or upgrade. I don’t want to share server list because the list will be different during time and new servers will be added to the list. You can find supported servers in VMware Compatibility Guide and it’s best reference for servers compatibility. Also you can check it on OEM web sites: HPE: VMware Support Matrix Just you should choose your ESXi version on the web page and trust to the result! Dell: Virtualization Solutions Choose VMware ESXi version and then should click on “Manual” and download a PDF which contains list of compatible servers. Cisco:UCS Hardware and Software Interoperability Matrix Tool (New) just you should select some items to find proper result. Also you can use older tools: Hardware and Software Interoperability Matrix Utility Tool Fujitsu: I couldn’t find a tools on their web site and we have to download a PDF file and find our product. Sample link for FUJITSU Server PRIMERGY: x86 Servers released OS Lenovo (IBM): OS Interoperability Guide I know, there is more OEM vendor and may...
