booting vm from iso file fails

asked 2015-02-17 11:25:52 -0600

RHK gravatar image

updated 2015-02-19 05:22:33 -0600

Hi All,

Any Pointers on how to Boot VM from iso in openstack?
What steps needs to be followed to install VM from iso file?

I did the same steps, but when VM reboots after installation on disk (which is lvm in my case) it boots from iso only, it’s not booting from disk, any steps to be followed to unmount iso, is there any steps/command to do so.

Regards,
RHK

edit retag flag offensive close merge delete

3 answers

Sort by » oldest newest most voted
1

answered 2015-02-18 09:24:58 -0600

dbaxps gravatar image

updated 2015-02-18 10:56:29 -0600

Nova (Juno Release) boots glance images of ISO type

Ubuntu14.04 Live CD was loaded , I selected test Ubuntu and got Internet access.
Ubuntu Server 14.04 started install right away and asked for iSCSI target as disk
for install , I just didn't have any configured. I will setup Gluster backend for Cinder
anyway and will try options :
1. Suggested by sfcloudman 
2. Boot  from image create a volume.

Live image of F21 appears to be much more friendly :-

    systemctl start sshd
    systemctl enable sshd
    password  (setup password for root )
    [root@junoSVC1 ~(keystone_demo)]# ssh root@192.168.1.154
    The authenticity of host '192.168.1.154 (192.168.1.154)' can't be established.
    ECDSA key fingerprint is ca:bc:c6:42:98:b1:eb:03:5b:c4:e6:39:da:df:74:3e.
    Are you sure you want to continue connecting (yes/no)? yes
    Warning: Permanently added '192.168.1.154' (ECDSA) to the list of known hosts.
    root@192.168.1.154's password: 
    Last login: Wed Feb 18 11:30:22 2015
    [root@localhost ~]# ifconfig
    eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1400
            inet 50.0.0.16  netmask 255.255.255.0  broadcast 50.0.0.255
            inet6 fe80::f816:3eff:fed7:bc5f  prefixlen 64  scopeid 0x20<link>
            ether fa:16:3e:d7:bc:5f  txqueuelen 1000  (Ethernet)
            RX packets 5686  bytes 6647672 (6.3 MiB)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 3340  bytes 338594 (330.6 KiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
            inet 127.0.0.1  netmask 255.0.0.0
            inet6 ::1  prefixlen 128  scopeid 0x10<host>
            loop  txqueuelen 0  (Local Loopback)
            RX packets 78  bytes 6400 (6.2 KiB)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 78  bytes 6400 (6.2 KiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

    [root@localhost ~]# df -h
    Filesystem           Size  Used Avail Use% Mounted on
    /dev/mapper/live-rw  5.8G  3.8G  2.0G  66% /
    devtmpfs             982M     0  982M   0% /dev
    tmpfs               1001M   84K 1001M   1% /dev/shm
    tmpfs               1001M  668K 1001M   1% /run
    tmpfs               1001M     0 1001M   0% /sys/fs/cgroup
    /dev/sr0             1.4G  1.4G     0 100% /run/initramfs/live
    tmpfs               1001M   20K 1001M   1% /tmp
    varcacheyum         1001M     0 1001M   0% /var/cache/yum
    vartmp              1001M   12K 1001M   1% /var/tmp
    tmpfs                201M   32K  201M   1% /run/user/1000
    tmpfs                201M     0  201M   0% /run/user/0
    [root@localhost ~]# curl http://169.254.169.254/latest/meta-data
    ami-id
    ami-launch-index
    ami-manifest-path
    block-device-mapping/
    hostname
    instance-action
    instance-id
    instance-type
    kernel-id
    local-hostname
    local-ipv4
    placement/
    public-hostname
    public-ipv4
    ramdisk-id
    reservation-id
    security-groups

[root@localhost ~]# yum install gimp
Loaded plugins: langpacks
Resolving Dependencies
--> Running transaction check
---> Package gimp.x86_64 2:2.8.14-1.fc21 will be installed
--> Processing Dependency: gimp-libs(x86-64) = 2:2.8.14-1.fc21 for package: 2:gimp-2.8.14-1.fc21.x86_64
--> Processing Dependency: gegl(x86-64) >= 0.2.0 for package ...
(more)
edit flag offensive delete link more
0

answered 2015-02-17 23:45:11 -0600

Yes boot from an ISO image is a straight forward process. The OpenStack documentation too talks about it.

edit flag offensive delete link more

Comments

I myself never tried booting an instance using ISO image. However, by looking at your question, I recollected my read on "boot from ISO" documentation. Well, I will try booting from an ISO image on my setup and let you know.

Yashpal Beppurana gravatar imageYashpal Beppurana ( 2015-02-18 04:11:57 -0600 )edit
0

answered 2015-02-17 13:33:57 -0600

1) Import ISO as an image to glance.

2) Boot an instance from that image and attach a volume with desired size.

3) The iso will recognize the attached volume as a /dev/sdX device and you can then install to volume.

You can then boot from volume or snapshot it to create a glance image from is.

If you just want to boot without installing then just import the ISO in to glance and launch a new instance from that glance image.

edit flag offensive delete link more

Comments

These steps are pretty much clear. Just add your desired ISO file to glance image list and launch an instance from this ISO image..!!

Praveen N gravatar imagePraveen N ( 2015-02-17 13:51:36 -0600 )edit

attaching volume to an instance fails

socfreak390 gravatar imagesocfreak390 ( 2015-06-10 02:25:48 -0600 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-02-17 11:25:52 -0600

Seen: 1,146 times

Last updated: Feb 19 '15