Hacksudo ProximaCentauri - VM creation network problems

[celebrated-dustpan7999]

Good evening,

I'm having issues obtaining a network address while trying to load this vulnerable VM. 

I've downloaded the original zip file https://www.vulnhub.com/entry/hacksudo-proximacentauri,709/, extracted the OVA, converted the vmdk (qemu-img convert -O qcow2 filename.vmdk disk1.qcow2).  From there the setup is pretty straightforward, with the BIOS being set to SeaBIOS, the network source being virbr1 (see below) and as for the network models (virtio-net, virtio, e1000, etc...), I've tried all of them without success.

 

Of course I'm trying to set all of this is up in a virtualized network environment:

<network ipv4='yes'>
  <name>lab-network</name>
  <bridge name="virbr1" stp="on" delay="0"/>
  <ip address="192.168.2.1" netmask="255.255.255.0">
    <dhcp>
      <range start="192.168.2.2" end="192.168.2.254"/>
    </dhcp>
  </ip>
</network>

 

While the VM boots up, there is an error though, I'm not sure if it's related:

[      1.215639] shpchp 0000:01:00.0: pci_hp_register failed with error -16

[      1.216192] shpchp 0000:01:00.0: Slot initialization failed

 

And when logged into the VM, I can see a link but it is down

1: lo: ....

2: enp4s0: <BROADCAST, MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000

       link/ether 52:54:00:xx:xx:xx brd ff:ff:ff:ff:ff:ff

 

The MAC is the one that's generated from the VM page.

 

Anyway, the same ova file does work flawlessly on virtualbox, but for consistencies sake I'd like to have access to it on my unraid platform.  Has anyone else ran into the same type of issue and can help?

Thank you very much and have a nice day!

[misterc]

After having gone through the same procedure and ending up with the same issues, I landed on a thread in parrallels (https://forum.parallels.com/threads/vulnhub-vms-no-network.343746/) which describes the issue.  It seems the only way to solve is by actually logging on the virtual machine as root and changing the interfaces.  Logging in as root would sort of defeat the purpose towards actually rooting the box.
That being said I'm at a loss as well, and wonder if there is any way around this -- would there be a way to use the solutions proposed in (https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/) to feed the kernel inside the VM with net.ifnames=0 for example, which could solve the issue?