From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: tosher 1 <akm2tosher@yahoo.com>
Cc: "rnikola@vt.edu" <rnikola@vt.edu>,
Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] HVM Driver Domain
Date: Wed, 22 Jan 2020 02:27:13 +0100 [thread overview]
Message-ID: <20200122012713.GB2995@mail-itl> (raw)
In-Reply-To: <1284035258.1445298.1579543677315@mail.yahoo.com>
[-- Attachment #1.1: Type: text/plain, Size: 1205 bytes --]
On Mon, Jan 20, 2020 at 06:07:57PM +0000, tosher 1 wrote:
> Hi all,
>
> I was doing some experiments on the Xen network Driver Domain using Ubuntu 18.04. I was able to see the driver domain works fine when I run it in PV mode. However, I wasn't able to make the driver domain work when I run it in HVM mode. I get the following error when I want my DomU to use HVM driver domain for network backend.
>
> libxl: error: libxl_nic.c:652:libxl__device_nic_set_devids: Domain 25:Unable to set nic defaults for nic 0
>
> Other than this, I didn't get any log messages from dmesg, xl dmesg commands, and files from /var/log/xen/ directory regarding this failure. Therefore, I was wondering if it is even possible to create an HVM Driver Domain. Please let me know what you think.
It's definitely possible, as we use it extensively in Qubes, including
for network device backend.
Can you give more details about your setup? Which Xen version, what your
domU configuration looks like (especially vif setting)?
--
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: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 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-22 1:27 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 [this message]
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
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=20200122012713.GB2995@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=akm2tosher@yahoo.com \
--cc=rnikola@vt.edu \
--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).