ova problems

Crazytoo

The image that i load is from this website this
https://www.ibm.com/community/qradar/ce/

and i am using til
xo-server 5.74.0
Xen Orchestra server

xo-web 5.77.0
Xen Orchestra web client

Crazytoo

When i load it in the xcp-center there is an error on vm version 15 that it does not recognize

but when i load it in orchestra it successfully imports but it the vm does not work

olivierlambert

So XOA import works. You are a bit vague on "the VM doesn't work". Can you be more specific? I mean, it's hard to assist with only that data.

Crazytoo

The vm does not work !!!!!
it does not start
but thanks for that....

Crazytoo

it does not look like the vm recognize the partition struckture or boot secktor as missing

the whole thing works in my vmware fusion without any problems

olivierlambert

Please re-read my post. Now we evacuated the OVA import issue, it's a problem of having the operating system to load.

You can use a live CD (like Ubuntu) in the VM and try to see what can you see inside the VM disk.

Crazytoo

@olivierlambert said in ova problems:

Please re-read my post. Now we evacuated the OVA import issue, it's a problem of having the operating system to load.

You can use a live CD (like Ubuntu) in the VM and try to see what can you see inside the VM disk.

Okay so if the system does not load on xcp-ng when i import it from a ova the xcp-ng system works ??

the ova works everytime i load it in fusion so it is not an image failior so therefor it must be xcp-ng that cant handle it.

or am i missing something ?

Also i have vms already running on my xcp-ng

HeMaN

@crazytoo So this image is not working, that was clear from your first post.
If you want suggestions how to get it going you need to provide details about your setup, and provide answers to the questions asked. Otherwise nobody will be able to help.

so far you only answered the xoa version you are using...

Crazytoo

@heman never mind i will switch back to vmware.
i now see what i am facing with this product and the support
thanks for your help

HeMaN

@crazytoo support is pretty good here but they are not in the possession of a crystal globe.
for things to get solved answers are needed, not only on the solution but even more on the issue at hand to be able to reach a solution

olivierlambert

So I would say problem solved Good bye and good luck

Crazytoo

@olivierlambert
no that is not solved
but what i find wiered is the way that you keep saying that everything is fine when i cant find any error logs and when i try to supply some info about the systems you just end up giving me a virtual middle finger and thats is a bigger problem in opensource projects
so no it is not solved and there is still an issue with Ibm qradar ova import

Forza

@crazytoo People here are just trying to help. Terms like "not working" are not enough for us to pinpoint where things are failing.

You mention that the VM boots but shows some error during the boot. Can you provide a screenshot from there? To me it sounds like the boot loader is looking for a specific device name/path and cant find it. remember that different hypervisors show different paths to devices and that bootloaders and other parts of the OS may not work without re-configuring the storage settings inside the guest.

For example:

Virtualbox: /dev/sda
XCP-ng/Xenserver: /dev/xvda
VMWare Workstation: /dev/sda

Another issue could be sector size. VMWare Fusion supports 4KiB sectors (A.K.A Advanced format), whereas XCP-ng does not.

Crazytoo

@s-pam
off cause
th vm or ova is created from vmware fusion so that must be it.

the os is centos 7
do you know how i fix this ?

Forza

@crazytoo Best way to be sure it to boot the VM using a live-cd, for example systemrescue-cd or ubuntu live-dvd. Then you can use tools like gparted to inspect your disk image from inside the booted vm.

Crazytoo

@s-pam got it loading it now

Crazytoo

@s-pam
tried it but cant seem to figure it out
it is a centos 7

olivierlambert

@s-pam said in ova problems:

@crazytoo Best way to be sure it to boot the VM using a live-cd, for example systemrescue-cd or ubuntu live-dvd. Then you can use tools like gparted to inspect your disk image from inside the booted vm.

That's exactly what I advised to do earlier, but it seems it was missed the first time I think that's the best approach to understand what's going on in the VM disk.