All, Right now I am in the process of migrating our Fedora Core 4 servers to Fedora Core 6. I set up the new xen server and transferred all the files from the old server to the new one. The directory structure has root.img, swap.img, and xmconfig. If I do: xm create c /xen/sec-int-dns/xmconfig I get the error: Using config file "/xen/sec-int-dns/xmconfig". Error: Kernel image does not exist: /boot/vmlinuz-2.6.12-1.1398_FC4xenU So it is looking for the older files which it should considering that is what is the xmconfig file. What is the best way to create the xen virtual machine from the root.img file and then do the upgrade to FC6? Any tips and pointers would be helpful - thank you, Travis ________________________________ Travis Formoso | Blue Slate Solutions Infrastructure Specialist | www.blueslate.net |518.810.0377| travis.formoso@blueslate.net 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.
Minor update: I moved the vmlinuz-2.6.12-1.1398_FC4xenU to /boot on the new server and then ran: xm create -c /xen/sec-int-dns/xmconfig and got this error: Error: (22, ''Invalid argument'') Thanks -----Original Message----- From: Formoso, Travis Sent: Thursday, July 19, 2007 3:44 PM To: ''fedora-xen@redhat.com'' Subject: Upgrading Xen machines All, Right now I am in the process of migrating our Fedora Core 4 servers to Fedora Core 6. I set up the new xen server and transferred all the files from the old server to the new one. The directory structure has root.img, swap.img, and xmconfig. If I do: xm create c /xen/sec-int-dns/xmconfig I get the error: Using config file "/xen/sec-int-dns/xmconfig". Error: Kernel image does not exist: /boot/vmlinuz-2.6.12-1.1398_FC4xenU So it is looking for the older files which it should considering that is what is the xmconfig file. What is the best way to create the xen virtual machine from the root.img file and then do the upgrade to FC6? Any tips and pointers would be helpful - thank you, Travis ________________________________ Travis Formoso | Blue Slate Solutions Infrastructure Specialist | www.blueslate.net |518.810.0377| travis.formoso@blueslate.net 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.
On Thu, Jul 19, 2007 at 03:51:21PM -0400, Formoso, Travis wrote:> Minor update: > > I moved the vmlinuz-2.6.12-1.1398_FC4xenU to /boot on the new server and then ran: > > xm create -c /xen/sec-int-dns/xmconfig and got this error: > > Error: (22, ''Invalid argument'')I''m guesing you''re trying a i386 kernel here ? FC4 is using the obsolete non-PAE kernels, while FC6 and later are all PAE. You can''t mix & match a PAE and non-PAE kernels in host & guest. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
Looking at the log files I did catch this: [root@xen5 xen]# cat /var/log/xen/xend-debug.log Nothing to flush. Nothing to flush. ERROR: Will only load images built for Xen v3.0 ERROR: Error constructing guest OS Anyone know what I could do to get this up and running?> Minor update:> I moved the vmlinuz-2.6.12-1.1398_FC4xenU to /boot on the new server and > > then ran:> xm create -c /xen/sec-int-dns/xmconfig and got this error:> Error: (22, ''Invalid argument'')> Thanks---> All,> Right now I am in the process of migrating our Fedora Core 4 servers to >Fedora Core 6. I set up the new xen server and transferred all the files > > from the old server to the new one.>The directory structure has root.img, swap.img, and xmconfig.>If I do: xm create c /xen/sec-int-dns/xmconfig I get the error: Using >config file "/xen/sec-int-dns/xmconfig". >Error: Kernel image does not exist: /boot/vmlinuz-2.6.12-1.1398_FC4xenU>So it is looking for the older files which it should considering that is >what is the xmconfig file.>What is the best way to create the xen virtual machine from the root.img >file and then do the upgrade to FC6?>Any tips and pointers would be helpful - thank you,>Travis________________________________ Travis Formoso | Blue Slate Solutions Infrastructure Specialist | www.blueslate.net |518.810.0377| travis.formoso@blueslate.net 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. -- Fedora-xen mailing list Fedora-xen@redhat.com https://www.redhat.com/mailman/listinfo/fedora-xen 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.