After installing the PV drivers into a Windows guest, the networking fails on reboot. What is likely wrong? 

Answer options:

A. The network type has not been changed from Paravirtualized to Fully Virtualized (the ioemu driver is not specified in the vm.cfg).
B. After install the PV drivers, the MAC address of the network interfaces must be changed in vm.cfg.
C. After installing the PV drivers, the bridge setting in vm.cfg is lost and must be reset.
D. The network type has not been changed from Fully Virtualized to Paravirtualized (the netfront driver is not specified in vm.cfg).

D

Oracle VM Windows Paravirtual Drivers Installation Guide Release 2.0 for Microsoft Windows E15298-02 May 2010 - 6.4 Network Devices May Fail If you install the Windows PV drivers into a guest with the vif type set to ioemu in the guest configuration file (vm.cfg), the network device(s) may fail. The Windows Device Manager displays an error code 10 and an exclamation point (!) to show the network driver cannot be started. This is caused by the network type being set incorrectly in the guest configuration file. The network card type can be set three ways:type=ioemu: Network card is available in QEMU mode only.type=netfront: Network card is available in paravirtualized mode.No type entry: Network card is available in both QEMU and paravirtualized modes. Workaround: The issue is only applicable to Oracle VM Server 2.1.5 and does not apply to Oracle VM Server 2.2 or later. If this issue occurs, change the network type from ioemu to netfront in the guest configuration file. Alternatively, delete the network type entry. You can make this change using Oracle VM Manager, or manually. To change the configuration manually: 1. Shut down the guest. 2. Edit the guest configuration file (vm.cfg) and change the type=ioemu entry to type=netfront, or delete the entry. 3. Restart the guest. The network driver is started.