From: tosher 1 <akm2tosher@yahoo.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
"Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>,
"Jason Andryuk" <jandryuk@gmail.com>
Subject: Re: [Xen-devel] HVM Driver Domain
Date: Thu, 30 Jan 2020 16:38:54 +0000 (UTC) [thread overview]
Message-ID: <869544230.355153.1580402334277@mail.yahoo.com> (raw)
In-Reply-To: <20200130090138.GA4679@Air-de-Roger>
> '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@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-01-30 16:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1284035258.1445298.1579543677315.ref@mail.yahoo.com>
2020-01-20 18:07 ` [Xen-devel] HVM Driver Domain tosher 1
2020-01-22 1:27 ` Marek Marczykowski-Górecki
2020-01-22 16:56 ` tosher 1
2020-01-22 19:01 ` Marek Marczykowski-Górecki
2020-01-22 19:50 ` tosher 1
2020-01-22 19:58 ` Marek Marczykowski-Górecki
2020-01-23 22:36 ` tosher 1
2020-01-23 23:11 ` Marek Marczykowski-Górecki
2020-01-24 20:38 ` tosher 1
2020-01-24 10:29 ` Roger Pau Monné
2020-01-27 20:43 ` tosher 1
2020-01-28 10:12 ` Roger Pau Monné
2020-01-29 22:43 ` tosher 1
2020-01-30 9:01 ` Roger Pau Monné
2020-01-30 16:38 ` tosher 1 [this message]
2020-01-24 14:07 ` Jason Andryuk
2020-01-24 20:36 ` tosher 1
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=869544230.355153.1580402334277@mail.yahoo.com \
--to=akm2tosher@yahoo.com \
--cc=jandryuk@gmail.com \
--cc=marmarek@invisiblethingslab.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).