xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Linden <oliver_linden@helimail.de>
To: xen-devel@lists.xenproject.org
Subject: HVM - 2nd bridge breaking DomU config
Date: Sun, 29 Nov 2020 17:28:09 +0100	[thread overview]
Message-ID: <a7b21eef-8580-c3e8-a93d-e625b88bb947@helimail.de> (raw)


[-- Attachment #1.1.1: Type: text/plain, Size: 2797 bytes --]

Hi all,

got the recommendation from the freenode xen IRC channel to open a
ticket here. Hoping that's ok.

Problem:

I want to provide a second bridge to a HVM Linux DomU. But as soon as I
add this to the DomU config file the DomU doesn't start and the qemu log
file does state

*qemu-system-i386: -device
rtl8139,id=nic1,netdev=net1,mac=00:16:3e:35:af:af: xen: failed to
populate ram at 1100c0000* (same with e1000)

Providing only one bridge does work fine. Since I couldn't find anything
meaningful to me on the Internet I'm asking here. Any help is highly
appreciated.

root@HAM-XEN1:/etc/xen# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.1 LTS
Release:        20.04
Codename:       focal

root@HAM-XEN1:/etc/xen# uname -a
Linux HAM-XEN1 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux

root@HAM-XEN1:/etc/xen# xl info
host                   : HAM-XEN1
release                : 5.4.0-54-generic
version                : #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC 2020
machine                : x86_64
nr_cpus                : 16
max_cpu_id             : 31
nr_nodes               : 1
cores_per_socket       : 8
threads_per_core       : 2
cpu_mhz                : 3593.326
hw_caps                :
178bf3ff:f6d8320b:2e500800:244037ff:0000000f:219c91a9:00400004:00000500
virt_caps              : hvm hvm_directio
total_memory           : 32699
free_memory            : 7150
sharing_freed_memory   : 0
sharing_used_memory    : 0
outstanding_claims     : 0
free_cpus              : 0
xen_major              : 4
xen_minor              : 11
xen_extra              : .4-pre
xen_version            : 4.11.4-pre
xen_caps               : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32
hvm-3.0-x86_32p hvm-3.0-x86_64
xen_scheduler          : credit
xen_pagesize           : 4096
platform_params        : virt_start=0xffff800000000000
xen_changeset          :
xen_commandline        : placeholder dom0_max_vcpus=2-3
dom0_mem=1024M,max:2048M iommu=amd-iommu-global-intremap loglvl=all
guest_loglvl=all quiet no-real-mode edd=off
cc_compiler            : gcc (Ubuntu 9.2.1-31ubuntu3) 9.2.1 20200306
cc_compile_by          : ubuntu-devel-di
cc_compile_domain      : lists.ubuntu.com
cc_compile_date        : Tue Mar 10 09:04:06 UTC 2020
build_id               : 70edf50fce444a706eb5c69735c35c1838e4eaee
xend_config_format     : 4

Best, Oliver


[-- Attachment #1.1.2: Type: text/html, Size: 3630 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

                 reply	other threads:[~2020-11-29 16:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=a7b21eef-8580-c3e8-a93d-e625b88bb947@helimail.de \
    --to=oliver_linden@helimail.de \
    --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).