Re: [Xen-devel] HVM Driver Domain

[Roger Pau Monné <roger.pau@xxxxxxxxxx>]

On Wed, Jan 29, 2020 at 10:43:07PM +0000, tosher 1 wrote:
>  > BTW, are you creating the driver domain with 'driver_domain=1' in the xl 
> config file?
> 
> No, I wasn't aware of the 'driver_domain' configuration option before, and 
> this is what I was missing. With this configuration option, I was able to 
> make the HVM driver domain work. However, the PV driver domain worked fine 
> without this option configured.
> 
> > Are you sure this command is run on the driver domain?
> 
> Since I had installed xen-utils in the driver domain for the bridge to work, 
> it installed Xen hypervisor in the driver domain. As a result, my driver 
> domain became another Dom0. Realizing that I ran regular Ubuntu in the driver 
> domain. This was another key point to make the driver domain work.

Remove the Xen entry from grub in order to prevent it booting in dom0
mode, or remove the package that installs the Xen kernel if your
distro has separate packages for the Xen kernel and the tools.

It's pointless to boot a driver domain as a dom0, it's just going to
slow things down.

> Thanks for all your help, which made it possible for me to test the HVM 
> driver domain.
> 
> One last thing, backend interfaces are not being added to the bridge 
> automatically.  Do you think it is because regular Ubuntu doesn't have Xen 
> vif scripts? If yes, what is the proper thing to do in this case?

'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.

Can you paste the output you get from 'xl -vvv devd -F' when that
happens?

Are you sure the bridge setup in the guest config file exists in the
driver domain?

Roger.

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