I really hope RH is doing his best for the community as usual, and that Proxmox can make enough money to have a look at virtion code and send some patches / provide signed drivers / whatever. something like "test the latest and the VM will never boot again, you have to restore the former backup", or "connectivity is lost sometime" etc.). In comparison for Fedora is all a guestwork, with some really bad experience (i.e. Windows XP Intel NIC Network Drivers Gigabit Installation on PowerEdge 750 After installing Windows XP, an unsupported and not guaranteed OS on this PowerEdge 750 server, the network drivers were still showing as unknown. I've been told that vmwhere "guest drivers" are stable, work with almost all M$ OS range, and let you do more things like clean shutdown of M$ server VM even if users are logged. I use GNU/Linux everywhere possible but all business needs some M$ Windows VM running for legacy apps, so not being able to provide a reliable and good performing solution is a big problem. If you are suggesting that Fedora virtio drivers are broken "by design" to force people use RH virtualization, or at least subscribe their RH server solution, that means that KVM outside RH is doomed.
I think XP does not need "signed" drivers, since this concept was "invented" later. This device driver package will install drivers for Intel 82540EM Gigabit Ethernet Controller for the Windows XP operating system.This driver is also compatible with the following devices:Intel PRO100B AdapterIntel PRO1000 PT Desktop AdapterIntel PRO1000 PM Network ConnectionIntel PRO1000 MT Dual Port Server AdapterIntel PRO1000 MT Desktop AdapterIntel PRO1000 GT Desktop AdapterIntel PRO1000. I've no access to and fedora virtio packages should belong to the same codebase, just the former should be always from "stable" branch, signed and certified.
0 kommentar(er)
