Hi, I am converting few physical machines to xen virtual machines. The virt-p2v requires my physical machines to shut down. These servers are centos / redhat 5.x. I will be using tap:aio. How do I create an img file from my partitions? some has 1 HDD and some has 2 or more. Thanks! Paras. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
For my manual p2v I just generally boot a livecd (knoppix in my case), and then dd the local storage exactly as is to a NFS share or using dd/netcat. Then you just need to create a matching cfg, and then do the proper tweaks for the os in question. - chris On Fri, May 14, 2010 at 12:52 PM, Paras pradhan <pradhanparas@gmail.com> wrote:> Hi, > I am converting few physical machines to xen virtual machines. The virt-p2v > requires my physical machines to shut down. These servers are centos / > redhat 5.x. I will be using tap:aio. How do I create an img file from my > partitions? some has 1 HDD and some has 2 or more. > > Thanks! > Paras. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Paras, I''ve done p2v migrations another way, that we''ve found a little easier to manage: - stop all services but networking on the host to migrate (httpd, mysql, etc.) - create a target volume on our virtualization SAN with the desired size - mke2fs the target volume, and mount it somewhere - "rsync -a" the entire filesystem from the host we are migrating to the target volume (probably easier if you umount /proc) - Edit /etc/fstab on the target volume, changing from physical devices to Xen block devices - unmount the target volume and stop the physical host - create a Xen configuration to go with the target volume, and appropriate kernel/ramdisk - "xm create" the new host A few extra steps may be necessary, such as adjusting ifconfig-eth0 for the new MAC address, adding xvc0 to /etc/securetty, etc. This plan lets us partition storage for the virtualization environment however we like. To keep it simple we often use a single large root partition-Xen does not require a /boot filesystem on a paravirtualized domU unless you use pygrub. Jeff From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Paras pradhan Sent: Friday, May 14, 2010 12:53 PM To: Xen Users Subject: [Xen-users] Manual p2v Hi, I am converting few physical machines to xen virtual machines. The virt-p2v requires my physical machines to shut down. These servers are centos / redhat 5.x. I will be using tap:aio. How do I create an img file from my partitions? some has 1 HDD and some has 2 or more. Thanks! Paras. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Jeff, Thanks for the reply. What I did is: * dd a image file and mounted as a loop file. * copied everything including /boot except /proc /sys I will be using Paravirt and Pygrub. So I am a bit confused how to handle /boot using pygrub. Thanks Paras. On Fri, May 14, 2010 at 12:24 PM, Jeff Sturm <jeff.sturm@eprize.com> wrote:> Hi Paras, > > > > I''ve done p2v migrations another way, that we''ve found a little easier to > manage: > > > > - stop all services but networking on the host to migrate (httpd, > mysql, etc.) > > - create a target volume on our virtualization SAN with the desired > size > > - mke2fs the target volume, and mount it somewhere > > - "rsync –a" the entire filesystem from the host we are migrating to > the target volume (probably easier if you umount /proc) > > - Edit /etc/fstab on the target volume, changing from physical > devices to Xen block devices > > - unmount the target volume and stop the physical host > > - create a Xen configuration to go with the target volume, and > appropriate kernel/ramdisk > > - "xm create" the new host > > > > A few extra steps may be necessary, such as adjusting ifconfig-eth0 for the > new MAC address, adding xvc0 to /etc/securetty, etc. > > > > This plan lets us partition storage for the virtualization environment > however we like. To keep it simple we often use a single large root > partition—Xen does not require a /boot filesystem on a paravirtualized domU > unless you use pygrub. > > > > Jeff > > > > *From:* xen-users-bounces@lists.xensource.com [mailto: > xen-users-bounces@lists.xensource.com] *On Behalf Of *Paras pradhan > *Sent:* Friday, May 14, 2010 12:53 PM > *To:* Xen Users > *Subject:* [Xen-users] Manual p2v > > > > Hi, > > > > I am converting few physical machines to xen virtual machines. The virt-p2v > requires my physical machines to shut down. These servers are centos / > redhat 5.x. I will be using tap:aio. How do I create an img file from my > partitions? some has 1 HDD and some has 2 or more. > > > > > > Thanks! > > Paras. > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Wed, May 19, 2010 at 3:40 AM, Paras pradhan <pradhanparas@gmail.com> wrote:> Hi Jeff, > Thanks for the reply. What I did is: > * dd a image file and mounted as a loop file. > * copied everything including /boot except /proc /sys > I will be using Paravirt and Pygrub. So I am a bit confused how to handle > /boot using pygrub.which part are you confused about? As long as you put the disk image containing /boot first in your domU config file, pygrub should pick it up just fine. The more important issue, since you''ll be using paravirt (PV) guest, is to prepare your system so it has PV-compatible kernel and config (grub.conf, fstab, etc.). See http://pastebin.com/f6a5022bf for example. The example is for converting HVM domU to PV, but some of the info should also apply to converting physical machine to PV. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Here is where I am stuck at:
I have a xenifed kernel installed for the PV. When I do: xm create domUname
-c
I get this:
---
[root@cvtst1 ~]# xm create centos1 -c
Using config file "/etc/xen/centos1".
Traceback (most recent call last):
File "/usr/bin/pygrub", line 684, in ?
data = fs.open_file(chosencfg["kernel"]).read()
IOError: [Errno 2] No such file or directory
No handlers could be found for logger "xend"
Error: Boot loader didn''t return any data!
Usage: xm create <ConfigFile> [options] [vars]
---
Looks like it is not finding kernel, initrd (?)
---
grub.conf entry is:
title CentOS (2.6.18-194.3.1.el5xen)
root (hd0,0)
kernel /xen.gz-2.6.18-194.3.1.el5
module /vmlinuz-2.6.18-194.3.1.el5xen ro root=/dev/xvda1 console=xvc0
module /initrd-2.6.18-194.3.1.el5xen.img
---
config file for domU is:
--
[root@cvtst1 vms]# more centos1
name = "centos1"
maxmem = 1024
memory = 256
vcpus = 1
cpus="1-2"
bootloader = "/usr/bin/pygrub"
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
disk = [ "tap:aio:/vms/centos1.img,xvda1,w",
"tap:aio:/vms/centos1.swap,xvdb1,w" ]
--
Thanks!
Paras
On Tue, May 18, 2010 at 10:03 PM, Fajar A. Nugraha <fajar@fajar.net>
wrote:
> On Wed, May 19, 2010 at 3:40 AM, Paras pradhan
<pradhanparas@gmail.com>
> wrote:
> > Hi Jeff,
> > Thanks for the reply. What I did is:
> > * dd a image file and mounted as a loop file.
> > * copied everything including /boot except /proc /sys
> > I will be using Paravirt and Pygrub. So I am a bit confused how to
handle
> > /boot using pygrub.
>
> which part are you confused about? As long as you put the disk image
> containing /boot first in your domU config file, pygrub should pick it
> up just fine. The more important issue, since you''ll be using
paravirt
> (PV) guest, is to prepare your system so it has PV-compatible kernel
> and config (grub.conf, fstab, etc.). See http://pastebin.com/f6a5022bf
> for example. The example is for converting HVM domU to PV, but some of
> the info should also apply to converting physical machine to PV.
>
> --
> Fajar
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Ignore my last email. I missed /boot in at grub.conf. Thanks Paras. On Wed, May 19, 2010 at 11:49 AM, Paras pradhan <pradhanparas@gmail.com>wrote:> Here is where I am stuck at: > > I have a xenifed kernel installed for the PV. When I do: xm create domUname > -c > > I get this: > > --- > > [root@cvtst1 ~]# xm create centos1 -c > Using config file "/etc/xen/centos1". > Traceback (most recent call last): > File "/usr/bin/pygrub", line 684, in ? > data = fs.open_file(chosencfg["kernel"]).read() > IOError: [Errno 2] No such file or directory > No handlers could be found for logger "xend" > Error: Boot loader didn''t return any data! > Usage: xm create <ConfigFile> [options] [vars] > > --- > > Looks like it is not finding kernel, initrd (?) > > --- > grub.conf entry is: > title CentOS (2.6.18-194.3.1.el5xen) > root (hd0,0) > kernel /xen.gz-2.6.18-194.3.1.el5 > module /vmlinuz-2.6.18-194.3.1.el5xen ro root=/dev/xvda1 console=xvc0 > module /initrd-2.6.18-194.3.1.el5xen.img > --- > > config file for domU is: > > -- > [root@cvtst1 vms]# more centos1 > name = "centos1" > maxmem = 1024 > memory = 256 > vcpus = 1 > cpus="1-2" > bootloader = "/usr/bin/pygrub" > on_poweroff = "destroy" > on_reboot = "restart" > on_crash = "restart" > disk = [ "tap:aio:/vms/centos1.img,xvda1,w", > "tap:aio:/vms/centos1.swap,xvdb1,w" ] > -- > > > Thanks! > Paras > > > On Tue, May 18, 2010 at 10:03 PM, Fajar A. Nugraha <fajar@fajar.net>wrote: > >> On Wed, May 19, 2010 at 3:40 AM, Paras pradhan <pradhanparas@gmail.com> >> wrote: >> > Hi Jeff, >> > Thanks for the reply. What I did is: >> > * dd a image file and mounted as a loop file. >> > * copied everything including /boot except /proc /sys >> > I will be using Paravirt and Pygrub. So I am a bit confused how to >> handle >> > /boot using pygrub. >> >> which part are you confused about? As long as you put the disk image >> containing /boot first in your domU config file, pygrub should pick it >> up just fine. The more important issue, since you''ll be using paravirt >> (PV) guest, is to prepare your system so it has PV-compatible kernel >> and config (grub.conf, fstab, etc.). See http://pastebin.com/f6a5022bf >> for example. The example is for converting HVM domU to PV, but some of >> the info should also apply to converting physical machine to PV. >> >> -- >> Fajar >> > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I think I am close to get this converted VM running. When I try to login to domU I am getting login permission denied.. --- localhost.localdomain login: root Password: Last login: Wed May 19 13:17:37 on xvc0 login: no shell: Permission denied. -- Don''t know what is wrong here. Thanks! Paras. On Wed, May 19, 2010 at 11:53 AM, Paras pradhan <pradhanparas@gmail.com>wrote:> Ignore my last email. I missed /boot in at grub.conf. > > Thanks > Paras. > > > On Wed, May 19, 2010 at 11:49 AM, Paras pradhan <pradhanparas@gmail.com>wrote: > >> Here is where I am stuck at: >> >> I have a xenifed kernel installed for the PV. When I do: xm create >> domUname -c >> >> I get this: >> >> --- >> >> [root@cvtst1 ~]# xm create centos1 -c >> Using config file "/etc/xen/centos1". >> Traceback (most recent call last): >> File "/usr/bin/pygrub", line 684, in ? >> data = fs.open_file(chosencfg["kernel"]).read() >> IOError: [Errno 2] No such file or directory >> No handlers could be found for logger "xend" >> Error: Boot loader didn''t return any data! >> Usage: xm create <ConfigFile> [options] [vars] >> >> --- >> >> Looks like it is not finding kernel, initrd (?) >> >> --- >> grub.conf entry is: >> title CentOS (2.6.18-194.3.1.el5xen) >> root (hd0,0) >> kernel /xen.gz-2.6.18-194.3.1.el5 >> module /vmlinuz-2.6.18-194.3.1.el5xen ro root=/dev/xvda1 console=xvc0 >> module /initrd-2.6.18-194.3.1.el5xen.img >> --- >> >> config file for domU is: >> >> -- >> [root@cvtst1 vms]# more centos1 >> name = "centos1" >> maxmem = 1024 >> memory = 256 >> vcpus = 1 >> cpus="1-2" >> bootloader = "/usr/bin/pygrub" >> on_poweroff = "destroy" >> on_reboot = "restart" >> on_crash = "restart" >> disk = [ "tap:aio:/vms/centos1.img,xvda1,w", >> "tap:aio:/vms/centos1.swap,xvdb1,w" ] >> -- >> >> >> Thanks! >> Paras >> >> >> On Tue, May 18, 2010 at 10:03 PM, Fajar A. Nugraha <fajar@fajar.net>wrote: >> >>> On Wed, May 19, 2010 at 3:40 AM, Paras pradhan <pradhanparas@gmail.com> >>> wrote: >>> > Hi Jeff, >>> > Thanks for the reply. What I did is: >>> > * dd a image file and mounted as a loop file. >>> > * copied everything including /boot except /proc /sys >>> > I will be using Paravirt and Pygrub. So I am a bit confused how to >>> handle >>> > /boot using pygrub. >>> >>> which part are you confused about? As long as you put the disk image >>> containing /boot first in your domU config file, pygrub should pick it >>> up just fine. The more important issue, since you''ll be using paravirt >>> (PV) guest, is to prepare your system so it has PV-compatible kernel >>> and config (grub.conf, fstab, etc.). See http://pastebin.com/f6a5022bf >>> for example. The example is for converting HVM domU to PV, but some of >>> the info should also apply to converting physical machine to PV. >>> >>> -- >>> Fajar >>> >> >> >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Do you have SELinux enabled? If so, you may need to relabel the
filesystem:
touch /.autorelabel
before you boot.
From: xen-users-bounces@lists.xensource.com
[mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Paras
pradhan
Sent: Wednesday, May 19, 2010 1:36 PM
To: Fajar A. Nugraha
Cc: Xen Users
Subject: Re: [Xen-users] Manual p2v
I think I am close to get this converted VM running. When I try to login
to domU I am getting login permission denied..
---
localhost.localdomain login: root
Password:
Last login: Wed May 19 13:17:37 on xvc0
login: no shell: Permission denied.
--
Don''t know what is wrong here.
Thanks!
Paras.
On Wed, May 19, 2010 at 11:53 AM, Paras pradhan <pradhanparas@gmail.com>
wrote:
Ignore my last email. I missed /boot in at grub.conf.
Thanks
Paras.
On Wed, May 19, 2010 at 11:49 AM, Paras pradhan <pradhanparas@gmail.com>
wrote:
Here is where I am stuck at:
I have a xenifed kernel installed for the PV. When I do: xm create
domUname -c
I get this:
---
[root@cvtst1 ~]# xm create centos1 -c
Using config file "/etc/xen/centos1".
Traceback (most recent call last):
File "/usr/bin/pygrub", line 684, in ?
data = fs.open_file(chosencfg["kernel"]).read()
IOError: [Errno 2] No such file or directory
No handlers could be found for logger "xend"
Error: Boot loader didn''t return any data!
Usage: xm create <ConfigFile> [options] [vars]
---
Looks like it is not finding kernel, initrd (?)
---
grub.conf entry is:
title CentOS (2.6.18-194.3.1.el5xen)
root (hd0,0)
kernel /xen.gz-2.6.18-194.3.1.el5
module /vmlinuz-2.6.18-194.3.1.el5xen ro root=/dev/xvda1
console=xvc0
module /initrd-2.6.18-194.3.1.el5xen.img
---
config file for domU is:
--
[root@cvtst1 vms]# more centos1
name = "centos1"
maxmem = 1024
memory = 256
vcpus = 1
cpus="1-2"
bootloader = "/usr/bin/pygrub"
on_poweroff = "destroy"
on_reboot = "restart"
on_crash = "restart"
disk = [ "tap:aio:/vms/centos1.img,xvda1,w",
"tap:aio:/vms/centos1.swap,xvdb1,w" ]
--
Thanks!
Paras
On Tue, May 18, 2010 at 10:03 PM, Fajar A. Nugraha <fajar@fajar.net>
wrote:
On Wed, May 19, 2010 at 3:40 AM, Paras pradhan <pradhanparas@gmail.com>
wrote:> Hi Jeff,
> Thanks for the reply. What I did is:
> * dd a image file and mounted as a loop file.
> * copied everything including /boot except /proc /sys
> I will be using Paravirt and Pygrub. So I am a bit confused how to
handle> /boot using pygrub.
which part are you confused about? As long as you put the disk image
containing /boot first in your domU config file, pygrub should pick it
up just fine. The more important issue, since you''ll be using paravirt
(PV) guest, is to prepare your system so it has PV-compatible kernel
and config (grub.conf, fstab, etc.). See http://pastebin.com/f6a5022bf
for example. The example is for converting HVM domU to PV, but some of
the info should also apply to converting physical machine to PV.
--
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Jeff, That was the problem. Thanks guys for the help. Paras. On Wed, May 19, 2010 at 2:01 PM, Jeff Sturm <jeff.sturm@eprize.com> wrote:> Do you have SELinux enabled? If so, you may need to relabel the > filesystem: > > > > touch /.autorelabel > > > > before you boot. > > > > *From:* xen-users-bounces@lists.xensource.com [mailto: > xen-users-bounces@lists.xensource.com] *On Behalf Of *Paras pradhan > *Sent:* Wednesday, May 19, 2010 1:36 PM > *To:* Fajar A. Nugraha > *Cc:* Xen Users > *Subject:* Re: [Xen-users] Manual p2v > > > > I think I am close to get this converted VM running. When I try to login to > domU I am getting login permission denied.. > > > > --- > > localhost.localdomain login: root > > Password: > > Last login: Wed May 19 13:17:37 on xvc0 > > login: no shell: Permission denied. > > -- > > > > Don''t know what is wrong here. > > > > Thanks! > > Paras. > > > > > > On Wed, May 19, 2010 at 11:53 AM, Paras pradhan <pradhanparas@gmail.com> > wrote: > > Ignore my last email. I missed /boot in at grub.conf. > > > > Thanks > > Paras. > > > > On Wed, May 19, 2010 at 11:49 AM, Paras pradhan <pradhanparas@gmail.com> > wrote: > > Here is where I am stuck at: > > > > I have a xenifed kernel installed for the PV. When I do: xm create domUname > -c > > > > I get this: > > > > --- > > > > [root@cvtst1 ~]# xm create centos1 -c > > Using config file "/etc/xen/centos1". > > Traceback (most recent call last): > > File "/usr/bin/pygrub", line 684, in ? > > data = fs.open_file(chosencfg["kernel"]).read() > > IOError: [Errno 2] No such file or directory > > No handlers could be found for logger "xend" > > Error: Boot loader didn''t return any data! > > Usage: xm create <ConfigFile> [options] [vars] > > > > --- > > > > Looks like it is not finding kernel, initrd (?) > > > > --- > > grub.conf entry is: > > title CentOS (2.6.18-194.3.1.el5xen) > > root (hd0,0) > > kernel /xen.gz-2.6.18-194.3.1.el5 > > module /vmlinuz-2.6.18-194.3.1.el5xen ro root=/dev/xvda1 > console=xvc0 > > module /initrd-2.6.18-194.3.1.el5xen.img > > --- > > > > config file for domU is: > > > > -- > > [root@cvtst1 vms]# more centos1 > > name = "centos1" > > maxmem = 1024 > > memory = 256 > > vcpus = 1 > > cpus="1-2" > > bootloader = "/usr/bin/pygrub" > > on_poweroff = "destroy" > > on_reboot = "restart" > > on_crash = "restart" > > disk = [ "tap:aio:/vms/centos1.img,xvda1,w", > "tap:aio:/vms/centos1.swap,xvdb1,w" ] > > -- > > > > > > Thanks! > > Paras > > > > > > On Tue, May 18, 2010 at 10:03 PM, Fajar A. Nugraha <fajar@fajar.net> > wrote: > > On Wed, May 19, 2010 at 3:40 AM, Paras pradhan <pradhanparas@gmail.com> > wrote: > > Hi Jeff, > > Thanks for the reply. What I did is: > > * dd a image file and mounted as a loop file. > > * copied everything including /boot except /proc /sys > > I will be using Paravirt and Pygrub. So I am a bit confused how to handle > > /boot using pygrub. > > which part are you confused about? As long as you put the disk image > containing /boot first in your domU config file, pygrub should pick it > up just fine. The more important issue, since you''ll be using paravirt > (PV) guest, is to prepare your system so it has PV-compatible kernel > and config (grub.conf, fstab, etc.). See http://pastebin.com/f6a5022bf > for example. The example is for converting HVM domU to PV, but some of > the info should also apply to converting physical machine to PV. > > -- > Fajar > > > > > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I think your domU.cfg file is missing a few things - like a kernel,
ramdisk, root, and network lines. What I have in my production VM (just
transferred from a physical machine):
ALSO needs kernel, init.d, and root= entries. What I have:
kernel = ''/boot/vmlinuz-2.6.26-2-xen-686''
ramdisk = ''/boot/initrd.img-2.6.26-2-xen-686''
memory = ''1024''
disk = [
''drbd:newserver1-root,xvda1,w'',
''drbd:newserver1-swap,xvda2,w'',
''drbd:newserver1-backup,xvda3,w''
]
root = ''/dev/xvda1 ro''
name = ''server1''
vif = [ ''ip=207.154.13.48,mac=00:16:3E:BE:68:F5'' ]
Paras pradhan wrote:> Here is where I am stuck at:
> I have a xenifed kernel installed for the PV. When I do: xm create
> domUname -c
> I get this:
>
> ---
> grub.conf entry is:
> title CentOS (2.6.18-194.3.1.el5xen)
> root (hd0,0)
> kernel /xen.gz-2.6.18-194.3.1.el5
> module /vmlinuz-2.6.18-194.3.1.el5xen ro root=/dev/xvda1 console=xvc0
> module /initrd-2.6.18-194.3.1.el5xen.img
> ---
>
> config file for domU is:
>
> --
> [root@cvtst1 vms]# more centos1
> name = "centos1"
> maxmem = 1024
> memory = 256
> vcpus = 1
> cpus="1-2"
> bootloader = "/usr/bin/pygrub"
> on_poweroff = "destroy"
> on_reboot = "restart"
> on_crash = "restart"
> disk = [ "tap:aio:/vms/centos1.img,xvda1,w",
> "tap:aio:/vms/centos1.swap,xvdb1,w" ]
> --
>
--
In theory, there is no difference between theory and practice.
In<fnord> practice, there is. .... Yogi Berra
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
I have documented of what I have done so far for successful conversion http://www.madanhost.org/wordpress/?p=5 Might be useful to others. Thanks Paras. On Wed, May 19, 2010 at 2:24 PM, Miles Fidelman <mfidelman@meetinghouse.net>wrote:> I think your domU.cfg file is missing a few things - like a kernel, > ramdisk, root, and network lines. What I have in my production VM (just > transferred from a physical machine): > > > ALSO needs kernel, init.d, and root= entries. What I have: > > kernel = ''/boot/vmlinuz-2.6.26-2-xen-686'' > ramdisk = ''/boot/initrd.img-2.6.26-2-xen-686'' > memory = ''1024'' > > disk = [ > ''drbd:newserver1-root,xvda1,w'', > ''drbd:newserver1-swap,xvda2,w'', > ''drbd:newserver1-backup,xvda3,w'' > ] > > root = ''/dev/xvda1 ro'' > > name = ''server1'' > vif = [ ''ip=207.154.13.48,mac=00:16:3E:BE:68:F5'' ] > > > Paras pradhan wrote: > >> Here is where I am stuck at: >> I have a xenifed kernel installed for the PV. When I do: xm create >> domUname -c >> I get this: >> >> --- >> grub.conf entry is: >> title CentOS (2.6.18-194.3.1.el5xen) >> root (hd0,0) >> kernel /xen.gz-2.6.18-194.3.1.el5 >> module /vmlinuz-2.6.18-194.3.1.el5xen ro root=/dev/xvda1 console=xvc0 >> module /initrd-2.6.18-194.3.1.el5xen.img >> --- >> >> config file for domU is: >> >> -- >> [root@cvtst1 vms]# more centos1 >> name = "centos1" >> maxmem = 1024 >> memory = 256 >> vcpus = 1 >> cpus="1-2" >> bootloader = "/usr/bin/pygrub" >> on_poweroff = "destroy" >> on_reboot = "restart" >> on_crash = "restart" >> disk = [ "tap:aio:/vms/centos1.img,xvda1,w", >> "tap:aio:/vms/centos1.swap,xvdb1,w" ] >> -- >> >> > -- > In theory, there is no difference between theory and practice. > In<fnord> practice, there is. .... Yogi Berra > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Paras pradhan wrote:> I have documented of what I have done so far for successful conversion > > http://www.madanhost.org/wordpress/?p=5 > > Might be useful to others. > >likewise, see my email from the other day: http://lists.xensource.com/archives/html/xen-users/2010-05/msg00589.html note that getting the console to respond post-boot involved adding: 8:2345:respawn:/sbin/getty 38400 hvc0 to the virtual machine''s /etc/inittab (I first logged in via ssh) -- In theory, there is no difference between theory and practice. In<fnord> practice, there is. .... Yogi Berra _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users