Re: cannot install FreeBSD 12.0 Xen 4.12.1 on Intel Core i7 CPU 930

2019-10-15 Thread Marcin Cieslak

On Wed, 16 Oct 2019, Stefan Parvu wrote:



Does it happen in Xen or in FreeBSD dom0 kernel?


Xen. Here:
http://www.kronometrix.org/bugs/freebsd_xen.jpg


I have Xeon E3-1234 but I run 11.2-STABLE with xen-kernel-4.7.2_9 for a very 
long time already.
I also have:

hw.pci.mcfg=0
machdep.hyperthreading_allowed=0


Should I add these to sysctl.conf ? I will try tomorrow. To me it looks 
whatever I try I cannot
get IOMMU on this hdw with FreeBSD 12 and Xen 4.12.1. I havent tried another 
FreeBSD version.


No idea, just showing what I have. Maybe totally not relevant to what you are 
having -
I am going to try 12 and Xen 4.12.1 soon.

I also don't have "iommu=required,force" in my Xen commandline:

"dom0_mem=4096M dom0_max_vcpus=1 dom0pvh=1 com1=115200,8n1 guest_loglvl=all 
loglvl=all vga=text-80x43,keep console=vga"

smime.p7s
Description: S/MIME Cryptographic Signature


Re: cannot install FreeBSD 12.0 Xen 4.12.1 on Intel Core i7 CPU 930

2019-10-15 Thread Stefan Parvu
> 
> Does it happen in Xen or in FreeBSD dom0 kernel?

Xen. Here:
http://www.kronometrix.org/bugs/freebsd_xen.jpg

> I have Xeon E3-1234 but I run 11.2-STABLE with xen-kernel-4.7.2_9 for a very 
> long time already.
> I also have:
> 
> hw.pci.mcfg=0
> machdep.hyperthreading_allowed=0

Should I add these to sysctl.conf ? I will try tomorrow. To me it looks 
whatever I try I cannot
get IOMMU on this hdw with FreeBSD 12 and Xen 4.12.1. I havent tried another 
FreeBSD version.

Previously this box was running Ubuntu 16.x and KVM with no problems.

Stefan
___
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: cannot install FreeBSD 12.0 Xen 4.12.1 on Intel Core i7 CPU 930

2019-10-15 Thread Marcin Cieslak

On Wed, 16 Oct 2019, Stefan Parvu wrote:


Hi,

I have a bit of problem, cannot install FreeBSD/Xen on a bit older hardware. 
The hardware
should support the minimal VT-D/IOMMU settings, required by Xen.

CPU: Intel(R) Core(TM) i7 CPU 930  @ 2.80GHz (2806.42-MHz K8-class CPU)
 Origin="GenuineIntel"  Id=0x106a5  Family=0x6  Model=0x1a  Stepping=5
 
Features=0xbfebfbff
 
Features2=0x98e3bd
 AMD Features=0x28100800
 AMD Features2=0x1
 VT-x: PAT,HLT,MTF,PAUSE,EPT,VPID
 TSC: P-state invariant, performance statistics

I get always a panic on CPU0 followed by a reboot. My /boot/loader.conf was set 
as:

xen_cmdline="dom0_mem=2048M dom0_max_vcpus=4 dom0=pvh console=com1,vga 
com1=115200,8n1 guest_loglvl=all loglvl=all iommu=debug,force”


Does it happen in Xen or in FreeBSD dom0 kernel?

I have Xeon E3-1234 but I run 11.2-STABLE with xen-kernel-4.7.2_9 for a very 
long time already.
I also have:

hw.pci.mcfg=0
machdep.hyperthreading_allowed=0

Marcin

smime.p7s
Description: S/MIME Cryptographic Signature


cannot install FreeBSD 12.0 Xen 4.12.1 on Intel Core i7 CPU 930

2019-10-15 Thread Stefan Parvu
Hi,

I have a bit of problem, cannot install FreeBSD/Xen on a bit older hardware. 
The hardware 
should support the minimal VT-D/IOMMU settings, required by Xen.

CPU: Intel(R) Core(TM) i7 CPU 930  @ 2.80GHz (2806.42-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x106a5  Family=0x6  Model=0x1a  Stepping=5
  
Features=0xbfebfbff
  
Features2=0x98e3bd
  AMD Features=0x28100800
  AMD Features2=0x1
  VT-x: PAT,HLT,MTF,PAUSE,EPT,VPID
  TSC: P-state invariant, performance statistics

I get always a panic on CPU0 followed by a reboot. My /boot/loader.conf was set 
as:

xen_cmdline="dom0_mem=2048M dom0_max_vcpus=4 dom0=pvh console=com1,vga 
com1=115200,8n1 guest_loglvl=all loglvl=all iommu=debug,force”

Any ideas what I could try ?

Thank you






Stefan Parvu
spa...@kronometrix.org



___
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: i/o is very slow on FreeBSD dom0 with Xen-4.12 and Freebsd-12

2019-10-15 Thread Brian Buhrow
hello Roger.  Sorry, my bad.  I didn't even look at the cause of the
panic.   Rebooting the system caused it to come up clean after another pass
with fsck.  With the ioapic_ack=old argument, the system comes up right
away and is quite responsive.
Can you explain how to select which argument to use on the command
line if the autoselection code doesn't work?

Thank you for your help!

-Brian

On Oct 15, 10:26am, Roger Pau =?iso-8859-1?Q?Monn=E9?= wrote:
} Subject: Re: i/o is very slow on FreeBSD dom0 with Xen-4.12 and Freebsd-12
} On Mon, Oct 14, 2019 at 02:45:04PM -0700, Brian Buhrow wrote:
} > hello.  Using: ioapic_ack=old causes the dom0 to crash.  Below are the
} > logs.
} 
} Does the crash happen every time you boot with ioapic_ack=old?
} 
} [...]
} > dev = gpt/gptroot, block = 1, fs = /
} > panic: ffs_blkfree_cg: freeing free block
} > cpuid = 2
} > time = 1571088217
} > KDB: stack backtrace:
___
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: i/o is very slow on FreeBSD dom0 with Xen-4.12 and Freebsd-12

2019-10-15 Thread Roger Pau Monné
On Mon, Oct 14, 2019 at 02:45:04PM -0700, Brian Buhrow wrote:
>   hello.  Using: ioapic_ack=old causes the dom0 to crash.  Below are the
> logs.

Does the crash happen every time you boot with ioapic_ack=old?

[...]
> dev = gpt/gptroot, block = 1, fs = /
> panic: ffs_blkfree_cg: freeing free block
> cpuid = 2
> time = 1571088217
> KDB: stack backtrace:
> #0 0x80be78d7 at kdb_backtrace+0x67
> #1 0x80b9b4b3 at vpanic+0x1a3
> #2 0x80b9b303 at panic+0x43
> #3 0x80e87345 at ffs_blkrelease_finish+0x6e5
> #4 0x80e8433d at ffs_blkfree+0xad
> #5 0x80eb10af at softdep_get_depcounts+0x48bf
> #6 0x80eb0fe5 at softdep_get_depcounts+0x47f5
> #7 0x80ea195a at softdep_update_inodeblock+0x178a
> #8 0x80eab94a at softdep_request_cleanup+0xa8a
> #9 0x80e95272 at softdep_flushworklist+0x1a2
> #10 0x80e991df at softdep_unmount+0x4af
> #11 0x80b5be83 at fork_exit+0x83
> #12 0x8105061e at fork_trampoline+0xe
> Uptime: 1m59s
> Automatic reboot in 15 seconds - press a key on the console to abort

This looks like a file system error, likely some corruption caused by
previous reboots?

Ie: I'm not sure this is caused by Xen or rather by underlying errors
in the filesystem. At least there are no hardware errors on the log
AFAICT.

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"