--- xen-guide.xml.orig 2007-07-25 03:40:57.000000000 +0000 +++ xen-guide.xml 2007-07-25 05:00:56.000000000 +0000 @@ -152,6 +152,57 @@ etc.)
++Processor type and features ---> + Subarchitecture Type (Xen-compatible) ++ +
+Processor type and features ---> + Subarchitecture Type (PC-compatible) + [*] Enable Xen compatible kernel ++ +
+Bus options (PCI etc.) ---> + [*] PCI support + [*] Xen PCI Frontend (NEW) + [ ] Xen PCI Frontend Debugging + +Networking ---> + Networking options ---> + <*> 802.1d Ethernet Bridging ++ +Only required by bridged networking. + +XEN ---> + [*] Privileged Guest (domain 0) + <*> Backend driver support + <*> Block-device backend driver + <*> Network-device backend driver + [*] Scrub memory before freeing it to Xen + [*] Disable serial port drivers + Xen version compatibility (3.0.4 and later) +
+Bus options (PCI etc.) ---> + [ ] PCI support + +Device Drivers ---> + SCSI device support ---> + < > SCSI device support ++Disabling SCSI support frees up the /dev/sd* device names + for use as Xen virtual block devices. + +XEN ---> + [ ] Privileged Guest (domain 0) + <*> Block-device frontend driver + <*> Network-device frontend driver + [*] Scrub memory before freeing it to Xen + [*] Disable serial port drivers + Xen version compatibility (3.0.4 and later) +
A nice hint is to have the kernel make process store its intermediate object files elsewhere so that you can reuse the same kernel tree to build different