Dear Community,
i'm new to grommunio... Ich have to change from Kopano Groupware and i want to try grommunio.
For that i tried to install the Appliance in a VM on Proxmox.
I booted the VM from the Appliance iso and ran the installscript. So fare so fine.
Upon reboot Proxmox claims that there is no bootable device...
That is my Proxmox VM config.
What am i doing wrong?

Thank you very much...

ps.
A search for Proxmox in the Forum did'nt turn up annything usefull to me...

    HBau die you Check the Boot order in the vm options to the scsi controller be the first?
    Rg Christian

    The settings look like standard which should work. I have a customer which uses Proxmox and there was no special configuration done.
    In Options-Bootorder should be scsi0 listed and activated tho (which should be true if you didn't tinker with it.).

    EDIT: AHH too slow!

    This is my Proxmox setting for a grommunio Appliance:

    Installed about 2 years ago.

    HBau changed the title to [SOLVED] Appliance does not boot in Proxmox after fresh install .

    Hi All,
    thanx for the Help.
    It had nothing to do with the boot order.... the HDD was not even recognised: "No Bootable device found"...

    But: I fixed it now.

    The trick was... i hade to install a different OS (Deb12) befor on the newly created virt.HDD... after that i booted from the Appliance iso and installes Grommunio over the now previosly installed OS.
    After that GRUB was properly initialized on the virt.HDD so that the VM is now booting. The HDD gets recognized, and the Appliance is booting.

    I have absolutely no idea, why just creating the VM an installing the appliance did not properly initialise GRUB in the first place. Something wrong in the RAW Immage in the Appliance.iso?
    But it was reproducable for me....

    Anny, how, now next steps in Testing :-)

    Thanx again for Help an Suggestiones.

    • crpb replied to this.

      Thats sounds odd, luckily i'm currently connected in a network with a proxmox 😀

      Well, that was quick and it works here.

      /etc/pve/nodes/pve/qemu-server/100.conf

      agent: 1,fstrim_cloned_disks=1
      boot: order=scsi0;ide2;net0
      cores: 4
      cpu: x86-64-v2-AES
      ide2: none,media=cdrom
      memory: 16000
      meta: creation-qemu=8.1.5,ctime=1717878211
      name: test
      net0: virtio=BC:24:11:5C:3C:CE,bridge=vmbr0,firewall=1
      numa: 0
      ostype: l26
      scsi0: nas-zfs:vm-100-disk-0,iothread=1,size=32G
      scsihw: virtio-scsi-single
      smbios1: uuid=aee9aa59-491b-4ad2-88d3-ad3fe9b051a9
      sockets: 1
      vmgenid: bd4f99a0-f016-40c8-afef-44a03c8aaddc

      HBau

      I suggest you try to install another vm just to see if it happens again.

      Hi crpb,

      thanx for the support!
      I must say, .... you see me speachless....
      I have a second Network at hand with a second Proxmox on which the fresh install from the Appliance.iso worked like a charme.
      None of my previous problems!
      Which i could reproduce sofar on the first system ... wich lead to me establishing this post in the first place...
      ...although i did nothing different...
      Right now i giv it a try again on the first Proxmox....

      ...ok...i don't know what to say... it worked on the first Proxmox now too....

      © 2020-2024 grommunio GmbH. All rights reserved. | https://grommunio.com | Data Protection | Legal notice