"setextradata" for CD-ROM on SATA doesn't work correct

[Lauscher]

Hello,

I have a problem with the "setextradata"-Option of vboxmanage. I'm not sure whether it is an issue of Virtualbox or of mine (Host=Xubuntu 11.10, Guest=Xubuntu 11.10).

False output I get with the CD-parameters; I set them, but they don't appear in the guest.

Looking for data in the host using

Code: Select all

udisks --show-info /dev/sr1

, I get the following output:

Code: Select all

[...]
  drive:
    vendor:                    MATSHITA
    model:                     MATSHITADVD-RAM UJ-831S
    revision:                  1.00
    serial:                    
[...]

Then I did this to give the guest the data of the host:

Code: Select all

VBoxManage setextradata "Vubuntu" "VBoxInternal/Devices/ahci/0/Config/Port1/ATAPIVendorId" "MATSHITA"
VBoxManage setextradata "Vubuntu" "VBoxInternal/Devices/ahci/0/Config/Port1/ATAPIProductId" "DVD-RAM UJ-831S"
VBoxManage setextradata "Vubuntu" "VBoxInternal/Devices/ahci/0/Config/Port1/ATAPIRevision" "string:1.00"

Using

Code: Select all

udisks --show-info /dev/sr1

in the guest, I get the following output. Only ATAPIVendorId="MATHSITA" appears, but not the ATAPIProductId and not the correct ATAPIRevision.

Code: Select all

[...]
  drive:
    vendor:                    MATSHITA
    model:                     VBOX CD-ROM
    revision:                  1.0
    serial:                    VB1-1a2b3c4d
[...]

-----------------------------
Similar, i did this with setextradata for harddisk, it works right. All parameters I set appear in the guest.
This is the harddisk-script:

Code: Select all

VBoxManage setextradata "Vubuntu" "VBoxInternal/Devices/ahci/0/Config/Port0/SerialNumber" "WD-WX60A89E4748"
VBoxManage setextradata "Vubuntu" "VBoxInternal/Devices/ahci/0/Config/Port0/ModelNumber" "WDC WD1200BEVE-00WZT0"
VBoxManage setextradata "Vubuntu" "VBoxInternal/Devices/ahci/0/Config/Port0/FirmwareRevision" "01.01A01"            

Using

Code: Select all

udisks --show-info /dev/sda

in the guest, I get the following output:

Code: Select all

[...]
  drive:
    vendor:                    ATA
    model:                     WDC WD1200BEVE-00WZT0
    revision:                  01.01A10
    serial:                    WD-WX60A89E4748
[...]

Can anyone tell me what is wrong? Am I looking at the false place?

[frank]

I assume that you chose the wrong port number when trying to set the parameters for the CDROM device. To find the correct parameters, start the VM and look at the VBox.log file. It will contain a database of configuration entries. Search for the CDROM device and you will see the correct parameters (mainly port). If in doubt, attach the VBox.log file here and we can help you.

[Lauscher]

Hello Frank,

thank you for looking at my question. Yes, I found the correct parameters in the log file:

Code: Select all

00:00:01.055 
00:00:01.055 [/Devices/ahci/0/Config/Port1/] (level 5)
00:00:01.055   ATAPIProductId      <string>  = "DVD-RAM UJ-831S" (cb=16)
00:00:01.055   ATAPIRevision       <string>  = "1.00" (cb=5)
00:00:01.055   ATAPIVendorId       <string>  = "MATSHITA" (cb=9)
00:00:01.055   NonRotationalMedium <integer> = 0x0000000000000000 (0)
00:00:01.055 

Because I found "ATAPIVendorId"="MATSHITA" as "vendor"="MATSHITA" in the ubuntu output, I think, it is not a problem of a false port number. Maybe I'm thinking wrong "ATAPIProductId" means the same as "model" in the output of 'udisks', nevertheless I think "ATAPIRevision" should be the same as "revision". So I think something doesn't work correct.

The background of this is an article in the wiki of ubuntuusers.de, where I give a guidance to virtualize physical installed systems to use them both physical and virtual. In case of Windows, there is the problem of changing hardware that triggers Windows to want get activated again at Microsoft whenever I change between virtual and physical boot. So I try to make the virtual hardware as similar as possible to the physical hardware. The link is http://wiki.ubuntuusers.de/Dualboot-Win ... ualisieren

(I hope you understand my funny english; I see you are from Germany, too, so I can explain everything in german if you don't understand me.)

Greetings, Lauscher

[Lauscher]

After updating to VirtualBox 4.1.12 it works now, so it has been an issue of VirtualBox that is solved yet.