I'm trying to burn a CD image file (.cdi) with Alcohol 120% to a blank CD-R in the host system. I enabled passthrough and the guest recognizes that i've inserted a blank CD-R, it asks me what i want to do and i tell it to open Alcohol 120% to burn an image. The .cdi image file has been copied into the guest.
When i start the burning process, my CD drive spins up and the light blinks, like its trying to write... however, after about 10 seconds, the guest OS seems to freeze. Over the next 10 minutes, the CD will slowly decrease the spin speed and the activity light will continue blinking. The guest OS appears frozen and i can't click on anything. However, after about 10 minutes, the CD spins up again but then i receive the errors shown in the screenshot:
"Write lead-in area error"
"image file loading aborted"
"something is wrong with the recording procedure"
i tried again using Discjuggler program. This program displayed similar behavior in the beginning, with the CD spinning down. I watched the host system log this time and every 5 minutes i noticed the errors below.
Code: Select all
Apr 24 12:45:10 kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Apr 24 12:45:10 kernel: sr 2:0:0:0: [sr0] CDB:
Apr 24 12:45:10 kernel: Write(10): 2a 00 ff ff d2 8e 00 00 0a 00 00 00
Apr 24 12:45:10 kernel: ata3.00: cmd a0/01:00:00:00:50/00:00:00:00:00/a0 tag 19 dma 20480 out
Apr 24 12:45:10 kernel: res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Apr 24 12:45:10 kernel: ata3.00: status: { DRDY }
Apr 24 12:45:10 kernel: ata3: hard resetting link
Apr 24 12:45:10 kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Apr 24 12:45:10 kernel: ata3.00: configured for UDMA/100
Apr 24 12:45:10 kernel: ata3: EH complete
Apr 24 12:50:12 kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Apr 24 12:50:12 kernel: sr 2:0:0:0: [sr0] CDB:
Apr 24 12:50:12 kernel: Write(10): 2a 00 ff ff d2 8e 00 00 0a 00 00 00
Apr 24 12:50:12 kernel: ata3.00: cmd a0/01:00:00:00:50/00:00:00:00:00/a0 tag 23 dma 20480 out
Apr 24 12:50:12 kernel: res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Apr 24 12:50:12 kernel: ata3.00: status: { DRDY }
Apr 24 12:50:12 kernel: ata3: hard resetting link
Apr 24 12:50:12 kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Apr 24 12:50:12 kernel: ata3.00: configured for UDMA/100
Apr 24 12:50:13 kernel: ata3: EH complete
Apr 24 12:55:14 kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Apr 24 12:55:14 kernel: sr 2:0:0:0: [sr0] CDB:
Apr 24 12:55:14 kernel: Write(10): 2a 00 ff ff d2 8e 00 00 0a 00 00 00
Apr 24 12:55:14 kernel: ata3.00: cmd a0/01:00:00:00:50/00:00:00:00:00/a0 tag 27 dma 20480 out
Apr 24 12:55:14 kernel: res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
Apr 24 12:55:14 kernel: ata3.00: status: { DRDY }
Apr 24 12:55:14 kernel: ata3: hard resetting link
Apr 24 12:55:15 kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
Apr 24 12:55:15 kernel: ata3.00: configured for UDMA/100
Apr 24 12:55:15 kernel: ata3: EH completeAccording to the documentation, the "timeout" error (on the host) means: "This is when timeout occurs and the command is still processing or the host and device are in unknown state. When this occurs, HSM could be in any valid or invalid state. To bring the device to known state and make it forget about the timed out command, resetting is necessary. The timed out command may be retried.
Timeouts can also be caused by transmission errors. Refer to the section called “ATA bus error” for more details."
is this an issue with the host system/linux?
