search for: atomatically

...: Re: [Patch][RFC] Support "xm dump" (is Re: [Xen-devel] Re: > [Patch]Enable "sysrq c" handler for domU coredump) > > Hi, all > > >> For example panic dump option is used when domU kernel is hungup, > >> and we want to reboot and make coredump atomatically. > >I''d prefer ''xm crash'' (or ''xm panic'') and ''xm dump'' . > >I''d prefer ''xm dump'' *not* to panic by default. It is too dangerous. > > > OK. I also think both are necessary. > How about...

...he point of the --noreboot option on ''xm dump'' -- I > >think this command > > should simply live-dump the specified domain - as above you can use > >other commands > > to cause the domain to restart afterwards. > > > Ordinary dump features have atomatically rebooting features. > (e.g. diskdump, kdump, and so on) > So I think this is necessary. xm dump foo xm reboot foo does the job nicely -- why complicate things by adding extra options/commands > > >3. There''s no need to pause the domain to dump it - I actually wrote a &gt...

I want to mirror an existing 40GB data only drive using software Raid1 on my new CentOS 4 server. The existing drive is connected to a Promise Ultra 100 TX2 controller (non-raid). I have read about mdadm and understand how to create the Raid1 on /dev/mdxx devices. However I would like to know if the existing data on the orignal 40GB drive in the system will be destroyed when I create the raid with

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).