WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

RE: [Xen-users] Help with a transfer

To: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] Help with a transfer
From: "Formoso, Travis" <Travis.Formoso@xxxxxxxxxxxxx>
Date: Mon, 9 Apr 2007 16:46:17 -0400
Delivery-date: Mon, 09 Apr 2007 13:39:09 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <H00000c1005e1ec9.1176144659.mars.blueslate.net@MHS>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
I found this page on the wiki: http://wiki.xensource.com/xenwiki/Fedora5Xen0DomU

This is the problem I am having and did try to use this to solve the problem.

It reads "and then specify /boot/$KERNEL-$DOMNAME.img as the ramdisk when 
booting $DOMNAME (either in the configuration file for $DOMNAME, or in the boot 
sequence in $DOMNAME -- in the latter case you'll have to copy 
/boot/$KERNEL-$DOMNAME.img from Dom0 into $DOMNAME's filesystem)"

Here is my monitoring config file (monitoring is the DOMNAME)

name = "monitoring"
memory = "230"
disk = [ 'file:/xen/disk.img,xvda,w' ]
vif = [ 'mac=00:16:3e:70:2b:0a' ]
uuid = "f15e7429-b109-0e66-f189-e3bab5a606bc"
bootloader="/usr/bin/pygrub"
ramdisk="/boot/2.6.19-1.2895.fc6xen-monitoring.img"

on_reboot   = 'restart'
on_crash    = 'restart'

is this correct?

I added the ramdisk part - not sure if that is correct according to the 
instructions.

Thanks,

Travis

-----Original Message-----
From: Formoso, Travis 
Sent: Monday, April 09, 2007 2:51 PM
To: xen-users
Subject: RE: [Xen-users] Help with a transfer

I made further progress. Now when I do a xm create -c I get the choice of 
choosing FC6. I choose it however I do get this error:

unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!

In the log file:
[2007-04-09 09:39:35 xend.XendDomainInfo 2087] DEBUG (XendDomainInfo:940) 
XendDomainInfo.handleShutdownWatch
[2007-04-09 09:39:39 xend.XendDomainInfo 2087] WARNING (XendDomainInfo:882) 
Domain has crashed: name=monitoring id=11.
[2007-04-09 09:39:40 xend.XendDomainInfo 2087] ERROR (XendDomainInfo:1675) VM 
monitoring restarting too fast (4.582215 seconds since the last restart).  
Refusing to restart to avoid loops.
[2007-04-09 09:39:40 xend.XendDomainInfo 2087] DEBUG (XendDomainInfo:1463) 
XendDomainInfo.destroy: domid=11
[2007-04-09 09:39:40 xend.XendDomainInfo 2087] DEBUG (XendDomainInfo:1471) 
XendDomainInfo.destroyDomain(11)

Thanks,

Travis

-----Original Message-----
From: Formoso, Travis 
Sent: Monday, April 09, 2007 2:18 PM
To: xen-users
Subject: [Xen-users] Help with a transfer

Hello,

I am transferring a disk.img from one xen server to another. The original 
disk.img was used with Fedora Core 5. The new server has Fedora Core 6. 

I transferred the disk.img and the config file from the old server to the new 
one. Here is the output when I try to create the virtual machine.

[root@xen4 xen]# xm create -c monitoring 
Using config file "./monitoring". 
Going to boot Fedora Core (2.6.18-1.2257.fc5xenU) 
  kernel: /vmlinuz-2.6.18-1.2257.fc5xenU 
  initrd: /initrd-2.6.18-1.2257.fc5xenU.img 
Error: (22, 'Invalid argument') 

I get the Error message above. Is there any way to get this up and working? Any 
suggestions appreciated.

Thank you,

Travis





This e-mail and any files transmitted with it are for the sole use of
Blue Slate Solutions and the intended recipient(s) and may contain
confidential and privileged information. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
or any action taken in reliance on this e-mail is strictly prohibited
and may be unlawful.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users





This e-mail and any files transmitted with it are for the sole use of
Blue Slate Solutions and the intended recipient(s) and may contain
confidential and privileged information. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
or any action taken in reliance on this e-mail is strictly prohibited
and may be unlawful.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users





This e-mail and any files transmitted with it are for the sole use of
Blue Slate Solutions and the intended recipient(s) and may contain
confidential and privileged information. If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message. Any unauthorized review, use,
disclosure, dissemination, forwarding, printing or copying of this email
or any action taken in reliance on this e-mail is strictly prohibited
and may be unlawful.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

<Prev in Thread] Current Thread [Next in Thread>