Bug 158895

Summary: Unable to 'xm save' domU
Product: [Fedora] Fedora Reporter: AJ Lewis <alewis>
Component: xenAssignee: Rik van Riel <riel>
Severity: medium Docs Contact:
Priority: medium    
Version: 4   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-05-31 12:16:49 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 158899    
Description Flags
strace of 'xm save oxygen ./oxygen.xen' none

Description AJ Lewis 2005-05-26 12:52:22 EDT
Description of problem:
I get an error when trying to run 'xm save dom dom.xen'

Version-Release number of selected component (if applicable):

How reproducible:
Every time

Steps to Reproduce:
1. Boot xen kernel
2. start xen domU
3. run 'xm save domain_name somefile'
Actual results:
Error: Internal Server Error

Expected results:
domU gets state saved into specified file and is suspended

Additional info:
migrating to localhost also fails.
# xm migrate oxygen localhost
Error: Internal Server Error

xfrd is running:
# ps ax | grep xfrd
 2399 ?        S      0:00 xfrd

I'll attach a backtrace as well
Comment 1 AJ Lewis 2005-05-26 12:53:38 EDT
Created attachment 114877 [details]
strace of 'xm save oxygen ./oxygen.xen'
Comment 2 AJ Lewis 2005-05-26 13:01:51 EDT
Hrm...looks like I can make it work by creating the directory
/var/lib/xen/xen-db/migrate - any reason that isn't created by the rpm?
Comment 3 Rik van Riel 2005-05-26 13:35:36 EDT
The RPM doesn't have that directory because it's not created by the "make
install" command that the spec file runs.


Guess I'll send some fixes upstream, as well as fixing it in the FC4 RPM...
Comment 4 Rik van Riel 2005-05-30 11:02:40 EDT
A fix for this issue was added to today's Xen RPM, 2-20050530
Comment 5 AJ Lewis 2005-05-31 11:37:43 EDT
Verified xen-2-20050530 corrects this issue.