xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
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: Wed, 29 Jan 2020 22:43:07 +0000 (UTC)	[thread overview]
Message-ID: <39893674.1202836.1580337787157@mail.yahoo.com> (raw)
In-Reply-To: <20200128101257.GJ57924@desktop-tdan49n.eng.citrite.net>

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

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?

Please let me know.

Thanks,
Mehrab


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

  reply	other threads:[~2020-01-29 22:43 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 [this message]
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=39893674.1202836.1580337787157@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).