On Tue, Jul 08, 2008 at 01:14:46PM +0100, Daniel P. Berrange wrote:
> > diff --git a/virtconv/parsers/virtimage.py b/virtconv/parsers/virtimage.py
> > --- a/virtconv/parsers/virtimage.py
> > +++ b/virtconv/parsers/virtimage.py
> > @@ -117,12 +117,12 @@ class virtimage_parser(vmconfig.parser):
> >
> > # FIXME: needs updating for later Xen enhancements; need to
> > # implement capabilities checking for max disks etc.
> > - pv_disks.append("""<drive disk="%s" target="xvd%s" />""" %
> > + pv_disks.append("""<drive disk="%s" target="xvd%s" />\n""" %
> > (path, ascii_letters[number % 26]))
> > - hvm_disks.append("""<drive disk="%s" target="hd%s" />""" %
> > + hvm_disks.append("""<drive disk="%s" target="hd%s" />\n""" %
> > (path, ascii_letters[number % 26]))
>
> IDE only allows upto 4 disks. To allow more than this requires use of
> SCSI or VirtIO/Xen paravirt drivers.
I missed the second part of this until I just thought about it. What do
we do here? Not sure how the Linux paravirt drivers work, but I think
the Solaris ones at least can do "hde" etc.
> I'd probably say default to IDE for first 4, and then switch to sdNNN
> for any subsequent disks.
Solaris doesn't have a shim to turn the SCSI device into a PV driver
though.
regards
john
_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
