failed to start see systemct 1 status

[bloodthirsty]

I TRIED vmware and virtualbox. parrotos and kali linux.
i am facing the same issue.
the system starts i guess and before i can see login screen or anything, i see this.
PLS HELP ME!!!!

[mpack]

You cross posted this question to "Windows Hosts" and "Windows Guests", neither of which is a relevant forum. I deleted one post and moved the other to "Linux Guests".

This looks like a Linux guest. Is that correct?

If so, which Linux distro is it, and what is your VirtualBox question, precisely?

In fact, please post a VM log file. With the VM fully shut down, right click and "Show Log" in the GUI, save "VBox.log" (no other file) to a zip, and attach the zip here.

[bloodthirsty]

first of all, i want to thank u as u r the only one who replied.

i posted the issue in windows host as i am using vbox on windows.

i tried kali and parrot with vmware and vbox, but same issue.

i am sharing the zip file of vbox with parrot os.

once again thanks alot

[mpack]

Thanks for the log, however I still need to know what your VirtualBox related question is.

If you can indicate where you think VirtualBox is failing, I can probably help with that. I can't give you generic tuition on how to install Parrot OS because (a) I've never heard of it, and (b) I assume there must be Parrot OS forums to help out with that sort of thing.

[bloodthirsty]

this issue is not related to specific os. i am facing this issue in different vm soft and diff os s.
after import ova or create new machine using iso file,
installation is successfully done and the vm reboots.
but after it reboots and before i see any login screen or anything, i see this.

[mpack]

Well, it can't be a generic problem since the screenshot is Linux specific. And to be clear: I am seeing no problem with the VM, I AM seeing a problem with the guest OS, so again it can't possibly not depend on the guest.

One thing that does concern me is that you don't seem to have installed the guest OS. My guess is that you took a hard disk from an OVA, maybe renamed it from vmdk to vdi (invalid btw), then built a VM around it?

If you have an OVA or OVF then the way to get it into VirtualBox is using File|Import Appliance....

[bloodthirsty]

https://youtu.be/cKmFt93aZpM

[mpack]

I don't normally watch external videos, but I did so this time.

It has not caused me to change my opinion previously given: you have a specific problem with Parrot OS. You do not have a problem with VirtualBox. Approach the people who prepared the appliance, ask them what the messages mean.

[bloodthirsty]

first of all, thanks for replying.
and u r right, this is not a vbox problem as i am facing same issue with vmware.
but this is not an issue of parrot os as i am getting same issue for kali and ubuntu too.
what should i do

[mpack]

Kali is another guest I have no experience with, but if you can demonstrate the same problem with Ubuntu then I'd certainly be interested to see the evidence of that, i.e. a log file and screenshot.

Because, AFAIK there's no way you can have the same problem with Ubuntu. Definitely not if you install it from an official ISO - Ubuntu is almost certainly the most popular Linux guest around.

[bloodthirsty]

https://youtu.be/kgKUMM-ezxg
i see the command line if i press esc or arrow keys

[bloodthirsty]

This issue has been addressed by AMD. i am using their latest zen2 cpu and they have confirmed there are issues with linux. they have provided solution to my mobo company. waiting for a bios update.

[mpack]

A saw it was a Ryzen CPU and wondered if it was something like that. OTOH I know some people are using Ryzen's successfully - though perhaps not the latest version.

Thanks for reporting back.