On Thu, May 21, 2009 at 4:05 AM, Alba <florfoto@xxxxxxxxx> wrote:
> Thanks a lot again for your reply.
>
>> tap:aio should be for file-backed images, not devices. You should have
>> disk = [ "tap:aio:/PathToMyImage.img,hda,w", "phy:/dev/sda1,xvdb,w" ]
>
> I followed this procedure, where says that tap:aio should be used (isn't it
> rigth?):
> http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5.2/html/Para-Virtualized_Windows_Drivers/sect-Para-Virtualized_Windows_Drivers-Installing_and_configuring_the_para_virtualized_drivers-Post_installation_host_configuration.html
Weird :P
While it works, that's not how it was meant to be used, and could
possibly lead to lower performance.
>
>>How many disks you have each? Do you have one or two QEMU disks?
>>QEMU harddisk should be hda, while RHEL disk should be xvdb.
>
> With this configuration I saw three devices:
> disk = [ "file:PathToMyImage.img,hda,w", "tap:aio:/dev/sda1,xvdb,w" ]
>
> The devices are:
>
> 1) "c:" (10GB)
> 2) "QEMU HARDDISK" (50GB)
> 3) "RHEL DISK SCSI Disk Device" (50GB)
>
> The only difference between 2) and 3) are in their Properties:
> 2) says "Location: Location 1 (1)"
> 3) says "Location: Bus Number 0, Target Id 0, LUN 1"
>
> So I'm not sure if I should put my data in 2) or 3).
You should contact Redhat support about this. It should be (3), but
(2) and (3) are the same disk, and having both visible means trouble.
If you're stil having problems, I suggest you use GPLPV:
- http://wiki.xensource.com/xenwiki/XenWindowsGplPv/Installing
(slightly outdated)
- http://lists.xensource.com/archives/html/xen-users/2009-04/msg00062.html
- http://meadowcourt.org/downloads/
It works for boot disk, and should work for file:, tap:aio:, or phy:.
It does NOT work for tap:qcow though (due to Xen bug).
--
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home