Re: [Xen-devel] HVM Driver Domain

[tosher 1 <akm2tosher@xxxxxxxxx>]

> 'xl devd' should add the backend interfaces (vifX.Y) to the bridge if 
> properly configured, as it should be calling the hotplug scripts to do that.

Yes, running ' xl devd' in the driver domain before launching the DomU, solved 
the bridge issue. Thanks a lot.

So, for the people who end up reading this thread, the following is a lesson I 
have learned. 

We need 'xl devd' running for the bridge to work, and to get the 'xl' program 
in the driver domain, depending on the distro being used, we may need to 
install xen-utils or other packages.  However, along with the xl, these 
packages may end up installing Xen hypervisor and update the grub accordingly. 
As a result, there is a chance that, in the next boot, the OS will boot into 
the hypervisor mode. In this case, the driver domain won't work. Therefore, be 
careful not to run the diver domain in Dom0 mode. Change the default boot to 
the regular Linux or delete the Xen image from /boot, and update the grub. 
After Booting the regular Linux, make sure the bridge is set up correctly, and  
'xl devd' is running to have the network driver domain working.

Regards,
Mehrab



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel