On Fri, 29 Apr 2016, Roger Pau Monné wrote: > On Thu, Apr 28, 2016 at 08:01:23PM +0000, Marcin Cieslak wrote: > > On Tue, 26 Apr 2016, Roger Pau Monné wrote: > > > > > On Tue, Apr 26, 2016 at 10:39:06AM +0000, Marcin Cieslak wrote: > > > > By the way, I just managed to crash a whole machine by trying to > > > > boot Solaris 11.3: > > > > > > > > # builder = "hvm" > > > > memory = 2048 > > > > vcpus = 1 > > > > name = "Solaris0" > > > > disk = [ 'file:/root/sol-11_3-text-x86.iso,6:cdrom,r', > > > > '/dev/zvol/zroot/solaris0,raw,hda,w' ] > > > > kernel = "/root/xen/solaris/unix" > > > > ramdisk = "/root/xen/solaris/boot_archive" > > > > extra = "/platform/i86xpv/kernel/amd64/unix -B > > > > console=ttya,livemode=text" > > > > #boot = "c" > > > > usbdevice = 'tablet' > > > > vnc = 1 > > > > vnclisten = '0.0.0.0' > > > > vif = [ 'bridge=bridge0' ] > > > > > > > > /root/xen/solaris/unix and /root/xen/solaris/boot_archive where > > > > extracted from sol-11_3-text-x86.iso > > > > ("Intel text-only image"). > > > > > > I don't think you can boot Solaris as a PV guest anymore, you should > > > instead > > > boot it as a HVM guest. You will have to remove the kernel and ramdisk > > > options and instead add builder="hvm" (that you have left commented out). > > > > However supported or not, I think it should not crash a whole host > > system?... > > Certainly. I assumed that you meant it crashed the VM, not the whole host. > Can you please provide the trace of the crash?
Apologies, forgot to let Xen keep VGA: http://marcincieslak.com/tmp/xencrash.png Manual OCR: FreeBSD/amd64 (o.saper.info) (xc0) login: (XEN) vmx.c:2464:d0v0 EPT violation 0x182 (-w-/---), gpa 0x0000010178f000 (XEN) p2m-ept.c:916:d0v0 Walking EPT tables for domain 0 gfn 10178f (XEN) p2m-ept.c:922:d0v0 gfn exceeds max_mapped_pfn 10178e (XEN) vmx.c:2469:d0v0 --- GLA 0x809f18000 (XEN) domain_crash called from vmx.c:2471 (XEN) Domain 0 (vcpu#0) crashed on cpu#0: (XEN) ----[ Xen-4.5.2 x86_64 debug=n Not tainted ]---- (XEN) CPU: 0 (XEN) RIP: 0043:[<000000080147bb94)] (XEN) RFLAGS: 0000000000010206 CONTEXT: hvm guest (d0v0) (XEN) rax: 0000000000000000 rbx: 0000000010f18000 rcx: 0000000002000000 (XEN) rdx: 0000000000000000 rsi: 0000000000000000 rdi: 0000000809f18000 (XEN) rbp: 00007fffffffe100 rsi: 00007fffffffe0a8 r8: 0000000010f18000 (XEN) r9: 00007fffffffdfc0 r10: 000000080170058e r11: 0000000809000000 (XEN) r12: 000000080286a2d8 r13: 0000000000010f18 r14: 0000000801700a3b (XEN) r15: 000000080286a000 cr0: 0000000080050033 cr4: 00000000000406e0 (XEN) cr3: 000000000fa21000 cr2: 0000000809f18000 (XEN) ds: 003b es: 003b fs: 0013 gs: 001b ss: 003b cs: 0043 (XEN) Guest stack trace from rsp=00007fffffffe0a8: (XEN) Fault while accessing guest memory. (XEN) Domain 0 crashed: 'noreboot' set - not rebooting. _______________________________________________ freebsd-virtualization@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization To unsubscribe, send any mail to "freebsd-virtualization-unsubscr...@freebsd.org"