Re: VIF network definition does not work with backend=domnet

[Shen Long <xen-mailinglist@xxxxxxxxxxxxxxxxxxxxxxx>]

Am 23.03.25 um 15:56 schrieb Jason Andryuk:
> On Sat, Mar 22, 2025 at 8:51 AM Shen Long
> <xen-mailinglist@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> > Hello,
> Hi Shen,
Hi Jason,

> Try:
> vif = [ 'backend=netbackend,bridge=dmz,type=vif' ]
>
> This will give "test" just a PV nic (and not an emulated nic).
yes, thank you thats it!

Though to be fair, i did cross post on xen-users because i got 
impatient. I tried to post here and didnt get activated on xen-devel but 
also did not get any feedback from the maillinglist server about my 
initial post. So i signed up for xen-users.
Then i found a solution but didnt understand it and posted my findings 
their.
> /var/log/xen/qemu-dm-test.log probably reports an error about bridge
> dmz not existing.
It does report about missing tun interface on dom0, but i missed to look 
at the log-files completely. Interesting the tun interface is not 
necessary on netbackend. But i think it would be, if i have to use the 
emulated type, maybe i need it later.
> qemu runs in dom0, but your bridge "dmz" is in the driver domain,
> "netbackend".  By using type=vif, xl skips creating the emulated nic
> with qemu.  I think `xl network-attach` uses type=vif by default,
> which also avoids the emulated nic issue.
That's the thing, i did see that the type=vif does something different 
in the documentation but i did not understand what the differences are. 
So because i now know something more. It makes sense and thanks for the 
clarification.
> Regards,
> Jason
Best regards,
Shen