I think that problem lies within the permissions of the "cloned" disk file.
I remember that I debugged the xen scripts and the error thrown by the
python code
was something with the required 755 instead of 700 (created by the ONE).
Anyway I think that this the bug.
You can run the /var/tmp/one/vmm/xen/deploy script manually and try to
put some stuff inside of the xend-deamon which must be restarted because
these scipts are pyc.
Hello,
thank you for your message. I installed the package, but nothing changed.
I also added the driver parameter into the disk section (driver
file:); the same result.
The deployment file shows the same content as the link you sent
first try:
root@debian-1:/var/log/one# cat
/var/lib/one//datastores/0/34/deployment.0
name = 'one-34'
#O CPU_CREDITS = 256
memory = '512'
bootloader = "/usr/bin/pygrub"
disk = [
'tap:aio:/var/lib/one//datastores/0/34/disk.0,xvda,w',
'tap:aio:/var/lib/one//datastores/0/34/disk.1,xvdb,r',
]
vif = [
' mac=02:00:84:b0:4e:76,ip=192.176.78.118,bridge=xenbr0',
]
vfb = ['type=vnc,vnclisten=0.0.0.0,vncdisplay=34']
another try:
root@debian-1:/var/log/one# cat
/var/lib/one//datastores/0/36/deployment.0
name = 'one-36'
#O CPU_CREDITS = 256
memory = '512'
bootloader = "/usr/bin/pygrub"
disk = [
'file:/var/lib/one//datastores/0/36/disk.0,xvda,w',
]
vif = [
' mac=02:00:84:b0:4e:78,ip=192.176.78.120,bridge=xenbr0',
]
vfb = ['type=vnc,vnclisten=0.0.0.0,vncdisplay=36']
Mon Aug 13 20:49:57 2012 [LCM][I]: New VM state is BOOT
Mon Aug 13 20:49:57 2012 [VMM][I]: Generating deployment file:
/var/lib/one/35/deployment.0
Mon Aug 13 20:49:57 2012 [VMM][I]: ExitCode: 0
Mon Aug 13 20:49:57 2012 [VMM][I]: Successfully execute network driver
operation: pre.
Mon Aug 13 20:49:58 2012 [VMM][I]: Command execution fail: cat << EOT
| /var/tmp/one/vmm/xen/deploy
/var/lib/one//datastores/0/35/deployment.0 debian-3 35 debian-3
Mon Aug 13 20:49:58 2012 [VMM][I]: Error: Disk isn't accessible
Mon Aug 13 20:49:58 2012 [VMM][E]: Unable
Mon Aug 13 20:49:58 2012 [VMM][I]: ExitCode: 1
I have to install the package in my ubuntu box. That will be done
tomorrow.
Regards Hendrik
On 13.08.2012 09:18, Daniel Molina wrote:
Hi,
On 8 August 2012 21:55, Hendrik Wißmann <wissm...@gmx.de> wrote:
Hello,
as many others, I was able to install OpenNebula on Debian 6.0.5 and
monitor
the hosts running xen 4.0 (Dom0 Debian). The PV-Ubuntu Image started
with
xm works without any problems.
But the instantiation of the registered image fails with the error:
Wed Aug 8 21:09:29 2012 [DiM][I]: New VM state is ACTIVE.
Wed Aug 8 21:09:29 2012 [LCM][I]: New VM state is PROLOG.
Wed Aug 8 21:09:29 2012 [TM][I]: ln: Linking
../../100/6dc9b9d8a7b34a3a47d7768212c2bae0 in
debian-3:/var/lib/one//datastores/0/21/disk.0
Wed Aug 8 21:09:29 2012 [TM][I]: ExitCode: 0
Wed Aug 8 21:09:29 2012 [TM][I]: context: Generating context block
device
at debian-3:/var/lib/one//datastores/0/21/disk.1
Wed Aug 8 21:09:29 2012 [TM][I]: ExitCode: 0
Wed Aug 8 21:09:29 2012 [LCM][I]: New VM state is BOOT
Wed Aug 8 21:09:29 2012 [VMM][I]: Generating deployment file:
/var/lib/one/21/deployment.0
Wed Aug 8 21:09:29 2012 [VMM][I]: ExitCode: 0
Wed Aug 8 21:09:29 2012 [VMM][I]: Successfully execute network driver
operation: pre.
Wed Aug 8 21:09:30 2012 [VMM][I]: Command execution fail: cat << EOT |
/var/tmp/one/vmm/xen/deploy /var/lib/one//datastores/0/21/deployment.0
debian-3 21 debian-3
Wed Aug 8 21:09:30 2012 [VMM][I]: Error: Disk isn't accessible
Wed Aug 8 21:09:30 2012 [VMM][E]: Unable
Wed Aug 8 21:09:30 2012 [VMM][I]: ExitCode: 1
Wed Aug 8 21:09:30 2012 [VMM][I]: Failed to execute virtualization
driver
operation: deploy.
Wed Aug 8 21:09:30 2012 [VMM][E]: Error deploying virtual machine:
Unable
Wed Aug 8 21:09:30 2012 [DiM][I]: New VM state is FAILED
Wed Aug 8 21:18:53 2012 [DiM][I]: New VM state is DONE.
Wed Aug 8 21:18:53 2012 [TM][W]: Ignored: LOG I 21 ExitCode: 0
Wed Aug 8 21:18:53 2012 [TM][W]: Ignored: LOG I 21 delete: Deleting
/var/lib/one/datastores/0/21
Wed Aug 8 21:18:53 2012 [TM][W]: Ignored: LOG I 21 ExitCode: 0
Wed Aug 8 21:18:53 2012 [TM][W]: Ignored: TRANSFER SUCCESS 21 -
The template shows the following content:
NAME = "Ubuntu-2 12.0.4"
CPU = 1
MEMORY = 512
OS = [
bootloader = "/usr/bin/pygrub"
]
DISK = [ IMAGE_ID = 0 ]
NIC = [ NETWORK_ID = 0, WHITE_PORTS_TCP="22" ]
GRAPHICS=[
LISTEN=0.0.0.0,
TYPE=vnc ]
FEATURES=[ acpi="no" ]
CONTEXT = [
hostname = "VM$VMID",
ip_public = "$NIC[IP, NETWORK_ID = 1]",
root_pubkey = "id_rsa.pub",
netmask = "255.255.255.0",
dns = "$NETWORK[DNS, NETWORK_ID=1]",
gateway = "$NETWORK[GATEWAY, NETWORK_ID=1]"
#files = "/var/lib/one/contextualization/init.sh
/var/lib/one/.ssh/id_rsa.pub"
]
After changing the line bootloader into the line kernel=/vmlinuz,
the vm is
able to boot
but it can not connect the "tap:aio devices".
I already replaced the package xen-utils-common as described in this
forum.
Can anybody give me some advice?
Could you try the solution proposed in this thread?
http://lists.opennebula.org/pipermail/users-opennebula.org/2012-June/009133.html
Cheers
_______________________________________________
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
--
Ph.D. Eng. Marcin Jarzab
m...@agh.edu.pl
http://www.ics.agh.edu.pl/people/mj
Department of Computer Science
AGH University of Science and Technology
Kawiory 21, Building D17, 30-055 Krakow, POLAND
phone: +48 (12) 328 33 72
==========================================================================
_______________________________________________
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
