© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
So just generally trying to summarize my "issue" with Xen behaviour here:
For the block device, no matter whether you have xvd? or hd? in the cfg, there will be a pv and an emulated device. Depending on having the pci platform driver and the pv driver built-in or as module, xen will remove the emulated devices (without the unplug parameter). At least in that case the pv device does work and you got a working disk.
For the nic, there *is* a difference whether type=ioemu is given or not. When it is present, there is a vif on the xenbus, but there seems to be no mac address set and it does not work. Still xen just unplugs the emulated device, when both drivers are present somehow. And that leaves you without working network (without Gihan's trick).
<rant>
Unfortunately there seems to be a reason for this whole unplug abomination (don't really understand it, but it is likely historical). If my config file says hda, I want an emulated disk and when it says xvda, I want to use the pv driver. Same for the network device. Now we got a situation where half the OS decides and half the config needs to be "clever". And I think there is no way of having for example a 3.0 kernel running that uses the emulated disks without showing the pv disks as well (when the kernel supports both).
</rant>