Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb)

On Tue, Aug 08, 2017 at 07:55:16PM +0300, Alexander Nusov wrote: > Hello, > > tried booting from qcow2 on FreeBSD 11.1-RELEASE, the issue still exists. Hm, great. Now it's too late to fix 11.1 :(. Have you tried with HEAD? Thanks, Roger. ___ freebsd-xe

Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb)

Hello, tried booting from qcow2 on FreeBSD 11.1-RELEASE, the issue still exists. -- thanks, alex On Mon, 27 Feb 2017 18:45:38 +0300 Alexander Nusov wrote Not yet, I’ll try the HEAD this week. — alex > On Feb 27, 2017, at 6:34 PM, R

Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb)

Not yet, I’ll try the HEAD this week. — alex > On Feb 27, 2017, at 6:34 PM, Roger Pau Monné wrote: > > On Mon, Feb 27, 2017 at 06:30:12PM +0300, Alexander Nusov wrote: >> Hi, >> Sorry for top posting. >> >> Any update on the issue? >> Please let me know if I need open a bug in Bugzilla. > >

Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb)

On Mon, Feb 27, 2017 at 06:30:12PM +0300, Alexander Nusov wrote: > Hi, > Sorry for top posting. > > Any update on the issue? > Please let me know if I need open a bug in Bugzilla. Sadly it seems like there are still some loose ends on the VM subsystem. I hope those will be fixed soon. Have you t

Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb)

Hi, Sorry for top posting. Any update on the issue? Please let me know if I need open a bug in Bugzilla. -- alex On Mon, 13 Feb 2017 06:39:16 -0800 alexander.nu...@nfvexpress.com wrote Hi! Please notify me when the issue will be fixed so I could start backporting patches to 11.0 t

Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb)

Hi! Please notify me when the issue will be fixed so I could start backporting patches to 11.0 to test qcow backend. On Fri, 03 Feb 2017 13:14:02 +0300 roger@citrix.com wrote On Thu, Feb 02, 2017 at 11:37:02PM +, Akshay Jaggi wrote: > [-Alex] > > Hi Roger, > > Did this ge

Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb)

On Thu, Feb 02, 2017 at 11:37:02PM +, Akshay Jaggi wrote: > [-Alex] > > Hi Roger, > > Did this get solved with the change you submitted to Xen? This issue is cased by a bug in the VM subsystem, kib is currently looking into it, and patches will be committed soon hopefully. The Xen patch I've

Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb)

[-Alex] Hi Roger, Did this get solved with the change you submitted to Xen? On 25 January 2017 at 11:58, Alexander Nusov wrote: > Cool, many thanks! > > -- > Alex > > On Wed, 25 Jan 2017 14:50:51 +0300 *Roger Pau Monné > >* wrote > > On Wed, Jan 25, 2017 at 02:20:55PM +0300, Alexande

Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb)

Cool, many thanks! -- Alex On Wed, 25 Jan 2017 14:50:51 +0300 Roger Pau Monné wrote On Wed, Jan 25, 2017 at 02:20:55PM +0300, Alexander Nusov wrote: > Got it, thanks. > > > > I found a workaround to avoid XENBUS delay in Linux DomUs by adding x

Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb)

On Wed, Jan 25, 2017 at 02:20:55PM +0300, Alexander Nusov wrote: > Got it, thanks. > > > > I found a workaround to avoid XENBUS delay in Linux DomUs by adding > xen_platform_pci = 0 to the configuration file. > > So FreeBSD 11.0 Dom0 can boot Linux guests and Windows Server (FreeBSD DomU > st

Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb)

Got it, thanks. I found a workaround to avoid XENBUS delay in Linux DomUs by adding xen_platform_pci = 0 to the configuration file. So FreeBSD 11.0 Dom0 can boot Linux guests and Windows Server (FreeBSD DomU still stuck on xenbusb_nop_confighook_cb) from QCOW2 images (also works with QCOW2 o

Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb)

Hi Alex and Roger, Without the patch and FreeBSD 12, qcow2 doesn't actually work. We were thinking of adding code to warn against this, but then thought gntdev implementation is in process anyway. With the patch, the crash needs to be investigated (because I did run one of the gntdev based image,

Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb)

On Tue, Jan 24, 2017 at 05:45:25PM +0300, Alexander Nusov wrote: > Yes, it was FreeBSD 11.0-STABLE Dom0 with xen-kernel/xen-tools built from the > ports tree (head) > > > > It seems there is an issue with xen pci devices, since booting from QCOW2 > images actually works (even on FreeBSD 11.0-R

Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb)

Yes, it was FreeBSD 11.0-STABLE Dom0 with xen-kernel/xen-tools built from the ports tree (head) It seems there is an issue with xen pci devices, since booting from QCOW2 images actually works (even on FreeBSD 11.0-RELEASE branch) except communication with /xen/vbd devices from the guest. By

Re: Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb)

On Mon, Jan 23, 2017 at 06:25:23PM +0300, Alexander Nusov wrote: > Hello, > Sorry for cross-posting, since it's related to Xen hypervisor I'm forwarding > this message to the freebsd-xen mailing list. > > I'm trying to launch a HVM DomU guest from QCOW2 image by using PV driver on > FreeBSD 11 D

Xen on FreeBSD 11: Cannot boot from QCOW2 properly (waiting for XENBUS, xenbusb_nop_confighook_cb)

Hello, Sorry for cross-posting, since it's related to Xen hypervisor I'm forwarding this message to the freebsd-xen mailing list. I'm trying to launch a HVM DomU guest from QCOW2 image by using PV driver on FreeBSD 11 Dom0. The issue is that guest cannot connect to the device/vbd and requires to