Hi, 
 
Check this link. 
http://lists.xensource.com/archives/html/xen-devel/2005-08/msg01228.html 
It seems to be(should be) that you are using an unstable version which
is 3.0, (looking at the configuration file of domain rawhide:
kernel="/boot/vmlinuz-2.6.12-1.1447_FC4xenU") 
I would advise you to try the latest stable version (2.0.7) which is available on the http://www.xensource.com/downloads/ 
installation. 
This link.. 
http://lists.xensource.com/archives/html/xen-devel/2005-08/msg00649.html 
...seems to be having resolution of this issue(I am not sure tho) 
Or else may be somebody else has the solution. 
 
Regards, 
Sharath.
 
 On 9/8/05, DIEDERIT@xxxxxxxxxxxxxxxxxxxxxxxxxxxx <
DIEDERIT@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
i used 
the manual from fedora, installing it via yum install 
xen.... 
  
Traceback (most recent call 
last):   File "/usr/lib/python2.4/logging/handlers.py", line 62, in 
emit     if self.shouldRollover(record):   File 
"/usr/lib/python2.4/logging/handlers.py", line 132, in 
shouldRollover     self.stream.seek(0, 2)  #due to 
non-posix-compliant Windows feature ValueError: I/O operation on closed 
file Traceback (most recent call last):   File 
"/usr/lib/python2.4/logging/handlers.py", line 62, in emit     
if self.shouldRollover(record):   File 
"/usr/lib/python2.4/logging/handlers.py", line 132, in 
shouldRollover     self.stream.seek(0, 2)  #due to 
non-posix-compliant Windows feature ValueError: I/O operation on closed 
file Traceback (most recent call last):   File 
"/usr/lib/python2.4/logging/handlers.py", line 62, in emit     
if self.shouldRollover(record):   File 
"/usr/lib/python2.4/logging/handlers.py", line 132, in 
shouldRollover     self.stream.seek(0, 2)  #due to 
non-posix-compliant Windows feature ValueError: I/O operation on closed 
file Traceback (most recent call last):   File 
"/usr/lib/python2.4/logging/handlers.py", line 62, in emit     
if self.shouldRollover(record):   File 
"/usr/lib/python2.4/logging/handlers.py", line 132, in 
shouldRollover     self.stream.seek(0, 2)  #due to 
non-posix-compliant Windows feature ValueError: I/O operation on closed 
file Traceback (most recent call last):   File 
"/usr/lib/python2.4/logging/handlers.py", line 62, in emit     
if self.shouldRollover(record):   File 
"/usr/lib/python2.4/logging/handlers.py", line 132, in 
shouldRollover     self.stream.seek(0, 2)  #due to 
non-posix-compliant Windows feature ValueError: I/O operation on closed 
file Traceback (most recent call last):   File 
"/usr/lib/python2.4/logging/handlers.py", line 62, in emit     
if self.shouldRollover(record):   File 
"/usr/lib/python2.4/logging/handlers.py", line 132, in 
shouldRollover     self.stream.seek(0, 2)  #due to 
non-posix-compliant Windows feature ValueError: I/O operation on closed 
file Traceback (most recent call last):   File 
"/usr/lib/python2.4/logging/handlers.py", line 62, in emit     
if self.shouldRollover(record):   File 
"/usr/lib/python2.4/logging/handlers.py", line 132, in 
shouldRollover     self.stream.seek(0, 2)  #due to 
non-posix-compliant Windows feature ValueError: I/O operation on closed 
file Traceback (most recent call last):   File 
"/usr/lib/python2.4/logging/handlers.py", line 62, in emit     
if self.shouldRollover(record):   File 
"/usr/lib/python2.4/logging/handlers.py", line 132, in 
shouldRollover     self.stream.seek(0, 2)  #due to 
non-posix-compliant Windows feature ValueError: I/O operation on closed 
file Traceback (most recent call last):   File 
"/usr/lib/python2.4/logging/handlers.py", line 62, in emit     
if self.shouldRollover(record):   File 
"/usr/lib/python2.4/logging/handlers.py", line 132, in 
shouldRollover "xend-debug.log" [nur Lesen] 1275L, 70422C
  
  
Thomas 
Diederich
  ************************************************** *  Boehringer 
Ingelheim Pharma GmbH & Co.KG *  A Informationsverarbeitung / I*Net 
Solution Center *  *  Mail: 
diederit@xxxxxxxxxxxxxxxxxxxxxxxxxxxx *  Phone: +49 
(0)6132/77-98151   
  
  -----Ursprüngliche Nachricht----- Von: Sharath Babu 
  [mailto:sharathx@xxxxxxxxx]  Gesendet: Donnerstag, 8. September 2005 
  11:58 Hi,
  Can you provide the xend-debug.log 
  file. and while.. 
  #xm create -c 
  rawhide 
  Using config file 
  "/etc/xen/rawhide". 
  started domain 
  rawhide  Does it provide the remote console or else 
  doest it freeze before providing you the remote console. Also, Are you 
  using the xen 3.0 version which came with FC4 or have you installed 
  2.0.7(stable) manually... Once i have tried the unstable version which came 
  with FC4, but that didnt work. it didnt boot up the domains, but dom0 boots up 
  fine. I gave up that and installed 2.0.7 which works 
  fne.
  Regards, Sharath
  
  On 9/8/05, DIEDERIT@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
 
  < 
  DIEDERIT@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
  
      
    #xm create -c 
    rawhide 
    Using config file 
    "/etc/xen/rawhide". 
    started domain 
    rawhide 
    -->nothing happens now, 
    seems like its frozen... 
      
    Config 
    file: 
      
    kernel = 
    "/boot/vmlinuz-2.6.12-1.1447_FC4xenU" 
    memory = 64 
    name = 
    "rawhide" 
    nics = 1 
    disk = 
    ['file:/root/fedora.img,sda1,w'] 
    root = 
    "/dev/sda1" 
    extra = "ro selinux=0 
    3" 
      
    Also the 
    command xm mem-set Domain-0 128 is not working. nothing 
    happens! 
       
      
      
    
  
      
    Thomas 
    Diederich
  ************************************************** *  
    Boehringer Ingelheim Pharma GmbH & Co.KG *  A 
    Informationsverarbeitung / I*Net Solution Center * 
     *  Mail: 
    diederit@xxxxxxxxxxxxxxxxxxxxxxxxxxxx
 *  Phone: +49 
    (0)6132/77-98151   
    
      
      
      Hi,  can you provide the 
      configuration file to look into this. also, you could provide much more 
      information, like, what do you see on the screen when you start a domain, 
      etc..
  Regards, Sharath
  
      
     
   
   
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users 
 |