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] FC3 domU using Xen 3.0

On Mon, Jan 15, 2007 at 08:14:31PM +0100, Henning Sprang wrote:
> On 1/15/07, AndreGround <andreground@xxxxxxxxx> wrote:
> >
> >Actually I've two questions:
> >1) Is there a way to migrate my old domU? (I can't find any hint both on
> >google and also on this mailing-list)
> >I can't find a way to boot it.
> >Here's my config file:
> >
> >kernel ="/boot/vmlinuz-2.6.18-1.2869.fc6xen"
> >#ramdisk = "/boot/initrd-2.6.18-1.2869.fc6xenU.img"
> >memory = 256
> >name = "mail"
> >vif = ['mac=aa:00:00:00:00:01']
> >disk =
> >['file:/xen/mail/fedora.img,sda1,w','file:/xen/mail/swap1.img,sda2,w']
> 
> I would not use file-based devices as block devices on production
> systems. I heard people having a lot trouble with them.

File backed devices are fine provided you:

  1. Use the blktap async-io backend - eg,   tap:aio:  instead of file:
  2. Pre-allocate the entire extent of the file - ie do NOT use a
     sparse file - it has unpredictable performance characteristics,
     and is unsafe if the host FS fills up.

> >root = "/dev/sda1"
> >extra = "ro selinux=0 3"
> >
> >This is the error I get:
> >VFS: Cannot open root device "sda1" or unknown-block(0,0)
> >Please append a correct "root=" boot option
> >Kernel panic - not syncing: VFS: Unable to mount root fs on
> >unknown-block(0,0)
> 
> Try using xvda, or add the scsi dik driver manually to the fedora
> Initrd. I think fedora wants to work only with xvda drives in DomU...

Fedora will work with sda/hda devices, however, we strongly recommend
you do NOT use them because its is practically 100% guarenteed support
will be removed when Xen guest patches are merged upstream. So to future
proof yourself only use the 'xvdN'  block devices in the guest.

> And, I'm not sure if fedora Xen Package can use the phy: block
> devices. At least, every domain created with their virt-install tool
> uses blocktap tap:aio for block device access.

You can use phy: if you're mapping in a physical device from the host.
The virt-install choose will automatically choose eithe phy: or tap:aio:
depending on whether the host side is a file or a block device. For
fully-virt (HVM) guests it will use file: instead of tap:aio: since
blktap is only meaningful for paravirt at this time.


Regards,
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  -=| 

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