Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

No Bootable Device

uncu
2012-06-08
2013-04-13
  • uncu
    uncu
    2012-06-08

    Hi Matt,

    Last time I have problem for vncviewer localhost :1 and I have been resolve that problem with comment
    #vncviewer <IP Address Server> :1 (I changed the localhost with IP Address Server)

    This is the log :
    root@ubuntulucid-laptop:~# vncviewer <IP Address Server>:1
    Connected to RFB server, using protocol version 3.8
    Performing standard VNC authentication
    Password:
    Authentication successful
    Desktop name "QEMU"
    VNC server default format:
      32 bits per pixel.
      Least significant byte first in each pixel.
      True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
    Using default colormap which is TrueColor.  Pixel format:
      32 bits per pixel.
      Least significant byte first in each pixel.
      True colour: max red 255 green 255 blue 255, shift red 16 green 8 blue 0
    Using shared memory PutImage
    Same machine: preferring raw encoding

    Now after it can, I getother problem:
    on the TightVNC:QEMU window
    I get message
    " Starting SeaBIOS ( version 0.5.1-20100120_010601-rothera )

    No bootable device "

    And the event list of Openqrm I get error event :
    " Could not create a new resource for request ID 1! "

    I have been follow every step on the document guide Setup_your_own_openQRM_Cloud_on_Ubuntu_Lucid_Lynx.10052010

    Can you help me for solve that problem, please?

    Regards
    Panjul

     
  • uncu
    uncu
    2012-06-10

    Hi Matt,

    I have been resolved this problem.
    I chaged the image using 32 bit because I implement openqrm on my laptop.

    I have been download the image from http://image-shelf.openqrm-enterprise.org and unpacking is success.
    but I get new problem after TightVNC: QEMU appear.

    "Importing kernel files
    SCSI subsystem initialized
    -(2) starting hardware detection (all system Components)
    -loading ata_piix
    -loading i2c-piix4
    -loading virtio_pci
    -scaning for physical lvm drives
    No matching phycisal volumes found
    -scanning for logical volumes groups
    reading all physical volumes. This may take a while…
    -activating logical volumes
    -scanning for logical volumes
    -activating logical volumes
    starting openQRM-client
    Notice: Checking connection to openQRM server at 192.168.88.3
    /usr/share/openqrm/bin/dropbearkey: /lib/libc.so.6: version 'GLIB_2.7' not found (required by /usr/share/openqrm/bin/dropbearkey)
    sending idle/available to openQRM-server at 192.168.88.3
    detected initrd as initramfs, starting a shell
    bash: no job control in this shell
    bash-3.2#"

    "bash: no job control in the shell"

    Please help me, Why the QEMU window view (bash: no job control in the shell) ?

    Regards,
    Panjul

     
  • Matt
    Matt
    2012-06-20

    Hi Panjul,

    :) cool, looks good.
    You can ignore the "bash: no job control in the shell" warning. No problem.

    Your system is now in "idle" mode

    -> sending idle/available to openQRM-server at 192.168.88.3

    You can now deploy with by creating an "appliance". Then it will boot/connect the configured image you have created.

    many thanks and have a nice day,

    Matt Rechenburg
    Project Manager openQRM