Re: [PROMOTIONAL]FreeBSD 14-CURRENT as a guest working?
On Fri, 7 May 2021, Roger Pau Monné wrote: On Fri, May 07, 2021 at 05:12:16AM +, Marcin Cieslak wrote: I have put FreeBSD-14.0-CURRENT-amd64-20210422-df456a1fcf7-246266.raw.xz on an zvol and tried booting it like this: (..) it starts to boot but subsequently crashes with various messages related to network front drivers. The following commit solves the issue in the domU: https://cgit.freebsd.org/src/commit/?id=5d8fd932e418f03e98b3469c4088a36f0ef34ffe I don't think there's any snapshot image with this yet. Thank you. I plan to start building -current there so I can try to build from source. I tried to collect some info but now an attempt to start it seems to bog down my Xen host :( (it responds to TCP connections but SSH connections are frozen and I can't open new ones) Hm, that's weird. Do you have a serial attached to the box to know what's going on? Unfortunately, no. I could only hit big red button via my hosting provide "Hardware reset" console :( They only offer KVM when I ask for it and there is no serial console option :( Marcin smime.p7s Description: S/MIME Cryptographic Signature
Name resolution from host to domUs?
This is more a question about best practice people are using... I run Xen mainly to start a myriad of various operating systems in my lab (Linux variants, Solaris, BSDs, Windows...). domUs have usually zvol's allocated to them. I assign the IPv4 addresses via a local DHCP server, all domUs have access to two bridge interfaces (one for IPv4 with NAT, one for IPv6). Currently I add all domU IPv4 addresses to /etc/hosts file, being too lazy to maintain a DNS zone. Is there any way to nicely have name-to-IP name resolution working without doing things like DHCP+dynamic DNS on every machine? How to find out easily the IPv4 addresses assigned to the domUs? I understand that Xen only bridges Ethernet frames and has no clue really what happens above that? Marcin smime.p7s Description: S/MIME Cryptographic Signature
Re: Issue with packet framing on xnb(4) connections and NetBSD domus
On Wed, Mar 17, 2021 at 01:23:46AM -0700, Brian Buhrow wrote: > hello. I've noticed that on my Xen server, running > FreeBSD-12.2/Xen-4.14.0, I see a lot > of messages like the following from my NetBSD-5 and NetBSD-current domu's: > xennet0: discarding oversize frame (len=1518) > > They happen when network traffic is heavy and when traffic is coming from a > physical switch in > the same vlan as the domu's. Since I don't think packets are actually > oversized on the wire, > the Cisco switch managing this network does not report any giant packets, I > think this is a > software problem either on the NetBSD domu's, or the FreeBSD dom0. Since > I've been running > these same NetBSD domu setups on a machine where NetBSD is the dom0, I think > this is an issue > with the xnb(4) or netback.c driver. Specifically, it looks like it > concatinates multiple > packets together before notifying the domu that there is traffic available. > Perhaps that is by > design, since I cannot reproduce the issue on a FreeBSD-domu running on the > same FreeBSD-dom0 > machine. In either case, while things are usable, it creates a very noisy > log on the > NetBSD-domu machines. Does the xnb(4) driver forward multiple packets to the > domu front ends > and set the length of the message to the sum of the lengths of all the > packets it's forwarding, > leaving it to the domu front end driver to separate the packets on reception? > Is there a > parameter that can be set on a per-domu basis to say whether you want > multiple-packets-per-transfer or not from the dom0? I think this is an issue with FreeBSD netback as it doesn't properly handle frontends that don't understand some of the features implemented in the FreeBSD backend and are enabled unconditionally. Could you paste the output of `xenstore-ls -fp` from dom0 when one of those NetBSD domUs is running? Thanks, Roger. ___ freebsd-xen@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: Strange error messages from xnb on dom0. What do they mean?
On Mon, Apr 26, 2021 at 11:41:13AM -0700, Brian Buhrow wrote: > hello. Occasionally I see messages like the following from my > FreeBSD-12.2/dom0 machine. > Is this related to the issue of the NetBSD domu's seeing bursts of oversized > packets, which I assume > is caused by packets getting sent from the dom0 to the domu in batches rather > than one at a > time, each with an interrupt signal, or, the xen equivalent? > > On the domu's I see: > xennet0: discarding oversize frame (len=1518) > > I see the following messages on the dom0, but not necessarily at the same > time as the above > messages appear in the domu's. > > Any ideas? > -thanks > -Brian > > > Apr 25 14:56:35 xen-lothlorien kernel: xnb(xnb_ring2pkt:1532): Unknown extra > info type 255. Discarding packet > Apr 25 14:56:35 xen-lothlorien kernel: xnb(xnb_dump_txreq:302): > netif_tx_request index =0 > Apr 25 14:56:35 xen-lothlorien kernel: xnb(xnb_dump_txreq:303): > netif_tx_request.gref =0 > Apr 25 14:56:35 xen-lothlorien kernel: xnb(xnb_dump_txreq:304): > netif_tx_request.offset=0 > Apr 25 14:56:35 xen-lothlorien kernel: xnb(xnb_dump_txreq:305): > netif_tx_request.flags =8 > Apr 25 14:56:35 xen-lothlorien kernel: xnb(xnb_dump_txreq:306): > netif_tx_request.id=69 > Apr 25 14:56:35 xen-lothlorien kernel: xnb(xnb_dump_txreq:307): > netif_tx_request.size =1000 > Apr 25 14:56:35 xen-lothlorien kernel: xnb(xnb_dump_txreq:302): > netif_tx_request index =1 > Apr 25 14:56:35 xen-lothlorien kernel: xnb(xnb_dump_txreq:303): > netif_tx_request.gref =255 > Apr 25 14:56:35 xen-lothlorien kernel: xnb(xnb_dump_txreq:304): > netif_tx_request.offset=0 > Apr 25 14:56:35 xen-lothlorien kernel: xnb(xnb_dump_txreq:305): > netif_tx_request.flags =0 > Apr 25 14:56:35 xen-lothlorien kernel: xnb(xnb_dump_txreq:306): > netif_tx_request.id=0 > Apr 25 14:56:35 xen-lothlorien kernel: xnb(xnb_dump_txreq:307): > netif_tx_request.size =0 > Apr 25 14:56:35 xen-lothlorien kernel: xnb(xnb_rxpkt2rsp:2066): Got error -1 > for hypervisor gnttab_copy status Those are from netback failing to recognize or process a packet. Likely netback is being too verbose here, as those should only appear on debug builds or with boot_verbose. It might help identify what's going wrong between NetBSD netfront and FreeBSD netback. Roger. ___ freebsd-xen@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
Re: [PROMOTIONAL]FreeBSD 14-CURRENT as a guest working?
On Fri, May 07, 2021 at 05:12:16AM +, Marcin Cieslak wrote: > I have put FreeBSD-14.0-CURRENT-amd64-20210422-df456a1fcf7-246266.raw.xz > on an zvol and tried booting it like this: > > builder = "hvm" > name = "current0" > disk = [ > '/dev/zvol/zroot/current0,raw,xvda,w' > ] > boot = "c" > bios = "ovmf" > usbdevice = 'tablet' > #nographics = 1 > serial = [ "/dev/nmdm0A" ] > vnc = 1 > #vnclisten = '0.0.0.0' > vif = > ['bridge=bridge0,mac=00:02:04:15:fd:e1','bridge=bridge1,mac=00:02:04:15:fd:e2'] > memory=8192 > vcpus=6 > vga = "stdvga" > videoram = 16 > ;xen_platform_pci=1 > > it starts to boot but subsequently crashes with various messages related to > network front drivers. The following commit solves the issue in the domU: https://cgit.freebsd.org/src/commit/?id=5d8fd932e418f03e98b3469c4088a36f0ef34ffe I don't think there's any snapshot image with this yet. > I tried to collect some info but now an attempt to start it seems to bog down > my Xen host :( > (it responds to TCP connections but SSH connections are frozen and I can't > open new ones) Hm, that's weird. Do you have a serial attached to the box to know what's going on? Thanks, Roger. ___ freebsd-xen@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-xen To unsubscribe, send any mail to "freebsd-xen-unsubscr...@freebsd.org"
