IceWhaleTech/ZimaOS

[Info] Installation on Proxmox VE 8.0.4 as a VM

silycr opened this issue · 15 comments

silycr commented

[Info]

Notes for installation onto Proxmox VE 8.0.4 as a VM of the ZimaOS Beta as at v0.4.8.1

  1. Download latest ZimaOS .img.xz file
    a. Either download directly to Proxmox /var/lib.vz/images and unzip .xz
    b. or like me, downloaded to PC, unzipped with 7zip and transferred ~4GB file with WinSCP.
  2. Create new VM in Proxmox. Other than the information below, the rest of the settings are your own to choose.
    • OS
      -> Select ‘Do not use any media’
      ->Guest OS = Linux and 6.x – 2.6 Kernel
    • System
      -> BIOS = OVMF (UEFI)
      -> Add and select the EFI storage location
      -> SCSI Controller = VirtIO SCSI Single
    • Disk
      -> Choose an option here:
      Delete the default disk, and only the OS will be installed later
      Increment to scsi 1 and use disk as storage. OS will be on a separate disk later
  3. Mount image to VM Disk. Enter the Promox Server shell, either by ssh or GUI.
    • Confirming the file details. $ qemu-img info /var/lib/vz/images/{FILENAME}.img
      -> Replace {FILENAME}
    • Import the .img to the VM $ qm set {VM_ID} --scsi0 {LOCAL_STORAGE}:0,import-from=/var/lib/vz/images/{FILENAME}.img
      -> Replace {VM_ID} and {FILENAME}
      -> For example $ qm set 999 --scsi0 local-zfs:0,import-from=/var/lib/vz/images/zimaos_zimacube-0.4.8.1.img
  4. Adjust Boot Order
    • On the VM, select Options and change the boot order to scsi0
  5. Disable SecureBoot
    • As per, https://www.youtube.com/watch?v=js_Xoa0f8zM
      -> Select console, Start the VM and mash the esc key
      -> Device Manager >> Secure Boot Configuration >> Attempt Secure Boot >> Enter (to disable)
      -> Escape and exit

ZimaOS will now boot. It will not display the IP address in the console, so you’ll need to find that yourself or use the application linked in the original instructions.

rucknapucknavitz commented

Thanks for this! I did find that I needed a “double -“ before scsi like so $ qm set {VM_ID} --scsi0

  • 👍2
silycr commented

Thanks for this! I did find that I needed a “double -“ before scsi like so $ qm set {VM_ID} --scsi0

Spot on, Thank you. Formatting in the comment changed -- to long –. I've just updated.

Lauren-ED209 commented

Thank you very much for organizing this. May we repost your tutorial?

silycr commented

Yes, more than welcome

  • 👍1
raller1028 commented

@silycr
img_v3_0255_46386026-741c-44e0-9572-587fac0635bg
We'll show more in version 0.4.9.1, what do you think of this display?

  • 👍1
silycr commented

@raller1028

Very useful. The WebGUI port would be handy as well.

Particularly for some of us that happen to forget which non-standard port we change it to last time we had to type the IP

jerrykuku commented

The default port 80 is hidden, but will be shown once other non-standard ports are used.

  • 👍2
KOPElan commented

按照以上步骤，在创建用户的时候提示 Fail，无法创建用户。
屏幕截图 2024-05-10 121204

heliveth commented

按照以上步骤，在创建用户的时候提示 Fail，无法创建用户。 屏幕截图 2024-05-10 121204

我也遇到同样的问题，无法创建用户，请问怎么解？

steveof2620 commented

I have it installed and running (on Proxmox). When I go the webUI it asks me to create an account. Every time I try to create one it just says "Fail". No idea why. Is there something specific I am supposed to enter?

steveof2620 commented

Can anyone shed some light on to this? Why can't I create an account as prompted?
Screenshot 2024-06-17 at 10 07 31

jarno9981 commented

Can anyone shed some light on to this? Why can't I create an account as prompted?

its actually a os problem Failed to load resource: the server responded with a status of 401 (Unauthorized)Understand this error
/v2/users/events:1

   Failed to load resource: the server responded with a status of 401 (Unauthorized)Understand this error

/v2/zimaos/connect/status:1

   Failed to load resource: the server responded with a status of 401 (Unauthorized)Understand this error

/v1/users/refresh:1

   Failed to load resource: the server responded with a status of 401 (Unauthorized)Understand this error

index-6f2f0d83.js:3 Unauthorized, logging out ... null
Y @ index-6f2f0d83.js:3Understand this warning
index-6f2f0d83.js:3 Unauthorized, logging out ... Error: 401 Unauthorized
at Y (index-6f2f0d83.js:3:13910)
at index-6f2f0d83.js:3:14262
at async Home-e82edb01.js:116:25095
Y @ index-6f2f0d83.js:3Understand this warning
Home-e82edb01.js:116 Error: 401 Unauthorized
at Y (index-6f2f0d83.js:3:13910)
at index-6f2f0d83.js:3:14262
at async Home-e82edb01.js:116:25095
Home-e82edb01.js:16 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'createElement')
at HTMLDocument.get [as createElement] (Home-e82edb01.js:16:33201)
at st (Home-e82edb01.js:16:36044)
at Home-e82edb01.js:23:12436Understand this error
/v1/users/register:1

   Failed to load resource: the server responded with a status of 500 (Internal Server Error)
  • 👍1
jarno9981 commented

Request URL:
http://192.168.2.18/v1/users/register
Request Method:
POST
Status Code:
500 Internal Server Error
Remote Address:
192.168.2.18:80
Referrer Policy:
strict-origin-when-cross-origin

megastary commented

I also had the user registration Fail error mentioned by @jarno9981 and @steveof2620.
Resizing the imported disk fixed the issue. (I added 12GB, but you probably don't need that much)

  • 👍1