[one-users] Nebula 4.0.1 Xen 4.1.4 Debian Wheezy - VM stuck in BOOT state

[Jacek Jarosiewicz]

I've researched it a little bit more, and found this message:

http://www.mail-archive.com/users@lists.opennebula.org/msg08546.html

..and when I run:

oneadmin at nebula1:~$ /var/tmp/one/vmm/xen4/poll one-19
NAME=one-19 STATE=a USEDCPU=0.0 USEDMEMORY=2093312 NETTX=1539072 NETRX=15360

..so according to the message above, the VM state should be RUNNING, but 
it still is BOOT... I'm confused..

J

On 06/05/2013 09:16 AM, Jacek Jarosiewicz wrote:
> Hi,
>
> I've searched google and this list but with no luck..
>
> I have setup an opennebula cloud (4.0.1) with xen (4.1) on debian
> wheezy. My problem is that vm's are deployed correctly (vm is running,
> networking is set up, I can ssh to it, run programs within it etc.) but
> opennebula shows vm stuck in boot state and i can't do anything with it
> from either sunstone nor with the onevm command.
>
> I can only delete the vm.
>
> The VM is debian squeeze from marketplace (
> http://marketplace.c12g.com/appliance/4fec9fb28fb81d2ebc000002 )
>
> no errors in oned.log - only monitoring stuff.. any help is appreciated!
>
> The deployment.0 file is:
>
> name = 'one-19'
> memory  = '2048'
> vcpus  = '1'
> bootloader = "/usr/lib/xen-4.1/bin/pygrub"
> disk = [
>      'tap2:tapdisk:aio:/var/lib/one//datastores/0/19/disk.0,xvda,w',
>      'tap2:tapdisk:aio:/var/lib/one//datastores/0/19/disk.1,xvdb,r',
> ]
> vif = [
>      ' mac=02:00:12:a8:01:0a,ip=192.168.1.10,bridge=br0',
> ]
> vfb = ['type=vnc,vnclisten=0.0.0.0,vncdisplay=19']
> device_model = '/usr/lib/xen-4.1/bin/qemu-dm'
>
> xm list command output:
>
> root at nebula1:/var/log/xen# xm list
> Name                                        ID   Mem VCPUs      State
> Time(s)
> Domain-0                                     0  1023     4     r-----
> 1194.4
> one-19                                       5  2048     1     -b----
> 1.7
>
>
> onevm list command output:
>
> oneadmin at nebula0:~$ onevm list
>      ID USER     GROUP    NAME            STAT UCPU    UMEM HOST      TIME
>      19 oneadmin oneadmin deb1            boot    0      2G nebula1  0d
> 01h05
>
>
> vm log:
>
> Wed Jun  5 08:09:59 2013 [DiM][I]: New VM state is ACTIVE.
> Wed Jun  5 08:09:59 2013 [LCM][I]: New VM state is PROLOG.
> Wed Jun  5 08:13:20 2013 [LCM][E]: monitor_done_action, VM in a wrong state
> Wed Jun  5 08:18:37 2013 [LCM][E]: monitor_done_action, VM in a wrong state
> Wed Jun  5 08:22:26 2013 [TM][I]: clone: Cloning
> nebula0:/var/lib/one/datastores/1/78b6cd5fe55967f183d9eabfd9cd7a28 in
> /var/lib/one/datastores/0/19/disk.0
> Wed Jun  5 08:22:26 2013 [TM][I]: ExitCode: 0
> Wed Jun  5 08:22:27 2013 [TM][I]: context: Generating context block
> device at nebula1:/var/lib/one//datastores/0/19/disk.1
> Wed Jun  5 08:22:27 2013 [TM][I]: ExitCode: 0
> Wed Jun  5 08:22:27 2013 [LCM][I]: New VM state is BOOT
> Wed Jun  5 08:22:27 2013 [VMM][I]: Generating deployment file:
> /var/lib/one/vms/19/deployment.0
> Wed Jun  5 08:22:28 2013 [VMM][I]: ExitCode: 0
> Wed Jun  5 08:22:28 2013 [VMM][I]: Successfully execute network driver
> operation: pre.
> Wed Jun  5 08:22:31 2013 [VMM][D]: deploy: Credits set to 256
> Wed Jun  5 08:22:31 2013 [VMM][I]: ExitCode: 0
> Wed Jun  5 08:22:31 2013 [VMM][I]: Successfully execute virtualization
> driver operation: deploy.
>
> xend.log:
>
> [2013-06-05 08:22:31 2847] DEBUG (XendDomainInfo:103)
> XendDomainInfo.create(['vm', ['name', 'one-19'], ['memory', '2048'],

[...]

> [2013-06-05 08:22:34 2847] WARNING (XendDomainInfo:581) Could not
> unpause blktap disk: ('unpause', '-p21487', '-m0') failed (5632  )
>
> Cheers,
> J
>


-- 
Jacek Jarosiewicz