[ovirt-users] Issues with vm start up
Koen Vanoppen
vanoppen.koen at gmail.com
Mon Dec 8 06:49:07 UTC 2014
We also had a issue when starting our vms. This was due the fact of the
NUMA option under the host section. I attached a procedure I created for
work. Maybe it is also useful for your case...
2014-12-02 5:58 GMT+01:00 Shanil S <xielesshanil at gmail.com>:
> Hi Omer,
>
> We have opened this as a bug, you can view the new bug here
> https://bugzilla.redhat.com/show_bug.cgi?id=1169625.
>
> --
> Regards
> Shanil
>
> On Tue, Dec 2, 2014 at 8:42 AM, Shanil S <xielesshanil at gmail.com> wrote:
>
>> Hi Omer,
>>
>> Thanks for your reply. We will open it as a bug.
>>
>> --
>> Regards
>> Shanil
>>
>> On Mon, Dec 1, 2014 at 4:38 PM, Omer Frenkel <ofrenkel at redhat.com> wrote:
>>
>>>
>>>
>>> ----- Original Message -----
>>> > From: "Shanil S" <xielesshanil at gmail.com>
>>> > To: "Omer Frenkel" <ofrenkel at redhat.com>, users at ovirt.org, "Juan
>>> Hernandez" <jhernand at redhat.com>
>>> > Sent: Monday, December 1, 2014 12:39:12 PM
>>> > Subject: Re: [ovirt-users] Issues with vm start up
>>> >
>>> > Hi Omer,
>>> >
>>> > Thanks for your reply.
>>> >
>>> > We are deploying those VM's through templates and all the templates has
>>> > first boot from hard disk and second with cdrom. We are using cdrom in
>>> > cloud-init section to insert the cloud-init data .Why we need this boot
>>> > loader (VM boot order or in the cloud-init section) as in the template
>>> the
>>> > first boot order is harddisk ?
>>> >
>>> >
>>>
>>> if the template's boot order has hard-disk it should be ok,
>>> not sure why it seems for this vm the boot order is only cd.
>>> does this happen to any vm created from this template?
>>> can you check the boot order is corrent in the edit vm dialog?
>>>
>>> if the boot order is ok in the template,
>>> and it happens to any new vm from this template,
>>> you should open a bug so we could investigate this.
>>>
>>> >
>>> > --
>>> > Regards
>>> > Shanil
>>> >
>>> > On Mon, Dec 1, 2014 at 3:37 PM, Omer Frenkel <ofrenkel at redhat.com>
>>> wrote:
>>> >
>>> > >
>>> > >
>>> > > ----- Original Message -----
>>> > > > From: "Shanil S" <xielesshanil at gmail.com>
>>> > > > To: "Shahar Havivi" <shaharh at redhat.com>
>>> > > > Cc: users at ovirt.org, "Juan Hernandez" <jhernand at redhat.com>, "Omer
>>> > > Frenkel" <ofrenkel at redhat.com>
>>> > > > Sent: Thursday, November 27, 2014 10:32:54 AM
>>> > > > Subject: Re: [ovirt-users] Issues with vm start up
>>> > > >
>>> > > > Hi Omer,
>>> > > >
>>> > > > I have attached the engine.log and vdsm.log. Please check it. The
>>> vm id
>>> > > is
>>> > > > - 7c7aa9dedb57248f5da291117164f0d7
>>> > > >
>>> > >
>>> > > sorry Shanil for the delay,
>>> > > it looks that in the vm settings, you have chosen to boot only from
>>> cd ?
>>> > > this is why the vm doest boot, the cloud-init disk is a settings
>>> disk, not
>>> > > a boot disk
>>> > > please go to update vm, change the boot order to use hard-disk, and
>>> boot
>>> > > the vm.
>>> > >
>>> > > let me know if it helps,
>>> > > Omer.
>>> > >
>>> > > > --
>>> > > > Regards
>>> > > > Shanil
>>> > > >
>>> > > > On Thu, Nov 27, 2014 at 1:46 PM, Shahar Havivi <shaharh at redhat.com
>>> >
>>> > > wrote:
>>> > > >
>>> > > > > Try to remove content and run the vm,
>>> > > > > ie remove the runcmd: or some of it - try to use the xml with
>>> out CDATA
>>> > > > > maybe
>>> > > > > you can pinpoint the problem that way...
>>> > > > >
>>> > > > >
>>> > > > > On 27.11.14 10:03, Shanil S wrote:
>>> > > > > > Hi All,
>>> > > > > >
>>> > > > > >
>>> > > > > > I am using the ovirt version 3.5 and having some issues with
>>> the vm
>>> > > > > startup
>>> > > > > > with cloud-init using api in run-once mode.....
>>> > > > > >
>>> > > > > > Below is the steps i follow :-
>>> > > > > >
>>> > > > > > 1. Create the VM by API from precreated Template..
>>> > > > > > 2. Start the VM in run-once mode and push the cloud-init data
>>> from
>>> > > API..
>>> > > > > > 3. VM stuck and from console it display the following :-
>>> > > > > > Booting from DVD/CD.. ...
>>> > > > > > Boot failed : could not read from CDROM (code 004)
>>> > > > > >
>>> > > > > > I am using the following xml for this operation :-
>>> > > > > >
>>> > > > > > <action>
>>> > > > > > <vm>
>>> > > > > > <os>
>>> > > > > > <boot dev='cdrom'/>
>>> > > > > > </os>
>>> > > > > > <initialization>
>>> > > > > > <cloud_init>
>>> > > > > > <host>
>>> > > > > > <address>test</address>
>>> > > > > > </host>
>>> > > > > > <network_configuration>
>>> > > > > > <nics>
>>> > > > > > <nic>
>>> > > > > > <interface>virtIO</interface>
>>> > > > > > <name>eth0</name>
>>> > > > > > <boot_protocol>static</boot_protocol>
>>> > > > > > <mac address=''/>
>>> > > > > > <network>
>>> > > > > > <ip address='' netmask='' gateway=''/>
>>> > > > > > </network>
>>> > > > > > <on_boot>true</on_boot><vnic_profile id='' />
>>> > > > > > </nic>
>>> > > > > > <nic>
>>> > > > > > <interface>virtIO</interface>
>>> > > > > > <name>eth1</name>
>>> > > > > > <boot_protocol>static</boot_protocol>
>>> > > > > > <mac address=''/>
>>> > > > > > <network>
>>> > > > > > <ip address='' netmask='255.255.255.0' gateway=''/>
>>> > > > > > </network>
>>> > > > > > <on_boot>true</on_boot><vnic_profile id='' />
>>> > > > > > </nic>
>>> > > > > > </nics>
>>> > > > > > </network_configuration>
>>> > > > > > <files>
>>> > > > > > <file>
>>> > > > > > <name>/ignored</name><content><![CDATA[#cloud-config
>>> > > > > > disable-ec2-metadata: true
>>> > > > > > disable_root: false
>>> > > > > > ssh_pwauth: true
>>> > > > > > ssh_deletekeys: true
>>> > > > > > chpasswd: { expire: False }
>>> > > > > >
>>> > > > > > users:
>>> > > > > > - name: root
>>> > > > > > primary-group: root
>>> > > > > > passwd: 8W7RQ5Bh
>>> > > > > > lock-passwd: false
>>> > > > > >
>>> > > > > > runcmd:
>>> > > > > > - sed -i '/nameserver/d' /etc/resolv.conf
>>> > > > > > - echo 'nameserver 8.8.8.8' >> /etc/resolv.conf
>>> > > > > > - echo 'nameserver 8.8.4.4' >> /etc/resolv.conf
>>> > > > > > - echo 'root:8W7RQ5Bh' | chpasswd
>>> > > > > > - yum -y update
>>> > > > > > - yum -y install rdate
>>> > > > > > - rdate -s stdtime.gov.hk]]></content>
>>> > > > > > <type>plaintext</type>
>>> > > > > > </file>
>>> > > > > > </files>
>>> > > > > > </cloud_init><custom_script><![CDATA[#cloud-config
>>> > > > > > disable-ec2-metadata: true
>>> > > > > > disable_root: false
>>> > > > > > ssh_pwauth: true
>>> > > > > > ssh_deletekeys: true
>>> > > > > > chpasswd: { expire: False }
>>> > > > > >
>>> > > > > > users:
>>> > > > > > - name: root
>>> > > > > > primary-group: root
>>> > > > > > passwd: 8W7RQ5Bh
>>> > > > > > lock-passwd: false
>>> > > > > >
>>> > > > > > runcmd:
>>> > > > > > - sed -i '/nameserver/d' /etc/resolv.conf
>>> > > > > > - echo 'nameserver 8.8.8.8' >> /etc/resolv.conf
>>> > > > > > - echo 'nameserver 8.8.4.4' >> /etc/resolv.conf
>>> > > > > > - echo 'root:8W7RQ5Bh' | chpasswd
>>> > > > > > - yum -y update
>>> > > > > > - yum -y install rdate
>>> > > > > > - rdate -s stdtime.gov.hk]]></custom_script>
>>> > > > > > </initialization>
>>> > > > > > </vm>
>>> > > > > > </action>
>>> > > > > >
>>> > > > > > I am also attaching the screen shot to this.
>>> > > > > >
>>> > > > > >
>>> > > > > >
>>> > > > > > --
>>> > > > > > Regards
>>> > > > > > Shanil
>>> > > > >
>>> > > > >
>>> > > > > > _______________________________________________
>>> > > > > > Users mailing list
>>> > > > > > Users at ovirt.org
>>> > > > > > http://lists.ovirt.org/mailman/listinfo/users
>>> > > > >
>>> > > > >
>>> > > >
>>> > >
>>> >
>>>
>>
>>
>
> _______________________________________________
> Users mailing list
> Users at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20141208/5ffa8a28/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ovirt 3.5 bug workaround.docx
Type: application/vnd.openxmlformats-officedocument.wordprocessingml.document
Size: 254888 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/users/attachments/20141208/5ffa8a28/attachment-0001.docx>
More information about the Users
mailing list