cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dean Kamali (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-2455) Cannot add a Debian host to a KVM cluster
Date Tue, 28 May 2013 19:59:21 GMT


Dean Kamali commented on CLOUDSTACK-2455:

Well, according to documentation supported OSs are CentOS & Ubuntu 12.4.1 for CS 4.1 only.

FYI,  I had issues using 12.4.(2)! so a minor release could break things! so it is obvious
it will break for Debian
> Cannot add a Debian host to a KVM cluster
> -----------------------------------------
>                 Key: CLOUDSTACK-2455
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Hypervisor Controller, Install and Setup, KVM
>    Affects Versions: 4.0.0, 4.0.1, 4.0.2
>            Reporter: Ahmad Saif
> After installing the cloud-agent packages on Debain system, you cannot add it to a KVM
cluster due to a bug on the python library ""  The script on "class Distribution"
will do the same operation for Ubuntu if the distor is Debian, which is wrong .. for the following
reasons :
> 1st: it will check as instructed for the following file "/etc/legal" and make sure it
have the word "Ubuntu" on it, and this file doesn’t exist on Debian 
> 2nd: It will check if the KVM is enabled by calling a system script that is not available
on Debian  the script is "/usr/sbin/kvm-ok" 
> The proposed work-around is : 
> for the first issue : echo "Ubuntu" > /etc/legal
> for the second issue is to copy the content of kvm-ok from an Ubuntu system and put it
on the same path on the Debian system.
> I think the fix for this bug should be like this :
> When looking for the distro check "/etc/issue", and when checking if the KVM enabled
or not use the same function used on Centos, by checking if the path ("/dev/kvm") exist 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message