Now that Xen version 4.3.0-3 is in testing, I see that this same bug, initially seen in 4.1.4-4, is still present in 4.3.0-3. The same fix works.
-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
