* dom0_shadow=1
@ 2005-10-21 13:14 Gerd Knorr
2005-10-21 14:31 ` dom0_shadow=1 Gerd Knorr
0 siblings, 1 reply; 4+ messages in thread
From: Gerd Knorr @ 2005-10-21 13:14 UTC (permalink / raw)
To: xen-devel
[-- Attachment #1: Type: text/plain, Size: 95 bytes --]
Hi,
Trying to boot domain0 with dom0_shadow=1 fails ...
Is this supposed to work?
Gerd
[-- Attachment #2: shadow_nopae --]
[-- Type: text/plain, Size: 7806 bytes --]
Booting command-list
kernel (hd0,1)/boot/tftp/xen.gz mem=984m dom0_mem=950m com1=115200,8n1 dom0_sha
dow=1
[Multiboot-elf, <0x100000:0x6c1cc:0x27e34>, shtab=0x194078, entry=0x100000]
module (hd0,1)/boot/tftp/vmlinuz3 console=tty0 console=ttyS0 root=/dev/sda2 ro
selinux=0 sysrq=yes
[Multiboot-module @ 0x195000, 0x4e94a0 bytes]
module (hd0,1)/boot/tftp/initrd
[Multiboot-module @ 0x67f000, 0x25ee00 bytes]
__ __ _____ ___ _ _
\ \/ /___ _ __ |___ / / _ \ __| | _____ _____| |
\ // _ \ '_ \ |_ \| | | |__ / _` |/ _ \ \ / / _ \ |
/ \ __/ | | | ___) | |_| |__| (_| | __/\ V / __/ |
/_/\_\___|_| |_| |____(_)___/ \__,_|\___| \_/ \___|_|
http://www.cl.cam.ac.uk/netos/xen
University of Cambridge Computer Laboratory
Xen version 3.0-devel (kraxel@ber.suse.de) (gcc version 4.0.2 20050901 (prerelease) (SUSE Linux)) Fri Oct 21 14:54:55 CEST 2005
Latest ChangeSet: Wed Oct 19 12:53:00 2005 +0100 7425:7c951e3eb5ab
(XEN) Truncating memory map to 1007616kB
(XEN) Physical RAM map:
(XEN) 0000000000000000 - 000000000009fc00 (usable)
(XEN) 000000000009fc00 - 00000000000a0000 (reserved)
(XEN) 00000000000e6000 - 0000000000100000 (reserved)
(XEN) 0000000000100000 - 000000003d800000 (usable)
(XEN) System RAM: 983MB (1007228kB)
(XEN) Xen heap: 10MB (10640kB)
(XEN) PAE disabled.
(XEN) found SMP MP-table at 000ff780
(XEN) DMI 2.3 present.
(XEN) Using APIC driver default
(XEN) ACPI: RSDP (v000 ACPIAM ) @ 0x000f55c0
(XEN) ACPI: RSDT (v001 INTEL @ÃS¸¨š
(XEN) 0x20050420 MSFT 0x00000097) @ 0x3f630000
(XEN) ACPI: FADT (v002 INTEL @ÃS¸¨š
(XEN) 0x20050420 MSFT 0x00000097) @ 0x3f630200
(XEN) ACPI: MADT (v001 INTEL @ÃS¸¨š
(XEN) 0x20050420 MSFT 0x00000097) @ 0x3f630390
(XEN) ACPI: MCFG (v001 INTEL @ÃS¸¨š
(XEN) 0x20050420 MSFT 0x00000097) @ 0x3f630400
(XEN) ACPI: MSEG (v001 INTEL @ÃS¸¨š
(XEN) 0x20050420 MSFT 0x00000097) @ 0x3f630440
(XEN) ACPI: WDDT (v001 INTEL OEMWDDT 0x00000001 INTL 0x02002026) @ 0x3f6363c0
(XEN) ACPI: DSDT (v001 INTEL @ÃS¸¨š
(XEN) 0x00000001 INTL 0x02002026) @ 0x00000000
(XEN) ACPI: Local APIC address 0xfee00000
(XEN) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
(XEN) Processor #0 15:4 APIC version 20
(XEN) ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
(XEN) Processor #1 15:4 APIC version 20
(XEN) ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
(XEN) ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
(XEN) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
(XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
(XEN) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
(XEN) ACPI: IRQ0 used by override.
(XEN) ACPI: IRQ2 used by override.
(XEN) ACPI: IRQ9 used by override.
(XEN) Enabling APIC mode: Flat. Using 1 I/O APICs
(XEN) Using ACPI (MADT) for SMP configuration information
(XEN) Initializing CPU#0
(XEN) Detected 3793.052 MHz processor.
(XEN) Using scheduler: Simple EDF Scheduler (sedf)
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 2048K
(XEN) CPU: Physical Processor ID: 0
(XEN) VMXON is done
(XEN) CPU0: Intel Genuine Intel(R) CPU 3.80GHz stepping 06
(XEN) Booting processor 1/1 eip 90000
(XEN) Initializing CPU#1
(XEN) CPU: Trace cache: 12K uops, L1 D cache: 16K
(XEN) CPU: L2 cache: 2048K
(XEN) CPU: Physical Processor ID: 0
(XEN) VMXON is done
(XEN) CPU1: Intel Genuine Intel(R) CPU 3.80GHz stepping 06
(XEN) Total of 2 processors activated.
(XEN) ENABLING IO-APIC IRQs
(XEN) ..TIMER: vector=0x31 pin1=2 pin2=-1
(XEN) checking TSC synchronization across 2 CPUs: passed.
(XEN) Platform timer is 1.193MHz PIT
(XEN) Brought up 2 CPUs
(XEN) mtrr: v2.0 (20020519)
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Xen-ELF header found: 'GUEST_OS=linux,GUEST_VER=2.6,XEN_VER=3.0,VIRT_BASE=0xC0000000,PAE=no,LOADER=generic'
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN) Dom0 alloc.: 3c000000->3d000000 (239104 pages to be allocated)
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN) Loaded kernel: c0100000->c0627244
(XEN) Init. ramdisk: c0628000->c0886e00
(XEN) Phys-Mach map: c0887000->c0974800
(XEN) Start info: c0975000->c0976000
(XEN) Page tables: c0976000->c097a000
(XEN) Boot stack: c097a000->c097b000
(XEN) TOTAL: c0000000->c0c00000
(XEN) ENTRY ADDRESS: c0100000
(XEN) Initrd len 0x25ee00, start at 0xc0628000
(XEN) dom0: shadow enable
(XEN) audit1
(XEN) audit1 done
(XEN) audit2
(XEN) audit2 done
(XEN) Audit 0: [l1mfn=3c979, i=176] Illegal RW t=58000001 mfn=3c976
(XEN) Audit 0: [l1mfn=3c979, i=177] Illegal RW t=33000001 mfn=3c977
(XEN) Audit 0: [l1mfn=3c979, i=178] Illegal RW t=33010001 mfn=3c978
(XEN) Audit 0: [l1mfn=3c979, i=179] Illegal RW t=33020001 mfn=3c979
(XEN) Audit 0: [l1mfn=3c979, i=176] Illegal RW t=58000002 mfn=3c976
(XEN) Audit 0: [l1mfn=3c979, i=177] Illegal RW t=33000001 mfn=3c977
(XEN) Audit 0: [l1mfn=3c979, i=178] Illegal RW t=33010001 mfn=3c978
(XEN) Audit 0: [l1mfn=3c979, i=179] Illegal RW t=33020001 mfn=3c979
(XEN) audit3
(XEN) audit3 done
(XEN) dom0: shadow setup done
(XEN) Scrubbing Free RAM: ..........done.
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to Xen).
Linux version 2.6.12.5-xen0-hg7425 (kraxel@eskarina) (gcc version 4.0.2 20050901 (prerelease) (SUSE Linux)) #1 SMP Fri Oct 21 14:39:00 CEST 2005
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 000000003b600000 (usable)
118MB HIGHMEM available.
832MB LOWMEM available.
found SMP MP-table at 000ff780
DMI 2.3 present.
0x20050420 MSFT 0x00000097) @ 0x3f630000
0x20050420 MSFT 0x00000097) @ 0x3f630200
0x20050420 MSFT 0x00000097) @ 0x3f630390
0x20050420 MSFT 0x00000097) @ 0x3f630400
0x20050420 MSFT 0x00000097) @ 0x3f630440
0x00000001 INTL 0x02002026) @ 0x00000000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
ACPI: LAPIC_NMI (acpi_id[0x01] dfl dfl lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] dfl dfl lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23
ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
Enabling APIC mode: Flat. Using 1 I/O APICs
Using ACPI (MADT) for SMP configuration information
IRQ lockup detection disabled
Allocating PCI resources starting at 3d800000 (gap: 3d800000:c2800000)
Built 1 zonelists
Kernel command line: console=tty0 console=ttyS0 root=/dev/sda2 ro selinux=0 sysrq=yes
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 65536 bytes)
Xen reported: 3793.052 MHz processor.
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Software IO TLB disabled
vmalloc area: f4800000-fb7fe000, maxmem 34000000
Memory: 953888k/972800k available (3481k kernel code, 18276k reserved, 1126k data, 364k init, 120832k highmem)
Checking if this processor honours the WP bit even in supervisor mode... Ok.
Mount-cache hash table entries: 512
CPU: Trace cache: 12K uops, L1 D cache: 16K
CPU: L2 cache: 2048K
Enabling fast FPU save and restore... done.
Enabling unmasked SIMD FPU exception support... done.
Checking 'hlt' instruction... disabled
(XEN) DOM0: (file=mm.c, line=1467) Bad type (saw 33020002 != exp e0000000) for mfn 3c979 (pfn 979)
(XEN) DOM0: (file=mm.c, line=478) Error getting mfn 3c979 (pfn 979) from L1 entry 3c979063 for dom0
(XEN) DOM0: (file=mm.c, line=2944) ptwr: Could not re-validate l1 page
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: dom0_shadow=1
2005-10-21 13:14 dom0_shadow=1 Gerd Knorr
@ 2005-10-21 14:31 ` Gerd Knorr
0 siblings, 0 replies; 4+ messages in thread
From: Gerd Knorr @ 2005-10-21 14:31 UTC (permalink / raw)
To: xen-devel
Hi,
> Is this supposed to work?
Oh, and btw, trying to use the "new" shadow code for 32bit non-pae
doesn't even compile. Is nobody testing that? Wasn't the plan to use
the new code everythere some day? What is the status of that?
cheers,
Gerd
--- a/xen/arch/x86/Makefile Wed Oct 19 10:53:00 2005
+++ b/xen/arch/x86/Makefile Fri Oct 21 16:24:46 2005
@@ -23,7 +23,8 @@
ifneq ($(pae),n)
OBJS += shadow.o shadow_public.o # x86_32p: new code
else
- OBJS += shadow32.o # x86_32: old code
+ OBJS += shadow.o shadow_public.o # x86_32: new code
+# OBJS += shadow32.o # x86_32: old code
endif
endif
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: dom0_shadow=1
@ 2005-10-21 15:16 Nakajima, Jun
0 siblings, 0 replies; 4+ messages in thread
From: Nakajima, Jun @ 2005-10-21 15:16 UTC (permalink / raw)
To: Gerd Knorr, xen-devel
Gerd Knorr wrote:
> Hi,
>
>> Is this supposed to work?
>
> Oh, and btw, trying to use the "new" shadow code for 32bit non-pae
> doesn't even compile. Is nobody testing that? Wasn't the plan to use
> the new code everythere some day? What is the status of that?
Gerd, Hi
We've been working on shadow.c to get/restore log-dirty mode for PAE and
x86_64. It's basically start working, and doing more tests. The plan is
to support 3-level and 4-level in shadow.c for now (for 3.0), and merge
2-level to shadow.c.
>
> cheers,
>
> Gerd
>
> --- a/xen/arch/x86/Makefile Wed Oct 19 10:53:00 2005
> +++ b/xen/arch/x86/Makefile Fri Oct 21 16:24:46 2005
> @@ -23,7 +23,8 @@
> ifneq ($(pae),n)
> OBJS += shadow.o shadow_public.o # x86_32p: new code
> else
> - OBJS += shadow32.o # x86_32: old code
> + OBJS += shadow.o shadow_public.o # x86_32: new code
> +# OBJS += shadow32.o # x86_32: old code
> endif
> endif
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
Jun
---
Intel Open Source Technology Center
^ permalink raw reply [flat|nested] 4+ messages in thread
* RE: dom0_shadow=1
@ 2005-10-21 16:17 Ian Pratt
0 siblings, 0 replies; 4+ messages in thread
From: Ian Pratt @ 2005-10-21 16:17 UTC (permalink / raw)
To: Gerd Knorr, xen-devel
> > Is this supposed to work?
I wouldn't rely on dom0_shadow=1 working at any moment in time as its
used for development purposes rather than production. It's usually
pretty easy to fix.
> Oh, and btw, trying to use the "new" shadow code for 32bit
> non-pae doesn't even compile. Is nobody testing that?
> Wasn't the plan to use the new code everythere some day?
> What is the status of that?
Yep that's the plan. The Intel folks are currently adding guest ref
count log dirty mode to shadow.c, which may well fix it as a side
effect.
As soon as we have the same level of confidence in shadow.c that we do
in shadow32.c we'll switch over for 32b non-pae builds too.
Ian
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2005-10-21 16:17 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-10-21 13:14 dom0_shadow=1 Gerd Knorr
2005-10-21 14:31 ` dom0_shadow=1 Gerd Knorr
-- strict thread matches above, loose matches on Subject: below --
2005-10-21 15:16 dom0_shadow=1 Nakajima, Jun
2005-10-21 16:17 dom0_shadow=1 Ian Pratt
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.