Hi Shriram,
Thank you for the reply.
> 1. What kind of workload were you running?
I was running default processes started with OS in the case of Dom0 and DomU.
> 2. Are there any debug outputs from xen when restoring the VM?
> (you can do "xm dmesg" and you ll know if xen has any complaints) If the
> error outputs from xen match with the one I had quoted in the email thread
> you refer to, then I would get a clearer picture of how to help you out.
The result of "xm dmesg" command at primary host is in "primary_xm_dmesg.txt"
file attached to this e-mail.
The result of "xm info" command at primary host is in "primary_xm_info.txt"
file.
The result of "xm dmesg" command at backup host is in "backup_xm_dmesg.txt"
file.
The result of "xm info" command at backup host is in "backup_xm_info.txt" file.
When "xm destroy DomU" command was executed at primary host, the xend log in
backup host was created.
The log is in "backup_xend.log" file.
When "xm destroy DomU" command was executed at primary host, the rest of log in
backup host was created.
The log is in "backup_all.log" file.
Details of my environment are as follows.
- Xen version
4.0.2-rc1
- Dom0 OS
Fedora13 64bit(kernel 2.6.32.27-xen)
- DomU OS
CentOS5.4 32bit(kernel 2.6.18.8-xen)
- kernel config(Dom0)
"Dom0_.config" file.
- kernel config(DomU)
"DomU_.config" file.
- Domain Config File
"Guest02" file.
- xend-config.sxp
"xend-config.sxp" file.
- Hardware
Dell PowerEdge T110
CPU : Xeon X3470 2.93GHz
Memory : 8GB
The procedure that I did is as follows.
1. Start Dom0 at primary host and backup host.
2. Start DomU at primary host. The DomU's name is Guest02.
3. Execute the "remus --no-net Guest02 10.21.35.30" command at primary host.
Backup host's IP address is 10.21.35.30.
4. Execute the "xm destroy Guest02" command at primary host.
Could you point them out if the mistakes are found in the above environment and
procedure?
Thanks in advance.
Best regards.
-----Original Message-----
From: Shriram Rajagopalan [mailto:rshriram@xxxxxxxxx]
Sent: Sunday, February 20, 2011 12:35 PM
To: Todd Deshane
Cc: Mori, Takeshi (Takeshi.M@xxxxxxxxxxxxxxx); xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] remus failure
Yes, I had solved that issue (albeit the solution is a hack).
I need the following info
1. What kind of workload were you running?
2. Are there any debug outputs from xen when restoring the VM?
(you can do "xm dmesg" and you ll know if xen has any complaints) If the
error outputs from xen match with the one I had quoted in the email thread you
refer to, then I would get a clearer picture of how to help you out.
cheers
shriram
On Sat, Feb 19, 2011 at 5:14 PM, Todd Deshane <todd.deshane@xxxxxxx> wrote:
> Maybe Shriram has some tips. I just added him to the CC.
>
> On Wed, Feb 16, 2011 at 7:57 AM,
primary_xm_dmesg.txt
Description: primary_xm_dmesg.txt
primary_xm_info.txt
Description: primary_xm_info.txt
backup_xm_dmesg.txt
Description: backup_xm_dmesg.txt
backup_xm_info.txt
Description: backup_xm_info.txt
backup_xend.log
Description: backup_xend.log
backup_all.log
Description: backup_all.log
Dom0_.config
Description: Dom0_.config
DomU_.config
Description: DomU_.config
Guest02
Description: Guest02
xend-config.sxp
Description: xend-config.sxp
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
| 
Home