[one-users] Cannot shutdown VM

Tue Aug 11 09:22:51 PDT 2009

Hi,

The change in my last email was wrong. ACPI was properly set by the
current version, and you need acpi to shutdown your VM, however you
need  acpid or similar in the guest VM for this to work. So probably
you can not shutdown the VM because you are not handling the acpi
events in the guest OS. If you do not want to use acpi just put
acpi="no", and the VM will shutdown the "hard way"...

Cheers!

Ruben

On Tue, Aug 11, 2009 at 5:46 PM, Ruben S. Montero<rubensm at dacya.ucm.es> wrote:
> Hi,
>
> BTW to use the shutdown feature ACPI should be enabled in the VM.
> However there is a bug in the libvirtdriver.cc. ACPI and PAE are
> inverted so if you want to get the ACPI feature just put ACPI="no" in
> the template or apply:
>
> http://dev.opennebula.org/projects/opennebula/repository/revisions/765/diff/trunk/src/vmm/LibVirtDriver.cc
>
> Also I am getting
>
>> virsh  reboot one-13
> error: Failed to reboot domain one-13
> error: this function is not supported by the hypervisor: virDomainReboot
>
>
>> > libvirtd --version
> libvirtd (libvirt) 0.6.5
>
>
> Can you reboot a domain (this domain have ACPI set, and can be shutdown)?
>
> Cheers!
>
> Ruben
>
> On Tue, Aug 11, 2009 at 8:52 AM, Harsha Buggi<Harsha_Buggi at mindtree.com> wrote:
>> Hi,
>>    Thanks for your response. To answer some of your questions :
>>
>> For the 1st issue - Yes I am able to boot the VM's but not shut them down. If I just replace v1.3.80 with v1.2 in the same environment everything works perfect. There are no errors in the logs. When I do a shutdown the VM goes to shut state and stays there. But the VM is still running on the node.
>>
>> Modifications made as described in the second issue does not solve the first issue.
>>
>> Comming to the third issue - what is the mechanism for oneadmin to define a user and related access controls? I could not find any 'oneuser' command which might let the oneadmin define permissions. Also what is the mechanism for a specific user to access his/her VM's. How does Nebula core know which user is currently logged into the system and executing 'one' commands.
>> I have created a user on the system called 'harsha' and after I log into the system I am able to run all the 'one' commands.I was able to delete Vnets and VM's created by 'oneadmin'. This got me a little confused and I am finding it difficult to understand what is the purpose of creating users in nebula?
>> I am not using 'sudo' to execute any commands.
>>
>> Few more issues....
>>
>> 1) The node statistics do not get updated to the Front end after adding a host with 'onehost' command. 'TCPU','FCPU' and 'TMEM' are all 0. Therefore VM do not automatically get deployed when they are created.
>>
>> 2) What state should a VM be in order to perform a 'restart'. Will this by any chance reboot a VM? I have tried restart when the VM is in runn,fail,shut states but I always get the response this is not in the right state to perform this operation.
>>
>>  Questions...
>>
>>  What is the version of VM ware that Nebula supports. If I want to run Nebula with VMware which packages and their corresponding version should I install?
>>
>>   Is VM reboot functionality included in the product roadmap? This is somthing which I require urgently and I am ready to test any partial builds if they are available with this functionality.
>>
>>
>> Regards,
>> Harsha
>>
>>
>>
>> ________________________________________
>> From: rsmontero at gmail.com [rsmontero at gmail.com] On Behalf Of Ruben S. Montero [rubensm at dacya.ucm.es]
>> Sent: Tuesday, August 11, 2009 3:39 AM
>> To: Harsha Buggi
>> Cc: users at lists.opennebula.org
>> Subject: Re: [one-users] Cannot shutdown VM
>>
>> On Mon, Aug 10, 2009 at 2:24 PM, Harsha Buggi<Harsha_Buggi at mindtree.com> wrote:
>>> Hi,
>>>
>>>   I have installed Nebula on an fc8 machine with NIS and NFS support. Using Oneadmin login to create VM's
>>>
>>>   I have couple of issues:
>>>
>>> 1) I am not able to shutdown VM's. By default fc8 installs 'qemu-kvm' and I have created the symbolic link 'kvm' for this file. But after I create the VM's I am not able to perform a shutdown. I tried changing the 'emulator' to 'qemu-kvm' in libvirtdriver.cc file and reinstalling but I am still not able to shutdown the VM. I am able to do this if I install v1.2. I am using the following versions of hypervisor and libvirt
>>> kvm-60
>>> qemu-0.9.0-7
>>> libvirt-0.4.4
>>> libvirt-python-0.4.4
>>
>> So, after the changes you are able to boot the VM but not to shutdown
>> it, right?. I am not sure why you can create but not shutdown. What
>> does the log files say?
>> I've updated the following issue to address also the "emulator" path:
>>
>> http://dev.opennebula.org/issues/131
>>
>>>
>>> 2) I found that libvirt v 0.4.4 does not support user logins apart from root. This seems to have been fixed in the  released recently v0.7.0. This could be the solution to the issue described in
>>> http://lists.opennebula.org/pipermail/users-opennebula.org/2009-August/000626.html
>>> In my case I have modified the one_vmm_kvm.rb file to reflect
>>> create   => "sudo virsh  create" instead of 'create   => "virsh -c qemu:///session create"'
>>>
>>
>> Yes, we plan to make the hypervisor URI a configurable parameter in
>> the vmm_kvm.conf file. BTW, Does this solve the previous issue?
>>
>>> 3) After creating a new user using 'oneuser create' command and setting the ONE_AUTH variable how do I set VM permissions for this user?
>>
>> The permissions are as follows:
>>
>> * Each VM and Network are owned by the user that creates them. (you
>> can now see ownership in the "list" commands)
>> * Each user can only managed her own VMs or Networks (i.e. shutdown
>> migrate delete...)
>> * Oneadmin can do anything
>>
>> This is enforced by the OpenNebula core.
>>
>>>Should this user be created on the system too?
>>
>> It is not really needed, it depends on the type of deployment you want
>> to make. If the users are *external* (e.g. will access to your
>> infrastructure through a cloud interface) you do not have to make a
>> system account for each user, just an OpenNebula one. However if those
>> users are the team of sysadmins managing the virtual infrastructure
>> for a site each one will probably have their own system and OpenNebula
>> accounts.
>>
>> Thanks for the feedback!
>>
>> Cheers!
>>
>> Ruben
>>>
>>> Regards,
>>> Harsha
>>>
>>>
>>>
>>> ________________________________
>>> http://www.mindtree.com/email/disclaimer.html
>>> _______________________________________________
>>> Users mailing list
>>> Users at lists.opennebula.org
>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>
>>
>>
>>
>> --
>> +---------------------------------------------------------------+
>>  Dr. Ruben Santiago Montero
>>  Associate Professor
>>  Distributed System Architecture Group (http://dsa-research.org)
>>
>>  URL:    http://dsa-research.org/doku.php?id=people:ruben
>>  Weblog: http://blog.dsa-research.org/?author=7
>>
>>  GridWay, http://www.gridway.org
>>  OpenNebula, http://www.opennebula.org
>> +---------------------------------------------------------------+
>>
>> http://www.mindtree.com/email/disclaimer.html
>>
>
>
>
> --
> +---------------------------------------------------------------+
>  Dr. Ruben Santiago Montero
>  Associate Professor
>  Distributed System Architecture Group (http://dsa-research.org)
>
>  URL:    http://dsa-research.org/doku.php?id=people:ruben
>  Weblog: http://blog.dsa-research.org/?author=7
>
>  GridWay, http://www.gridway.org
>  OpenNebula, http://www.opennebula.org
> +---------------------------------------------------------------+
>

-- 
+---------------------------------------------------------------+
 Dr. Ruben Santiago Montero
 Associate Professor
 Distributed System Architecture Group (http://dsa-research.org)

 URL:    http://dsa-research.org/doku.php?id=people:ruben
 Weblog: http://blog.dsa-research.org/?author=7

 GridWay, http://www.gridway.org
 OpenNebula, http://www.opennebula.org
+---------------------------------------------------------------+