search for: allow_unsaf

...nstallation does not appear to have been successful. Digging a little deeper, I saw in xm dmesg: (XEN) Xen does not allow DomU creation on this CPU for security reasons. And also the hint: (XEN) *** Xen will not allow creation of DomU-s on this CPU for security reasons. *** (XEN) *** Pass "allow_unsafe" if you\047re trusting all your (PV) guest kernels. *** So, I added allow_unsafe to my kernel parameters and rebooted: [root@dom0-a ~]# cat /proc/cmdline placeholder root=/dev/mapper/vg_dom0--a-lv_root ro rd.md=0 rd.dm=0 SYSFONT=True rd.lvm.lv=vg_dom0-a/lv_root KEYTABLE=uk rd.luks=0 rd.lvm....

Hi, I've also recently hit this bug und it should be fixed by [1], also see the original analysis at [2]. Passing "allow_unsafe" as a Hypervisor option circumvents the crash. A serial boot log is attached. [1]: http://lists.xen.org/archives/html/xen-devel/2012-10/msg01856.html [2]: http://lists.xen.org/archives/html/xen-devel/2012-10/msg01396.html Regards, Christian -------------- next part -------------- An embedd...

The iommu is enabled by default when xen is booting and later disabled in iommu_setup() when no iommu is present. But under some circumstances iommu code can be called before iommu_setup() is processed. If there is no iommu available xen crashes. This can happen for example when panic(...) is called as introduced with the patch "x86-64: detect processors subject to AMD erratum #121 and

Good day - This is my first post to this list , and I''m new to Xen - any help on this issue would be much appreciated . I downloaded, built and installed xen-4.2.1 (hypervisor and tools) on an x86_64 ArchLinux box updated to latest software as of today. I am trying to bring up a Linux guest from a remote iSCSI disk. The iSCSI-initiator (open-iscsi) logs in to the remote target OK and