Tagged: homeserver 4.12 vm hyper-v
-
AuthorPosts
-
cavaParticipant2023-09-30 at 10:25Post count: 3
Bei mir läuft es unter ESXi auch nicht. Hab die genannten Parameter gesetzt, aber immer kommt forbidden
cavaParticipant2023-09-30 at 11:05Post count: 3Hier hab ich noch etwas gefunden und ich hab das ROM auch schon angepasst, aber auch das hilft nicht:
- This reply was modified 1 year, 2 months ago by cava.
masjerangParticipant2023-09-30 at 19:33Post count: 15Unfortunately my image is not patched to allow all MAC addresses and board.
I’ve tested it with qemu and VirtualBox with the below settings:qemu:
<sysinfo type=”smbios”>
<system>
<entry name=”product”>d3003</entry>
<entry name=”serial”>000ab3021111</entry>
</system>
</sysinfo>
<interface type=”direct”>
<mac address=”00:0a:b3:02:11:11″/>
<model type=”virtio”/>
<link state=”up”/>
</interface>Virtualbox:
on cli:
VBoxManage setextradata HS4 “VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial” “000ab3021111”
VBoxManage setextradata HS4 “VBoxInternal/Devices/pcbios/0/Config/DmiSystemProduct” “d3003”
And set the same MAC address on the proper ethernet interface.I’ll try to test with VMWare/ESXi as well.
AlbertParticipant2023-10-01 at 11:30Post count: 20Danke masjerang,
unter Virtualbox habe ich es jetzt auch hinbekommen.
Interessant wäre aber dennoch VMware und oder Proxmox muss hierfür auch nochmal probieren.
Vielen Dank auf jedenfall schon mal.
Grüße Albert
masjerangParticipant2023-10-01 at 12:18Post count: 15Hi Albert, good to hear you have it running.
Please find a new version at https://workupload.com/file/DGGaSFRk7st
In this version the firmware is patched to overcome the issue with VMWare. Note that every new version needs a new patch!
All credentials are the same as in the first post.kevkevevParticipant2023-10-01 at 21:32Post count: 22It works under Proxmox, thx👍
cicoParticipant2023-10-01 at 22:16Post count: 21<masjerang>
I tried your image but I got this :udhcpc: sending discovery
udhcpc: sending discovery
udhcpc: sending discovery
…. and after a while .. many other errors .. and WM not connect to the networkrobomovParticipant2023-10-01 at 22:48Post count: 3What are the correct hardware settings under Proxmox?
nazarevychParticipant2023-10-02 at 19:14Post count: 3Hi, It’s worked under Proxmox – just make sure you put correct Mac address as said before @masjerang and navigate to VM options -> Double click SMBIOS settings: fill the Product: and Serial: fields.
robomovParticipant2023-10-02 at 20:35Post count: 3Thanks.
The problem is a loop “dr.bcu2.py”, line 287, in Main OS Error: [Errno 5] Input/Output”. maybe a network problem?masjerangParticipant2023-10-02 at 21:02Post count: 15That is not an immediate issue. It should have network access, even with this error. After uploading your project, this error is gone.
Can you ping and/or reach it using SSH?sinn3rParticipant2023-10-03 at 08:39Post count: 368The errors “dr.bcu2.py” are just a problem of the default projekt. Just upload your own project are those are gone.
The @masjerjang image works with VMware, but not with Hyper-V. There’s the same error I receive with my image.
lebi1976Participant2023-10-05 at 17:18Post count: 45Das Image läuft bei mir aber leider dürften nicht alle notwendigen USB-Treiber integriert sein. Meine USB Schnittstelle funktioniert auf alle Fälle nicht. Wie ist das bei euch ?
- This reply was modified 1 year, 2 months ago by lebi1976.
sinn3rParticipant2023-10-05 at 18:42Post count: 368@lebi1976 Hier zum Testen mal mein aktueller Stand als vmdk-Image, es sollte alles laufen, was auch unter 4.11 funktioniert hat.
Download: https://workupload.com/file/PCUqZz6pFuNBeim Booten werden auch alle erkannten USB-Geräte gelistet (direkt nach dem Starten von Dropbear SSHD).
Hier kannst Du prüfen, ob Deine USB-Schnittstelle erkannt wird.Leider läuft das Image unter Hyper-V nicht, hier gibt es irgendein Treiberproblem.
sinn3rParticipant2023-10-07 at 14:46Post count: 368My 4.12 image is finally online:
-
AuthorPosts
- You must be logged in to reply to this topic.