As you can probably guess by now I am working my way down through my
outstanding issue list trying to get as many deferred items closed out as I
can before the next security storm hits.
We have a Win7pro KVM guest that has been giving us networking issues since it
was created. The last problem was that it was picking up its network address
from the virtio DHCP service, with predicable results. This turned out to be
an issue with how the virtual nic was configured (it was using NAT instead of
the br0 bridge.
We have adjusted the settings on the guest so the the nic is configured as a
shared device / br0 / Device Model=virtio. Now after it boots the thing says
that it does not have a driver for Ethernet adaptor at all. Is there a
different setting for the model that I should be using?
I have to point out that this thing was originally installed from cd-rom and
then updated from the internet. So at some point it must have had a working
network connection. Any ideas as to how to get it to find the network
interface again?
--
*** E-Mail is NOT a SECURE channel ***
James B. Byrne mailto:ByrneJB@xxxxxxxxxxxxx
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@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
