[one-users] OpenNebula 3.4 hangs pre.
Javier Fontan
jfontan at opennebula.org
Thu Jul 5 07:09:17 PDT 2012
Hello,
The problem is definitely not in network pre script as it says that
was executed successfully. It is most probably hanging in 'deploy'
script or even the driver can be crashing. Please, make these changes
to see if it we can get more info:
* Change /etc/one/defaultrc and set ONE_MAD_DEBUG to 1
* Change /var/lib/one/remotes/vmm/xen/deploy and comment the line:
$XM_CREDITS -d $name -w $credits
* export RUBYOPT='-wd' and restart opennebula
Then try to deploy the VM again. You'll have more log files in
/var/log/one, one of them should be called one_vmm_exec.log. Check if
it contains some error info and send it to me.
On Wed, Jul 4, 2012 at 2:52 PM, Noah <lancen at sdf.org> wrote:
> I have a new Debian 6 testing (wheezy) install using packages from
> repositories - OpenNebula 3.4.1-3, openvswitch 1.4.2 (with brcompat/module).
>
> Everything works fine if I perform a sudo xm create newmachine.cfg (same as
> the template) as oneadmin user. NICs are added to the appropriate bridges,
> console is live...
>
> If I instantiate a vm via opennebula it hangs at:
>
> Wed Jul 4 06:41:25 2012 [DiM][I]: New VM state is ACTIVE.
> Wed Jul 4 06:41:25 2012 [LCM][I]: New VM state is PROLOG.
> Wed Jul 4 06:41:26 2012 [TM][I]: clone: Cloning
> ../../1/71e79681a890f0baecec8d0f228ec7ae in
> xenflame:/var/lib/one//datastores/0/25/disk.0
> Wed Jul 4 06:41:26 2012 [TM][I]: ExitCode: 0
> Wed Jul 4 06:41:26 2012 [TM][I]: context: Generating context block device
> at xenflame:/var/lib/one//datastores/0/25/disk.1
> Wed Jul 4 06:41:26 2012 [TM][I]: ExitCode: 0
> Wed Jul 4 06:41:26 2012 [LCM][I]: New VM state is BOOT
> Wed Jul 4 06:41:26 2012 [VMM][I]: Generating deployment file:
> /var/lib/one/25/deployment.0
> Wed Jul 4 06:41:27 2012 [VMM][I]: ExitCode: 0
> Wed Jul 4 06:41:27 2012 [VMM][I]: Successfully execute network driver
> operation: pre.
>
> This leads me to believe it is failing at network configuration, such as the
> "post" just fails....
>
> However if I attach to the console (via xm console) there is nothing.
>
> This occurs on both contextualized or non-contextualized templates, using
> one* on CLI or Sunstone.
>
> I've attached all the logs I think to be of use. The last VM I attempted to
> instantiate was 26 based on this template:
>
> CONTEXT=[
> FILES="/srv/storage/imagestore/ttylinux-Context/init.sh",
> HOSTNAME="TinyFLAME",
> IP_PUBLIC="192.168.117.7",
> USERNAME="opennebula" ]
> DISK=[
> DRIVER="file:",
> IMAGE_ID="6" ]
> FEATURES=[
> ACPI="no" ]
> GRAPHICS=[
> TYPE="vnc" ]
> MEMORY="1024"
> NAME="Tiny Linux"
> NIC=[
> NETWORK_ID="6" ]
> OS=[
> BOOTLOADER="/usr/lib/xen-default/boot/hvmloader" ]
> TEMPLATE_ID="0"
> VCPU="1"
>
> In addition this is an all-in-one development box. So it has Xen,
> OpenNebula, Sunstone on the same machine (on the metal).
>
> Any advice or troubleshooting suggestions would be much appreciated.
>
> Thank you
>
> Noah
>
>
> ~~~ One who has no where to go is not lost...
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
--
Javier Fontán Muiños
Project Engineer
OpenNebula - The Open Source Toolkit for Data Center Virtualization
www.OpenNebula.org | jfontan at opennebula.org | @OpenNebula
More information about the Users
mailing list