Re: [Xen-users] not to create domain

[Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx>]

Am Donnerstag 19 April 2012, 14:47:06 schrieb æ??å®?伦:
> this is the information of ' xm dmesg', i can not see any problem . my
> computer total memory is 2G, my first guest domain's memory is 512M, my
> second domian's memory is 1024M, previously i can start the two guest
> domain at the same time fine, but today i start the two ones , only one
> guest domain can run naturally, another crashed .

Maybe you have a problem with the free memory. Try 'xm info' and look for
free_memory and what your new guest would need.
If the guest is a linux domain you can try:
# xm create -c vm.cfg
to see the kernel boot messages.

Dietmar.

> 
> 2012/4/19 Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx>
> 
> > Am Donnerstag 19 April 2012, 09:55:51 schrieben Sie:
> > > thanks for your reply; but what's the meaning of what your say. i have
> > tried
> > > on_crash = 'preserve' , but there is nothing to do;
> >
> > If the domU didn't get destroyed maybe you are able to do some analysis to
> > find
> > the reason within your domU for the crash. If you use the -c flag in the
> > xm command a console connection is created to your domU.
> > Did you try 'xm dmesg' to see some hypervisor messages?
> >
> > Dietmar.
> >
> > >
> > > 2012/4/18 Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx>
> > >
> > > > Am Mittwoch 18 April 2012, 17:28:27 schrieb �¦ 
> > > > �½�¥�®â�°�¤�¼�¦:
> > > > > hi , there guys
> > > > >
> > > > > some days ago ,i asked you some questions about the xen. now , i am
> > > > > confused with a crashed domain.
> > > > >
> > > > > one of my VM was working fine, then i create another. Now I am not
> > able
> > > > to
> > > > > start that VM.
> > > > >
> > > > > # xm create vm.cfg
> > > > > Using config file "./vm.cfg".
> > > > > Started domain clientvm1(id=2)
> > > > >
> > > > > It does give me the vm ID but it is not listed under "xm list"
> > > > >
> > > > > # xm list
> > > > > Name ID Mem VCPUs State Time(s)
> > > > > Domain-0 0 890 4 r----- 14808.1
> > > > >
> > > > > clientvm 1 1024 2 -b---- 939.2
> > > > >
> > > > > again i have to do xm create ..and the story repeats...
> > > > >
> > > > > I looked into logs and i see following:
> > > > >
> > > > > [2010-02-04 22:47:52 23777] INFO (XendDomain:1180) Domain
> >  clientvm1(2)
> > > > > unpaused.
> > > > > [2010-02-04 22:47:57 23777] WARNING (XendDomainInfo:1898) Domain has
> > > > > crashed: name=clientvm1 id=2.
> > > >
> > > > Try
> > > > on_crash = 'preserve'
> > > > in your domU configuration file.
> > > >
> > > > In this case the domU should stay in the crash state but never gets
> > > > destroyed
> > > > from the tools. You have to do this by hand later.
> > > >
> > > > For this see:
> > > > http://wiki.xen.org/wiki/XenConfigurationFileOptions
> > > >
> > > > Dietmar.
> > > >
> > > > > [2010-02-04 22:47:57 23777] ERROR (XendDomainInfo:2032) VM clientvm1
> > > > > restarting too fast (Elapsed time: 4.960329 seconds). Refusing to
> > restart
> > > > > to avoid loops.
> > > > > [2010-02-04 22:47:57 23777] DEBUG (XendDomainInfo:2748)
> > > > > XendDomainInfo.destroy: domid=2
> > > > > [2010-02-04 22:47:58 23777] DEBUG (XendDomainInfo:2221) Destroying
> > device
> > > > > model
> > > > > [2010-02-04 22:47:58 23777] INFO (image:553) clientvm1 device model
> > > > > terminated
> > > > >  what's up with " restarting too fast" and how to avoid that ?

-- 
Company details: http://ts.fujitsu.com/imprint.html

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users