Re: -current host, 10.1 client loops

"please run fsck again" jungle. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.

Re: -current host, 10.1 client loops

0xc100feb0 rip[2] 0xc100feb0 rip[2] 0x0000c100feb0 rip[2] 0xc100feb2 Any ideas ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BS

Re: -current host, 10.1 client loops

r the weekend. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ fr

Re: -current host, 10.1 client loops

In message , Neel Natu writes: I tried a i386 -current guest, and it hung, both cores spinning during a buildworld. This should make it pretty easy for somebody else to reproduce. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956

Re: -current host, 10.1 client loops

that it's a >simple workaround it should be worth a try. That may have helped, at least I got all the way through a nanobsd build this time. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tah

Re: -current host, 10.1 client loops

>- try to reproduce with the ahci-hd device emulation instead of virtio-blk. That might make sense. The filesystems were mightily hosed afterwards. I'll try to give that a shot. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD comm

Re: -current host, 10.1 client loops

sked about this: Are there any special params needed to run a 10.1-R guest ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be expl

Re: -current host, 10.1 client loops

c 1 \ -t ${VMN} \ -d ${P}.root.dd \ -d ${P}.swap.dd \ -d ${P}.tami_install.dd \ -d ${P}.tami_git.dd \ vm${VMU} || true How do I tell that script to use ahci-hd ? -- Poul-Henning Kamp | UNIX since Zi

Re: -current host, 10.1 client loops

In message , Neel Natu writes: >Can you try to reproduce after setting 'vfs.unmapped_buf_allowed=0' at >the guest loader prompt? It hung in a buildworld over night with this set. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/

Re: -current host, 10.1 client loops

In message , =?UTF-8?Q?Olivier_Cochard=2D Labb=C3=A9?= writes: >You just need to replace virtio-blk by ahci-hd in the script, like: Crude :-) Ok, started it with two vcpus, will report later... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org |

Re: -current host, 10.1 client loops

t my builds done. So some kind of synchronization issue maybe ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained

-current host, 10.1 client loops

OS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 64/32 (20150818/tbfadt-649) Guest: 10.1-RELEASE i386 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute t

Re: New jail framework - the userland side

n is that we should try to share as much of the string-munging code between the nmount and jail implementations as possible. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to mal