Re: [Xci-devel] Second VM does not start!

[Jean Guyader <jean.guyader@xxxxxxxxx>]

It seams that we try to use the same vnc port for both, that why the
second qemu crashes.

Could you give use the config file for your second vm (the one that
doesn't work)?

Jean

On 19 August 2010 20:24, João Medina <joaomedina@xxxxxxxxx> wrote:
> Hi all!!
> I have installed the XCI in my HP 6930p and try to start some VM's. The
> first VM came to life, very, very well but, the second is a pain!!
> Memory, is no a trouble, I have 3gb ins the system, 512mb to my dom0 and
> 256mb for each VM.
> Let me explain this with some xenops -list outputs:
> 1º - only with 1 vm:
> # xenvm arch.vm
> # xenops list
> id |  state |   cpu_time |                                 uuid
>  0 |     R  | 4177000604 | 00000000-0000-0000-0000-000000000000
>  1 |      H |  451150993 | 00000000-0000-0000-0000-000000000002
>
> 2º - during the startup of the second vm:
> # xenvm arch2.vm
> # xenops list
> id |  state |    cpu_time |                                 uuid
>  0 |     R  |  5480771748 | 00000000-0000-0000-0000-000000000000
>  1 |     RH | 28375713061 | 00000000-0000-0000-0000-000000000002
>  2 |   P  H |           0 | 00000000-0000-0000-0000-000000000003
>
> 3º - the dead vm:
> # xenops list
> id |  state |    cpu_time |                                 uuid
>  0 |     R  |  5906673036 | 00000000-0000-0000-0000-000000000000
>  1 |     RH | 41568002515 | 00000000-0000-0000-0000-000000000002
>  2 |   P  H |           0 | 00000000-0000-0000-0000-000000000003
> and:
> # xenops list
> id |  state |    cpu_time |                                 uuid
>  0 |     R  |  6070872304 | 00000000-0000-0000-0000-000000000000
>  1 |     RH | 46479406154 | 00000000-0000-0000-0000-000000000002
>  2 |      H |      202305 | 00000000-0000-0000-0000-000000000003
>
>
>
> Another thing is the qemu instances, on my ps i see this:
> # ps | grep qemu
>  2495 root     /usr/lib/xen/bin/qemu-dm -name qemu-1 -d 1 -m 256 -boot dc
> -serial pty -vcpus 1 -videoram 8 -M xenfv -vnc :0 -k en-us
>  2520 root     /usr/lib/xen/bin/qemu-dm -name qemu-1 -d 1 -m 256 -boot dc
> -serial pty -vcpus 1 -videoram 8 -M xenfv -vnc :0 -k en-us
>  2521 root     /usr/lib/xen/bin/qemu-dm -name qemu-1 -d 1 -m 256 -boot dc
> -serial pty -vcpus 1 -videoram 8 -M xenfv -vnc :0 -k en-us
> Looking at my /tmp I have the logs of this 2 vms
>
> this is the working vm:
> # cat /tmp/xenvm-debug-00000000-0000-0000-0000-000000000002 | grep qemu
> [20100819 13:04:32.426|debug|xenops] qemu-dm: executing commandline:
> /opt/xensource/libexec/closeandexec --
> /opt/xensource/libexec/qemu-dm-wrapper 1 /tmp/qemu.1 -d 1 -m 256 -boot dc
> -serial pty -vcpus 1 -videoram 8 -M xenfv -vnc :0 -k en-us
> [20100819 13:04:32.427|debug|xenops] qemu-dm: should be running in the
> background (stdout and stderr redirected to /tmp/qemu.1)
> [20100819 13:04:32.649|debug|xenops] qemu-dm: pid = 2495
> [20100819 13:04:32.650|debug|xenops] qemu-dm: wrote vnc port 5900 into the
> store
>
> And this is the not working VM:
> # cat /tmp/xenvm-debug-00000000-0000-0000-0000-000000000003 | grep qemu
> [20100819 13:05:03.066|debug|xenops] qemu-dm: executing commandline:
> /opt/xensource/libexec/closeandexec --
> /opt/xensource/libexec/qemu-dm-wrapper 2 /tmp/qemu.2 -d 2 -m 256 -boot dc
> -serial pty -vcpus 1 -videoram 8 -M xenfv -vnc :0 -k en-us
> [20100819 13:05:03.067|debug|xenops] qemu-dm: should be running in the
> background (stdout and stderr redirected to /tmp/qemu.2)
> [20100819 13:05:18.077|debug|xenops] qemu-dm: timeout waiting for
> /local/domain/2/device-misc/dm-ready
>
> So, if I forgot some important details please, tell me ;)
>
> Tks,
> Medina
> _______________________________________________
> Xci-devel mailing list
> Xci-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/mailman/listinfo/xci-devel
>
>

_______________________________________________
Xci-devel mailing list
Xci-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xci-devel