search for: atomaticly

Two things: 1. I''m not convinced ''xm crash'' is needed - ''xm destroy'' will do this (and if you want a dump, do ''xm dump'' followed by ''xm destroy'') 2. I don''t see the point of the --noreboot option on ''xm dump'' -- I think this command should simply live-dump the specified domain - as

> Hi, Simon > > >Two things: > > > >1. I''m not convinced ''xm crash'' is needed - ''xm destroy'' will do this > >(and if you want > > a dump, do ''xm dump'' followed by ''xm destroy'') > > > What do you mean? > I think we cannot dump with "xm destroy" now. >

...to know if the existing data on the orignal 40GB drive in the system will be destroyed when I create the raid with mdadm. Also do the 2 drives after being setup with mdadm have to be reformated? Both the 40GB drives are now formated with ext3. If not, will the added 40GB drive assigned to the Raid1 atomaticly sync to the original 40GB drive. If so, what do I need to do to assure this will happend automaticly? Your comments are appreciated, as this is my first time to setup a software Raid1. Lee __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the be...

Hi, In the case of linux, crash_kexec() is occured by "sysrq c". In the case of DomainU on xen, Help is occured by "sysrq c" now. So The way of dumping DomainU''s memory manualy is nothing. I fix this issue by the following way. 1. Panic is occured by "sysrq c" on both Domain0 and DomainU. 2. On DomainU, coredump is generated in /var/xen/dump (on Domain0).