lightscribe support

lightscribe support

[Nerijus Baliunas]

Hello,

is it possible to support lightscribe in KVM? Now Windows VM sees QEMU
DVD-ROM ATA Device and labeling software shows "No LightScribe Drives Found".

Regards,
Nerijus

Re: lightscribe support

[Oliver Rath]

Hi Nerijus,

Am 14.02.2014 22:29, schrieb Nerijus Baliunas:
> Hello,
>
> is it possible to support lightscribe in KVM? Now Windows VM sees QEMU
> DVD-ROM ATA Device and labeling software shows "No LightScribe Drives Found".
>

Normally kvm emulates the cdrom drive. If you want to use the native
functionality, you have to passthrough the drive (depending on the your
device usb or pci sata-hardware). If your drive is attached via usb, you
can try passthrough the usb-device, if it is connected via sata, you
have to passthrough the sata-pci-device.

Regards
Oliver

Re: lightscribe support

[Nerijus Baliunas]

Oliver Rath <rath <at> mglug.de> writes:

> Normally kvm emulates the cdrom drive. If you want to use the native
> functionality, you have to passthrough the drive (depending on the your
> device usb or pci sata-hardware). If your drive is attached via usb, you
> can try passthrough the usb-device, if it is connected via sata, you
> have to passthrough the sata-pci-device.

It is connected via PCI IDE controller (Silicon Image, Inc. PCI0680 Ultra
ATA-133 Host Controller). Is it possible to passthrough it?

Thanks,
Nerijus

Re: lightscribe support

[Nerijus Baliunas]

Nerijus Baliunas <nerijus <at> users.sourceforge.net> writes:

> It is connected via PCI IDE controller (Silicon Image, Inc. PCI0680 Ultra
> ATA-133 Host Controller). Is it possible to passthrough it?

Tried it, but unsuccessfully:

Error starting domain: internal error: early end of file from monitor:
possible problem:
qemu-system-x86_64: -device
pci-assign,configfd=26,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x8: PCI
region 5 at address 0xf7ce0000 has size 0x100, which is not a multiple of
4K.  You might experience some performance hit due to that.
qemu-system-x86_64: -device
pci-assign,configfd=26,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x8: No IOMMU
found.  Unable to assign device "hostdev0"
qemu-system-x86_64: -device
pci-assign,configfd=26,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x8: Device
initialization failed.
qemu-system-x86_64: -device
pci-assign,configfd=26,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x8: Device
'kvm-pci-assign' could not be initialized

Re: lightscribe support

[Nerijus Baliunas]

Nerijus Baliunas <nerijus <at> users.sourceforge.net> writes:

> pci-assign,configfd=26,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x8: No IOMMU
> found.  Unable to assign device "hostdev0"

I added intel_iommu=on' to the kernel cmdline, # dmesg|grep -i iommu
[    0.000000] Command line: ro root=/dev/md0 intel_iommu=on
[    0.000000] Kernel command line: ro root=/dev/md0 intel_iommu=on
[    0.000000] Intel-IOMMU: enabled

But still the same. My CPU is i5-3570K, and I do not see it in
https://en.wikipedia.org/wiki/List_of_IOMMU-supporting_hardware, so it means
it cannot be supported?

Thanks,
Nerijus

Re: lightscribe support

[Alex Williamson]

On Sat, 2014-02-15 at 18:26 +0000, Nerijus Baliunas wrote:
> Nerijus Baliunas <nerijus <at> users.sourceforge.net> writes:
> 
> > pci-assign,configfd=26,host=04:00.0,id=hostdev0,bus=pci.0,addr=0x8: No IOMMU
> > found.  Unable to assign device "hostdev0"
> 
> I added intel_iommu=on' to the kernel cmdline, # dmesg|grep -i iommu
> [    0.000000] Command line: ro root=/dev/md0 intel_iommu=on
> [    0.000000] Kernel command line: ro root=/dev/md0 intel_iommu=on
> [    0.000000] Intel-IOMMU: enabled
> 
> But still the same. My CPU is i5-3570K, and I do not see it in
> https://en.wikipedia.org/wiki/List_of_IOMMU-supporting_hardware, so it means
> it cannot be supported?

Correct, most of the unlocked 'K' models do not support VT-d:

http://ark.intel.com/products/65520/Intel-Core-i5-3570K-Processor-6M-Cache-up-to-3_80-GHz

Re: lightscribe support

[Brian Jackson]

On 02/14/2014 03:29 PM, Nerijus Baliunas wrote:
> Hello,
>
> is it possible to support lightscribe in KVM? Now Windows VM sees QEMU
> DVD-ROM ATA Device and labeling software shows "No LightScribe Drives Found".


You could try to use virtio-scsi and scsi passthru. I believe there's
been a post on this in the past (more than likely on the qemu-devel
mailing list.


>
> Regards,
> Nerijus
>
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: lightscribe support

[Nerijus Baliunas]

Brian Jackson <iggy <at> theiggy.com> writes:

> You could try to use virtio-scsi and scsi passthru. I believe there's
> been a post on this in the past (more than likely on the qemu-devel
> mailing list.

I see I can choose VirtIO SCSI bus type in virt-manager. I added as a raw
cdrom, then changed VM.xml like this:

    <disk type='file' device='cdrom'>
      <driver name='qemu' type='raw'/>
      <source file='/dev/sr0'/>
      <target dev='sda' bus='scsi'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>

Red Hat VirtIO SCSI pass-through controller was installed in a Vista VM, and
additional QEMU CD-ROM SCSI CdRom Device appeared. But Lightscribe software
still does not find lightscribe capable drives.

Re: lightscribe support

[Nerijus Baliunas]

Nerijus Baliunas <nerijus <at> users.sourceforge.net> writes:

> I see I can choose VirtIO SCSI bus type in virt-manager. I added as a raw
> cdrom, then changed VM.xml like this:
> 
>     <disk type='file' device='cdrom'>
>       <driver name='qemu' type='raw'/>
>       <source file='/dev/sr0'/>
>       <target dev='sda' bus='scsi'/>
>       <address type='drive' controller='0' bus='0' target='0' unit='0'/>
>     </disk>
> 
> Red Hat VirtIO SCSI pass-through controller was installed in a Vista VM, and
> additional QEMU CD-ROM SCSI CdRom Device appeared. But Lightscribe software
> still does not find lightscribe capable drives.

I changed device from 'cdrom' to 'lun':
    <disk type='file' device='lun'>
also tried
    <disk type='block' device='lun'>

but in both cases VM does not start:

Error starting domain: unsupported configuration: disk device='lun' is only
valid for block type disk source.

Re: lightscribe support

[Paolo Bonzini]

Il 16/02/2014 02:55, Nerijus Baliunas ha scritto:
>     <disk type='block' device='lun'>
>
> but in both cases VM does not start:
>
> Error starting domain: unsupported configuration: disk device='lun' is only
> valid for block type disk source.
>

It should work with <disk type='block' device='lun'>, but you also need 
to use

    <source dev='/dev/sr0'/>

(i.e. dev instead of file).

Paolo

Re: lightscribe support

[Nerijus Baliunas]

Paolo Bonzini <pbonzini <at> redhat.com> writes:

> It should work with <disk type='block' device='lun'>, but you also need 
> to use
> 
>     <source dev='/dev/sr0'/>
> 
> (i.e. dev instead of file).

Thanks, it worked! VM now sees the lightscribe drive, Just for the
information, the following works:

    <disk type='block' device='lun'>
      <driver name='qemu' type='raw'/>
      <source dev='/dev/sr0'/>
      <target dev='sda' bus='scsi'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>