nice vid. btw the "ip a" command shows the altname of the interface. helps to check before editing the /etc/network/interfaces
@lowspeclabs6 ай бұрын
Thanks for the info!
@_cissp3 ай бұрын
Hey Man! Awesome guide! The one thing I'm missing - how have you got the access to remote screen 7:09? After qemu-system-x86_64 nothing happens for me, and I assume you started something additionally?
@lowspeclabs3 ай бұрын
You'll need a vnc app, something like tiger vnc or rnvc on windows or virtviewer on linux.
@ИгорьПушистиковАй бұрын
Good manual, and you are funny in the comments! Please tell me, what program in video do you use for SSH-connections?
@paulbundy0728 күн бұрын
Bitvise
@hamdijedidi63755 ай бұрын
hello bro i followed ur old video when i came to reboot the instance i cannot access it anymore ssh i keep getting access denied any ideas please
@lowspeclabs5 ай бұрын
Check the interface name, that was my roadblock. The interface name changes during reboot, another tip is to boot up the hetzner console and manually change the interface name from there after reboot
@TheXSairam2 ай бұрын
Why not simply use the KVM, since its free for 3 hours?
@lowspeclabsАй бұрын
That involves talking to people and waiting 😂
@domjag6006 ай бұрын
Why not just type installimage in rescue mode select other and select the os. It will automatically install proxymox
@lowspeclabs6 ай бұрын
That version does not support zfs as a root fs, it uses ext4 for the root fs if I remember correctly. Doesn’t fit my use case
@domjag6006 ай бұрын
@@lowspeclabs I know that when I installed it there was an option to select ZFS but I just went with the default. Whether it works or not with ZFS I don't know but the option is there
@lowspeclabs6 ай бұрын
@@domjag600 Thank you for the info, I'll add it to the top of the video as an alternative solution.
@nsuneirl4 ай бұрын
Thanks for the video. After install, "-bios /usr/share/ovmf/OVMF.fd" this wasn't working for me. Trying the second command without that parameter did work. It went into GRUB then I was able to log in as root. Cheers
@ulrichbeutenmuller81014 ай бұрын
Same issue here. Omitting the -bios command let the VM boot up just fine.
@lowspeclabs4 ай бұрын
This guide is for newer hertzner boxes, the newer ones (8 core Ryzen 7 series) use uefi instead of bios. Hence the need to pass through the uefi bios(omvf.fd). It sounds like the box hertzner assigned you is one of the old ones or uses a motherboard that configured for bios instead of uefi. Glad you got it running regardless