search for: oem_table_id

...sources.ovirt.org/pub/ovirt-3.5-pre/ > [2] http://cbs.centos.org/repos/virt7-kvm-common-testing/x86_64/os/ Patch mjt-set-oem-in-rsdt-like-slic.diff with workaround not included into qemu-kvm-ev-2.1.2-23.el7_1.6.1.src.rpm Bug not in qemu, bug in windows - windows reject SLIC table if oem_id and oem_table_id from SLIC table and from RSDT table is different, and this windows bug prevent any virt-p2v migration of OEM windows from hardware node to VM inside CentOS/RHEL server, even with config <qemu:commandline> <qemu:arg value='-acpitable'/> <qemu:arg value='file=...

...emu:arg value='-acpitable'/> >> <qemu:arg value='file=/sys/firmware/acpi/tables/SLIC'/> >> </qemu:commandline> >> </domain> >> >> Winodws not working correctly in this case, because Windows requires, >> what oem_id and oem_table_id from SLIC must be also placed >> into oem_id and oem_table_id of RSDT. >> >> Debian version of qemu-kvm contains workaround for this windows bug, >> and using Debian - Windows VM will works fine. But CentOS packages >> does not contain such workaround, so qemu-kvm-ev n...

...#39;> ..... <qemu:commandline> <qemu:arg value='-acpitable'/> <qemu:arg value='file=/sys/firmware/acpi/tables/SLIC'/> </qemu:commandline> </domain> Winodws not working correctly in this case, because Windows requires, what oem_id and oem_table_id from SLIC must be also placed into oem_id and oem_table_id of RSDT. Debian version of qemu-kvm contains workaround for this windows bug, and using Debian - Windows VM will works fine. But CentOS packages does not contain such workaround, so qemu-kvm-ev now must be patched manually with each new re...

...ndline> > <qemu:arg value='-acpitable'/> > <qemu:arg value='file=/sys/firmware/acpi/tables/SLIC'/> > </qemu:commandline> > </domain> > > Winodws not working correctly in this case, because Windows requires, > what oem_id and oem_table_id from SLIC must be also placed > into oem_id and oem_table_id of RSDT. > > Debian version of qemu-kvm contains workaround for this windows bug, > and using Debian - Windows VM will works fine. But CentOS packages > does not contain such workaround, so qemu-kvm-ev now must be patched...

...table'/> >>> <qemu:arg value='file=/sys/firmware/acpi/tables/SLIC'/> >>> </qemu:commandline> >>> </domain> >>> >>> Winodws not working correctly in this case, because Windows requires, >>> what oem_id and oem_table_id from SLIC must be also placed >>> into oem_id and oem_table_id of RSDT. >>> >>> Debian version of qemu-kvm contains workaround for this windows bug, >>> and using Debian - Windows VM will works fine. But CentOS packages >>> does not contain such workarou...

Hello, All! Is it possible to use binary packages build from http://resources.ovirt.org/pub/ovirt-3.5/rpm/el7/SRPMS/qemu-kvm-ev-2.1.2-23.el7_1.3.1.src.rpm with plain CentOS 7.1 and use all other packages from CentOS (libvirt, virt-manager, etc) Is it have reasons, if I not use live migrations and qcow2 snapshots? (instead use zfs, zvols and zfs snapshots for VM disks online backups) Is using

...provide a special BIOS." From ''xl dmesg'': (XEN) AMD-Vi: Found MSI capability block at 0x54 (XEN) AMD-Vi: ACPI Table: (XEN) AMD-Vi: Signature IVRS (XEN) AMD-Vi: Length 0xd0 (XEN) AMD-Vi: Revision 0x1 (XEN) AMD-Vi: CheckSum 0x9b (XEN) AMD-Vi: OEM_Id AMD (XEN) AMD-Vi: OEM_Table_Id RD890S (XEN) AMD-Vi: OEM_Revision 0x202031 (XEN) AMD-Vi: Creator_Id AMD (XEN) AMD-Vi: Creator_Revision 0x0 (XEN) AMD-Vi: IVRS Block: type 0x10 flags 0x3e len 0xa0 id 0x2 (XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0x0 flags 0x0 (XEN) AMD-Vi: Dev_Id Range: 0x0 -> 0x2 (XEN) AMD-Vi: IVHD Devi...

...ature[4]; + /** Length of table, in bytes, including header */ + uint32_t length; + /** ACPI Specification minor version number */ + uint8_t revision; + /** To make sum of entire table == 0 */ + uint8_t checksum; + /** OEM identification */ + char oem_id[6]; + /** OEM table identification */ + char oem_table_id[8]; + /** OEM revision number */ + uint32_t oem_revision; + /** ASL compiler vendor ID */ + char asl_compiler_id[4]; + /** ASL compiler revision number */ + uint32_t asl_compiler_revision; +} __attribute__ (( packed )); + diff --git a/memdisk/memdisk.inc b/memdisk/memdisk.inc index a37218b..8be815c...

Hi! From other people posting to this list, I know that there has been a bug related to the issue described in Xen Security Advisory 36 that disables iommu for some AMD users like me. However, even when passing "iommu=no-amd-iommu-perdev-intremap" it still disables i/o virtualisatoin. Related Xen dmesg output: (XEN) IVHD Error: Invalid IO-APIC 0 (XEN) AMD-Vi: Error initialization

..."Bus #%d is %s\n", m->mpc_busid, name); -} - -static inline void mpc_oem_pci_bus(struct mpc_config_bus *m, - struct mpc_config_translation *translation) -{ -} - int mps_oem_check(struct mp_config_table *mpc, char *oem, char *productid); int acpi_madt_oem_check(char *oem_id, char *oem_table_id); --- 2011-03-09.orig/xen/include/asm-x86/mpspec.h +++ 2011-03-09/xen/include/asm-x86/mpspec.h @@ -5,25 +5,22 @@ #include <asm/mpspec_def.h> #include <mach_mpspec.h> -extern int mp_bus_id_to_type [MAX_MP_BUSSES]; -extern int mp_bus_id_to_node [MAX_MP_BUSSES]; -extern int mp_bus_id...

...play start a VNC server on display i386 target only: -win2k-hack use it when installing Windows 2000 to avoid a disk full bug -no-fd-bootchk disable boot signature checking for floppy disks -no-acpi disable ACPI -no-hpet disable HPET -acpitable [sig=str][,rev=n][,oem_id=str][,oem_table_id=str][,oem_rev=n][,asl_compiler_id=str][,asl_compiler_rev=n][,{data|file}=file1[:file2]...] ACPI table description -smbios file=binary load SMBIOS entry from binary file -smbios type=0[,vendor=str][,version=str][,date=str][,release=%d.%d] specify SMBIO...

Hi guys, I am new to QEMU-KVM, libvmi and libvirt stuff. Libvmi uses libvirt. I am trying to to run process-list example of libvmi and getting error as below. It seems that this error may be due to libvirt as it is not able to find domain. I seek your kind help on below error: spanhal1@seclab2:~/KVMModule/libvmi-0.10.1$ sudo ./examples/process-list ubuntu libvir: QEMU error : Domain not found:

...buses 00 - ff (XEN) PCI: Not using MCFG for segment 0000 bus 00-ff (XEN) AMD-Vi: Found MSI capability block at 0x54 (XEN) AMD-Vi: ACPI Table: (XEN) AMD-Vi: Signature IVRS (XEN) AMD-Vi: Length 0xc0 (XEN) AMD-Vi: Revision 0x1 (XEN) AMD-Vi: CheckSum 0x23 (XEN) AMD-Vi: OEM_Id AMD (XEN) AMD-Vi: OEM_Table_Id RD890S (XEN) AMD-Vi: OEM_Revision 0x202031 (XEN) AMD-Vi: Creator_Id AMD (XEN) AMD-Vi: Creator_Revision 0 (XEN) AMD-Vi: IVRS Block: type 0x10 flags 0x3e len 0x90 id 0x2 (XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0 flags 0 (XEN) AMD-Vi: Dev_Id Range: 0 -> 0x2 (XEN) AMD-Vi: IVHD Device Entry...

...buses 00 - ff (XEN) PCI: Not using MCFG for segment 0000 bus 00-ff (XEN) AMD-Vi: Found MSI capability block at 0x54 (XEN) AMD-Vi: ACPI Table: (XEN) AMD-Vi: Signature IVRS (XEN) AMD-Vi: Length 0xd0 (XEN) AMD-Vi: Revision 0x1 (XEN) AMD-Vi: CheckSum 0x40 (XEN) AMD-Vi: OEM_Id AMD (XEN) AMD-Vi: OEM_Table_Id RD890S (XEN) AMD-Vi: OEM_Revision 0x202031 (XEN) AMD-Vi: Creator_Id AMD (XEN) AMD-Vi: Creator_Revision 0 (XEN) AMD-Vi: IVRS Block: type 0x10 flags 0x3e len 0xa0 id 0x2 (XEN) AMD-Vi: IVHD Device Entry: type 0x3 id 0 flags 0 (XEN) AMD-Vi: Dev_Id Range: 0 -> 0x2 (XEN) AMD-Vi: IVHD Device Entry...

Hi Konrad, Today i tried linuses tree of today (last commit is 4c4d285ad5665bfbd983b95fde8d7a477d24a361). It boots dom0 fine, but it fails to start any domU with: "Error: Failed to query current memory allocation of dom0." With my previous 3.1.5 kernel everything is fine, nothing else changed in config in between. dmesg and xm dmesg attached -- Sander Dom0 shows: total