search for: mtrrs

...rt=c100 f_mport=9000 np=100 (XEN) HVM4: pci dev 05:0 bar 10 size 00000100: 0000c201 (XEN) domctl.c:1041:d0 ioport_map:add f_gport=c200 f_mport=d000 np=100 (XEN) HVM4: pci dev 01:1 bar 20 size 00000010: 0000c301 (XEN) HVM4: Multiprocessor initialisation: (XEN) HVM4: - CPU0 ... 40-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done. (XEN) HVM4: - CPU1 ... 40-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done. (XEN) HVM4: - CPU2 ... 40-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done. (XEN) HVM4: - CPU3 ... 40-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done. (XEN) HVM4: - CPU4 ......

...000000100: 00000c001 (d6) pci dev 04:0 bar 10 size 000000100: 00000c101 (d6) pci dev 04:0 bar 14 size 000000100: 0f3051000 (d6) pci dev 01:2 bar 20 size 000000020: 00000c201 (d6) pci dev 01:1 bar 20 size 000000010: 00000c221 (d6) Multiprocessor initialisation: (d6) - CPU0 ... 39-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done. (d6) - CPU1 ... 39-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... done. (d6) Writing SMBIOS tables ... (d6) Loading SeaBIOS ... (d6) Creating MP tables ... (d6) Loading ACPI ... (d6) vm86 TSS at fc00a180 (d6) BIOS map: (d6) 10000-100e3: Scratch space (d6) c0000-fff...

...gistered new driver hci_usb md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. NET: Registered protocol family 10 Disabled Privacy Extensions on device ffffffff80451480(lo) IPv6 over IPv4 tunneling driver divert: not allocating divert_blk for non-ethernet device sit0 mtrr: no more MTRRs available mtrr: no more MTRRs available mtrr: no more MTRRs available mtrr: no more MTRRs available EXT3 FS on hda2, internal journal device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel at redhat.com cdrom: open failed. kjournald starting. Commit interval 5 seconds EXT3 FS on hda4, inter...

...) pci dev 04:0 bar 10 size 000000100: 00000c101 > (d6) pci dev 04:0 bar 14 size 000000100: 0f3051000 > (d6) pci dev 01:2 bar 20 size 000000020: 00000c201 > (d6) pci dev 01:1 bar 20 size 000000010: 00000c221 > (d6) Multiprocessor initialisation: > (d6) - CPU0 ... 39-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... > done. > (d6) - CPU1 ... 39-bit phys ... fixed MTRRs ... var MTRRs [1/8] ... > done. > (d6) Writing SMBIOS tables ... > (d6) Loading SeaBIOS ... > (d6) Creating MP tables ... > (d6) Loading ACPI ... > (d6) vm86 TSS at fc00a180 > (d6) BIOS map: &...

...s, we run into an issue launching an HVM. As soon as the HVM bios is loaded, VCPU0 gets a triple fault and the HVM is destroyed (this is with "loglvl=all guest_loglvl=all hvm_debug=3" boot options). (XEN) HVM1: Multiprocessor initialisation: (XEN) HVM1: - CPU0 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done. (XEN) HVM1: Writing SMBIOS tables ... (XEN) HVM1: Loading SeaBIOS ... (XEN) hvm.c:1253:d1 Triple fault on VCPU0 - invoking HVM shutdown action 1. If I just replace the "hvmloader" with the one from the Debian archive xen-utils-4.3 package, things begin to wo...

...01 (XEN) [2013-07-17 19:10:12] HVM17: pci dev 01:2 bar 20 size 000000020: 00000c141 (XEN) [2013-07-17 19:10:12] HVM17: pci dev 01:1 bar 20 size 000000010: 00000c161 (XEN) [2013-07-17 19:10:12] HVM17: Multiprocessor initialisation: (XEN) [2013-07-17 19:10:12] HVM17: - CPU0 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done. (XEN) [2013-07-17 19:10:12] HVM17: - CPU1 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done. (XEN) [2013-07-17 19:10:12] HVM17: - CPU2 ... 48-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done. (XEN) [2013-07-17 19:10:12] HVM17: Testing HVM environment:...

...1000 (XEN) HVM18: pci dev 03:0 bar 10 size lx: 00000100 (XEN) HVM18: pci dev 04:0 bar 10 size lx: 00000100 (XEN) HVM18: pci dev 04:0 bar 14 size lx: 00000100 (XEN) HVM18: pci dev 01:1 bar 20 size lx: 00000010 (XEN) HVM18: Multiprocessor initialisation: (XEN) HVM18: - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done. (XEN) HVM18: - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done. (XEN) HVM18: Testing HVM environment: (XEN) HVM18: - REP INSB across page boundaries ... passed (XEN) HVM18: - GS base MSRs and SWAPGS ... passed (XEN) HVM18: Passed 2 of 2 tests (XEN)...

...s, we run into an issue launching an HVM. As soon as the HVM bios is loaded, VCPU0 gets a triple fault and the HVM is destroyed (this is with "loglvl=all guest_loglvl=all hvm_debug=3" boot options). (XEN) HVM1: Multiprocessor initialisation: (XEN) HVM1: - CPU0 ... 46-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done. (XEN) HVM1: Writing SMBIOS tables ... (XEN) HVM1: Loading SeaBIOS ... (XEN) hvm.c:1253:d1 Triple fault on VCPU0 - invoking HVM shutdown action 1. If I just replace the "hvmloader" with the one from the Debian archive xen-utils-4.3 package, things begin to wo...

...v 04:0 bar 10 size 00000100: 0000c101 (XEN) HVM14: pci dev 04:0 bar 14 size 00000100: f3001000 (XEN) HVM14: pci dev 01:2 bar 20 size 00000020: 0000c201 (XEN) HVM14: pci dev 01:1 bar 20 size 00000010: 0000c221 (XEN) HVM14: Multiprocessor initialisation: (XEN) HVM14: - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done. (XEN) HVM14: Testing HVM environment: (XEN) HVM14: - REP INSB across page boundaries ... passed (XEN) HVM14: - GS base MSRs and SWAPGS ... passed (XEN) HVM14: Passed 2 of 2 tests (XEN) HVM14: Writing SMBIOS tables ... (XEN) HVM14: Loading ROMBIOS ... (XEN) HVM14: 12...

On Sun, Jun 03, 2012 at 05:31:32PM +1000, aorchis@gmail.com wrote: > Hi Jeremy and Konrad, CC-ing xen-devel. > > Basically the driver NVIDIA provided is a binary blob and recent > versions does not work with the PAT layout of XEN so it falls back to > MTRR to provide write combining (please correct me if I''m wrong). OK? Which is still OK. Are you using a v3.4 kernel

...45] (--) fglrx(0): MMIO registers at 0xf0200000 [ 36.245] (--) fglrx(0): I/O port at 0x00004000 [ 36.245] (==) fglrx(0): ROM-BIOS at 0x000c0000 [ 36.267] (II) fglrx(0): ATIF platform detected [ 36.268] (II) fglrx(0): AC Adapter is used [ 36.375] (WW) System lacks support for changing MTRRs [ 36.377] (EE) fglrx(0): V_BIOS address 0x575a0 out of range [ 36.377] (II) fglrx(0): Invalid ATI BIOS from int10, the adapter is not VGA-enabled [ 36.377] *(EE) fglrx(0): Invalid video BIOS signature!* [ 36.378] (EE) fglrx(0): GetBIOSParameter failed [ 36.378] (EE) fglrx(0): PreInit...

...i dev 03:0 bar 10 size lx: 00000100 (XEN) HVM18: pci dev 04:0 bar 10 size lx: 00000100 (XEN) HVM18: pci dev 04:0 bar 14 size lx: 00000100 (XEN) HVM18: pci dev 01:1 bar 20 size lx: 00000010 (XEN) HVM18: Multiprocessor initialisation: (XEN) HVM18: - CPU0 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done. (XEN) HVM18: - CPU1 ... 36-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done. (XEN) HVM18: Testing HVM environment: (XEN) HVM18: - REP INSB across page boundaries ... passed (XEN) HVM18: - GS base MSRs and SWAPGS ... passed (XEN) HVM18: Passe...

...45] (--) fglrx(0): MMIO registers at 0xf0200000 [ 36.245] (--) fglrx(0): I/O port at 0x00004000 [ 36.245] (==) fglrx(0): ROM-BIOS at 0x000c0000 [ 36.267] (II) fglrx(0): ATIF platform detected [ 36.268] (II) fglrx(0): AC Adapter is used [ 36.375] (WW) System lacks support for changing MTRRs [ 36.377] (EE) fglrx(0): V_BIOS address 0x575a0 out of range [ 36.377] (II) fglrx(0): Invalid ATI BIOS from int10, the adapter is not VGA-enabled [ 36.377] *(EE) fglrx(0): Invalid video BIOS signature!* [ 36.378] (EE) fglrx(0): GetBIOSParameter failed [ 36.378] (EE) fglrx(0): PreInit...

...ci dev 04:0 bar 10 size 00000100: 0000c101 (XEN) HVM1: pci dev 04:0 bar 14 size 00000100: f3009000 (XEN) HVM1: pci dev 01:2 bar 20 size 00000020: 0000c201 (XEN) HVM1: pci dev 01:1 bar 20 size 00000010: 0000c221 (XEN) HVM1: Multiprocessor initialisation: (XEN) HVM1:  - CPU0 ... 40-bit phys ... fixed MTRRs ... var MTRRs [2/8] ... done. (XEN) HVM1: Testing HVM environment: (XEN) HVM1:  - REP INSB across page boundaries ... passed (XEN) HVM1:  - GS base MSRs and SWAPGS ... passed (XEN) HVM1: Passed 2 of 2 tests (XEN) HVM1: Writing SMBIOS tables ... (XEN) HVM1: Loading ROMBIOS ... (XEN) HVM1: 9628 bytes...

...uncs = { > + .free = i915_gem_free_object, > + .close = i915_gem_close_object, > + .export = i915_gem_prime_export, > +}; > + Any reason not to make this static in i915_gem_object.c next to its only user? BR, Jani. > static struct drm_driver driver = { > /* Don't use MTRRs here; the Xserver or userspace app should > * deal with them for Intel hardware. > @@ -1853,12 +1859,8 @@ static struct drm_driver driver = { > .lastclose = i915_driver_lastclose, > .postclose = i915_driver_postclose, > > - .gem_close_object = i915_gem_close_object, >...

...Privacy Extensions [ 103.657521] Bluetooth: L2CAP ver 2.9 [ 103.657521] Bluetooth: L2CAP socket layer initialized [ 103.864517] Bluetooth: RFCOMM socket layer initialized [ 103.864592] Bluetooth: RFCOMM TTY layer initialized [ 103.864651] Bluetooth: RFCOMM ver 1.8 [ 105.339112] mtrr: no more MTRRs available [ 105.339233] mtrr: no more MTRRs available [ 105.339301] mtrr: no more MTRRs available [ 105.339366] mtrr: no more MTRRs available [ 105.339432] mtrr: no more MTRRs available [ 105.339498] mtrr: no more MTRRs available [ 105.339564] mtrr: no more MTRRs available [ 105.339629] mtrr...

...Privacy Extensions [ 103.657521] Bluetooth: L2CAP ver 2.9 [ 103.657521] Bluetooth: L2CAP socket layer initialized [ 103.864517] Bluetooth: RFCOMM socket layer initialized [ 103.864592] Bluetooth: RFCOMM TTY layer initialized [ 103.864651] Bluetooth: RFCOMM ver 1.8 [ 105.339112] mtrr: no more MTRRs available [ 105.339233] mtrr: no more MTRRs available [ 105.339301] mtrr: no more MTRRs available [ 105.339366] mtrr: no more MTRRs available [ 105.339432] mtrr: no more MTRRs available [ 105.339498] mtrr: no more MTRRs available [ 105.339564] mtrr: no more MTRRs available [ 105.339629] mtrr...

Hello all Xen devels, I''m writing howto''s in brazilian portuguese language about Xen-3.3.0 stubdom, pv-grub and others configurations. Following what is written in xen-3.3.0/stubdom/README, I tried start a HVM but without success. When I start the virtual machine calling ''xm create hvmtest'' command, in a few seconds the virtual machine is dead (see

On Mon, 5 Nov 2018 at 19:04, David Greene <dag at cray.com> wrote: > I guess it would be up to the people interested in a particular target > to figure out a reasonable, maintainable way to manage models for > possibly many subtargets. This proposal is about providing > infrastructure to allow models to be created with not too much effort. > It doesn't say anything about

We created a 64bit SLES11 SP1 guest, and then used a script to change memory (using mem-set command) periodically (in 1 second): set 1G, set 2G, set 1G, set 2G, and so on. After a few minutes, we encountered QEMU exit due to SIGBUS error. Below is the call trace captured by gdb: The call trace: Program received signal SIGBUS, Bus error. 0x00007f94f74773d7 in memcpy () from /lib64/libc.so.6 (gdb)