[one-users] stuck in boot
Hi, I am new to Opennbula and I was trying to deploy a simple cloud. I used the following configurations: Name = nebula cpu = 0.1 memory = 64 Disk = [ source = /var/lib/one/images/tmp1N2BrS.qcow2, target = sda1, readonly = no] NIC = [network = small network] features =[acpi=no] the machine sticks in boot state. The new log file ends with New VM state is BOOT. Generating deployment file /var/lib/one/7/deployment.0 what can I do to pass the boot state ? thanks -- Muhammad Ahmad Daif ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] stuck in boot
Hallo Luca.. could you please be somehow verboser to which is the problem with qcow2 in the version 2.0? I'm planing my migration to this version and it would be a no go for me if I could not use qcow2. Br Marlon Zitat von Luca Lorenzini lorenzini.l...@gmail.com: there are some issues with qcow2 format in version 2.0, try with a raw image On Thu, Nov 25, 2010 at 12:37 PM, Muhammad Daif daif.cont...@gmail.comwrote: Hi, I am new to Opennbula and I was trying to deploy a simple cloud. I used the following configurations: Name = nebula cpu = 0.1 memory = 64 Disk = [ source = /var/lib/one/images/tmp1N2BrS.qcow2, target = sda1, readonly = no] NIC = [network = small network] features =[acpi=no] the machine sticks in boot state. The new log file ends with New VM state is BOOT. Generating deployment file /var/lib/one/7/deployment.0 what can I do to pass the boot state ? thanks -- Muhammad Ahmad Daif ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] stuck in boot
I noticed that the DRIVER attribute is bypassed and by default libvirt set the image type as raw. This feature will be implemented on the next release (there is a patch if u need it now). I had the same problem and i tricked the system to add the correct line in the deployment file before submission to libvirt. I modified the deploy file (i cant modified source code because i havent administrator right on the machine) placed in /usr/lib/one/remotes/vmm/kvm/. On Thu, Nov 25, 2010 at 2:30 PM, openneb...@nerling.ch wrote: Hallo Luca.. could you please be somehow verboser to which is the problem with qcow2 in the version 2.0? I'm planing my migration to this version and it would be a no go for me if I could not use qcow2. Br Marlon Zitat von Luca Lorenzini lorenzini.l...@gmail.com: there are some issues with qcow2 format in version 2.0, try with a raw image On Thu, Nov 25, 2010 at 12:37 PM, Muhammad Daif daif.cont...@gmail.com wrote: Hi, I am new to Opennbula and I was trying to deploy a simple cloud. I used the following configurations: Name = nebula cpu = 0.1 memory = 64 Disk = [ source = /var/lib/one/images/tmp1N2BrS.qcow2, target = sda1, readonly = no] NIC = [network = small network] features =[acpi=no] the machine sticks in boot state. The new log file ends with New VM state is BOOT. Generating deployment file /var/lib/one/7/deployment.0 what can I do to pass the boot state ? thanks -- Muhammad Ahmad Daif ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
