On Thu, October 23, 2014 02:58, Patrick Bervoets wrote:
James,
on the client, which driver do you use? Mine is 'Red Hat VirtIO Ethernet Adapter' 61.65.104.7400 20/11/2013. I got it from virtio-win-0.1-74.iso
At the moment none I guess. The message is that the client cannot find a driver. I have virtio-win-0.1-74.iso and virtio-win-0.1-81.iso on the hypervisor host. How do I get the driver from there into the guest? Does the client have access to the hypervisor's file-systems? Do I mount the ISO as a cd-rom in the guest? How is that done? In virt-manager? Is there a document somewhere that I can get an idea on how this is supposed to work?
Bear in mind that other than the occasional configuration and diagnostic issue I have very, very little experience with MS-Win since XPsp3 and none at all in running it as a guest on KVM.
On Thu, Oct 23, 2014 at 12:00 PM, James B. Byrne byrnejb@harte-lyne.ca wrote:
On Thu, October 23, 2014 02:58, Patrick Bervoets wrote:
James,
on the client, which driver do you use? Mine is 'Red Hat VirtIO Ethernet Adapter' 61.65.104.7400 20/11/2013. I got it from virtio-win-0.1-74.iso
At the moment none I guess. The message is that the client cannot find a driver. I have virtio-win-0.1-74.iso and virtio-win-0.1-81.iso on the hypervisor host. How do I get the driver from there into the guest? Does the client have access to the hypervisor's file-systems? Do I mount the ISO as a cd-rom in the guest? How is that done? In virt-manager? Is there a document
Yes, you attach the ISO to the CD-ROM of the guest.
From there the guest can access the ISO as if it was a normal CD-ROM.
I've used VirtIO drivers with WinXP, 7, and 8 in the past without network or disk performance issues. They're test VMs only seeing occasional usage, but they perform quite well. VirtIO is the way to go.
somewhere that I can get an idea on how this is supposed to work?
Bear in mind that other than the occasional configuration and diagnostic issue I have very, very little experience with MS-Win since XPsp3 and none at all in running it as a guest on KVM.
-- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited http://www.harte-lyne.ca 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Op 23-10-14 om 18:00 schreef James B. Byrne:
At the moment none I guess. The message is that the client cannot find a driver. I have virtio-win-0.1-74.iso and virtio-win-0.1-81.iso on the hypervisor host. How do I get the driver from there into the guest? Does the client have access to the hypervisor's file-systems? Do I mount the ISO as a cd-rom in the guest? How is that done? In virt-manager? Is there a document somewhere that I can get an idea on how this is supposed to work?
James,
I don't know if help is still needed.
You can mount the iso via virt-manager if you have (or create) a virt-storage-pool.
If you can reboot the client you could edit /etc/libvirt/qemu/virtclientname.xml and add <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/opt/isos/virtio-win-0.1-81.iso'/> <target dev='hdc' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='1' target='0' unit='0'/> to <devices>
(if your client already has more than 2 drives attached, change target dev hdc to hdd or ...)
You can switch your storages to virtio too, I did it in the past but fail to find my notes.
I think that the steps on this page are correct: http://setdosa.blogspot.be/2013/09/moving-your-windows-guest-from-ide-to.htm...
And, of course, work on a snapshot or at least have a copy of your client.
If you need help to change the driver in Windows I suggest we take this off-list since some are very allergic to Microsoft.
Patrick
-
James B. Byrne -
Patrick Bervoets -
SilverTip257