search for: jsonnek

Does Xen Cloud Platform (XCP) support the notion of a driver domain? I can assign a VIF to a domain, but it seems that I can only attach that VIF to a network. What I''d like to do is attach the front-end VIF in one domain to a backend running in another domain. The second domain will control the physical interface (via PCI passthrough). This use case is easily supported using Xen +

I''ll try this one more time, any help greatly appreciated. When I create an HVM domain in Xen 4.0.X, network vif frontend initialization stalls at some point and the frontend/backend are never connected. This works properly in Xen 3.3.1, but does not work in either Xen 4.0.0 or Xen 4.0.1. When I start an HVM domain: 1. QEMU creates a tap device and attaches it to the specified bridge

When I try to use stubdom-dm in lieu of qemu-dm, the guest domain crashes almost immediately if I specify an emulated NIC (''vif='') in the guest configuration file. If I don''t specify a vif, it works fine. If I use the same configuration with qemu-dm instead of sutbdom-dm, it works fine. Is there some reason QEMU emulated networking doesn''t work with stub domains