xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: tosher 1 <akm2tosher@yahoo.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] HVM Driver Domain
Date: Wed, 22 Jan 2020 20:01:33 +0100	[thread overview]
Message-ID: <20200122190133.GS2507@mail-itl> (raw)
In-Reply-To: <1699773700.2581218.1579712175340@mail.yahoo.com>


[-- Attachment #1.1: Type: text/plain, Size: 2188 bytes --]

On Wed, Jan 22, 2020 at 04:56:15PM +0000, tosher 1 wrote:
> Hi Marek,
> 
> Thanks for your response. The server machine I am using for this setup is an x86_64 Intel Xeon. For the Dom0, I am using Ubuntu 18.04 running on kernel version 5.0.0-37-generic. My Xen version is 4.9.2. 
> 
> For the HVM driver domain, I am using Ubuntu 18.04 running on kernel version 5.0.0-23-generic. I am doing a NIC PCI passthrough to this domain. The Xen config file for this domain looks like the following.
> 
> builder = "hvm"
> name = "ubuntu-doment-hvm"
> memory = "2048"
> pci = [ '01:00.0,permissive=1' ]
> vcpus = 1
> disk = ['phy:/dev/vg/ubuntu-hvm,hda,w']
> vnc = 1
> boot="c"
> 
> I have installed xen-tools of version 4.7 in this driver domain so that the vif-scirpts work. The network configuration here looks like the following where ens5f0 is the interface name for the NIC I did passthrough.
> 
> auto lo
> iface lo inet loopback
> 
> iface ens5f0 inet manual
> 
> auto xenbr1
> iface xenbr1 inet static
>         bridge_ports ens5f0
>         address 192.168.1.3
>         netmask 255.255.255.0
>         gateway 192.168.1.1

Probably irrelevant at this stage, but do you have "xendriverdomain"
service running in the backend?

> The Xen config file content for the DomU is as the following.
> 
> name = "ubuntu_on_ubuntu"
> bootloader = "/usr/lib/xen-4.9/bin/pygrub"
> memory = 1024
> vcpus = 1
> vif = [ 'backend=ubuntu-domnet-hvm,bridge=xenbr1' ]
> disk = [ '/dev/vg/lv_vm_ubuntu_guest,raw,xvda,rw' ]
> 
> When I try to launch this DomU, I get the following error.
> 
> libxl: error: libxl_nic.c:652:libxl__device_nic_set_devids: Domain 31:Unable to set nic defaults for nic 0.

I don't see what is wrong here. Are you sure the backend domain is
running?

> Are these configurations basically very different for what you do for Qubes? Please let me know your thoughts.

Looks similar, although we do that through libvirt.

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

  reply	other threads:[~2020-01-22 19:01 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 [this message]
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=20200122190133.GS2507@mail-itl \
    --to=marmarek@invisiblethingslab.com \
    --cc=akm2tosher@yahoo.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).