[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Xen 4.4 - Error passing more than 4 bridges to a guest

Woops, looks like the "e1000" belongs in the model column. I switched my configuration to use the following and it works fine.ÂI have tested on RHEL and Solaris 10.
Â
Thanks.

vif = [ 'type=vif,bridge=xenbr0', 'type=vif,bridge=xenbr10', 'type=vif,bridge=xenbr20', 'type=vif,bridge=xenbr30', 'type=vif,bridge=xenbr40', 'type=vif,bridge=xenbr50', 'type=vif,bridge=xenbr60', 'type=vif,bridge=xenbr70' ]


On Thu, Nov 20, 2014 at 10:52 AM, Bill Gercken <bgercken@xxxxxxxxx> wrote:
Thanks Ian,
Â
It looks like it was using the PV driverÂOK with the "traditional" model, but I tried your suggestion from your other post and that worked fine, so I am going to go with that. So for my HVM config I amÂusing the example below. (type=pv also worked.)
Â
Thanks again,

-billÂ

#device_model_override="/usr/lib/xen/bin/qemu-dm"
#device_model_version="qemu-xen-traditional"
Â
vif = [ 'type=e1000,bridge=xenbr0', 'type=e1000,bridge=xenbr10', 'type=e1000,bridge=xenbr20', 'type=e1000,bridge=xenbr30', 'type=e1000,bridge=xenbr40', 'type=e1000,bridge=xenbr50', 'type=e1000,bridge=xenbr60', 'type=e1000,bridge=xenbr70' ]
Â
Xen version 4.4.
Xen Platform PCI: I/O protocol version 1
Netfront and the Xen platform PCI driver have been compiled for this kernel: unplug emulated NICs.
..
Initialising Xen virtual ethernet driver.
Â
[root@rhvm5-dev ~]# ethtool -i eth0
driver: vif
version:
firmware-version:
bus-info: vif-0
supports-statistics: no
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
...
Â
[root@rhvm5-dev ~]# ethtool -i eth6
driver: vif
version:
firmware-version:
bus-info: vif-6
supports-statistics: no
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
Â

Â


On Thu, Nov 20, 2014 at 4:13 AM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
4.5 is not yet released (we've had 4.5.0-rc2 so far). Any moving to
using it should bear that in mind. Of course we always welcome testing
of release candidates, but you should be aware that they are candidates,
not releases.

IMHO it is very unlikely that systemd support or RPM packaging will make
any different to passing more than 4 bridges to the guest. My guess is
that you are ending up with emulated devices and that qemu has a
limitation. See
http://lists.xen.org/archives/html/xen-users/2014-11/msg00062.html

Ian.

ÂOn Wed, 2014-11-19 at 20:14 -0500, Bill Gercken wrote:
> Thanks Mark.
>
>
> I appreciate the tip. I had not checked out 4.5 yet.
>
>
> -bill
>
> On Wed, Nov 19, 2014 at 2:01 PM, Mark Pryor <tlviewer@xxxxxxxxx>
> wrote:
>Â Â Â Â ÂHello,
>Â Â Â Â ÂI noticed a few things about your xen build:
>    Â>xen_major       : 4
>    Â>xen_minor       : 4
>    Â>xen_extra       : .2-pre
>    Â>xen_version      : 4.4.2-pre
>
>
>Â Â Â Â Âthat xen version has no support for systemd. Nor does it have
>Â Â Â Â Âa target to make an RPM. Move to 4.5
>Â Â Â Â Âand you will have both of those. Since you are on rhel7 this
>Â Â Â Â Âmight help, especially if you want to separate the build
>Â Â Â Â Âenvironment from the dom0.
>
>
>
>
>Â Â Â Â ÂOn Tuesday, November 18, 2014 2:34 PM, Bill Gercken
>Â Â Â Â Â<bgercken@xxxxxxxxx> wrote:
>
>
>
>
>Â Â Â Â ÂHello,
>
>Â Â Â Â ÂI have an issue where passing more than 4 bridges to a guest
>Â Â Â Â Âcauses guest startup to fail due to memory issues.
>
>Â Â Â Â ÂThe same guest configuration will start fine with 4 bridges
>Â Â Â Â Âpassed.
>
>Â Â Â Â ÂI have researched this quite a bit and have not found the
>Â Â Â Â Âsolution. Any help is greatly appreciated.
>
>Â Â Â Â ÂThe error message that I am seeing is as follows.
>
>Â Â Â Â ÂThanks.
>Â Â Â Â Â-bill
>
>Â Â Â Â Â Error Message:
>Â Â Â Â Â-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>Â Â Â Â Â[root@rhel7xen xen]# xl create rhel-vm5.hvm
>Â Â Â Â ÂParsing config from rhel-vm5.hvm
>Â Â Â Â Âlibxl: error: libxl_dm.c:1371:device_model_spawn_outcome:
>Â Â Â Â Âdomain 2 device model: spawn failed (rc=-3)
>Â Â Â Â Âlibxl: error: libxl_create.c:1186:domcreate_devmodel_started:
>Â Â Â Â Âdevice model did not start: -3
>Â Â Â Â Âlibxl: error: libxl_dm.c:1475:kill_device_model: Device Model
>Â Â Â Â Âalready exited
>Â Â Â Â Â-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
>Â Â Â Â ÂRelevant info from xl dmesg:
>Â Â Â Â Â-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>Â Â Â Â Â(XEN) page_alloc.c:1468:d0 Over-allocation for domain 2:
>Â Â Â Â Â1048833 > 1048832
>Â Â Â Â Â(XEN) memory.c:158:d0 Could not allocate order=0 extent: id=2
>Â Â Â Â Âmemflags=0 (8 of 64)
>Â Â Â Â Â-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
>Â Â Â Â ÂGuest config file (rhel-vm5.hvm):
>Â Â Â Â Â-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>Â Â Â Â Âbuilder = "hvm"
>Â Â Â Â Âmemory = 4096
>Â Â Â Â Â#maxmem = 512
>Â Â Â Â Âvcpus = 1
>Â Â Â Â Âname = "rhvm5-dev"
>Â Â Â Â Â#vif = [ 'bridge=xenbr0' ]
>Â Â Â Â Âvif = [
>Â Â Â Â Â Â Â Â Â'bridge=xenbr1',
>Â Â Â Â Â Â Â Â Â'bridge=xenbr2',
>Â Â Â Â Â Â Â Â Â'bridge=xenbr3',
>Â Â Â Â Â Â Â Â Â'bridge=xenbr4',
>Â Â Â Â Â Â Â Â Â'bridge=xenbr5',
>Â Â Â Â Â Â Â Â Â'bridge=xenbr6',
>Â Â Â Â Â Â Â Â Â'bridge=xenbr7'
>Â Â Â Â Â Â Â Â]
>Â Â Â Â Âboot="c"
>Â Â Â Â Âdisk = [
>Â Â Â Â Â Â Â Â Â'/dev/mapper/vg3-RHVM5_24G,,hda',
>Â Â Â Â Â Â Â Â Â'/isos/rhel-server-6.5-x86_64-dvd.iso,,hdc:cdrom'
>Â Â Â Â Â Â Â Â Â]
>Â Â Â Â Âserial='pty'
>Â Â Â Â Âsdl=0
>Â Â Â Â Âvnc=1
>Â Â Â Â Âvnclisten="0.0.0.0"
>Â Â Â Â Âvncpasswd="a"
>Â Â Â Â Âusbdevice='tablet'
>Â Â Â Â Âstdvga=1
>Â Â Â Â Âmonitor=1
>Â Â Â Â Â# Support Physical Address Extension (enable for 64bit guest
>Â Â Â Â ÂOS)
>Â Â Â Â Âpae=1
>Â Â Â Â Â# Advanced Configuration and Power Interface (default)
>Â Â Â Â Âacpi=1
>Â Â Â Â Â# Advanced programmable interrupt controller (default)
>Â Â Â Â Âapic=1
>Â Â Â Â Â# Enable or disbale xen platform pci
>Â Â Â Â Â#Â Â- if you set this to zero it disables the PV driver (vif)
>Â Â Â Â Âand
>Â Â Â Â Â#Â Âuses driver emulation.
>Â Â Â Â Âxen_platform_pci=1
>Â Â Â Â Â# Time Stamp Counter
>Â Â Â Â Âtsc_mode="default"
>Â Â Â Â Â-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
>Â Â Â Â Â[root@rhel7xen xen]# xl info -n
>Â Â Â Â Â-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>    Âhost         Â: rhel7xen
>    Ârelease        : 3.10.51
>    Âversion        : #1 SMP Tue Aug 5 13:01:33 EDT 2014
>    Âmachine        : x86_64
>    Ânr_cpus        : 12
>    Âmax_cpu_id      Â: 11
>    Ânr_nodes       Â: 1
>    Âcores_per_socket   Â: 6
>    Âthreads_per_core   Â: 2
>    Âcpu_mhz        : 2300
>    Âhw_caps        :
>Â Â Â Â Âbfebfbff:2c100800:00000000:00003f00:17bee3ff:00000000:00000001:00000000
>    Âvirt_caps       : hvm hvm_directio
>    Âtotal_memory     Â: 65499
>    Âfree_memory      : 56465
>    Âsharing_freed_memory Â: 0
>    Âsharing_used_memory  : 0
>    Âoutstanding_claims  Â: 0
>    Âfree_cpus       : 0
>    Âcpu_topology     Â:
>    Âcpu:  core  socket  Ânode
>Â Â Â Â Â Â0:Â Â Â Â0Â Â Â Â 0Â Â Â Â 0
>Â Â Â Â Â Â1:Â Â Â Â0Â Â Â Â 0Â Â Â Â 0
>Â Â Â Â Â Â2:Â Â Â Â1Â Â Â Â 0Â Â Â Â 0
>Â Â Â Â Â Â3:Â Â Â Â1Â Â Â Â 0Â Â Â Â 0
>Â Â Â Â Â Â4:Â Â Â Â2Â Â Â Â 0Â Â Â Â 0
>Â Â Â Â Â Â5:Â Â Â Â2Â Â Â Â 0Â Â Â Â 0
>Â Â Â Â Â Â6:Â Â Â Â3Â Â Â Â 0Â Â Â Â 0
>Â Â Â Â Â Â7:Â Â Â Â3Â Â Â Â 0Â Â Â Â 0
>Â Â Â Â Â Â8:Â Â Â Â4Â Â Â Â 0Â Â Â Â 0
>Â Â Â Â Â Â9:Â Â Â Â4Â Â Â Â 0Â Â Â Â 0
>Â Â Â Â Â 10:Â Â Â Â5Â Â Â Â 0Â Â Â Â 0
>Â Â Â Â Â 11:Â Â Â Â5Â Â Â Â 0Â Â Â Â 0
>    Ânuma_info       :
>    Ânode:  memsize  memfree  distances
>Â Â Â Â Â Â 0:Â Â Â67584Â Â Â 56465Â Â Â 10
>    Âxen_major       : 4
>    Âxen_minor       : 4
>    Âxen_extra       : .2-pre
>    Âxen_version      : 4.4.2-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     : Fri Oct 17 15:57:42 2014 +0200
>Â Â Â Â Âgit:c8ed54e-dirty
>    Âxen_commandline    : placeholder dom0_mem=8192M,max:8192M
>Â Â Â Â Âdom0_max_vcpus=1 dom0_vcpus_pin loglvl=all guest_loglvl=all
>    Âcc_compiler      : gcc (GCC) 4.8.2 20140120 (Red Hat
>Â Â Â Â Â4.8.2-16)
>    Âcc_compile_by     : bgercken
>    Âcc_compile_domain   :
>    Âcc_compile_date    : Fri Nov 14 13:37:30 EST 2014
>    Âxend_config_format  Â: 4
>Â Â Â Â Â-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
>Â Â Â Â ÂGrub:
>Â Â Â Â Â-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>Â Â Â Â Â#
>Â Â Â Â Â# XEN on 3.10.51 w/XSM/FLASK
>Â Â Â Â Â#
>Â Â Â Â Âmenuentry 'RHEL Server 7 (3.10.51) Xen (4.4)(XSM/FLASK)'
>Â Â Â Â Â--class gnu-linux --class gnu --class os --class xen
>Â Â Â Â Â$menuentry_id_option 'xen-gnulinux-simple-' {
>      echo  'Loading Xen 4.4 ...'
>Â Â Â Â Â Â xen_opts="dom0_mem=8192M,max:8192M dom0_max_vcpus=1
>Â Â Â Â Âdom0_vcpus_pin loglvl=all guest_loglvl=all"
>Â Â Â Â Â Â # console_to_ring sync_console"
>Â Â Â Â Â Â kern_args="placeholder root=/dev/mapper/vg0-lv_root ro
>Â Â Â Â Ânet.ifnames=0"
>Â Â Â Â Â Â kern_extras="rd_NO_LUKS rd_NO_MD rd_NO_DM
>Â Â Â Â Âxen-pciback.hide=(04:00.0)(04:00.1)(05:00.0)(05:00.1)(0b:00.0)(0b:00.1)(0c:00.0)(0c:00.1)"
>Â Â Â Â Â Â multiboot /xen.gz placeholder ${xen_opts}
>Â Â Â Â Â Â echo 'Loading Linux 3.10.51 ...'
>Â Â Â Â Â Â module /vmlinuz-3.10.51 placeholder ${kern_args}
>Â Â Â Â Â${kern_extras}
>Â Â Â Â Â Â echo 'Loading initial ramdisk ...'
>Â Â Â Â Â Â module --nounzip /initramfs-3.10.51.img
>Â Â Â Â Â Â module /xenpolicy.24
>Â Â Â Â Â}
>Â Â Â Â Â-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>Â Â Â Â Â[root@rhel7xen xen]# xl getenforce
>Â Â Â Â ÂPermissive
>Â Â Â Â Â-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>
>
>
>
>Â Â Â Â Â_______________________________________________
>Â Â Â Â ÂXen-users mailing list
>Â Â Â Â ÂXen-users@xxxxxxxxxxxxx
>Â Â Â Â Âhttp://lists.xen.org/xen-users
>
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxx
> http://lists.xen.org/xen-users




_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users

 

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.