Right, it used to work, somehow didnt this time. With a bit of tinkering i remembered vmware used to have similar issue. Solution was to set LSI_SAS driver on "boot start". I did the same to virtio disk driver and then it worked. Yay..
On 2015.12.28 11:20, Karsten Elfenbein wrote: > Hi, > > I had the same issue after upgrading to win10. > I kept the boot disk on ATA/IDE and added an other disk with virtio. > Then I installed the windows 10 virtio drivers for the second disk. > (latest virtio-win.iso should have those) > With that in place I could switch back to virtio for my boot disk. > > Karsten > > 2015-12-28 9:40 GMT+01:00 rndbit <rnd...@sysret.net>: >> I bumped into this strange issue - i can no longer boot windows guest >> from VirtIO disk. Windows logo shows up briefly and then it throws >> INACCESSIBLE_BOOT_DEVICE error. Switching disk to IDE works. Interesting >> part is that i actually have installed virtio drivers and virtio disks >> added after VM is booted can be accessed without any problem. Since i >> can see actual windows logo and error message i suppose it goes half-way >> at least and firmware can understand virtio disks just fine. Im out of >> ideas here. Does anyone have any clue what could be wrong here? >> >> _______________________________________________ >> vfio-users mailing list >> vfio-users@redhat.com >> https://www.redhat.com/mailman/listinfo/vfio-users _______________________________________________ vfio-users mailing list vfio-users@redhat.com https://www.redhat.com/mailman/listinfo/vfio-users
