Re: Booting Solaris 11.3 (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?)
On Thu, 5 May 2016, Roger Pau Monné wrote: > On Sat, Apr 30, 2016 at 08:56:54PM +, Marcin Cieslak wrote: > > > 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 > > 0x010178f000 > > Hello, > > I've been able to debug this and found the issue. I have two patches that > should be applied to FreeBSD in order to fix it, they can be found at: > > https://people.freebsd.org/~royger/privcmd_fixes/ > > Could you please give them a try? > I have however been unable to boot a Solaris 11.3 guest under PV mode, but > at least the host is not crashing anymore :). Thanks, I can confirm that the patches fix the crash for me. The half-life of PV Solaris is still under the microsecond. Btw. I have managed to get gdbsx going by replacing "/proc/xen/privcmd" with "/dev/xen/privcmd". Indeed, the state of Solaris is pretty bad: - Solaris 11.3 under HVM boots, but the installer complains there are no local disks (which is not true, even device nodes are there under /dev/dsk/ ... ) - OpenIndiana (OI-hipster-text-20160421.iso as HVM) hangs after printing out the kernel version message - SmartOS (smartos-20160428T170316Z.iso) seems to work at first, but after the initial configuration it cannot bring the network interface up because its link state is unknown (tried model=e1000 and the default Realtek): [root@master0 ~]# dladm show-phys LINK MEDIASTATE SPEED DUPLEX DEVICE e1000g0 Ethernet unknown 0 half e1000g0 Marcin ___ 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"
[Bug 198344] [virtio] virtio-balloon does not work
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198344 --- Comment #8 from Vick Khera --- Created attachment 169998 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=169998&action=edit graph of memory usage of my VM I've been watching my 10.3 VM for a while now, and I finally found evidence that it did release some memory. The VM environment is Proxmox VE, which is basically a fancy pants GUI on top of Debian linux + KVM. The memory usage graph is attached. -- You are receiving this mail because: You are the assignee for the bug. ___ 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"
Re: Booting Solaris 11.3 (was Re: Booting r298488 as Xen Dom0 may break ZFS pool?)
On Sat, Apr 30, 2016 at 08:56:54PM +, Marcin Cieslak wrote:
> On Fri, 29 Apr 2016, Roger Pau Monné wrote:
>
> > On Thu, Apr 28, 2016 at 08:01:23PM +, Marcin Cieslak wrote:
> > > On Tue, 26 Apr 2016, Roger Pau Monné wrote:
> > >
> > > > On Tue, Apr 26, 2016 at 10:39:06AM +, 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
> 0x010178f000
Hello,
I've been able to debug this and found the issue. I have two patches that
should be applied to FreeBSD in order to fix it, they can be found at:
https://people.freebsd.org/~royger/privcmd_fixes/
Could you please give them a try?
I have however been unable to boot a Solaris 11.3 guest under PV mode, but
at least the host is not crashing anymore :).
Roger.
___
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"
