Samuel,
Yes, the messages are from the guest kernel. Sorry to have missed that point.
Would they be caused by an out of space condition on the host side of things? The guest "thinks" it has 30% utilization but the host is at 99%.
Regards,
George...
________________________________
From: Samuel Sieb <samuel@xxxxxxxx>
To: For testing and quality assurance of Fedora releases <test@xxxxxxxxxxxxxxxxxxxxxxx>
Sent: Friday, June 16, 2017 11:40 PM
Subject: Re: Messages from VB dev version VirtualBox-5.1.23-116111-Linux_amd64.run
On 06/16/2017 07:49 AM, George R Goffe wrote:
> Are these messages expected now, I have a ton of them? I have never seen them in all the devel versions of VB that I've used.
>
> Do I need to do anything?
>
> 509 Jun 16 05:01:10 fc27-rawhide kernel: ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
> 510 Jun 16 05:01:10 fc27-rawhide kernel: ata1.00: failed command: WRITE FPDMA QUEUED
> 511 Jun 16 05:01:10 fc27-rawhide kernel: ata1.00: cmd 61/08:00:40:6e:e8/00:00:01:00:00/40 tag 0 ncq dma 4096 out#012 res 40 511 /00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> 512 Jun 16 05:01:10 fc27-rawhide kernel: ata1.00: status: { DRDY }
> 513 Jun 16 05:01:10 fc27-rawhide kernel: ata1.00: failed command: WRITE FPDMA QUEUED
> 514 Jun 16 05:01:10 fc27-rawhide kernel: ata1.00: cmd 61/08:08:f0:6e:e8/00:00:01:00:00/40 tag 1 ncq dma 4096 out#012 res 40 514 /00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> 515 Jun 16 05:01:10 fc27-rawhide kernel: ata1.00: status: { DRDY }
> 516 Jun 16 05:01:10 fc27-rawhide kernel: ata1.00: failed command: WRITE FPDMA QUEUED
> 517 Jun 16 05:01:10 fc27-rawhide kernel: ata1.00: cmd 61/28:10:a0:6f:e8/00:00:01:00:00/40 tag 2 ncq dma 20480 out#012 res 4 517 0/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> te
>
> VirtualBox-5.1.23-116111-Linux_amd64.run
To be clear, these messages are produced by the kernel running *in* the
VM, not the kernel hosting the VM, correct?
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to test-leave@xxxxxxxxxxxxxxxxxxxxxxx
