From nobody Wed Oct 20 14:23:17 2021 X-Original-To: freebsd-xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id B742D17FE42B for ; Wed, 20 Oct 2021 14:23:24 +0000 (UTC) (envelope-from royger@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HZCWw4sZBz3Dcn; Wed, 20 Oct 2021 14:23:24 +0000 (UTC) (envelope-from royger@freebsd.org) Received: from localhost (unknown [93.176.190.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: royger) by smtp.freebsd.org (Postfix) with ESMTPSA id 2D21795F9; Wed, 20 Oct 2021 14:23:24 +0000 (UTC) (envelope-from royger@freebsd.org) Date: Wed, 20 Oct 2021 16:23:17 +0200 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: Miranda MS van den Breukelingen Cc: Gerd Hafenbrack , freebsd-xen@freebsd.org Subject: Re: another xen-kernel UEFI story Message-ID: References: <3839452.BRNeRiNLvY@freebsd_current> <6DF76321-EBF1-403A-A9AE-971EA6A43C59@gmail.com> <2838647.hHqAuc6tWs@freebsd_current> <88AF3148-2ABA-471A-B411-4255B99899B9@gmail.com> List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <88AF3148-2ABA-471A-B411-4255B99899B9@gmail.com> X-ThisMailContainsUnwantedMimeParts: N On Wed, Oct 20, 2021 at 01:14:25PM +0200, Miranda MS van den Breukelingen wrote: > Hiya! > > How about my updated thread here: > > https://forums.freebsd.org/threads/xen-kernel-doesnt-start-at-all.81556/page-2#post-533567 > > What’s wrong with that? The infos are not really more in quantity but in quality. Thx a lot for letting me grounding like this. Hello, I've been away for a long time, and my inbox is overflowing. AFAICT you got the serial working which is great, but the current output seems to be missing any Xen-related output. Can you paste the contents of your /boot/loader.conf? sudo minicom -b 9600 -D /dev/cuaU0 Wachtwoord: ______ ____ _____ _____ | ____| | _ \ / ____| __ \ | |___ _ __ ___ ___ | |_) | (___ | | | | | ___| '__/ _ \/ _ \| _ < \___ \| | | | , , | | | | | __/ __/| |_) |____) | |__| | /( )` | | | | | | || | | | \ \___ / | |_| |_| \___|\___||____/|_____/|_____/ /- _ `-/ ' (/\/ \ \ /\ +---------- Welcome to FreeBSD -----------+ / / | ` \ | | O O ) / | | 1. Boot Multi user [Enter] | `-^--'`< ' | 2. Boot Single user | (_.) _ ) / | 3. Escape to loader prompt | `.___/` / | 4. Reboot | `-----' / | 5. Cons: Serial | <----. __ / __ \ | | <----|====O)))==) \) /====| | Options: | <----' `--' `.__,' \ | 6. Kernel: LIZBETH-VERBOSE (2 of 2) | | | | 7. Boot Options | \ / /\ | | ______( (_ / \______/ | | ,' ,-----' | +-----------------------------------------+ `--{__________) Loading Xen kernel... /boot/xen data=0x27e9c8+0x143638 - Loading kernel... /boot/LIZBETH-VERBOSE/kernel size=0x1bd0ca8 Loading configured modules... splash_pcx.../boot/LIZBETH-VERBOSE/splash_pcx.ko size 0x32a8 at 0x2194000 cuse.../boot/LIZBETH-VERBOSE/cuse.ko size 0xb060 at 0x2198000 kernel.../boot/entropy.../boot/entropy size=0x1000 splash_txt.../boot/LIZBETH-VERBOSE/splash_txt.ko size 0x2c78 at 0x21a5000 /boot/splash.../boot/splash size=0x1d4f6 green_saver.../boot/LIZBETH-VERBOSE/green_saver.ko size 0x2a70 at 0x21c6000 if_tap...fusefs.../boot/LIZBETH-VERBOSE/fusefs.ko size 0x26698 at 0x21c9000 snd_driver.../boot/LIZBETH-VERBOSE/snd_driver.ko size 0x4e98 at 0x21f0000 loading required module 'snd_vibes' /boot/LIZBETH-VERBOSE/snd_vibes.ko size 0x62a0 at 0x21f5000 loading required module 'snd_via82c686' /boot/LIZBETH-VERBOSE/snd_via82c686.ko size 0x5ed0 at 0x21fc000 loading required module 'snd_t4dwave' /boot/LIZBETH-VERBOSE/snd_t4dwave.ko size 0x6010 at 0x2202000 loading required module 'snd_spicds' /boot/LIZBETH-VERBOSE/snd_spicds.ko size 0x3228 at 0x2209000 loading required module 'snd_solo' /boot/LIZBETH-VERBOSE/snd_solo.ko size 0x85e8 at 0x220d000 loading required module 'snd_sbc' /boot/LIZBETH-VERBOSE/snd_sbc.ko size 0x66f0 at 0x2216000 loading required module 'snd_sb8' /boot/LIZBETH-VERBOSE/snd_sb8.ko size 0x6550 at 0x221d000 loading required module 'snd_sb16' /boot/LIZBETH-VERBOSE/snd_sb16.ko size 0x6268 at 0x2224000 loading required module 'snd_neomagic' /boot/LIZBETH-VERBOSE/snd_neomagic.ko size 0x126a0 at 0x222b000 loading required module 'snd_mss' /boot/LIZBETH-VERBOSE/snd_mss.ko size 0x135b0 at 0x223e000 loading required module 'snd_maestro3' /boot/LIZBETH-VERBOSE/snd_maestro3.ko size 0xc908 at 0x2252000 loading required module 'snd_maestro' /boot/LIZBETH-VERBOSE/snd_maestro.ko size 0xbf20 at 0x225f000 loading required module 'snd_fm801' /boot/LIZBETH-VERBOSE/snd_fm801.ko size 0x4b58 at 0x226b000 loading required module 'snd_ess' /boot/LIZBETH-VERBOSE/snd_ess.ko size 0x8ce0 at 0x2270000 loading required module 'snd_envy24ht' /boot/LIZBETH-VERBOSE/snd_envy24ht.ko size 0x9f20 at 0x2279000 loading required module 'snd_envy24' /boot/LIZBETH-VERBOSE/snd_envy24.ko size 0xb358 at 0x2283000 loading required module 'snd_ds1' /boot/LIZBETH-VERBOSE/snd_ds1.ko size 0xdb68 at 0x228f000 loading required module 'snd_cs4281' /boot/LIZBETH-VERBOSE/snd_cs4281.ko size 0x7208 at 0x229d000 loading required module 'snd_atiixp' /boot/LIZBETH-VERBOSE/snd_atiixp.ko size 0x7ee0 at 0x22a5000 loading required module 'snd_als4000' /boot/LIZBETH-VERBOSE/snd_als4000.ko size 0x6608 at 0x22ad000 loading required module 'snd_ad1816' /boot/LIZBETH-VERBOSE/snd_ad1816.ko size 0x9278 at 0x22b4000 /etc/hostid.../etc/hostid size=0x25 if_bridge.../boot/LIZBETH-VERBOSE/if_bridge.ko size 0xe4d8 at 0x22be000 loading required module 'bridgestp' /boot/LIZBETH-VERBOSE/bridgestp.ko size 0x7860 at 0x22cd000 splash_bmp.../boot/LIZBETH-VERBOSE/splash_bmp.ko size 0x3ed0 at 0x22d5000 EFI framebuffer information: addr, size 0xe0000000, 0x300000 dimensions 1024 x 768 stride 1024 masks 0x00ff0000, 0x0000ff00, 0x000000ff, 0xff000000 From nobody Fri Oct 22 06:59:54 2021 X-Original-To: freebsd-xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 992DE180AE6C for ; Fri, 22 Oct 2021 07:00:01 +0000 (UTC) (envelope-from royger@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HbFbP43QLz3FV4; Fri, 22 Oct 2021 07:00:01 +0000 (UTC) (envelope-from royger@freebsd.org) Received: from localhost (unknown [93.176.190.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: royger) by smtp.freebsd.org (Postfix) with ESMTPSA id 118A52E1FE; Fri, 22 Oct 2021 07:00:00 +0000 (UTC) (envelope-from royger@freebsd.org) Date: Fri, 22 Oct 2021 08:59:54 +0200 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: "Lizbeth Mutterhunt, Ph.D" Cc: freebsd-xen@freebsd.org Subject: Re: another xen-kernel UEFI story Message-ID: References: <3839452.BRNeRiNLvY@freebsd_current> List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-ThisMailContainsUnwantedMimeParts: N On Thu, Oct 21, 2021 at 10:48:57PM +0200, Lizbeth Mutterhunt, Ph.D wrote: > /boot/loader.conf: > cuse_load="YES" > kernel_load="YES" > vfs.root.mountfrom="ufs:ada1p6" > #beastie_disable="YES" > hint.hwpstate_intel.0.disabled="1" > set vfs.root.mountfrom.options="rw" > if_bridge_load="YES" > debug.hwpstate_verbose="1" > if_tap_load="YES" > fusefs_load="YES" > xen_kernel="/boot/xen" > xen_cmdline="dom0_mem=4048M dom0_max_vcpus=4 dom0=pvh1 com1=115200,8n1 > guest_loglvl=all loglvl=all" > boot_multicons="YES" > boot_serial="YES" > comconsole_speed="9600" > console="comconsole,efi" *[not accepting any vidconsole]* > boot_verbose="YES" > vga=current > bitmap_name="/boot/splash" > net.link.bridge.inherit_mac=1 > snd_driver_load="YES" > kern.racct.enable=1 > compat.linuxkpi.i915_disable_power_well="0" > > Thanks, Roger. > > > So far, so good, what do you think? will we get this thing to work? Your xen_cmdline is slightly wrong, it should be: xen_cmdline="dom0_mem=4048M dom0_max_vcpus=4 dom0=pvh com1=9600,8n1 guest_loglvl=all loglvl=all" Note it's dom0=pvh, not pvh1. And the speed of the serial console needs to be adjusted to match the one you are using (9600), or you won't see any output. Also make sure the line is not split by your editor, or else it won't be parsed correctly. Regards, Roger. From nobody Fri Oct 22 07:01:56 2021 X-Original-To: freebsd-xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id B4B1E180BF21 for ; Fri, 22 Oct 2021 07:01:58 +0000 (UTC) (envelope-from royger@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HbFdf4h1xz3Fwl; Fri, 22 Oct 2021 07:01:58 +0000 (UTC) (envelope-from royger@FreeBSD.org) Received: from localhost (unknown [93.176.190.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: royger) by smtp.freebsd.org (Postfix) with ESMTPSA id 27AA72D87A; Fri, 22 Oct 2021 07:01:58 +0000 (UTC) (envelope-from royger@FreeBSD.org) Date: Fri, 22 Oct 2021 09:01:56 +0200 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: Brian Buhrow Cc: freebsd-xen@freebsd.org Subject: Re: Missing MAC addresses for domu VM's Message-ID: List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <202109280004.18S04d7Q016828@nfbcal.org> X-ThisMailContainsUnwantedMimeParts: N On Mon, Sep 27, 2021 at 05:04:39PM -0700, Brian Buhrow wrote: > hello. Under Xen-4.14.0 and FreeBSD-12.2 running a command like: > netstat -bin > shows all the interfaces, including the virtual interfaces for the domU machines running on > that server, but the MAC addresses are all 0's on those entries that show the link level > address. Is this a deliberate design decision or a bug that needs to be filed? > If it's a deliberate design decision, is there a way to get at the MAC address for a particular > domU and match it to a specific virtual interface on the dom0? There's a comment in the code about this: /* * Set the MAC address to a dummy value (00:00:00:00:00), * if the MAC address of the host-facing interface is set * to the same as the guest-facing one (the value found in * xenstore), the bridge would stop delivering packets to * us because it would see that the destination address of * the packet is the same as the interface, and so the bridge * would expect the packet has already been delivered locally * (and just drop it). */ IIRC I've added that myself. I think this is mostly a consequence of how bridges work on FreeBSD. Maybe there's another way to fix this by setting different bridge or interface flags. You can forcefully set the MAC address using: $ ifconfig xnbXX ether 02:01:02:03:04:FF If you wish to play with it, so you can try to give the host facing interface (xnbXX) the same MAC address as the guest facing one and see if it can still get network traffic delivered as expected. Regards, Roger. From nobody Fri Oct 22 13:55:45 2021 X-Original-To: freebsd-xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id DAE351807221 for ; Fri, 22 Oct 2021 13:55:47 +0000 (UTC) (envelope-from royger@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HbQq7513Kz51qd; Fri, 22 Oct 2021 13:55:47 +0000 (UTC) (envelope-from royger@freebsd.org) Received: from localhost (unknown [93.176.190.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: royger) by smtp.freebsd.org (Postfix) with ESMTPSA id 341031922; Fri, 22 Oct 2021 13:55:47 +0000 (UTC) (envelope-from royger@freebsd.org) Date: Fri, 22 Oct 2021 15:55:45 +0200 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: "Lizbeth Mutterhunt, Ph.D" Cc: freebsd-xen@freebsd.org Subject: Re: another xen-kernel UEFI story Message-ID: References: <3839452.BRNeRiNLvY@freebsd_current> <963984F2-DC4C-4ADB-AFD4-0ADE8724F75B@gmail.com> List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <963984F2-DC4C-4ADB-AFD4-0ADE8724F75B@gmail.com> X-ThisMailContainsUnwantedMimeParts: N On Fri, Oct 22, 2021 at 11:53:59AM +0200, Lizbeth Mutterhunt, Ph.D wrote: > This wasn’t it; still the same: preempt and stuck! > > Lizbeth > > > On 22 Oct 2021, at 08:59, Roger Pau Monné wrote: > > > > On Thu, Oct 21, 2021 at 10:48:57PM +0200, Lizbeth Mutterhunt, Ph.D wrote: > >> /boot/loader.conf: > >> cuse_load="YES" > >> kernel_load="YES" > >> vfs.root.mountfrom="ufs:ada1p6" > >> #beastie_disable="YES" > >> hint.hwpstate_intel.0.disabled="1" > >> set vfs.root.mountfrom.options="rw" > >> if_bridge_load="YES" > >> debug.hwpstate_verbose="1" > >> if_tap_load="YES" > >> fusefs_load="YES" > >> xen_kernel="/boot/xen" > >> xen_cmdline="dom0_mem=4048M dom0_max_vcpus=4 dom0=pvh1 com1=115200,8n1 > >> guest_loglvl=all loglvl=all" > >> boot_multicons="YES" > >> boot_serial="YES" > >> comconsole_speed="9600" > >> console="comconsole,efi" *[not accepting any vidconsole]* > >> boot_verbose="YES" > >> vga=current > >> bitmap_name="/boot/splash" > >> net.link.bridge.inherit_mac=1 > >> snd_driver_load="YES" > >> kern.racct.enable=1 > >> compat.linuxkpi.i915_disable_power_well="0" > >> > >> Thanks, Roger. > >>> > >> So far, so good, what do you think? will we get this thing to work? > > > > Your xen_cmdline is slightly wrong, it should be: > > > > xen_cmdline="dom0_mem=4048M dom0_max_vcpus=4 dom0=pvh com1=9600,8n1 guest_loglvl=all loglvl=all" > > > > Note it's dom0=pvh, not pvh1. And the speed of the serial console > > needs to be adjusted to match the one you are using (9600), or you > > won't see any output. > > > > Also make sure the line is not split by your editor, or else it won't > > be parsed correctly. Let's try with a slightly simpler loader.conf then, just to see if we can get some output from Xen: xen_kernel="/boot/xen" xen_cmdline="dom0_mem=4048M dom0=pvh com1=9600,8n1 console=com1,vga" boot_multicons="YES" boot_serial="YES" comconsole_speed="9600" console="comconsole,efi" vfs.root.mountfrom="ufs:ada1p6" Can you paste all the output you get on the serial when using this loader.conf? Thanks, Roger. From nobody Sun Oct 24 21:10:12 2021 X-Original-To: freebsd-xen@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 35A481816227 for ; Sun, 24 Oct 2021 21:10:23 +0000 (UTC) (envelope-from buhrow@nfbcal.org) Received: from nfbcal.org (ns.NFBCAL.ORG [157.22.230.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "nfbcal.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4HcrMf19pwz4tTN; Sun, 24 Oct 2021 21:10:21 +0000 (UTC) (envelope-from buhrow@nfbcal.org) Received: from nfbcal.org (localhost [127.0.0.1]) by nfbcal.org (8.15.2/8.14.1-NFBNETBSD) with ESMTPS id 19OLACar029814 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 24 Oct 2021 14:10:13 -0700 (PDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.102.2 at lothlorien.nfbcal.org Received: (from buhrow@localhost) by nfbcal.org (8.15.2/8.12.11) id 19OLACSx003317; Sun, 24 Oct 2021 14:10:12 -0700 (PDT) Message-Id: <202110242110.19OLACSx003317@nfbcal.org> From: Brian Buhrow Date: Sun, 24 Oct 2021 14:10:12 -0700 In-Reply-To: X-Mailer: Mail User's Shell (7.2.6 beta(4.pl1)+dynamic 20000103) To: Roger Pau =?utf-8?B?TW9ubsOp?= Subject: Re: Missing MAC addresses for domu VM's Cc: freebsd-xen@freebsd.org, buhrow@nfbcal.org X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (nfbcal.org [127.0.0.1]); Sun, 24 Oct 2021 14:10:13 -0700 (PDT) X-Rspamd-Queue-Id: 4HcrMf19pwz4tTN X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=pass (mx1.freebsd.org: domain of buhrow@nfbcal.org designates 157.22.230.125 as permitted sender) smtp.mailfrom=buhrow@nfbcal.org X-Spamd-Result: default: False [-2.63 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:ns.nfbcal.org]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[nfbcal.org]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; NEURAL_HAM_SHORT(-0.33)[-0.331]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:7091, ipnet:157.22.0.0/16, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_TLS_ALL(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Spam: Yes X-ThisMailContainsUnwantedMimeParts: N List-Id: Discussion List-Archive: https://lists.freebsd.org/archives/freebsd-xen List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-xen@freebsd.org X-BeenThere: freebsd-xen@freebsd.org Hello Roger. Thanks for the feedback. What I'm trying to do is figure out how to track the bandwidth of a particular domu from the dom0. I have a NetBSD installation where I just match the MAC address of the domu with the address shown with netstat -bin or brconfig. However, as noted, that doesn't work under FreeBSD-12.2. I've thought of using the interface name, but the output of netstat -bin truncates that name so that not all of the interface name appears in the output. For the NetBSD bridge driver, having the MAC address show up on the dom0 facing interface isn't a problem. While Im guessing I could figure out how to get the MAC address out of the xen store, it wouldn't really help me, because I would then want to map it to something I could uniquely pull from the output of netstat -bin. Any suggestions? -thanks -Brian On Oct 22, 9:01am, Roger Pau =?utf-8?B?TW9ubsOp?= wrote: } Subject: Re: Missing MAC addresses for domu VM's } On Mon, Sep 27, 2021 at 05:04:39PM -0700, Brian Buhrow wrote: } > hello. Under Xen-4.14.0 and FreeBSD-12.2 running a command like: } > netstat -bin } > shows all the interfaces, including the virtual interfaces for the domU machines running on } > that server, but the MAC addresses are all 0's on those entries that show the link level } > address. Is this a deliberate design decision or a bug that needs to be filed? } > If it's a deliberate design decision, is there a way to get at the MAC address for a particular } > domU and match it to a specific virtual interface on the dom0? } } There's a comment in the code about this: } } /* } * Set the MAC address to a dummy value (00:00:00:00:00), } * if the MAC address of the host-facing interface is set } * to the same as the guest-facing one (the value found in } * xenstore), the bridge would stop delivering packets to } * us because it would see that the destination address of } * the packet is the same as the interface, and so the bridge } * would expect the packet has already been delivered locally } * (and just drop it). } */ } } IIRC I've added that myself. I think this is mostly a consequence of } how bridges work on FreeBSD. Maybe there's another way to fix this by } setting different bridge or interface flags. } } You can forcefully set the MAC address using: } } $ ifconfig xnbXX ether 02:01:02:03:04:FF } } If you wish to play with it, so you can try to give the host facing } interface (xnbXX) the same MAC address as the guest facing one and see } if it can still get network traffic delivered as expected. } } Regards, Roger. >-- End of excerpt from Roger Pau =?utf-8?B?TW9ubsOp?=