IBM QRadar

 View Only

 IBM Qradar ISO file Installation on Virtual Box

Ebenezer Aibor's profile image
Ebenezer Aibor posted Fri March 28, 2025 04:59 PM

So I downloaded the latest version of the IBM Qradar Community Edition ISO file from the IBM official Website and after doing proper installation on virtual box , it is asking for  "LocalHost Login & password" which I didn't create any login or password during the installation process. I have tried all default logins possible no one is working. Even tried my normal laptop login and password maybe that's what it needs it still says incorrect . And from what I know about Qradar when you are promoted to login at first you just put in "root" and then click enter . It will ask you to create password. But mine is not asking to create password it's asking for a password like I already created one. I have researched and trouble shooted this issue trying to get the login but in not getting anything helpful so far . So please if you have the login for this or can offer any help , I'll really appreciate.

localhost Login request from Qradar
Jonathan Pechta's profile image
Jonathan Pechta

@Ebenezer Aibor I think this might help you. It isn't a virtual box configuration but a basic walk through of the installation steps from @Karl Jaeger. Take a look at this PDF for reference: https://community.ibm.com/community/user/security/viewdocument/qradar-community-edition-750-setu?CommunityKey=f9ea5420-0984-4345-ba7a-d93b4e2d4864

You should be prompted to create the password for root at installation time. So, I'm not sure if virtualbox created the user or what happened during your install. For example, I had VMware workstation install issues with CE when I tried to select "Typical" versus "Custom" install. I haven't tried on Virtualbox, but I believe there are a few YouTube videos on this topic. 

Karl Jaeger's profile image
Karl Jaeger IBM Champion

Ebenezer, as Jonathan has outlined already, Qradar should ask you for setting a password during install process. Shubham and I are just working on a similar installation issue in workstation 17.

There are so many things that possibly can go wrong during setup when you are not meeting requirements needed. My guess is that your setup did go "sideways" somewhere. What I can offer is a MS team session to have a look at your setup. Just write to my inbox if you like.