Re: VirtIO in new upgraded 4.2.5 for FreeBSD is very poor (could not use)

HI All: Even I managed to change the VIrtIO to VirtIO-SCSI in FreeBSD I still got the error occasionally below Aug 7 15:52:32 MX1 kernel: vtscsi0: bus reset disabled Aug 7 15:52:32 MX1 kernel: (da0:vtscsi0:0:0:0): WRITE(10). CDB: 2a 00 02 80 a7 62 00 00 40 00 Aug 7 15:52:32 MX1 kernel: (da0:vtscsi0:0:0:0): CAM status: Command timeout Aug 7 15:52:32 MX1 kernel: (da0:vtscsi0:0:0:0): Retrying command Aug 7 15:52:32 MX1 kernel: (da0:vtscsi0:0:0:0): WRITE(10). CDB: 2a 00 02 80 a4 a2 00 00 40 00 Aug 7 15:52:32 MX1 kernel: (da0:vtscsi0:0:0:0): CAM status: Command timeout Aug 7 15:52:32 MX1 kernel: (da0:vtscsi0:0:0:0): Retrying command Aug 7 15:52:32 MX1 kernel: (da0:vtscsi0:0:0:0): WRITE(10). CDB: 2a 00 02 80 a3 22 00 00 40 00 Aug 7 15:52:32 MX1 kernel: (da0:vtscsi0:0:0:0): CAM status: Command timeout Aug 7 15:52:32 MX1 kernel: (da0:vtscsi0:0:0:0): Retrying command Aug 7 15:52:32 MX1 kernel: (da0:vtscsi0:0:0:0): WRITE(10). CDB: 2a 00 02 80 a2 62 00 00 40 00 Aug 7 15:52:32 MX1 kernel: (da0:vtscsi0:0:0:0): CAM status: Command timeout Aug 7 15:52:32 MX1 kernel: (da0:vtscsi0:0:0:0): Retrying command Aug 7 15:52:32 MX1 kernel: (da0:vtscsi0:0:0:0): WRITE(10). CDB: 2a 00 02 80 9e 22 00 00 40 00 Aug 7 15:52:32 MX1 kernel: (da0:vtscsi0:0:0:0): CAM status: Command timeout Aug 7 15:52:32 MX1 kernel: (da0:vtscsi0:0:0:0): Retrying command . . . Aug 7 15:52:32 MX1 kernel: (da0:vtscsi0:0:0:0): WRITE(10). CDB: 2a 00 02 80 9e 22 00 00 40 00 Aug 7 15:52:32 MX1 kernel: (da0:vtscsi0:0:0:0): CAM status: Command timeout Aug 7 15:52:32 MX1 kernel: (da0:vtscsi0:0:0:0): Retrying command another bad thing is the "VMs intermittently go into not responding" bug is come back *Bug 1449967* <https://bugzilla.redhat.com/show_bug.cgi?id=1449967>, It is mostly occuring in the midnight daily cronjob time 03:XX BR, Paul.LKW Karli Sjöberg 於 5/8/2018 19:59 寫道:
On Aug 5, 2018 13:57, "Paul.LKW" <paul.lkw@gmail.com> wrote:
HI K. Not yet but will report this later time tonight, I am trying to see does it possible to change the FreeBSD VM's harddisk to VirtIO-SCSI to make the VMs work first.
Sounds good! Good luck with it!
/K
Karli Sjöberg 於 5/8/2018 19:53 寫道:
On Aug 5, 2018 13:52, "Paul.LKW" <paul.lkw@gmail.com> <mailto:paul.lkw@gmail.com> wrote:
Hi Karli: It is FreeBSD 10.4 in production and Testing for 11.1 also have such issue.
Thanks!
Have you reported this issue, either to FreeBSD's bugzilla or oVirt's, or both?
/K
Karli Sjöberg 於 5/8/2018 19:50 寫道:
On Aug 5, 2018 13:48, "Paul.LKW" <paul.lkw@gmail.com> <mailto:paul.lkw@gmail.com> wrote:
HI Karli: It is oVirt-4.2.5.2-1.el7
Yeah, I know that, but what version of _FreeBSD_ are you using? :)
/K
Karli Sjöberg 於 5/8/2018 19:03 寫道:
On Aug 5, 2018 12:39, "Paul.LKW" <paul.lkw@gmail.com> <mailto:paul.lkw@gmail.com> wrote:
Dear All: I just upgraded my oVIrt-4.2.4 to 4.2.5 and nightmare begin, FreeBSD VMs hangs once the VM's VirtIO harddisk is some loading (eg. extracting a big tar ball, portsnap extract, etc.), I tried to create a VMs using back the IDE do not has any problem but got slow IO performance once using VirtIO it will hang as it like. I also tried to create another VMs with VirtIO-SCSI it seems the hang problem no occur but I got the oVirt-Host loading over 40 when VM harddisk have some little job, so conclusion is if you guys will using FreeBSD as guest please do not upgrade at the moment. In fact I feel every time the new version always have problem and causing user to nightmare.
BR, Paul.LKW _______________________________________________ Users mailing list -- users@ovirt.org <mailto:users@ovirt.org> To unsubscribe send an email to users-leave@ovirt.org <mailto:users-leave@ovirt.org> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/OL6XB5PLCWRXLT...
Daem, thanks for the heads up! I was thinking about updating but now I'll hold that off for sure!
What version FreeBSD are you using?
Is this issue reported?
/K
participants (2)
-
Karli Sjöberg
-
Paul.LKW