Hi. Package: xen-hypervisor-4.1-amd64 Starting guest VM, after package upgrade: xm create winxp Using config file "./winxp". Error: failed to assign device: maybe the platform doesn't support VT-d, or VT-d isn't enabled properly? If I set up VM properly after few months, but I remember, I met same error only after package upgrade. Pastebin logs, for check my errors: xm info http://pastebin.com/qGdKdVft dmesg http://pastebin.com/uLBTH1se IOMMU in BIOS: enable Virtualization in BIOS: enable grub kernel command line: root=UUID=2ecaab92-170f-4b51-a342-79c03fca0f3f ro iommu=1 iommu_inclusive_mapping=1 xen-pciback.passthrough=1 elevator=noop iommu=pt amd_iommu=fullflush xen-pciback.hide=(05:00.0)(05:00.1)(02:00.0) xen-pciback.hide=(05:00.1) xen-pciback.hide=(02:00.0) HW: gigabyte 970a-ds3, athlon-645 (guest VM already started successfully) Or, otherwise it is a package bug, or my settings? P.S. sorry for my english. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/pkg-xen-devel/attachments/20130705/9851d140/attachment.html>
On Fri, 2013-07-05 at 04:44 +0400, darkshvein l wrote:> Hi. > Package: xen-hypervisor-4.1-amd64 > Starting guest VM, after package upgrade: > xm create winxp > Using config file "./winxp". > Error: failed to assign device: maybe the platform doesn't support > VT-d, or VT-d isn't enabled properly? > > If I set up VM properly after few months, but I remember, I met same > error only after package upgrade. > Pastebin logs, for check my errors: > xm info > http://pastebin.com/qGdKdVft > dmesg > http://pastebin.com/uLBTH1seIf you check "xm dmesg" I expect you will find that VT-d has been disabled due to a security errata. If you accept the risks then the error message will tell you how to reenable it. Ian.
On Fri, 2013-07-05 at 18:33 +0400, darkshvein l wrote:> http://pastebin.com/UFDUpW7r > >XEN) IVHD Error: Conflicting IO-APIC 0x8 entriesThis rings a bell, although I don't recall the specifics. I suggest you google for it. It's probably also worth ensuring you have the very latest firmware (BIOS) for your system, since ISTR it involves the BIOS provided tables being invalid. If all that doesn't work then I suggest trying the upstream xen-users@ list. Ian.> (XEN) AMD-Vi: Error initialization > (XEN) I/O virtualisation disabled > > > > 2013/7/5 Ian Campbell <ijc at hellion.org.uk> > On Fri, 2013-07-05 at 04:44 +0400, darkshvein l wrote: > > Hi. > > Package: xen-hypervisor-4.1-amd64 > > Starting guest VM, after package upgrade: > > xm create winxp > > Using config file "./winxp". > > Error: failed to assign device: maybe the platform doesn't > support > > VT-d, or VT-d isn't enabled properly? > > > > If I set up VM properly after few months, but I remember, I > met same > > error only after package upgrade. > > Pastebin logs, for check my errors: > > xm info > > http://pastebin.com/qGdKdVft > > dmesg > > http://pastebin.com/uLBTH1se > > > If you check "xm dmesg" I expect you will find that VT-d has > been > disabled due to a security errata. If you accept the risks > then the > error message will tell you how to reenable it. > > Ian. > > > > >