aloa list, i have an existing fedora core 1 machine and want to convert this machine to a xen-domU on a fc6(7) dom0. i tried the following: - create an imagefile and format it. - rsync the existing machine to the xen-dom0 into the mounted image file - then i took the existing kernel of a fc6 domU and copied it to the fc1-domU there is a problem during the systemboot and so i think there should be better ways to convert the fc1 machine to a xen-domU. what way would you suggest? thanks and greetings jm
aloa, > FC-1 is EOL. Dead. Try FC6 or later. no, that''s not an option. i have an existing FC1 machine and i need to get this one working in a xen enviroment. there HAS TO be a way to get it working ;) g. jm Deependra Shekhawat schrieb:> HI, > > FC-1 is EOL. Dead. Try FC6 or later. > > Thanks > > On 5/24/07, *jm-ml* <jm-ml@guzman.at <mailto:jm-ml@guzman.at>> wrote: > > aloa list, > i have an existing fedora core 1 machine and want to convert this > machine to a xen-domU on a fc6(7) dom0. > i tried the following: > - create an imagefile and format it. > - rsync the existing machine to the xen-dom0 into the mounted > image file > - then i took the existing kernel of a fc6 domU and copied it to the > fc1-domU > > there is a problem during the systemboot and so i think there > should be > better ways to convert the fc1 machine to a xen-domU. > what way would you suggest? > > thanks and greetings > jm > > -- > Fedora-xen mailing list > Fedora-xen@redhat.com <mailto:Fedora-xen@redhat.com> > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > -- > Enjoy Life !
Hmmm... there are to many changes to different libraries since Version 1 and a differen format of the initrd. So you will have only a very little chance to run it. Try to compile a 2.6.20 kernel with xen-extensions without any module on your FC1! Then try to start the virtual machine with this DomU-kernel. Perhaps you have to remove the /lib/tls to get more performance. More informations to compile the xen-kernel under http://www.xensource.com. Greetings Frank Am Donnerstag Mai 24 2007 schrieb jm-ml:> aloa, > > > FC-1 is EOL. Dead. Try FC6 or later. > > no, that''s not an option. i have an existing FC1 machine and i need to > get this one working in a xen enviroment. there HAS TO be a way to get > it working ;) > g. jm > > Deependra Shekhawat schrieb: > > HI, > > > > FC-1 is EOL. Dead. Try FC6 or later. > > > > Thanks > > > > On 5/24/07, *jm-ml* <jm-ml@guzman.at <mailto:jm-ml@guzman.at>> wrote: > > > > aloa list, > > i have an existing fedora core 1 machine and want to convert this > > machine to a xen-domU on a fc6(7) dom0. > > i tried the following: > > - create an imagefile and format it. > > - rsync the existing machine to the xen-dom0 into the mounted > > image file > > - then i took the existing kernel of a fc6 domU and copied it to the > > fc1-domU > > > > there is a problem during the systemboot and so i think there > > should be > > better ways to convert the fc1 machine to a xen-domU. > > what way would you suggest? > > > > thanks and greetings > > jm > > > > -- > > Fedora-xen mailing list > > Fedora-xen@redhat.com <mailto:Fedora-xen@redhat.com> > > https://www.redhat.com/mailman/listinfo/fedora-xen > > > > > > > > > > -- > > Enjoy Life ! > > -- > Fedora-xen mailing list > Fedora-xen@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-xen-- Gruß Frank Rosendahl Fingerprint: 7506 6D0F 2C79 09A6 A8CF E51D BEF0 0279 A989 8450
On Thu, 24 May 2007, jm-ml wrote:> i have an existing fedora core 1 machine and want to convert this machine to a > xen-domU on a fc6(7) dom0. > i tried the following: > - create an imagefile and format it. > - rsync the existing machine to the xen-dom0 into the mounted image file > - then i took the existing kernel of a fc6 domU and copied it to the fc1-domUYou also put the modules of that kernel in /lib/modules/ ? If you don''t the initrd process will break.> there is a problem during the systemboot and so i think there should be better > ways to convert the fc1 machine to a xen-domU.You''re on the right track, but remember: - use an FC6 kernel+initrd and make sure /lib/modules/XXX are there - on the physical machine, build module-init-tools (fc1 still uses modutils AFAIK) and transfer this to your new image (not needed if you don''t need any modules not loaded by initrd, eg disk, net, ext3,) - mv /lib/tls /lib/tls-disabled on your image - rebuild the initrd to include xenblk using: mkinitrd --preload xenblk --with=xennet /boot/initrd-2.6.20-1.2944.fc6-xenu.img 2.6.20-1.2944.fc6 - don''t use pygrub to boot, but specify the kernel/ramdisk options in the xen config file. - disable sshd and only use the xen console to login (remember, FC is after all EOL) This worked to get our FC1 legacy machine virtualised. I might have forgotten something, since it''s been a long time since we converted this machine. So feel free to ask if you get any other problems. Paul
I would like to ask a question that I was hoping would get answered in this thread. With physical hardware machines you can boot from an Install CD and do an upgrade. I doubt a F7 will be able to handle a FC1 or lower, but I have upgraded very old machines doing steps (RH8 to FC1 to FC3 to FC5 in the past). I don''t have hardware virtualization, so booting an install CD within a XenU isn''t possible. I am wondering if there is a way to launch an upgrade process similar to what is on the CD, but within a paravirtualized XenU. Just forcing an upgrade of the fedora-release, and then doing a ''yum update'' doesn''t work well given the packages are being upgraded in the same context that yum is running. This is one of those things with I''ve seen Debian based systems handle better, and is one of the areas I''d love to see improvements in Fedora. Side-note: My ISP recommends against doing upgrades with RHEL -- I have customers with RHEL3 and RHEL4 that I want to upgrade to RHEL5, and I''m told that the only reliable way to do that is to wipe and re-install RHEL5 and then reconfigure all my software. -- Russell McOrmond, Internet Consultant: <http://www.flora.ca/> Please help us tell the Canadian Parliament to protect our property rights as owners of Information Technology. Sign the petition! http://www.digital-copyright.ca/petition/ict/ "The government, lobbied by legacy copyright holders and hardware manufacturers, can pry my camcorder, computer, home theatre, or portable media player from my cold dead hands!"
Russell McOrmond wrote:> > I would like to ask a question that I was hoping would get answered > in this thread. With physical hardware machines you can boot from an > Install CD and do an upgrade. I doubt a F7 will be able to handle a > FC1 or lower, but I have upgraded very old machines doing steps (RH8 > to FC1 to FC3 to FC5 in the past). > > I don''t have hardware virtualization, so booting an install CD > within a XenU isn''t possible. I am wondering if there is a way to > launch an upgrade process similar to what is on the CD, but within a > paravirtualized XenU. > > Just forcing an upgrade of the fedora-release, and then doing a ''yum > update'' doesn''t work well given the packages are being upgraded in the > same context that yum is running. This is one of those things with > I''ve seen Debian based systems handle better, and is one of the areas > I''d love to see improvements in Fedora.Always after a couple of tests on my machines at home, I''ve two dozen remote upgrades on production servers using yum. RH9->FC1 was a complete disaster, but every iteration of FC has been better. I have one server that has gone from FC2->3->4->5->6 all via yum upgrades and all remotely (I hate that datacenter). This last go around I took 4 other machines from FC4->5->6 with no problems whatsoever. The one additional step I always take is: 1) force the upgrade of fedora release, 2) *upgrade yum*, then 3) yum upgrade the rest of the system.> Side-note: My ISP recommends against doing upgrades with RHEL -- I > have customers with RHEL3 and RHEL4 that I want to upgrade to RHEL5, > and I''m told that the only reliable way to do that is to wipe and > re-install RHEL5 and then reconfigure all my software. >It''s in your ISP''s best interest to err on the side of caution, but I don''t have any personal experience with RHEL, so I''ll leave it at that.