I'm trying to find where it documents the minimum memory requirements for the Worklight analytics component.
I can see the disk space and the fact that it needs a 64-bit Linux or AIX platform but no mention of memory. (http://www-01.ibm.com/support/docview.wss?uid=swg27024838)
Have I just missed it somewhere?
The reason I ask is that I've just installed it on a Red Hat 6.2 vm and it complained that it needed to have 8GB minimum before I could install it. Easy enough for me as I installed on a VM, but it wouldn't have been had I tried to install it on a physical server if I didn't know before hand.
I need to send the requirements to an operations team and I'd like to know where I can point them to the full hardware requirements.
You can find system requirements specification for Operational Analytics here
Look at the Operational Analytics Getting Started Module on slide 9 or in IBM Information Center here.
From the document:
* Supported operating systems:
– AIX V6.1 and V7.1 on ppc 64-bit
– Red Hat Enterprise Linux (RHEL) 6 Server editions on x86-64
– Red Hat Enterprise Linux (RHEL) 5 Update 6 Advanced Platform on x86-64
– SUSE Linux Enterprise Server (SLES) 10 and 11 on x86-64
* 200 MB of disk space for installation
* 8 GB of RAM required
* Local file system with minimum
* 100-GB disk space (ideally more)
* Python 2.6.x or Python 2.7.x
* Root access for installation
* Ability to open firewall ports
Related
I am using VMWare Workstation 14, with Windows Server 2016 installed on it. A few weeks ago in my server class, we had an in class lab to setup a Nano Server. I successfully got that up and running and installed Hyper-V and loaded it into it. Started up, and signed in. Then two days later at class again, the VM just freezes at the windows logo with circling white dots.
I have installed multiple VMs trying to get it up and running. Always the same result. I have the virtualization enable in BIOS on my laptop.
I have a VM snapshot I just took before installing Hyper-V, installed the role, rebooted, and again, stops at the windows logo with circling dots.
I don't know where to check if there is an issue, or if something is configured incorrectly. I am just looking for some help and ideas on what I should check. I do also have the virtualization stuff within VMWare enabled under the properties for the VM.
System details:
Asus GL502VMZ
Version 10.0.17134 Build 17134
Processor Intel(R) Core(TM) i7-7700HQ CPU # 2.80GHz, 2808 Mhz, 4 Core(s), 8 Logical Processor(s)
Installed Physical Memory (RAM) 16.0 GB
NVIDIA GeForce GTX 1060 3GB
Have you tried uninstalling the anti-virus? I was running into the same issue in my server class (Using VMware to run server 2016 which we where using to nest hyper-v)until a class mate said he didn't have the AV (we where looking for differences on why his worked and mind didn't). I removed my AV (was AVG) now the server no longer stalls at the boot screen.
Just my 2 cents that may help someone in the future. I had the same issue on an HP Proliant ML310e that worked fine for the full install until enabling the Hyper-V role, then it would hang at the Windows icon screen with the swirling dots. I was able to get past that by disabling Intel VT-d in the bios. Not a particularly good solution, but it allowed the system to boot successfully and run normally.
My computer is Windows7 64bit , RAM : 4Gb , Processor : Core2 Duo 2.26 GHz. When I launch the start-pentaho batch file ( biserver-ce-6.1.0.1-196 ) then the console exits after a while when the system is initialized. So I wondered my computer lacks some requirements. So what is the minimum system requirements to launch the server ?
The Pentaho server is hardware-independent and runs on server-class computers that comply with these specifications for minimum hardware and required operating systems:
Hardware -64 bit
Processor: Intel EM64T or AMD64 Dual-Core
RAM: 8 GB with 4 GB dedicated to Pentaho servers
Disk Space: 20 GB free after installation
Operating System—64 bit
Microsoft Windows 2008 Server R2 & 2012 Server R2
CentOS 6 & 7
Red Hat Enterprise 6 & 7
Ubuntu Server 14.04 LTS & 16.04 LTS
SUSE Linux SLES 11 (SP3+)
Workstation
These Pentaho design tools are hardware-independent and run on client-class computers that comply with these specifications for minimum hardware and required operation systems.
Pentaho Aggregation Designer
Pentaho Data Integration
Pentaho Metadata Editor
Pentaho Report Designer
Pentaho Schema Workbench
Hardware
Processors:Apple Macintosh Dual-Core Intel EM64T or AMD64 Dual-Core
RAM: 2 GB RAM for most of the design tools, PDI requires 2 GB dedicated
Disk Space: 2 GB free after installation
Minimum Screen Size: 1280 x 960
Software
Microsoft Windows 7, 8, & 10
Ubuntu Desktop 14.04 LTS & 16.04
OS X 10.11 & 10.12
From: https://help.pentaho.com/Documentation/7.1/0D0/160/000
My virtual machine of 64-bit Debian 7.5 (wheezy) was working in VirtualBox 4.3.12r93733 on a Windows 8.1 Pro (64-bit Operating System, x64-based processor: Intel(R) Xeon(R) CPU E5-1620 v2 # 3.70GHz 3.69 GHz) machine (Dell Precision T3610) yesterday. But when I tried it this morning I got an error message saying: VT-x/AMD-V hardware acceleration is not available on your system. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot. I chose to continue but as promised I made it as far as choosing between system modes (regular or recovery) before the screen blacked out.
When I searched this message online I found answers saying to make sure the BIOS had virtualization enabled. My BIOS has 3 options under Virtualization Support: Virtualization, Virtualization for Direct I/O, and Trusted Execution. The first two were enabled but the last was not. (This is a work machine, so I am hesitant to load defaults without speaking to someone from IT first.)
Aside from downloading and initiating an install for Visual Studio Express 2012 (which has since been uninstalled), little has happened on this machine since the Debian virtual machine was last working. So I also investigated and uninstalled the Windows Updates from yesterday on, in case they were involved. (One in particular mentioned having to fix the BIOS.) The ones that were marked important, including the one that fixes BIOS, have been reinstalled.
At this point I started looking into VirtualBox's settings. In my online research I found several forum posts recommended going into Settings->System->Acceleration, a tab that is greyed out for me. While at Settings->System->Motherboard, I noticed my pointing device was set to USB Tablet. When I changed it to PS/2 Mouse and tried the VirtualBox again, the error message went away but the OS still does not successfully boot.
My most recent revelation happened after this: Under Settings->General->Basic, I noticed my version was set to Ubuntu (32 bit), even though I am sure it was at Debian (64 bit) yesterday. But only 32-bit OS's are options, when my machine ought to be capable of having 64-bit ones too.
My question is: What could have caused VirtualBox to lose all 64 bit options, including a working Debian (64 bit), overnight?
You probably have had Hyper-V installed and enabled.
Cross check and Disable the setting from :
Control Panel >> Programs and Features >> Turn Windows features on or off
Reference : https://forums.virtualbox.org/viewtopic.php?f=6&t=57926
try this on virtualbox:
go to your virtual machine setting (right click on VM icon > setting) then go to system > acceleration and ensure that "Enable VT-x/AMD-V" checkbox is checked.
I'm trying to get my Android Emulator running faster,
but i can't enable virtualization. When i open
bios, it saids that it is enabled, but when i run Intel Processor Identification Utility, it display "Supporting advanced intel processor technologies: Intel(R) Virtualization Technology: no" . But when i look at the page about my processor on intels page, it saids that my processor supports virtualization
About my machine:
Dell Studio 1749
4 GB Ram
Intel Core i5-450M CPU (specifications)
Windows 8 64bit
Thank you all!
I found the solution!
In Windows 8 i need to disable Hyper-V.. I don't know why.
Hyper-V uses the VT resources and if they are already being used by another process then they will not be available for HAXM to use.
How can I run Windows RT (the restricted ARM version of Windows 8) in an emulator, for development purposes? This question contains two parts:
Obtaining the image: Does an installation image exist (for vendors, in MSDN, ...)? Can I take a snapshot of the Surface RT disk (how?), or can I extract it somehow from recovery data (I don't know how the recovery system works, but there's a function to wipe and reinstall the software on the Surface completely).
Running the image: What can I emulate it on? I've heard about QEMU, but it has the reputation of being slow. Also, the program must emulate the neccessary hardware (Tegra-3).
I'm aware this question was asked 9 years ago, but now it's possible to emulate Windows RT in patched QEMU 6.2.0, you can also read more about the work being done for it.
The repo with downloads is here: https://github.com/binarymaster/qemu/releases
Please note that there is no audio, no network, and no GPU acceleration supported. Although you can have network connection with Windows 10 ARM, just read my previous answer below.
Answer from May 13, 2020:
I'm aware this question was asked 7 years ago, but now it's possible to emulate Windows on ARM in the latest QEMU 4.2.0.
Steps to follow:
Patch QEMU to report EL3 TrustZone available: https://github.com/TeoIzAwezome/rtemu/commit/0f8b8ec18725cd0f66a39b5520fb6a435a757f95 - if you're using Windows and don't want to build QEMU from source, you can patch qemu-system-arm.exe : replace this hex sequence with NOPs 4531C931D24C8D05BE515C004889F1E87AD82E00 => 9090909090909090909090909090909090909090 - it replaces this part:
Download Linaro firmware for QEMU 32-bit ARM platform, specifically 15.12 version which is the last one that boots Windows on ARM without problems: https://releases.linaro.org/components/kernel/uefi-linaro/15.12/release/qemu/QEMU_EFI.fd
Download an ESD image of Windows RT 8.1, these are publicly available from Microsoft.
You can find download links here https://tech.myonlylonely.com/wimboot-for-surface-2-en/
or by using Google with this string: 9600.17053.winblue_refresh.141120-0031_woafre_client_CoreARM_O15_en-us-IR5_CCSA_WOAFRER_EN-US_ESD_2F1E1C773E39C4672F52B1F3A0AE7844FD837B23.esd
Either convert ESD to ISO or just extract it with esd-decrypter-wimlib-8.7z : https://www.tenforums.com/software-apps/27180-windows-10-recovery-tools-bootable-rescue-disk-2.html
You will need VirtIO drivers for QEMU compiled for 32-bit ARM platform, precompiled viostor.sys driver is available here https://www.betaarchive.com/forum/viewtopic.php?f=62&t=40522 - if you built drivers yourself in Visual Studio, make sure to create catalog files by using Inf2Cat /driver:C:\Drivers\ /os:8_ARM,6_3_ARM and test-sign them (all .cat and .sys files); once drivers are ready, you can slipstream them into boot.wim and install.wim by using dism /Mount-Wim + /Add-Driver + /Unmount-Wim
If you don't want to boot and install from ISO, you can create a VHD/VHDX disk image and format/partition it the same way as it's done for Windows installation on UEFI systems — GPT partitioning: EFI partition - FAT32, MSR partition, Primary partition - NTFS. Use dism /Apply-Image with install.wim to install Windows files to created disk, and bcdboot to install EFI files
Since you're using test-signed drivers, you need to tweak BCD file on EFI partition:
set BCD=E:\EFI\Microsoft\Boot\BCD
bcdedit /store %BCD% /set {globalsettings} testsigning on
bcdedit /store %BCD% /set {globalsettings} nointegritychecks on
Once everything is done, start QEMU with these parameters:
set HDD=windows-on-arm.vhd
set ISO=en_windows_8.1_ir4_ARM_dvd.iso
qemu-system-arm ^
-M virt ^
-cpu cortex-a15 ^
-smp 2 ^
--accel tcg,thread=multi ^
-m 2G ^
-bios QEMU_EFI_1512.fd ^
-device VGA ^
-device ich9-usb-ehci1 ^
-device usb-kbd ^
-device usb-tablet ^
-drive if=virtio,file=%HDD% ^
-device virtio-scsi-pci,id=scsi0 ^
-device scsi-cd,drive=install,bus=scsi0.0 ^
-drive if=none,format=raw,id=install,file=%ISO%,readonly=on ^
-rtc base="2013-07-15",clock=vm
Notes:
There is known problem with PCI MMIO area, and USB input wouldn't work because of it. You can workaround that by replacing -M virt with -M virt,highmem=false however with this option Windows 8.1 RT will throw BSOD with code SYSTEM_THREAD_EXCEPTION_NOT_HANDLED.
It's known Windows 10 for ARM does not throw this BSOD code and works in QEMU pretty well with -M virt,highmem=false. You can use Google to get it: 10.0.15035.0.rs2_release.170209-1535_armfre_client-enterprise_volume_en-us :
Also note that full emulation of 32-bit ARM is very slow even on Intel Core i7-8700 # 3.2 GHz, so it's better to use some modern ARM board like Raspberry Pi 4 that have hardware accelerated KVM hypervisor.
Windows for 32-bit ARM is already considered legacy, better switch to AArch64 aka Windows for ARM64, see https://withinrafael.com/2018/02/12/boot-arm64-builds-of-windows-10-in-qemu/
There's no way to truly emulate a Windows RT enivonrment on ARM. You have two options...
1) Go pick yourself up a Surface tablet.
2) Contact your local Microsoft Technical Evangelist to see if they have loaner hardware available.
Also, chances are your local Microsoft Evangelist team is holding Windows 8 developer events where they may have test hardware on hand for you to try. If you're in the US, you can find a list of these events at http://msdnevents.com.