Fedora xen - Dec 2008 - RE: Urgent Help Required: FC10 as DomU on FC8 as Dom0

I have FC8 running as dom0 and i want to install FC10 as domU. I have installed
python-virtinst-0.300.2-5.fc8 from fedora standard repo on FC8. But still i am
unable to boot FC10 kernel on FC8.

Following error comes when I  try to boot F10 with Ramdisk created on FC8/ Dom0.

# xm create -c xxx.cfg

........
Creating root device.
Mounting root filesystem.
mount: could not find filesystem ''/dev/root''
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running init.
unmounting old /dev
unmounting old /proc
unmounting old /sys
switchroot: mount failed: No such file or directory
Booting has failed.
....................................................................

Here is my xen configuration file. 

-----------------------------------------
kernel = "/boot/vmlinuz-2.6.27.7-134.fc10.i686.PAE"
ramdisk = "/boot/initrd-2.6.27.7-134.fc10.i686.PAE-DomU.img"
memory = 128
name = "xxxx"
vif = [ ''ip=xx.xxx.xxxx.xxx'' ]
disk = [''tap:aio:/var/vm13/root,sda1,w'',
''tap:aio:/var/vm13/var,sda2,w'',
''tap:aio:/var/vm13/swap,sda3,w'']
root = "/dev/sda1 ro"
on_reboot   = ''restart''
on_crash    = ''restart''
------------------------------------------

How to boot FC-10 as domU on FC8?  I will appreciate help from xen experts.


Regards. Mateen

_________________________________________________________________
Send e-mail anywhere. No map, no compass.
http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_anywhere_122008

MOHAMMAD MATEEN ASLAM wrote:
> 
> I have FC8 running as dom0 and i want to install FC10 as domU. I have 
> installed python-virtinst-0.300.2-5.fc8 from fedora standard repo on 
> FC8. But still i am unable to boot FC10 kernel on FC8.
> 
The relevant doc is:
http://fedoraproject.org/wiki/Docs/Beats/Virtualization

More specifically:
http://fedoraproject.org/wiki/Docs/Beats/Virtualization#Xen_Updated_to_3.3.0

Fedora 8 would need pretty much all of its Xen-related packages updated 
to be able to handle the new F10 pv_ops kernel as a domU.  I believe 
there was discussion about building such packages and leaving them in 
the testing repo for F8 (i.e. not pushing them out before EOL) but I 
don''t remember what came of it.  Search the list for more details.

The short answer is pretty much use KVM instead or roll-your-own from 
upstream to get a dom0 that works with Fedora 10 as a domU.

Aaron

Hi Aaron,

Thanks for quick help. Infact my current network architecture dont allow me to
upgrade quickly to KVM. My FC8 is fully updated with standard update repo, but
not from test repo. Is there any difference between standard repo versions and
test repo versions ? My FC8 have the same python-vertinst version which was in
test repo.

Regards
Mohammad Mateen

> The relevant doc is:
> http://fedoraproject.org/wiki/Docs/Beats/Virtualization
> 
> More specifically:
>
http://fedoraproject.org/wiki/Docs/Beats/Virtualization#Xen_Updated_to_3.3.0
> 
> Fedora 8 would need pretty much all of its Xen-related packages updated 
> to be able to handle the new F10 pv_ops kernel as a domU.  I believe 
> there was discussion about building such packages and leaving them in 
> the testing repo for F8 (i.e. not pushing them out before EOL) but I 
> don''t remember what came of it.  Search the list for more details.
> 
> The short answer is pretty much use KVM instead or roll-your-own from 
> upstream to get a dom0 that works with Fedora 10 as a domU.
> 
> Aaron
_________________________________________________________________
Send e-mail faster without improving your typing skills.
http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_speed_122008

On Wed, Dec 17, 2008 at 06:43:52PM +0000, MOHAMMAD MATEEN ASLAM
wrote:
> 
> 
> I have FC8 running as dom0 and i want to install FC10 as domU. I have
installed python-virtinst-0.300.2-5.fc8 from fedora standard repo on FC8. But
still i am unable to boot FC10 kernel on FC8.
> 
> Following error comes when I  try to boot F10 with Ramdisk created on FC8/
Dom0.
> 
> # xm create -c xxx.cfg
> 
> ........
> Creating root device.
> Mounting root filesystem.
> mount: could not find filesystem ''/dev/root''
> Setting up other filesystems.
> Setting up new root fs
> setuproot: moving /dev failed: No such file or directory
> no fstab.sys, mounting internal defaults
> setuproot: error mounting /proc: No such file or directory
> setuproot: error mounting /sys: No such file or directory
> Switching to new root and running init.
> unmounting old /dev
> unmounting old /proc
> unmounting old /sys
> switchroot: mount failed: No such file or directory
> Booting has failed.
> ....................................................................
> 
> Here is my xen configuration file. 
> 
> -----------------------------------------
> kernel = "/boot/vmlinuz-2.6.27.7-134.fc10.i686.PAE"
> ramdisk = "/boot/initrd-2.6.27.7-134.fc10.i686.PAE-DomU.img"
> memory = 128
> name = "xxxx"
> vif = [ ''ip=xx.xxx.xxxx.xxx'' ]
> disk = [''tap:aio:/var/vm13/root,sda1,w'',
''tap:aio:/var/vm13/var,sda2,w'',
''tap:aio:/var/vm13/swap,sda3,w'']
> root = "/dev/sda1 ro"
> on_reboot   = ''restart''
> on_crash    = ''restart''
> ------------------------------------------
> 
> How to boot FC-10 as domU on FC8?  I will appreciate help from xen experts.
> 
https://bugzilla.redhat.com/show_bug.cgi?id=458164

"python-virtinst-0.300.2-5.fc8 has been pushed to the Fedora 8 stable
repository.  If problems still persist, please make note of it in this bug
report."

So the python-virtinst you have should be OK.

Are you sure your ramdisk/initrd is correct? based on the output you pasted
it seems your initrd image is not working correctly..

Have you tried installing F10 domU with the installer? 

-- Pasi

Hi Pasi,

Thanks for helping. Yes, apparently, the problem looks in Ramdisk. I have
created Ramdisk with following command but it is unable to boot FC10:-

mkinitrd -f --builtin=xenner --preload=xenblk --builtin=ehci-hcd
--builtin=ohci-hcd --builtin=uhci-hcd --builtin=ahci
--builtin=ata_piix /boot/initrd-2.6.27.7-134.fc10.i686.PAE-domU.img
2.6.27.7-134.fc10.i686.PAE
if i dont mention these modules  "--builtin=xenner --builtin=ehci-hcd
--builtin=ohci-hcd --builtin=uhci-hcd --builtin=ahci --builtin=ata_piix"  i
got following errors.
No module xenblk found for kernel 2.6.27.7-134.fc10.i686, aborting.
No module ehci-hcd found for kernel 2.6.27.7-134.fc10.i686, aborting.
No module ohci-hcd found for kernel 2.6.27.7-134.fc10.i686, aborting.
.....

I have also try to use Fedora 10 Ramdisk instead of re-creating but VM halt few
steps earlier giving these errors:-

...................................
TCP cubic registered
Initializing XFRM netlink socket
NET: Registered protocol family 17
Using IPI No-Shortcut mode
registered taskstats version 1
XENBUS: Device with no driver: device/vbd/2049
XENBUS: Device with no driver: device/vbd/2050
XENBUS: Device with no driver: device/vbd/2051
XENBUS: Device with no driver: device/vif/0
XENBUS: Device with no driver: device/console/0
  Magic number: 1:252:3141
Freeing unused kernel memory: 424k freed
Write protecting the kernel text: 2788k
Write protecting the kernel read-only data: 1184k
Mounting proc filesystem
Mounting sysfs filesystem
Creating /dev
Creating initial device nodes
Loading /lib/kbd/keymaps/i386/qwerty/us.map
------------------------------------------------------------


I have live updated my Old DomU (FC8)  -> to New DomU (FC10).  Plz let me
know if there is a batter way for Ramdisk.


Regards, Mateen


 
> https://bugzilla.redhat.com/show_bug.cgi?id=458164
> 
> "python-virtinst-0.300.2-5.fc8 has been pushed to the Fedora 8 stable
> repository.  If problems still persist, please make note of it in this bug
> report."
> 
> So the python-virtinst you have should be OK.
> 
> Are you sure your ramdisk/initrd is correct? based on the output you pasted
> it seems your initrd image is not working correctly..
> 
> Have you tried installing F10 domU with the installer? 
> 
> -- Pasi
_________________________________________________________________
Send e-mail anywhere. No map, no compass.
http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_anywhere_122008

On Wed, 17 Dec 2008, MOHAMMAD MATEEN ASLAM wrote:
> I have FC8 running as dom0 and i want to install FC10 as domU. I have
> installed python-virtinst-0.300.2-5.fc8 from fedora standard repo on FC8.
> But still i am unable to boot FC10 kernel on FC8.
...
> kernel = "/boot/vmlinuz-2.6.27.7-134.fc10.i686.PAE"
> ramdisk = "/boot/initrd-2.6.27.7-134.fc10.i686.PAE-DomU.img"
It worked for me using the vmlinuz-PAE and and initrd-PAE.img files from 
the DVD image (in the images/pxeboot directory). I suggest you retry 
with these in case there was some problem with the ramdisk you created.
The python-virtinst version shouldn''t matter if you are installing
using
xm and a configuration file, but the xen package does need to be updated 
to the latest fc8 version.

 	Michael Young

On Wed, Dec 17, 2008 at 09:45:52PM +0000, MOHAMMAD MATEEN ASLAM
wrote:
> 
> Hi Pasi,
> 
> Thanks for helping. Yes, apparently, the problem looks in Ramdisk. I have
created Ramdisk with following command but it is unable to boot FC10:-
> 
> mkinitrd -f --builtin=xenner --preload=xenblk --builtin=ehci-hcd
--builtin=ohci-hcd --builtin=uhci-hcd --builtin=ahci
> --builtin=ata_piix /boot/initrd-2.6.27.7-134.fc10.i686.PAE-domU.img
2.6.27.7-134.fc10.i686.PAE
> if i dont mention these modules  "--builtin=xenner --builtin=ehci-hcd
--builtin=ohci-hcd --builtin=uhci-hcd --builtin=ahci --builtin=ata_piix"  i
got following errors.
> No module xenblk found for kernel 2.6.27.7-134.fc10.i686, aborting.
> No module ehci-hcd found for kernel 2.6.27.7-134.fc10.i686, aborting.
> No module ohci-hcd found for kernel 2.6.27.7-134.fc10.i686, aborting.
> .....
> 
xenner is something you use on a KVM host to emulate Xen.. I think you
shouldn''t need/use xenner with the real Xen. And especially not in
domU,
xenner is for KVM "dom0".
> I have also try to use Fedora 10 Ramdisk instead of re-creating but VM halt
few steps earlier giving these errors:-
> 
> ...................................
> TCP cubic registered
> Initializing XFRM netlink socket
> NET: Registered protocol family 17
> Using IPI No-Shortcut mode
> registered taskstats version 1
> XENBUS: Device with no driver: device/vbd/2049
> XENBUS: Device with no driver: device/vbd/2050
> XENBUS: Device with no driver: device/vbd/2051
This means xen block/disk device (xvd) driver was not loaded.
> XENBUS: Device with no driver: device/vif/0
This means xen network driver was not loaded.

Does your kernel contain those modules? or are they built-in in the pv_ops
kernels? 
> XENBUS: Device with no driver: device/console/0
>   Magic number: 1:252:3141
> Freeing unused kernel memory: 424k freed
> Write protecting the kernel text: 2788k
> Write protecting the kernel read-only data: 1184k
> Mounting proc filesystem
> Mounting sysfs filesystem
> Creating /dev
> Creating initial device nodes
> Loading /lib/kbd/keymaps/i386/qwerty/us.map
> ------------------------------------------------------------
> 
> 
> I have live updated my Old DomU (FC8)  -> to New DomU (FC10).  Plz let
me know if there is a batter way for Ramdisk.
> 
So.. just to get it correctly:

1. You installed Fedora 8 domU 
2. You updated Fedora 8 domU to Fedora 10 (on the fly) with yum
3. You create initrd image for the F10 kernel using the mkinitrd command above

That should work.. assuming you get the initrd correct. 

You could also try installing a fresh F10 domU (with virt-install or
virt-manager) and see if that works.. 

-- Pasi

> xenner is something you use on a KVM host to emulate Xen.. I think you
> shouldn''t need/use xenner with the real Xen. And especially not in
domU,
> xenner is for KVM "dom0".

True, xenner is also required for KVM. I have used xenner module successfully
for my old FC8 (DomU) and it worked fine. On your advice I have tried to created
RamDisk without xenner but no luck.

> > XENBUS: Device with no driver: device/vbd/2049
> > XENBUS: Device with no driver: device/vbd/2050
> > XENBUS: Device with no driver: device/vbd/2051
> This means xen block/disk device (xvd) driver was not loaded.
> 
> > XENBUS: Device with no driver: device/vif/0
> 
> This means xen network driver was not loaded.
> 
> Does your kernel contain those modules? or are they built-in in the pv_ops
> kernels? 

This seems sound, i am using Latest FC10 kernel -2.6.27.7-134.fc10.i686.PAE as
DomU and Latest kernel 2.6.21.7-5.fc8xen on FC8 (Dom0). Ideally FC10 pv_ops
kernel should have these modules support, either built-in or as module.
 
> > I have live updated my Old DomU (FC8)  -> to New DomU (FC10).  Plz
let me know if there is a batter way for Ramdisk.
> > 
> 
> So.. just to get it correctly:
> 
> 1. You installed Fedora 8 domU 
> 2. You updated Fedora 8 domU to Fedora 10 (on the fly) with yum
> 3. You create initrd image for the F10 kernel using the mkinitrd command
above
> 
> That should work.. assuming you get the initrd correct. 

Yes you got exactly right,  logically it should work, but its not working. 

 
> You could also try installing a fresh F10 domU (with virt-install or
> virt-manager) and see if that works.. 

I am checking fresh installation via virt-install on another box with same
setup. I will post results here.


Regards, Mateen

_________________________________________________________________
You live life online. So we put Windows on the web. 
http://clk.atdmt.com/MRT/go/127032869/direct/01/

Hi young,

thanks for looking into problem.  I have used vmlinuz-PAE and and initrd-PAE.img
files from the DVD image (in the images/pxeboot directory). Installation starts,
after selecting language, i got this

            +-----------------+ No driver found +------------------+
            |                                                      |
            |       Unable to find any devices of the type         |
            |       needed for this installation type.                  |
            |       Would you like to manually select your         |
            |       driver or use a driver disk?                             |
            |                                                                   
|
            | +---------------+   +-------------------+  +------+  |
            | | Select driver |   | Use a driver disk |  | Back |  |
            | +---------------+   +-------------------+  +------+  |


I have tried to used both xen-blkfront, xen-netfront drivers, but installation
is unable to proceed further.

Do you successfully install and boot FC10 as DomU  on FC8 box?


 > It worked for me using the vmlinuz-PAE and and initrd-PAE.img files from
> the DVD image (in the images/pxeboot directory). I suggest you retry 
> with these in case there was some problem with the ramdisk you created.
> The python-virtinst version shouldn''t matter if you are installing
using
> xm and a configuration file, but the xen package does need to be updated 
> to the latest fc8 version.
> 
>  	Michael Young
_________________________________________________________________
Send e-mail faster without improving your typing skills.
http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_speed_122008

On Thu, Dec 18, 2008 at 05:21:30PM +0000, MOHAMMAD MATEEN ASLAM
wrote:
> 
> Hi young,
> 
> thanks for looking into problem.  I have used vmlinuz-PAE and and
initrd-PAE.img files from the DVD image (in the images/pxeboot directory).
Installation starts, after selecting language, i got this
> 
>             +-----------------+ No driver found +------------------+
>             |                                                      |
>             |       Unable to find any devices of the type         |
>             |       needed for this installation type.                  |
>             |       Would you like to manually select your         |
>             |       driver or use a driver disk?                           
|
>             |                                                              
|
>             | +---------------+   +-------------------+  +------+  |
>             | | Select driver |   | Use a driver disk |  | Back |  |
>             | +---------------+   +-------------------+  +------+  |
> 
> 
> I have tried to used both xen-blkfront, xen-netfront drivers, but
installation is unable to proceed further.
> 
> Do you successfully install and boot FC10 as DomU  on FC8 box?
> 
Can you please post the exact commands and/or cfgfiles you used to start the
installation? 

-- Pasi
> 
>  > It worked for me using the vmlinuz-PAE and and initrd-PAE.img files
from
> > the DVD image (in the images/pxeboot directory). I suggest you retry 
> > with these in case there was some problem with the ramdisk you
created.
> > The python-virtinst version shouldn''t matter if you are
installing using
> > xm and a configuration file, but the xen package does need to be
updated
> > to the latest fc8 version.
> > 
> >  	Michael Young
>

# cat  vm.cfg

kernel = "/boot/vmlinuz-PAE"
ramdisk = "/boot/initrd-PAE.img"

memory = 128
name = "xxxxx"
vif = [ ''ip=xx.xx.xx.xx'' ]
disk = [''tap:aio:/var/xen/vm13/root,sda1,w'',
''tap:aio:/var/xen/vm13/var,sda2,w'',
''tap:aio:/var/xen/vm13/swap,sda3,w'']
root = "/dev/sda1 ro"
on_reboot   = ''restart''
on_crash    = ''restart''

# xm create -c vm.cfg    -> for booting vm

> Can you please post the exact commands and/or cfgfiles you used to start
the
> installation? 
> 
> -- Pasi
> 
> > 
> >  > It worked for me using the vmlinuz-PAE and and initrd-PAE.img
files from
> > > the DVD image (in the images/pxeboot directory). I suggest you
retry
> > > with these in case there was some problem with the ramdisk you
created.
> > > The python-virtinst version shouldn''t matter if you are
installing using
> > > xm and a configuration file, but the xen package does need to be
updated
> > > to the latest fc8 version.
> > > 
> > >  	Michael Young
> > 
_________________________________________________________________
Send e-mail faster without improving your typing skills.
http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_speed_122008

i think it doesn''t matter what xenserver block devices is for Guest OS.
You can get more details from

http://searchservervirtualization.techtarget.com/tip/0,289483,sid94_gci1281401,00.html

> Should that be xvda rather than sda? I think xvda is required in some 
> situations. I am not familar with the tap:aio: prefix either, I would have 
> expected something like file: but as I mostly map partitions to disks or 
> partitions it isn''t an area I am expert it.
> 
>  	Michael Young
_________________________________________________________________
Send e-mail faster without improving your typing skills.
http://windowslive.com/Explore/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_speed_122008

On Thu, Dec 18, 2008 at 07:14:50PM +0000, MOHAMMAD MATEEN ASLAM
wrote:
> 
> # cat  vm.cfg
> 
> kernel = "/boot/vmlinuz-PAE"
> ramdisk = "/boot/initrd-PAE.img"
> 
> memory = 128
> name = "xxxxx"
> vif = [ ''ip=xx.xx.xx.xx'' ]
> disk = [''tap:aio:/var/xen/vm13/root,sda1,w'',
''tap:aio:/var/xen/vm13/var,sda2,w'',
''tap:aio:/var/xen/vm13/swap,sda3,w'']
> root = "/dev/sda1 ro"
> on_reboot   = ''restart''
> on_crash    = ''restart''
> 
> # xm create -c vm.cfg    -> for booting vm
> 
Your disk configuration is wrong. 

You need to have xvda disk for domU.

Something like this:

disk = [''tap:aio:/var/xen/vm13/xvda,xvda,w'']

if ''tap:aio'' doesn''t work, then try just
''file''.

-- Pasi

On Thu, Dec 18, 2008 at 09:46:21PM +0000, MOHAMMAD MATEEN ASLAM
wrote:
> 
> 
> i think it doesn''t matter what xenserver block devices is for
Guest OS.
IIRC Fedora installer expects to find and use xvd* devices only. 

-- Pasi

On Thu, Dec 18, 2008 at 11:47:01PM +0200, Pasi Kärkkäinen
wrote:
> On Thu, Dec 18, 2008 at 07:14:50PM +0000, MOHAMMAD MATEEN ASLAM wrote:
> > 
> > # cat  vm.cfg
> > 
> > kernel = "/boot/vmlinuz-PAE"
> > ramdisk = "/boot/initrd-PAE.img"
> > 
> > memory = 128
> > name = "xxxxx"
> > vif = [ ''ip=xx.xx.xx.xx'' ]
> > disk = [''tap:aio:/var/xen/vm13/root,sda1,w'',
''tap:aio:/var/xen/vm13/var,sda2,w'',
''tap:aio:/var/xen/vm13/swap,sda3,w'']
> > root = "/dev/sda1 ro"
> > on_reboot   = ''restart''
> > on_crash    = ''restart''
> > 
> > # xm create -c vm.cfg    -> for booting vm
> > 
> 
> Your disk configuration is wrong. 
> 
> You need to have xvda disk for domU.
> 
> Something like this:
> 
> disk = [''tap:aio:/var/xen/vm13/xvda,xvda,w'']
> 
> if ''tap:aio'' doesn''t work, then try just
''file''.
> 
Have you tried installing with virt-install? or virt-manager? 

Example how I installed rawhide on CentOS 5.2 dom0:
(NOTE: This was earlier, before Fedora 9 was released. I haven''t tried
it now for F10 or F11 rawhide)

$ virt-install -n test -r 512 --vcpus=1 -f /dev/vg0/test_disk1 --vnc -p -l
"ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/development/i386/os"

Replace the FTP mirror with your local mirror.

Does that work? 

-- Pasi

On Fri, Dec 19, 2008 at 02:08:15PM +0200, Pasi K?rkk?inen
wrote:
> On Thu, Dec 18, 2008 at 09:46:21PM +0000, MOHAMMAD MATEEN ASLAM wrote:
> > 
> > 
> > i think it doesn''t matter what xenserver block devices is for
Guest OS.
> 
> IIRC Fedora installer expects to find and use xvd* devices only. 
Support for hijacking SCSI/IDE device names was ripped out of the
Xen blkfront when it was merged in upstream Linux. Since Fedora 10
guest is based on upstream, you need to use xvda not sda, regardless
of installer. 

We did warn people this would likely happen when upstream got hold
of the code...

Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

On Fri, Dec 19, 2008 at 02:13:44PM +0200, Pasi Kärkkäinen
wrote:
> On Thu, Dec 18, 2008 at 11:47:01PM +0200, Pasi Kärkkäinen wrote:
> > On Thu, Dec 18, 2008 at 07:14:50PM +0000, MOHAMMAD MATEEN ASLAM wrote:
> > > 
> > > # cat  vm.cfg
> > > 
> > > kernel = "/boot/vmlinuz-PAE"
> > > ramdisk = "/boot/initrd-PAE.img"
> > > 
> > > memory = 128
> > > name = "xxxxx"
> > > vif = [ ''ip=xx.xx.xx.xx'' ]
> > > disk = [''tap:aio:/var/xen/vm13/root,sda1,w'',
''tap:aio:/var/xen/vm13/var,sda2,w'',
''tap:aio:/var/xen/vm13/swap,sda3,w'']
> > > root = "/dev/sda1 ro"
> > > on_reboot   = ''restart''
> > > on_crash    = ''restart''
> > > 
> > > # xm create -c vm.cfg    -> for booting vm
> > > 
> > 
> > Your disk configuration is wrong. 
> > 
> > You need to have xvda disk for domU.
> > 
> > Something like this:
> > 
> > disk = [''tap:aio:/var/xen/vm13/xvda,xvda,w'']
> > 
> > if ''tap:aio'' doesn''t work, then try just
''file''.
> > 
> 
> Have you tried installing with virt-install? or virt-manager? 
> 
> Example how I installed rawhide on CentOS 5.2 dom0:
> (NOTE: This was earlier, before Fedora 9 was released. I haven''t
tried it now for F10 or F11 rawhide)
> 
> $ virt-install -n test -r 512 --vcpus=1 -f /dev/vg0/test_disk1 --vnc -p -l
"ftp://ftp.funet.fi/pub/mirrors/fedora.redhat.com/pub/fedora/linux/development/i386/os"
> 
> Replace the FTP mirror with your local mirror.
> 
> Does that work? 
> 
.. The reason you upgraded python-virtinst is to be able to use
virt-install and/or virt-manager .. 

-- Pasi

Hi Pasi,

I successfully booted FC10 kernel (DomU) on FC8 (Dom0) by changing sda with
xvd*.

Thanks alot for your and Young help. This is how community works.

 
> IIRC Fedora installer expects to find and use xvd* devices only. 
> 
> -- Pasi
_________________________________________________________________
Life on your PC is safer, easier, and more enjoyable with Windows Vista®. 
http://clk.atdmt.com/MRT/go/127032870/direct/01/

Thanks Daniel, my problem resolved by using xvd* instead of sda.

Regards, Mateen

> Support for hijacking SCSI/IDE device names was ripped out of the
> Xen blkfront when it was merged in upstream Linux. Since Fedora 10
> guest is based on upstream, you need to use xvda not sda, regardless
> of installer. 
> 
> We did warn people this would likely happen when upstream got hold
> of the code...
> 
> Daniel
_________________________________________________________________
Send e-mail faster without improving your typing skills.
http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_hotmail_acq_speed_122008