OVA on XCP-ng in boot loop

[Darkmelman]

Describe the issue you are experiencing

After all steps in the install manual for XCP-ng, after staring the vm, it shows the Bootloader-Menu but the blackscreen and after a short time reboots.

Describe the behavior you expected

Expect the system to boot up

Steps to reproduce the issue

1.Import VM to XCP-ng from .ova-File
2.Make all USB-Passtrough steps
3.Start the VM
4. View the Console

What is the version this bug report is based on?

3.75.7.20240420

Which base platform are you running?

ova (Open Virtual Infrastructure, AMD64/x86_64)

Which HomeMatic/homematicIP radio module are you using?

HmIP-RFUSB

Anything in the logs that might be useful for us?

Cant access the machine.

Additional information

No response

[jens-maus]

Please try to test with which version of RaspberryMatic this behavior started to appear.

[Darkmelman]

Hi! Yes, i will try it later. 3.75.6.20240316 is also affected. But I can't rule out that it's due to my XCP-ng... will try any other .ova File later.

[Darkmelman]

RaspberryMatic-3.73.9.20240130.ova is starting up!

[Darkmelman]

But "Starting HMServer..." is taking very long time and after that, there are the following errors:

ReGa "One of the Homematic devices is not resonding ."
BidCos-RF "One of the Homematic devices is not resonding ."
VirtualDevices "One of the Homematic devices is not resonding ."

Cant see the CCU or any other device...

Seems that the boot loop is only later on startup now. Unfortunately in XOA its not possible to send ALT+F2 in the console, so i cant see more details

[Darkmelman]

So, i have tested other releases and it seems that version "RaspberryMatic-3.71.12.20231014.ova" is working now.

[AxeSie]

Hello,
same issue here on my end. Also with xcp-ng in the boot loop
I need to go back to 3.73.9.20240130 and it starts booting.
When I apply an update or a new installation of any later version it fails.

Thank you very much.
Greetings

[github-actions]

There hasn't been any activity on this issue recently. To keep our backlog manageable we have to clean old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest RaspberryMatic version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[pgumpoldsberger]

Still having the same issue when trying to update to 3.77.7.20240826