From: tosher 1 <akm2tosher@yahoo.com>
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] HVM Driver Domain
Date: Fri, 24 Jan 2020 20:38:11 +0000 (UTC) [thread overview]
Message-ID: <1300692217.17055.1579898291701@mail.yahoo.com> (raw)
In-Reply-To: <20200123231107.GI1314@mail-itl>
[-- Attachment #1.1: Type: text/plain, Size: 1694 bytes --]
Marek,
Thanks for the config files.
Regards,Mehrab
On Thursday, January 23, 2020, 6:11:12 PM EST, Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com> wrote:
On Thu, Jan 23, 2020 at 10:36:34PM +0000, tosher 1 wrote:
>
>
> I wasn't able to make the HVM driver domain work even with the latest Xen version which is 4.14. I see the 'xendriverdomain' executable in the /etc/init.d/ directory, but it doesn't seem to be running in the background.
>
> On the other hand, I see the official "Qubes OS Architecture" document (https://www.qubes-os.org/attachment/wiki/QubesArchitecture/arch-spec-0.3.pdf) defines the driver domain as the following.
>
> "A driver domain is an unprivileged PV-domain that has been securely granted access to certain PCI device (e.g. the network card or disk controller) using Intel VT-d." - Page 12
>
> Moreover, section 6.1 reads "The network domain is granted direct access to the networking hardware, e.g. the WiFi or ethernet card. Besides, it is a regular unprivileged PV domain."
>
> Maybe you guys later moved to the HVM driver domain from PV. Would you please share the Xen config you use for the network driver domain?
Yes, that PDF is quite outdated, we use HVM now.
As for the configs, as said before, we use libvirt, with some extra
patches, so the config won't be directly useful for you. I'm attaching
both libvirt XML for the driver domain, and also converted to XL (using
virsh domxml-to-native), may be inaccurate.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
[-- Attachment #1.2: Type: text/html, Size: 3124 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
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-24 20:38 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 [this message]
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
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=1300692217.17055.1579898291701@mail.yahoo.com \
--to=akm2tosher@yahoo.com \
--cc=marmarek@invisiblethingslab.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).