From owner-freebsd-xen@freebsd.org Mon Jun 13 09:07:47 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 36A4DAF0869 for ; Mon, 13 Jun 2016 09:07:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2709825A1 for ; Mon, 13 Jun 2016 09:07:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u5D97lfQ047883 for ; Mon, 13 Jun 2016 09:07:47 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host. Date: Mon, 13 Jun 2016 09:07:47 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kpielorz@tdx.co.uk X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2016 09:07:47 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188261 --- Comment #28 from kpielorz@tdx.co.uk --- (In reply to Roger Pau Monn=C3=83=C2=A9 from comment #27) Hi, I've applied the patch and rebuilt/re-installed the kernel. Sadly I too get= no output to the console / dmesg or /var/log/messages while packets are being forwarded. If I move the VM to another node (so it works) - I get nothing logged, and if I move it back to the same node as the other test VM's - it stops working, and I still get nothing logged - sorry! -Karl --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Mon Jun 13 09:10:07 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CAFFAAF0973; Mon, 13 Jun 2016 09:10:07 +0000 (UTC) (envelope-from royger@gmail.com) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com [IPv6:2a00:1450:400c:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 53261264B; Mon, 13 Jun 2016 09:10:07 +0000 (UTC) (envelope-from royger@gmail.com) Received: by mail-wm0-x22b.google.com with SMTP id n184so68904889wmn.1; Mon, 13 Jun 2016 02:10:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=3IlL4TRNgGbMTqJUW7QgJtU9aU411A7CTAsEymTqsMc=; b=sLM2Sf28+Mk9E3fe2qRwH+EKwq0t8uPSF/M6AMz8or04HgJadnjNbM7neAJMNLFAoo uqUT5O4qZqJuQ9lYwoK2HnXbrD8FZQMSofr3NOYXMV4kZjTQeAUxrUtgioWMVMBPO31q skL/s7qIWxRsd5eXe6EXYiYcOXVMaBruV3nUmexS137PdYRs/QWdHug2DG/aHJokoD0i KmWLdoTX3Zoi30ziAf/GX/jDWFL8u9G3O9/0cm2tOwqMe5wDrDvy1GTuVxNSA5Uc0kKu 5HnQ9HRGgbamJaYBAOp6Q9gvND2MWzqXSd1nB27yWvHKovyxpNTKDziwyS+vN3Y3SCed 55XQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=3IlL4TRNgGbMTqJUW7QgJtU9aU411A7CTAsEymTqsMc=; b=Habmo4ZuZsM3ELjgK2VAe5Rt/4v0hgIMzRw30W6wl+7Q9i8+kFIOkSthDErYJzS/8S HVXKj1eQ406IbOTzyMFW5A+GLu5xl9VxQN/CP6gqZ2jYM5D5P0HWe7eMljbQ5puCRxLq 2BnxAxy1sbjW6yC60OIBrgeMFDHWUysfO9CzXZbXl5GaGCC4+RJQFV6cUhHkXnsb8ePT riPWGPiFpkzOK8I4Wk1jGggwQ41blq/+qsyeH7KzTMA2sXfrcdiYhGF4EeTtDJWGN6Ui rsY/zeBfUiow1JQSYK+lyNvaOL/iyzdf2eKk2+ddJw/qdGApn7YvpExnR1iNdt52uQmY X4zw== X-Gm-Message-State: ALyK8tIxuAz6FrbY5FNAN+Hp5pKjx8zfs0JAAjhnKMYTNE9eCb5lozND0zJrMblXWj3cQA== X-Received: by 10.28.21.204 with SMTP id 195mr34545wmv.64.1465809004445; Mon, 13 Jun 2016 02:10:04 -0700 (PDT) Received: from localhost (147.red-83-50-120.dynamicip.rima-tde.net. [83.50.120.147]) by smtp.gmail.com with ESMTPSA id u6sm26364509wjy.17.2016.06.13.02.10.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Jun 2016 02:10:03 -0700 (PDT) Sender: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= Date: Mon, 13 Jun 2016 11:10:04 +0200 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: Marcin Cieslak Cc: freebsd-xen@FreeBSD.org, xen-devel@lists.xenproject.org, freebsd-virtualization@freebsd.org Subject: Re: HEADS UP: Imported Xen 4.7: no blkback Message-ID: <20160613091003.cejnbuqepp25zanc@mac> References: <20160603120921.y5l362zgrhf4fdcb@mac> <20160609080343.44rvpda4hskiy3ge@mac> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.6.0-neo (2016-04-07) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2016 09:10:07 -0000 On Fri, Jun 10, 2016 at 09:38:59PM +0000, Marcin Cieslak wrote: > On Thu, 9 Jun 2016, Roger Pau Monné wrote: > > > On Thu, Jun 09, 2016 at 12:16:59AM +0000, Marcin Cieslak wrote: > > > On Fri, 3 Jun 2016, Roger Pau Monné wrote: > > > > > > > One of the more relevant changes in 4.7 regarding FreeBSD is the support for > > > > block hotplug scripts. This means that we now have the option to use > > > > backends different than simple block or regular files, provided that someone > > > > writes the proper hotplug scripts to attach them (I've heard there are some > > > > iSCSI hotplug scripts around). This however requires changes in blkback, so > > > > if you plan to use the Xen 4.7 port, please make sure that you are running a > > > > kernel that contains revision r301269 (or any later version). The same also > > > > > > I am running it with r301685 and the HVM guests have some trouble with > > > block devices. > > > > > > SeaBIOS does not find /dev/zvol/zroot/freebsd1,raw,xvda,w to boot FreeBSD > > > from, after chaging to "hda" I get up to the kernel mountroot prompt > > > (Xen block devices seem to be detected in dmesg). > > > > Yes, this is intentional, see: > > > > https://marc.info/?l=xen-devel&m=144482080812353 > > those guests worked fine with 4.5, that's why I am surprised. > > xbd0 and xbd1 show up in dmesg, mouting root from xbd0p2 fails, but > ada0p2 seems to work. > > I remember that during my previous attempts ZFS ate most of > my machine's memory (dom0 was too small I think) and the > symptom was very similar if not identical. > > One thing which struck me is that I was able to fully but > one Linux HVM domU. I am also toying with OpenFirmware > which boots from floppy as a HVM guest. > > > Have you checked if you need to change your /etc/fstab to correctly point > > to the new device? Does FreeBSD correctly list the disk(s) at the mountroot > > prompt when issuing a "?" command? > > "?" does not work - it mostly causes a panic, the console is slow, but I managed > to switch it to /dev/ada0p2, dmesg below: This has now been reverted, so when I import the new RC this should be fixed and you won't need to change anything. > Copyright (c) 1992-2016 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 11.0-CURRENT #1 r298620: Tue Apr 26 13:21:50 UTC 2016 > root@o.saper.info:/usr/obj/usr/src/sys/GENERIC amd64 > FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 3.8.0) > WARNING: WITNESS option enabled, expect reduced performance. > VT(vga): text 80x25 > XEN: Hypervisor version 4.7 detected. > CPU: Intel(R) Xeon(R) CPU E31245 @ 3.30GHz (3300.08-MHz K8-class CPU) > Origin="GenuineIntel" Id=0x206a7 Family=0x6 Model=0x2a Stepping=7 > Features=0x17c3fbff > Features2=0x9fba2203 > AMD Features=0x28100800 > AMD Features2=0x1 > XSAVE Features=0x1 > Hypervisor: Origin = "XenVMMXenVMM" > real memory = 2130706432 (2032 MB) > avail memory = 2018213888 (1924 MB) > Event timer "LAPIC" quality 400 > ACPI APIC Table: > WARNING: L1 data cache covers less APIC IDs than a core > 0 < 1 > WARNING: L2 data cache covers less APIC IDs than a core > 0 < 1 > WARNING: L3 data cache covers less APIC IDs than a core > 0 < 1 > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > FreeBSD/SMP: 1 package(s) x 2 core(s) > random: unblocking device. > ioapic0: Changing APIC ID to 1 > MADT: Forcing active-low polarity and level trigger for SCI > ioapic0 irqs 0-47 on motherboard > random: entropy device external interface > kbd1 at kbdmux0 > netmap: loaded module > module_register_init: MOD_LOAD (vesa, 0xffffffff80f0ffb0, 0) error 19 > vtvga0: on motherboard > cryptosoft0: on motherboard > acpi0: on motherboard > acpi0: Power Button (fixed) > acpi0: Sleep Button (fixed) > cpu0: on acpi0 > cpu1: on acpi0 > hpet0: iomem 0xfed00000-0xfed003ff on acpi0 > Timecounter "HPET" frequency 62500000 Hz quality 950 > attimer0: port 0x40-0x43 irq 0 on acpi0 > Timecounter "i8254" frequency 1193182 Hz quality 0 > Event timer "i8254" frequency 1193182 Hz quality 100 > atrtc0: port 0x70-0x71 irq 8 on acpi0 > Event timer "RTC" frequency 32768 Hz quality 0 > Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0xb008-0xb00b on acpi0 > pcib0: port 0xcf8-0xcff on acpi0 > pci0: on pcib0 > isab0: at device 1.0 on pci0 > isa0: on isab0 > atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xc200-0xc20f at device 1.1 on pci0 > ata0: at channel 0 on atapci0 > ata1: at channel 1 on atapci0 > pci0: at device 1.3 (no driver attached) > xenpci0: port 0xc000-0xc0ff mem 0xf0000000-0xf0ffffff irq 24 at device 2.0 on pci0 > vgapci0: mem 0xf1000000-0xf1ffffff,0xf2050000-0xf2050fff at device 3.0 on pci0 > vgapci0: Boot video device > atkbdc0: port 0x60,0x64 irq 1 on acpi0 > atkbd0: irq 1 on atkbdc0 > kbd0 at atkbd0 > atkbd0: [GIANT-LOCKED] > psm0: irq 12 on atkbdc0 > psm0: [GIANT-LOCKED] > psm0: model IntelliMouse Explorer, device ID 4 > fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0 > fdc0: does not respond > device_attach: fdc0 attach returned 6 > xenpv0: on motherboard > granttable0: on xenpv0 > xen_et0: on xenpv0 > Event timer "XENTIMER" frequency 1000000000 Hz quality 950 > Timecounter "XENTIMER" frequency 1000000000 Hz quality 950 > xenstore0: on xenpv0 > evtchn0: on xenpv0 > privcmd0: on xenpv0 > debug0: on xenpv0 > orm0: at iomem 0xed800-0xeffff on isa0 > vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > fdc0: No FDOUT register! > ppc0: cannot reserve I/O port range > Timecounters tick every 1.000 msec > xenballoon0: on xenstore0 > xctrl0: on xenstore0 > xs_dev0: on xenstore0 > xenbusb_front0: on xenstore0 > xenbusb_add_device: Device device/suspend/event-channel ignored. State 6 > xn0: at device/vif/0 on xenbusb_front0 > xbd0: 16384MB at device/vbd/768 on xenbusb_front0 > xbd0: attaching as ada0 > xbd0: features: flush, write_barrier > xbd0: synchronize cache commands enabled. > xn0: Ethernet address: 00:02:04:08:fd:f0 > xenbusb_back0: on xenstore0 > xbd1: 40960MB at device/vbd/832 on xenbusb_front0 > xbd1: attaching as ada1 > xbd1: features: flush, write_barrier > xbd1: synchronize cache commands enabled. > xn0: backend features: feature-sg > SMP: AP CPU #1 Launched! > WARNING: WITNESS option enabled, expect reduced performance. > Trying to mount root from ufs:/dev/xbd0p2 [rw]... > mountroot: waiting for device /dev/xbd0p2... > Mounting from ufs:/dev/xbd0p2 failed with error 19. > > Loader variables: > vfs.root.mountfrom=ufs:/dev/xbd0p2 > vfs.root.mountfrom.options=rw > > Manual root filesystem specification: > : [options] > Mount using filesystem > and with the specified (optional) option list. > > eg. ufs:/dev/da0s1a > zfs:tank > cd9660:/dev/cd0 ro > (which is equivalent to: mount -t cd9660 -o ro /dev/cd0 /) > > ? List valid disk boot devices > . Yield 1 second (for background tasks) > Abort manual input > > mountroot> Trying to mount root from ufs:/dev/ada0p2 []... > xn0: link state changed to DOWN > xn0: link state changed to UP > > > Also, can you paste the output of `xenstore-ls -fp` from Dom0 when this > > happens? > > Windows: [...] > /local/domain/279/device/vbd/768/backend = "/local/domain/0/backend/vbd/279/768" (n279,r0) > /local/domain/279/device/vbd/768/backend-id = "0" (n279,r0) > /local/domain/279/device/vbd/768/state = "1" (n279,r0) > /local/domain/279/device/vbd/768/virtual-device = "768" (n279,r0) > /local/domain/279/device/vbd/768/device-type = "disk" (n279,r0) > /local/domain/279/device/vbd/832 = "" (n279,r0) > /local/domain/279/device/vbd/832/backend = "/local/domain/0/backend/vbd/279/832" (n279,r0) > /local/domain/279/device/vbd/832/backend-id = "0" (n279,r0) > /local/domain/279/device/vbd/832/state = "1" (n279,r0) > /local/domain/279/device/vbd/832/virtual-device = "832" (n279,r0) > /local/domain/279/device/vbd/832/device-type = "disk" (n279,r0) > /local/domain/279/device/vkbd = "" (n0,r279) > /local/domain/279/device/vkbd/0 = "" (n279,r0) > /local/domain/279/device/vkbd/0/backend = "/local/domain/0/backend/vkbd/279/0" (n279,r0) > /local/domain/279/device/vkbd/0/backend-id = "0" (n279,r0) > /local/domain/279/device/vkbd/0/state = "1" (n279,r0) > /local/domain/279/device/vif = "" (n0,r279) > /local/domain/279/device/vif/0 = "" (n279,r0) > /local/domain/279/device/vif/0/backend = "/local/domain/0/backend/vif/279/0" (n279,r0) > /local/domain/279/device/vif/0/backend-id = "0" (n279,r0) > /local/domain/279/device/vif/0/state = "1" (n279,r0) > /local/domain/279/device/vif/0/handle = "0" (n279,r0) > /local/domain/279/device/vif/0/mac = "00:16:3e:5d:0d:48" (n279,r0) It seems like Windows PV drivers don't attach at all, or are you running Windows without the PV drivers? [...] > FreeBSD: [...] > /local/domain/11/device/vbd/768/backend = "/local/domain/0/backend/vbd/11/768" (n11,r0) > /local/domain/11/device/vbd/768/backend-id = "0" (n11,r0) > /local/domain/11/device/vbd/768/state = "4" (n11,r0) > /local/domain/11/device/vbd/768/virtual-device = "768" (n11,r0) > /local/domain/11/device/vbd/768/device-type = "disk" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref0 = "8" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref1 = "9" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref2 = "10" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref3 = "11" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref4 = "12" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref5 = "13" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref6 = "14" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref7 = "15" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref8 = "16" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref9 = "17" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref10 = "18" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref11 = "19" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref12 = "20" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref13 = "21" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref14 = "22" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref15 = "23" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref16 = "24" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref17 = "25" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref18 = "26" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref19 = "27" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref20 = "28" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref21 = "29" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref22 = "30" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref23 = "31" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref24 = "32" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref25 = "33" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref26 = "34" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref27 = "35" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref28 = "36" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref29 = "37" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref30 = "38" (n11,r0) > /local/domain/11/device/vbd/768/ring-ref31 = "39" (n11,r0) > /local/domain/11/device/vbd/768/num-ring-pages = "32" (n11,r0) > /local/domain/11/device/vbd/768/ring-page-order = "5" (n11,r0) > /local/domain/11/device/vbd/768/event-channel = "10" (n11,r0) > /local/domain/11/device/vbd/768/protocol = "x86_64-abi" (n11,r0) > /local/domain/11/device/vbd/832 = "" (n11,r0) > /local/domain/11/device/vbd/832/backend = "/local/domain/0/backend/vbd/11/832" (n11,r0) > /local/domain/11/device/vbd/832/backend-id = "0" (n11,r0) > /local/domain/11/device/vbd/832/state = "4" (n11,r0) > /local/domain/11/device/vbd/832/virtual-device = "832" (n11,r0) > /local/domain/11/device/vbd/832/device-type = "disk" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref0 = "40" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref1 = "41" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref2 = "42" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref3 = "43" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref4 = "44" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref5 = "45" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref6 = "46" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref7 = "47" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref8 = "48" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref9 = "49" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref10 = "50" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref11 = "51" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref12 = "52" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref13 = "53" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref14 = "54" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref15 = "55" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref16 = "56" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref17 = "57" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref18 = "58" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref19 = "59" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref20 = "60" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref21 = "61" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref22 = "62" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref23 = "63" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref24 = "64" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref25 = "65" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref26 = "66" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref27 = "67" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref28 = "68" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref29 = "69" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref30 = "70" (n11,r0) > /local/domain/11/device/vbd/832/ring-ref31 = "71" (n11,r0) > /local/domain/11/device/vbd/832/num-ring-pages = "32" (n11,r0) > /local/domain/11/device/vbd/832/ring-page-order = "5" (n11,r0) > /local/domain/11/device/vbd/832/event-channel = "11" (n11,r0) > /local/domain/11/device/vbd/832/protocol = "x86_64-abi" (n11,r0) Everything seems fine regarding FreeBSD, PV devices have attached correctly AFAICT. [...] > /local/domain/11/console/vnc-port = "5900" (n0,r11) > /local/domain/11/image = "" (n0,r11) > /local/domain/11/image/device-model-pid = "6311" (n0,r11) > > > > What used to be Windows 2016 domU with /dev/zvol/zroot/windows0,raw,hda,w > > > ends up in the Tianocore UEFI shell. Block devices seem to be available, > > > I can even list the fs0: partition, but no booting further possible. > > > > Hm, I've never used Tianocore myself, so I'm not sure what the issue could > > be here. Again, can you post the output of `xenstore-ls -fp` from Dom0 when > > this happens? At least this will show if the PV block device has been > > correctly attached. > > See above. > > How do I rollback to 4.5.2, do I need to downgrade the FreeBSD kernel > as well? Yes, you will need to switch back to an older kernel, but I thing we should aim to solve this, or else you will get stuck with an older Xen and FreeBSD kernel. Since you mention that the console is very slow, if you run 'top' on Dom0, do you see any process (eg: qemu) taking a lot of CPU time? Also, do you see Dom0 consuming a lot of CPU if you run 'xentop'? Thanks. From owner-freebsd-xen@freebsd.org Mon Jun 13 09:15:55 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E6701AF0DDC for ; Mon, 13 Jun 2016 09:15:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D6BE12A04 for ; Mon, 13 Jun 2016 09:15:55 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u5D9Ft4e005443 for ; Mon, 13 Jun 2016 09:15:55 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host. Date: Mon, 13 Jun 2016 09:15:55 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: royger@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2016 09:15:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188261 --- Comment #29 from Roger Pau Monn=C3=83=C2=A9 --- (In reply to kpielorz from comment #28) Can you provide a little more info about your router configuration? In my t= ests I've only enabled net.inet.ip.forwarding=3D1 in the VM acting as a router a= nd configured different subnets in two interfaces, and exchanged packets betwe= en them. Are you doing NAT/Filtering/...? --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Mon Jun 13 09:22:52 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EBD4BAF10C8 for ; Mon, 13 Jun 2016 09:22:52 +0000 (UTC) (envelope-from royger@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 818FC2EAC for ; Mon, 13 Jun 2016 09:22:52 +0000 (UTC) (envelope-from royger@gmail.com) Received: by mail-wm0-x236.google.com with SMTP id v199so69171318wmv.0; Mon, 13 Jun 2016 02:22:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=sa7kEeLRzarujj5JtOPI5tZG1aElNhgieARSK82sbRo=; b=uJrxdzGuGFM7Z3AoYMCf9SDA8z2VnFrKO5SbZ+BlEQ6/T36EU4xRyag0o8r61+honE JEoYPu/hghgDanU8uANP0fa6reYNgdtOrZFDLMmfJkrIbwXkSz7hXCEZ+/XF0Ij4cO4z knHlfUEV/bjP+Jn/V17hy3FULe3Tw69ipM/ddqF7OjxCUuLIrb/Ie2Qb3H8+fKdBsNZy sQOoj08mCvnwjX1L1hTf9NzPJkABw24ta9cNk3ZU7PcuvGDub1LrmX5J7YSUS9H1nEsH zoQcut5bh+07EYRYdxLLWCEtE9oEg2vP0JOJFLwMhd33wkAL/PGOwWE9fPPNlfY4MGZL 76AA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=sa7kEeLRzarujj5JtOPI5tZG1aElNhgieARSK82sbRo=; b=Ss09S8GA5hOYDorXkIU+n/de1Sz8oDCjLhLP35YbWYyP+8u5QgLYo0iq8hN+pQsxGe x55vZK9QNPIYz1zsWvCBDcn1sGFQmgjsPVZMqaTgwzjeNeYOhs1qVwFAiU+fog1ZiiNU 1jF9ImZI8OvKfNrwnYFgYoUKw1wDRK+nVPcN3yq66wJd4Ugwq6+Ne1E0DGKoDUXTT6D3 T+0aL10EhzyUWqqn84E98Scb8Ev8o6A25AqzgTNWGffaU9Zhq1jD83T173/SnzcRKTQQ d1YtemjfrJELZOe5zObuckHhfgRmHATBoXb8O2QAVUO3I7QRp86JZv5JQWqtO8YJROzX eqsg== X-Gm-Message-State: ALyK8tJy15lumye+WeXzgP5Aqsad6O14roErjzhoGYZ2SWE3nKPoQHPtEpUBjBAXz/EeHw== X-Received: by 10.194.133.135 with SMTP id pc7mr58993wjb.49.1465809771005; Mon, 13 Jun 2016 02:22:51 -0700 (PDT) Received: from localhost (147.red-83-50-120.dynamicip.rima-tde.net. [83.50.120.147]) by smtp.gmail.com with ESMTPSA id k127sm13234447wmf.21.2016.06.13.02.22.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 Jun 2016 02:22:50 -0700 (PDT) Sender: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= Date: Mon, 13 Jun 2016 11:22:50 +0200 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: Marcin Cieslak Cc: freebsd-xen@FreeBSD.org, xen-devel@lists.xenproject.org, freebsd-virt@freebsd.org Subject: Re: HEADS UP: Imported Xen 4.7 and blkback changes Message-ID: <20160613092250.4sikkje2immrdovt@mac> References: <20160603120921.y5l362zgrhf4fdcb@mac> <20160609074021.uqtjio2vn7wo5h4m@mac> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.6.0-neo (2016-04-07) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2016 09:22:53 -0000 On Fri, Jun 10, 2016 at 09:41:04PM +0000, Marcin Cieslak wrote: > On Thu, 9 Jun 2016, Roger Pau Monné wrote: > > > On Wed, Jun 08, 2016 at 10:18:09PM +0000, Marcin Cieslak wrote: > > > On Fri, 3 Jun 2016, Roger Pau Monné wrote: > > > > > > > Hello, > > > > > > > > First of all, this message is only relevant to those that use FreeBSD as > > > > Dom0 (host), not as a DomU (guest), so don't panic. > > > > > > > > I've imported the latest Xen version (4.7-rc4) into the ports tree, it's > > > > still not the final version, but it's quite close, so we better start > > > > testing it to make sure it works fine with FreeBSD. > > > > > > Thank you Roger, this is excellent. Are xen-tools-devel 4.5 now? > > > Looks confusing. > > > > > > I have also tried building xen-tools (4.7) without python > > > and qemu configure reported this. > > > > Python is required, you cannot get rid of it. > > Strange, seems USES= python in the port's Makefile didn't work for me and > continued happily after. Have you been able to build the tools successfully? I'm afraid I cannot provide much help regarding this, since I don't know that much about the ports build system :(. Roger. From owner-freebsd-xen@freebsd.org Mon Jun 13 09:37:36 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BDC4EAF12F3 for ; Mon, 13 Jun 2016 09:37:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id ADD9F2252 for ; Mon, 13 Jun 2016 09:37:36 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u5D9bZ6v055303 for ; Mon, 13 Jun 2016 09:37:36 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host. Date: Mon, 13 Jun 2016 09:37:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kpielorz@tdx.co.uk X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2016 09:37:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188261 --- Comment #30 from kpielorz@tdx.co.uk --- (In reply to Roger Pau Monn=C3=83=C2=A9 from comment #29) Hi, This machine is running natd [this was briefly mentioned in the original ti= cket way-back-when] - so in /etc/rc.conf I have: ifconfig_xn1=3D"DHCP" // This is our 'Internet' feed via ADSL modem ifconfig_xn0=3D"inet x.x.x.x netmask 255.255.255.0" // Local LAN IP gateway_enable=3D"YES" firewall_enable=3D"YES" firewall_type=3D"OPEN" natd_enable=3D"YES" natd_interface=3D"xn1" natd_flags=3D"" 'ipfw show' gives: 00050 1226 417933 divert 8668 ip4 from any to any via xn1 ... 65000 7324 1573607 allow ip from any to any 65535 0 0 deny ip from any to any I can try and setup a non natd case again - but that will involve quite a f= ew changes, as I have no easily routed networks at our office. -Karl --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Mon Jun 13 09:44:41 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DAD61AF1588; Mon, 13 Jun 2016 09:44:41 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 7A34A26B9; Mon, 13 Jun 2016 09:44:41 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id u5D9ib2w022941 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 13 Jun 2016 09:44:37 GMT (envelope-from saper@saper.info) Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id u5D9iaLH022938; Mon, 13 Jun 2016 09:44:37 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Mon, 13 Jun 2016 09:44:35 +0000 From: Marcin Cieslak To: =?ISO-8859-15?Q?Roger_Pau_Monn=E9?= cc: freebsd-xen@FreeBSD.org, xen-devel@lists.xenproject.org, freebsd-virtualization@freebsd.org Subject: Re: HEADS UP: Imported Xen 4.7: no blkback In-Reply-To: <20160613091003.cejnbuqepp25zanc@mac> Message-ID: References: <20160603120921.y5l362zgrhf4fdcb@mac> <20160609080343.44rvpda4hskiy3ge@mac> <20160613091003.cejnbuqepp25zanc@mac> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2016 09:44:42 -0000 On Mon, 13 Jun 2016, Roger Pau Monné wrote: > Since you mention that the console is very slow, if you run 'top' on Dom0, > do you see any process (eg: qemu) taking a lot of CPU time? > > Also, do you see Dom0 consuming a lot of CPU if you run 'xentop'? Just quick info regarding console problem at the mountroot prompt: - it was also very slow and behaving strange with older kernel and 4.5.2. - it works better when I use dual console - one can type on the serial console and see the results immediately, vidconsole is slower but thins seem to work (at least I get no panics due to "cannot mount root" anymore). - will check top Marcin From owner-freebsd-xen@freebsd.org Mon Jun 13 09:51:30 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0F64AF1821 for ; Mon, 13 Jun 2016 09:51:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B0EDC2951 for ; Mon, 13 Jun 2016 09:51:30 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u5D9pURn081925 for ; Mon, 13 Jun 2016 09:51:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host. Date: Mon, 13 Jun 2016 09:51:30 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: royger@freebsd.org X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2016 09:51:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188261 --- Comment #31 from Roger Pau Monn=C3=83=C2=A9 --- (In reply to kpielorz from comment #30) Oh right, this is kind of different from my test setup, it could explain wh= y it works in my case but not in yours. Do you see any checksum errors? 'netstat= -s -f inet' should tell you if there are any checksum errors, at least from a FreeBSD point of view. It would also be interesting to do the same on the Dom0 itself, but I'm not aware of the rune to obtain that information from Linux. Roger. --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Mon Jun 13 12:48:04 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A1870AF1EB5 for ; Mon, 13 Jun 2016 12:48:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 915982A50 for ; Mon, 13 Jun 2016 12:48:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u5DCm3bM095249 for ; Mon, 13 Jun 2016 12:48:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-xen@FreeBSD.org Subject: [Bug 188261] [xen] FreeBSD DomU PVHVM guests cannot 'route' traffic for other Xen PV guests on same Dom0 Host. Date: Mon, 13 Jun 2016 12:48:04 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 9.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: kpielorz@tdx.co.uk X-Bugzilla-Status: In Progress X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: freebsd-xen@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2016 12:48:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D188261 --- Comment #32 from kpielorz@tdx.co.uk --- (In reply to Roger Pau Monn=C3=83=C2=A9 from comment #31) Hi, I can't see any obvious checksum errors recorded, and like yourself - I don= 't know how to get similar information from dom0 -Karl --=20 You are receiving this mail because: You are the assignee for the bug.= From owner-freebsd-xen@freebsd.org Mon Jun 13 19:26:34 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6D839AF2F93; Mon, 13 Jun 2016 19:26:34 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 0CFA8222A; Mon, 13 Jun 2016 19:26:33 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id u5DJQUQu027622 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 13 Jun 2016 19:26:30 GMT (envelope-from saper@saper.info) Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id u5DJQUkA027619; Mon, 13 Jun 2016 19:26:30 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Mon, 13 Jun 2016 19:26:30 +0000 From: Marcin Cieslak To: =?ISO-8859-15?Q?Roger_Pau_Monn=E9?= cc: freebsd-xen@FreeBSD.org, xen-devel@lists.xenproject.org, freebsd-virtualization@freebsd.org Subject: Re: HEADS UP: Imported Xen 4.7: no blkback In-Reply-To: <20160613091003.cejnbuqepp25zanc@mac> Message-ID: References: <20160603120921.y5l362zgrhf4fdcb@mac> <20160609080343.44rvpda4hskiy3ge@mac> <20160613091003.cejnbuqepp25zanc@mac> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2016 19:26:34 -0000 On Mon, 13 Jun 2016, Roger Pau Monné wrote: > On Fri, Jun 10, 2016 at 09:38:59PM +0000, Marcin Cieslak wrote: > > "?" does not work - it mostly causes a panic, the console is slow, but I managed > > to switch it to /dev/ada0p2, dmesg below: > > This has now been reverted, so when I import the new RC this should be fixed > and you won't need to change anything. I am confused now - so with a new Xen kernel (not yet in ports) I can use /dev/xbd* devices again? They are in fact missing - xbd driver says "attaching as ada0" and I can mount it only as /dev/ada > It seems like Windows PV drivers don't attach at all, or are you running > Windows without the PV drivers? Yes, I have. Those Windows partitions used to work properly without changes under xen 4.5. But we are too early - the problem is that even ovmf does not se them drives now, this is before Windows boots. > Since you mention that the console is very slow, if you run 'top' on Dom0, > do you see any process (eg: qemu) taking a lot of CPU time? Yes, 1635 root 7 100 0 241M 101M RUN 7:16 91.14% qemu-system-i386 or more > Also, do you see Dom0 consuming a lot of CPU if you run 'xentop'? Domain-0 -----r 446 100.0 4194300 25.2 no limit n/a 1 0 0 0 0 0 0 0 0 0 0 Marcin From owner-freebsd-xen@freebsd.org Thu Jun 16 15:29:26 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 38C2BA7300F; Thu, 16 Jun 2016 15:29:26 +0000 (UTC) (envelope-from royger@gmail.com) Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BE8DE1ECD; Thu, 16 Jun 2016 15:29:25 +0000 (UTC) (envelope-from royger@gmail.com) Received: by mail-wm0-x230.google.com with SMTP id v199so197003656wmv.0; Thu, 16 Jun 2016 08:29:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=mCJrEFDEEcdPQoJdiUTiwpH9ONiGLWQnjkKColRG8SM=; b=ZjnrCE4oMDzAMxXTc++Nh5jduTxyEs+B8hyJ/lpijDwLhE0jLRHLhPrNszfnYwwK3f XuLpNBMB2PZ/y14NbUxgh+O0msirZ7UgiJKAHj/rTED4Vkn7hao+C7yeRDkGnngiVbXz BLsewwigZOwlart9UytcovQLi0S7XWe7ZTDCbHBZ6de8mcRGI575h26TJcKNDughIT4T bfHFpHJKGNvmOHg5FXCbjNTXgjeA8KA89ei/rXgIsAWtGrXZhbqkzrSAOBTJpmq+4Qi5 UmL8Y61OppPJAL6YgKnptjKTUs3NH1iN94DUcvayRmgKnXCPHjXY4cUH3+4vbO6bwVkp 2kag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=mCJrEFDEEcdPQoJdiUTiwpH9ONiGLWQnjkKColRG8SM=; b=Ag8it4KMIsNs3EKN0WNp/taC7MPic583VR2/oAw2N0/fkyTsuUzXhXE5AWtbVvQrEj fcQyw0nqsFKCFQnO+PjGuF8+YMutn71WwZa7hIIzREa0RaiZAwmt2+JR9s5vCvyK7NEm GwnGFXmdLcmRimSNRUtpnaeB6qqTPaBsLZMRGl8QUza4WhMzY4wVlJvzEyrGQBDe7fJj c1RI5K5MNGbNcGpfHHbYeeohqm0HQGlHWzmHnRhxKke8NVN8j+nILVdoNwICdzvHdF7t lB2qvtbj2tKY2U63rRFgmXlUEdJsKrF+noKaKFSCLJyO7E22IK0svWg3SIyM/fnucDvX 9e5g== X-Gm-Message-State: ALyK8tLDth2hIVSlnPGwqDW4ktGKi2mHrkZGNA+cZRfARX7d/CLAN4LAWLaPh6j7fZJlFw== X-Received: by 10.194.109.232 with SMTP id hv8mr210579wjb.115.1466090964095; Thu, 16 Jun 2016 08:29:24 -0700 (PDT) Received: from localhost (43.red-83-46-25.dynamicip.rima-tde.net. [83.46.25.43]) by smtp.gmail.com with ESMTPSA id s123sm9133941wmb.15.2016.06.16.08.29.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 16 Jun 2016 08:29:23 -0700 (PDT) Sender: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= Date: Thu, 16 Jun 2016 17:29:19 +0200 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: Marcin Cieslak Cc: freebsd-xen@FreeBSD.org, xen-devel@lists.xenproject.org, freebsd-virtualization@freebsd.org Subject: Re: HEADS UP: Imported Xen 4.7: no blkback Message-ID: <20160616152919.3nelncwerh3nir27@mac> References: <20160603120921.y5l362zgrhf4fdcb@mac> <20160609080343.44rvpda4hskiy3ge@mac> <20160613091003.cejnbuqepp25zanc@mac> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.6.0-neo (2016-04-07) X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jun 2016 15:29:26 -0000 On Mon, Jun 13, 2016 at 07:26:30PM +0000, Marcin Cieslak wrote: > On Mon, 13 Jun 2016, Roger Pau Monné wrote: > > > On Fri, Jun 10, 2016 at 09:38:59PM +0000, Marcin Cieslak wrote: > > > "?" does not work - it mostly causes a panic, the console is slow, but I managed > > > to switch it to /dev/ada0p2, dmesg below: > > > > This has now been reverted, so when I import the new RC this should be fixed > > and you won't need to change anything. > > I am confused now - so with a new Xen kernel (not yet in ports) I can use > /dev/xbd* devices again? They are in fact missing - xbd driver says "attaching as ada0" > and I can mount it only as /dev/ada > > > It seems like Windows PV drivers don't attach at all, or are you running > > Windows without the PV drivers? > > Yes, I have. Those Windows partitions used to work properly without changes > under xen 4.5. But we are too early - the problem is that even ovmf > does not se them drives now, this is before Windows boots. > > > Since you mention that the console is very slow, if you run 'top' on Dom0, > > do you see any process (eg: qemu) taking a lot of CPU time? > > Yes, > > 1635 root 7 100 0 241M 101M RUN 7:16 91.14% qemu-system-i386 > > or more > > > Also, do you see Dom0 consuming a lot of CPU if you run 'xentop'? > > Domain-0 -----r 446 100.0 4194300 25.2 no limit n/a 1 0 0 0 0 0 0 0 0 0 0 > Hello, I've just imported Xen 4.7.0-rc6 into the ports tree, could you give it a try when you have a moment? FWIW, I'm going on vacations until the 4th of July, and I will be mostly AFK. Roger. From owner-freebsd-xen@freebsd.org Thu Jun 16 17:05:21 2016 Return-Path: Delivered-To: freebsd-xen@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BEDF7A762F0; Thu, 16 Jun 2016 17:05:21 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2016" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 59E4A1662; Thu, 16 Jun 2016 17:05:21 +0000 (UTC) (envelope-from saper@saper.info) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.15.2/8.15.2) with ESMTPS id u5GH5Ifb066170 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 16 Jun 2016 17:05:18 GMT (envelope-from saper@saper.info) Received: from localhost (saper@localhost) by m.saper.info (8.15.2/8.15.2/Submit) with ESMTP id u5GH5Hts066167; Thu, 16 Jun 2016 17:05:18 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Thu, 16 Jun 2016 17:05:17 +0000 From: Marcin Cieslak To: =?ISO-8859-15?Q?Roger_Pau_Monn=E9?= cc: freebsd-xen@FreeBSD.org, xen-devel@lists.xenproject.org, freebsd-virtualization@freebsd.org Subject: Re: HEADS UP: Imported Xen 4.7: no blkback In-Reply-To: <20160616152919.3nelncwerh3nir27@mac> Message-ID: References: <20160603120921.y5l362zgrhf4fdcb@mac> <20160609080343.44rvpda4hskiy3ge@mac> <20160613091003.cejnbuqepp25zanc@mac> <20160616152919.3nelncwerh3nir27@mac> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jun 2016 17:05:21 -0000 On Thu, 16 Jun 2016, Roger Pau Monné wrote: > I've just imported Xen 4.7.0-rc6 into the ports tree, could you give it a > try when you have a moment? Yes, of course. A quick test shows no change - Windows get stuck at the UEFI shell with some block devices listed (I use "hda" for Windows), SeaBIOS cannot boot FreeBSD with "xvda". FreeBSD works with "hda", but I have to mount "/dev/ada0p1". Marcin