Hi, I''m trying to get Windows Server 2008 R2 installation booting on Xen 4.0.4. Using the following config: kernel = "/usr/lib/xen/boot/hvmloader" builder = "hvm" shadow_memory = "8" memory = "4096" name = "ts" vcpus = "8" cpus = ["0", "1", "2", "3", "4", "5", "6", "7"] pae = "1" acpi = "1" apic = "1" vfb = [ ''type=vnc, vnclisten=10.100.100.1, vncpasswd=xxxx'' ] xen_extended_power_mgmt = "0" vif = [ "type=ioemu, mac=00:16:3e:d7:d7:5d, bridge=xenbr0" ] disk = [ "phy:/dev/virtuals/ts,hda,w", "file:/media/iso/windows_server_2008_r2_sp1.iso,hdc:cdrom,r" ] on_poweroff = "destroy" on_reboot = "restart" on_crash = "restart" viridian = "1" device_model = "/usr/lib/xen/bin/qemu-dm" boot = "dc" snapshot = "0" vncconsole = "1" sdl = "0" opengl = "0" vnc = "1" nographic = "0" stdvga = "0" tsc_mode = "1" monitor = "0" localtime = "1" usb = "0" keymap = "fi" xen_platform_pci = "1" pci_msitranslate = "1" pci_power_mgmt = "0" The domU will start booting just fine, but after a few minutes the VNC screen goes black. After that when typing "xm destroy ts" it will trigger a kernel BUG: BUG: unable to handle kernel NULL pointer dereference at 0000000000000030 IP: [<ffffffff810c50c4>] iput+0x3e/0x195 PGD 0 Oops: 0000 [#1] SMP CPU 6 Pid: 3571, comm: qemu-dm Not tainted 3.5.0-dom0 #1 /DQ77MK RIP: e030:[<ffffffff810c50c4>] [<ffffffff810c50c4>] iput+0x3e/0x195 RSP: e02b:ffff8800389ffbf8 EFLAGS: 00010246 RAX: 0000000000000001 RBX: ffff8800377b0720 RCX: ffff8800501c0000 RDX: ffff8800501c0000 RSI: ffff8800377b0790 RDI: ffff8800377b0790 RBP: 0000000000000000 R08: ffffffff815cdd00 R09: 0000000000000016 R10: fefefefefefefeff R11: ffff8800377b0400 R12: 00000001000a3e0c R13: 0000000000000000 R14: 00000001000a3e0c R15: ffff8800389ffc28 FS: 00007f1af70a8700(0000) GS:ffff880050180000(0000) knlGS:0000000000000000 CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000000030 CR3: 000000000156d000 CR4: 0000000000002660 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process qemu-dm (pid: 3571, threadinfo ffff8800389fe000, task ffff88003a721260) Stack: ffff88003a6d6400 ffff8800377b0000 00000001000a3e0c ffffffff8133ce8f ffff8800377b0400 ffffffff8134b6cd ffff8800389ffc28 ffff8800389ffc28 ffff8800377b00f8 ffff8800377b0680 ffff880038cdcd60 ffff8800377b0000 Call Trace: [<ffffffff8133ce8f>] ? sk_release_kernel+0x23/0x39 [<ffffffff8134b6cd>] ? netdev_run_todo+0x1e9/0x206 [<ffffffff8129798f>] ? tun_chr_close+0x4c/0x7b [<ffffffff810b39d3>] ? fput+0xe4/0x1c5 [<ffffffff810b202c>] ? filp_close+0x61/0x68 [<ffffffff81035e62>] ? put_files_struct+0x62/0xb9 [<ffffffff81036374>] ? do_exit+0x24a/0x74c [<ffffffff81036906>] ? do_group_exit+0x6b/0x9d [<ffffffff8103ea0b>] ? get_signal_to_deliver+0x449/0x46e [<ffffffff81009fa5>] ? do_signal+0x28/0x4c4 [<ffffffff81027079>] ? pvclock_clocksource_read+0x48/0xbf [<ffffffff8105b745>] ? ktime_get_ts+0x66/0xa8 [<ffffffff810bfb18>] ? poll_select_copy_remaining+0xe0/0xf5 [<ffffffff8100a48d>] ? do_notify_resume+0x3b/0x74 [<ffffffff81411a70>] ? int_signal+0x12/0x17 Code: 00 00 00 40 74 02 0f 0b 48 8d 77 70 48 8d bf 08 01 00 00 e8 8b 71 10 00 85 c0 0f 84 5d 01 00 00 48 8b 6b 18 f6 83 80 00 00 00 08 <4c> 8b 65 30 74 11 be 68 05 00 00 48 c7 c7 8e df 4f 81 e8 bb d0 RIP [<ffffffff810c50c4>] iput+0x3e/0x195 RSP <ffff8800389ffbf8> CR2: 0000000000000030 ---[ end trace 67cc1654658fedcc ]--- Fixing recursive fault but reboot is needed! I also tested Xen 4.2.0 and problem is the same. So is this a Xen bug or a kernel bug? I am running vanilla kernel.org kernel 3.5.0 and my hardware is Intel Core i7-3770 CPU and Intel DQ77MK motherboard with latest bios. Best regards, Valtteri Kiviniemi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Pasi Kärkkäinen
2012-Oct-01 06:22 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
On Sun, Sep 30, 2012 at 11:18:03PM +0300, Valtteri Kiviniemi wrote:> Hi, >Hello,> I''m trying to get Windows Server 2008 R2 installation booting on Xen > 4.0.4. Using the following config: ><snip>> > The domU will start booting just fine, but after a few minutes the VNC > screen goes black. After that when typing "xm destroy ts" it will trigger > a kernel BUG: > > BUG: unable to handle kernel NULL pointer dereference at 0000000000000030 > IP: [<ffffffff810c50c4>] iput+0x3e/0x195 > PGD 0 > Oops: 0000 [#1] SMP > CPU 6 > Pid: 3571, comm: qemu-dm Not tainted 3.5.0-dom0 #1First of all upgrade to latest 3.5.x Linux kernel release .. so at least 3.5.4. -- Pasi> /DQ77MK > RIP: e030:[<ffffffff810c50c4>] [<ffffffff810c50c4>] iput+0x3e/0x195 > RSP: e02b:ffff8800389ffbf8 EFLAGS: 00010246 > RAX: 0000000000000001 RBX: ffff8800377b0720 RCX: ffff8800501c0000 > RDX: ffff8800501c0000 RSI: ffff8800377b0790 RDI: ffff8800377b0790 > RBP: 0000000000000000 R08: ffffffff815cdd00 R09: 0000000000000016 > R10: fefefefefefefeff R11: ffff8800377b0400 R12: 00000001000a3e0c > R13: 0000000000000000 R14: 00000001000a3e0c R15: ffff8800389ffc28 > FS: 00007f1af70a8700(0000) GS:ffff880050180000(0000) > knlGS:0000000000000000 > CS: e033 DS: 0000 ES: 0000 CR0: 000000008005003b > CR2: 0000000000000030 CR3: 000000000156d000 CR4: 0000000000002660 > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 > Process qemu-dm (pid: 3571, threadinfo ffff8800389fe000, task > ffff88003a721260) > Stack: > ffff88003a6d6400 ffff8800377b0000 00000001000a3e0c ffffffff8133ce8f > ffff8800377b0400 ffffffff8134b6cd ffff8800389ffc28 ffff8800389ffc28 > ffff8800377b00f8 ffff8800377b0680 ffff880038cdcd60 ffff8800377b0000 > Call Trace: > [<ffffffff8133ce8f>] ? sk_release_kernel+0x23/0x39 > [<ffffffff8134b6cd>] ? netdev_run_todo+0x1e9/0x206 > [<ffffffff8129798f>] ? tun_chr_close+0x4c/0x7b > [<ffffffff810b39d3>] ? fput+0xe4/0x1c5 > [<ffffffff810b202c>] ? filp_close+0x61/0x68 > [<ffffffff81035e62>] ? put_files_struct+0x62/0xb9 > [<ffffffff81036374>] ? do_exit+0x24a/0x74c > [<ffffffff81036906>] ? do_group_exit+0x6b/0x9d > [<ffffffff8103ea0b>] ? get_signal_to_deliver+0x449/0x46e > [<ffffffff81009fa5>] ? do_signal+0x28/0x4c4 > [<ffffffff81027079>] ? pvclock_clocksource_read+0x48/0xbf > [<ffffffff8105b745>] ? ktime_get_ts+0x66/0xa8 > [<ffffffff810bfb18>] ? poll_select_copy_remaining+0xe0/0xf5 > [<ffffffff8100a48d>] ? do_notify_resume+0x3b/0x74 > [<ffffffff81411a70>] ? int_signal+0x12/0x17 > Code: 00 00 00 40 74 02 0f 0b 48 8d 77 70 48 8d bf 08 01 00 00 e8 8b 71 10 > 00 85 c0 0f 84 5d 01 00 00 48 8b 6b 18 f6 83 80 00 00 00 08 <4c> 8b 65 30 > 74 11 be 68 05 00 00 48 c7 c7 8e df 4f 81 e8 bb d0 > RIP [<ffffffff810c50c4>] iput+0x3e/0x195 > RSP <ffff8800389ffbf8> > CR2: 0000000000000030 > ---[ end trace 67cc1654658fedcc ]--- > Fixing recursive fault but reboot is needed! > > I also tested Xen 4.2.0 and problem is the same. So is this a Xen bug or a > kernel bug? I am running vanilla [1]kernel.org kernel 3.5.0 and my > hardware is Intel Core i7-3770 CPU and Intel DQ77MK motherboard with > latest bios. > > Best regards, > Valtteri Kiviniemi > > References > > Visible links > 1. http://kernel.org/> _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel
Valtteri Kiviniemi
2012-Oct-02 12:11 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
Hi, Another update: I wanted to check that if a Linux HVM would boot with working VNC console, so I tried to launch a Debian Squeeze installer on HVM. It refused to start ant told me that vbd hotplug scripts were not working. After that failure even the Windows domU would not anymore start which was previously starting ok. The hotplug scripts also starts hanging on the processes. root 9401 0.1 0.1 17700 1640 ? S 15:05 0:00 /bin/bash /etc/xen/scripts/xen-hotplug-cleanup root 9441 0.1 0.1 17700 1644 ? S 15:05 0:00 /bin/bash /etc/xen/scripts/xen-hotplug-cleanup root 9481 0.1 0.1 17700 1640 ? S 15:05 0:00 /bin/bash /etc/xen/scripts/xen-hotplug-cleanup root 9560 0.1 0.1 17700 1640 ? S 15:05 0:00 /bin/bash /etc/xen/scripts/xen-hotplug-cleanup root 10738 0.1 0.1 17696 1636 ? S 15:05 0:00 /bin/bash /etc/xen/scripts/xen-hotplug-cleanup root 10747 0.1 0.1 17792 1736 ? S 15:05 0:00 /bin/bash /etc/xen/scripts/block remove root 11286 0.0 0.0 4080 324 ? S 15:06 0:00 sleep 1 root 11290 0.0 0.0 4080 324 ? S 15:06 0:00 sleep 1 root 11294 0.0 0.0 4080 324 ? S 15:06 0:00 sleep 1 root 11298 0.0 0.0 4080 324 ? S 15:06 0:00 sleep 1 root 11302 0.0 0.0 4080 320 ? S 15:06 0:00 sleep 1 root 11306 0.0 0.0 4080 320 ? S 15:06 0:00 sleep 1 Then I did a xm destroy and I had again the kernel BUG on dmesg. So it seems that the problem is not fixed by using 3.6.0. Udev version is 175-7. 2012/10/1 Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com>> Hi, > > CPU: Intel Core i7-3770 3.4GHz > http://ark.intel.com/products/65719/ > > MB: Intel DQ77MK (latest bios updated) > > http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > > Memory: 32GB (4 x 8GB DDR3-1600MHz) > > Host is Debian wheezy/testing, Xen 4.0.4 and latest 3.6.0 kernel. > > Noticed also some errors in xm dmesg: > > root@xen-2:~# xm dmesg > > (XEN) Xen version 4.0.4 (root@dataproof.fi) (gcc version 4.7.1 (Debian > 4.7.1-7) ) Sun Sep 30 20:28:26 EEST 2012 > (XEN) Latest ChangeSet: unavailable > (XEN) Bootloader: GNU GRUB 0.97 > (XEN) Command line: dom0_mem=1280M cpufreq=xen clocksource=hpet > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds > (XEN) EDID info not retrieved because no DDC retrieval method detected > (XEN) Disc information: > (XEN) Found 4 MBR signatures > (XEN) Found 4 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 000000000009d800 (usable) > (XEN) 000000000009d800 - 00000000000a0000 (reserved) > (XEN) 00000000000e0000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 0000000020000000 (usable) > (XEN) 0000000020000000 - 0000000020200000 (reserved) > (XEN) 0000000020200000 - 0000000040004000 (usable) > (XEN) 0000000040004000 - 0000000040005000 (reserved) > (XEN) 0000000040005000 - 00000000dbe44000 (usable) > (XEN) 00000000dbe44000 - 00000000dc2d7000 (reserved) > (XEN) 00000000dc2d7000 - 00000000dc2e7000 (ACPI data) > (XEN) 00000000dc2e7000 - 00000000dc40c000 (ACPI NVS) > (XEN) 00000000dc40c000 - 00000000dc6af000 (reserved) > (XEN) 00000000dc6af000 - 00000000dc6b0000 (usable) > (XEN) 00000000dc6b0000 - 00000000dc6f3000 (ACPI NVS) > (XEN) 00000000dc6f3000 - 00000000dd000000 (usable) > (XEN) 00000000dd800000 - 00000000dfa00000 (reserved) > (XEN) 00000000f8000000 - 00000000fc000000 (reserved) > (XEN) 00000000fec00000 - 00000000fec01000 (reserved) > (XEN) 00000000fed00000 - 00000000fed04000 (reserved) > (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > (XEN) 00000000ff000000 - 0000000100000000 (reserved) > (XEN) 0000000100000000 - 000000081e600000 (usable) > (XEN) ACPI: RSDP 000F0490, 0024 (r2 INTEL) > (XEN) ACPI: XSDT DC2DB080, 007C (r1 INTEL DQ77MK 32 AMI 10013) > (XEN) ACPI: FACP DC2E51F0, 010C (r5 INTEL DQ77MK 32 AMI 10013) > (XEN) ACPI Warning (tbfadt-0232): FADT (revision 5) is longer than ACPI > 2.0 version, truncating length 0x10C to 0xF4 [20070126] > (XEN) ACPI: DSDT DC2DB188, A061 (r2 INTEL DQ77MK 32 INTL 20051117) > (XEN) ACPI: FACS DC40A080, 0040 > (XEN) ACPI: APIC DC2E5300, 0092 (r3 INTEL DQ77MK 32 AMI 10013) > (XEN) ACPI: FPDT DC2E5398, 0044 (r1 INTEL DQ77MK 32 AMI 10013) > (XEN) ACPI: TCPA DC2E53E0, 0032 (r2 INTEL DQ77MK 32 MSFT 1000013) > (XEN) ACPI: MCFG DC2E5418, 003C (r1 INTEL DQ77MK 32 MSFT 97) > (XEN) ACPI: HPET DC2E5458, 0038 (r1 INTEL DQ77MK 32 AMI. 5) > (XEN) ACPI: SSDT DC2E5490, 036D (r1 INTEL DQ77MK 32 INTL 20091112) > (XEN) ACPI: SSDT DC2E5800, 09AA (r1 INTEL DQ77MK 32 INTL 20051117) > (XEN) ACPI: SSDT DC2E61B0, 0A92 (r1 INTEL DQ77MK 32 INTL 20051117) > (XEN) ACPI: DMAR DC2E6C48, 00B8 (r1 INTEL DQ77MK 32 INTL 1) > (XEN) ACPI: ASF! DC2E6D00, 00A5 (r32 INTEL DQ77MK 32 TFSM > F4240) > (XEN) System RAM: 32682MB (33467320kB) > (XEN) Domain heap initialised > (XEN) ACPI: 32/64X FACS address mismatch in FADT - > dc40a080/0000000000000000, using 32 > (XEN) Processor #0 7:10 APIC version 21 > (XEN) Processor #2 7:10 APIC version 21 > (XEN) Processor #4 7:10 APIC version 21 > (XEN) Processor #6 7:10 APIC version 21 > (XEN) Processor #1 7:10 APIC version 21 > (XEN) Processor #3 7:10 APIC version 21 > (XEN) Processor #5 7:10 APIC version 21 > (XEN) Processor #7 7:10 APIC version 21 > (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) Switched to APIC driver x2apic_cluster. > (XEN) x2APIC mode enabled. > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Detected 3392.369 MHz processor. > (XEN) Initing memory sharing. > (XEN) VMX: Supported advanced features: > (XEN) - APIC MMIO access virtualisation > (XEN) - APIC TPR shadow > (XEN) - Extended Page Tables (EPT) > (XEN) - Virtual-Processor Identifiers (VPID) > (XEN) - Virtual NMI > (XEN) - MSR direct-access bitmap > (XEN) - Unrestricted Guest > (XEN) EPT supports 2MB super page. > (XEN) HVM: ASIDs enabled. > (XEN) HVM: VMX enabled > (XEN) HVM: Hardware Assisted Paging detected. > (XEN) Intel VT-d Snoop Control not enabled. > (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. > (XEN) Intel VT-d Queued Invalidation enabled. > (XEN) Intel VT-d Interrupt Remapping enabled. > (XEN) I/O virtualisation enabled > (XEN) - Dom0 mode: Relaxed > (XEN) Enabled directed EOI with ioapic_ack_old on! > (XEN) Total of 8 processors activated. > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using old ACK method > (XEN) TSC is reliable, synchronization unnecessary > (XEN) Platform timer appears to have unexpectedly wrapped 1 times. > (XEN) Platform timer is 14.318MHz HPET > (XEN) Allocated console ring of 16 KiB. > (XEN) Brought up 8 CPUs > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1ae7000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000000804000000->0000000806000000 (319488 pages to > be allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff81000000->ffffffff81ae7000 > (XEN) Init. ramdisk: ffffffff81ae7000->ffffffff81ae7000 > (XEN) Phys-Mach map: ffffffff81ae7000->ffffffff81d67000 > (XEN) Start info: ffffffff81d67000->ffffffff81d674b4 > (XEN) Page tables: ffffffff81d68000->ffffffff81d7b000 > (XEN) Boot stack: ffffffff81d7b000->ffffffff81d7c000 > (XEN) TOTAL: ffffffff80000000->ffffffff82000000 > (XEN) ENTRY ADDRESS: ffffffff815e3210 > (XEN) Dom0 has maximum 8 VCPUs > (XEN) [VT-D]iommu.c:718: BIOS did not enable IGD for VT properly. > Disabling IGD VT-d engine. > (XEN) Scrubbing Free RAM: done. > (XEN) Xen trace buffers: disabled > (XEN) Std. Loglevel: Errors and warnings > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) > (XEN) Xen is relinquishing VGA console. > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch input > to Xen) > (XEN) Freed 172kB init memory. > (XEN) traps.c:2333:d0 Domain attempted WRMSR 000000000000008b from > 00000012:00000000 to 00000000:00000000. > > - Valtteri > > > 2012/10/1 Pasi Kärkkäinen <pasik@iki.fi> > >> On Mon, Oct 01, 2012 at 09:12:50PM +0300, Valtteri Kiviniemi wrote: >> > Hi, >> > >> > Lowering memory or vcpu''s does not help, problem is the same. I >> originally >> > installed Xen 4.2.0 and the problem was same on that too. Then I >> > downgraded back to 4.0.4 since I thought that this might be a bug on >> > 4.2.0. I have been previously running Windows Server 2008 R2 >> succesfully >> > on Xen 4.0.x on different hardware with this same config. Hypervisor >> is >> > 64bit and windows is 64bit. >> > >> > Any ideas what to try next? >> > >> >> What kind of hardware is that? >> >> xen.org automated testing regularly tests Windows VMs, and it works OK >> there. >> >> -- Pasi >> >> > Ps. qemu-dm.log is the following: >> > >> > domid: 10 >> > config qemu network with xen bridge for tap10.0 xenbr0 >> > Using file /dev/virtuals/ts in read-write mode >> > Using file /media/iso/windows_server_2008_r2_sp1.iso in read-only >> mode >> > Watching /local/domain/0/device-model/10/logdirty/cmd >> > Watching /local/domain/0/device-model/10/command >> > qemu_map_cache_init nr_buckets = 10000 size 4194304 >> > shared page at pfn feffd >> > buffered io page at pfn feffb >> > Guest uuid = 52f19e23-2955-c27d-a22c-60c5d8c60d5a >> > Time offset set 0 >> > populating video RAM at ff000000 >> > mapping video RAM from ff000000 >> > Register xen platform. >> > Done register platform. >> > platform_fixed_ioport: changed ro/rw state of ROM memory area. now >> is rw >> > state. >> > xs_read(/local/domain/0/device-model/10/xen_extended_power_mgmt): >> read >> > error >> > medium change watch on `hdc'' (index: 1): >> > /media/iso/windows_server_2008_r2_sp1.iso >> > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 >> > Log-dirty: no command yet. >> > xs_read(/local/domain/10/log-throttling): read error >> > qemu: ignoring not-understood drive `/local/domain/10/log-throttling'' >> > medium change watch on `/local/domain/10/log-throttling'' - unknown >> device, >> > ignored >> > cirrus vga map change while on lfb mode >> > mapping vram to f0000000 - f0400000 >> > platform_fixed_ioport: changed ro/rw state of ROM memory area. now >> is rw >> > state. >> > platform_fixed_ioport: changed ro/rw state of ROM memory area. now >> is ro >> > state. >> > >> > 2012/10/1 Pasi Kärkkäinen <[1]pasik@iki.fi> >> > >> > On Mon, Oct 01, 2012 at 07:23:44PM +0300, Valtteri Kiviniemi wrote: >> > > Hi, >> > > >> > > I have tried other config files, but the problem is the same. >> At >> > the >> > > moment I''m using a config file from another server where I >> have a >> > working >> > > Windows Server 2008 R2 installation, so I dont think that >> there is >> > > anything wrong with my config: >> > > >> > >> > Did you try with less vcpus, for example 2 ? >> > how about with less memory, say 2 GB ? >> > >> > Did you try with later Xen versions? Is that a 32bit Xen, or 64bit >> Xen >> > hypervisor? >> > >> > -- Pasi >> > > kernel = "/usr/lib/xen/boot/hvmloader" >> > > builder = "hvm" >> > > shadow_memory = "8" >> > > memory = "4096" >> > > name = "ts" >> > > vcpus = "8" >> > > cpus = ["0", "1", "2", "3", "4", "5", "6", "7"] >> > > pae = "1" >> > > acpi = "1" >> > > apic = "1" >> > > vfb = [ ''type=vnc, vnclisten=10.100.100.50, vncpasswd=xxx'' ] >> > > xen_extended_power_mgmt = "0" >> > > vif = [ "type=ioemu, mac=00:16:3e:d7:d7:5d, bridge=xenbr0" ] >> > > disk = [ "phy:/dev/virtuals/ts,hda,w", >> > > "file:/media/iso/windows_server_2008_r2_sp1.iso,hdc:cdrom,r" ] >> > > on_poweroff = "destroy" >> > > on_reboot = "restart" >> > > on_crash = "restart" >> > > viridian = "1" >> > > device_model = "/usr/lib/xen/bin/qemu-dm" >> > > boot = "dc" >> > > snapshot = "0" >> > > vncconsole = "1" >> > > sdl = "0" >> > > opengl = "0" >> > > vnc = "1" >> > > nographic = "0" >> > > stdvga = "0" >> > > tsc_mode = "1" >> > > monitor = "0" >> > > localtime = "1" >> > > usb = "0" >> > > keymap = "fi" >> > > xen_platform_pci = "1" >> > > pci_msitranslate = "1" >> > > pci_power_mgmt = "0" >> > > >> > > 2012/10/1 Pasi Kärkkäinen <[1][2]pasik@iki.fi> >> > > >> > > On Mon, Oct 01, 2012 at 06:46:08PM +0300, Valtteri Kiviniemi >> > wrote: >> > > > Hi, >> > > > >> > > > Yes, I have viridian=1 on my domU config. >> > > > >> > > >> > > Try with some known good domU configfile. >> > > >> > > -- Pasi >> > > > 2012/10/1 Pasi Kärkkäinen <[1][2][3]pasik@iki.fi> >> > > > >> > > > On Mon, Oct 01, 2012 at 05:06:53PM +0300, Valtteri >> > Kiviniemi >> > > wrote: >> > > > > Hi, >> > > > > >> > > > > I''m now using 3.6.0 and can''t reproduce that >> crash >> > anymore, >> > > so it >> > > > seems >> > > > > that it was a kernel bug. >> > > > > >> > > > >> > > > OK. >> > > > > However I''m still getting black screen on VNC >> > > > > when trying to install Windows Server 2008 R2. >> I can >> > see the >> > > > "windows is >> > > > > loading files" screen but after the installer >> starts >> > the VNC >> > > > display goes >> > > > > black. >> > > > > >> > > > > Any ideas? >> > > > > >> > > > >> > > > Do you have viridian=1 specified for the windows vm? >> > > > >> > > > -- Pasi >> > > > >> > > > > - Valtteri >> > > > > >> > > > > 2012/10/1 Pasi Kärkkäinen <[1][2][3][4] >> pasik@iki.fi> >> > > > > >> > > > > On Sun, Sep 30, 2012 at 11:18:03PM +0300, >> Valtteri >> > > Kiviniemi >> > > > wrote: >> > > > > > Hi, >> > > > > > >> > > > > >> > > > > Hello, >> > > > > > I''m trying to get Windows Server 2008 R2 >> > installation >> > > > booting on >> > > > > Xen >> > > > > > 4.0.4. Using the following config: >> > > > > > >> > > > > >> > > > > <snip> >> > > > > > >> > > > > > The domU will start booting just fine, >> but >> > after a >> > > few >> > > > minutes the >> > > > > VNC >> > > > > > screen goes black. After that when >> typing "xm >> > destroy >> > > ts" it >> > > > will >> > > > > trigger >> > > > > > a kernel BUG: >> > > > > > >> > > > > > BUG: unable to handle kernel NULL pointer >> > dereference >> > > at >> > > > > 0000000000000030 >> > > > > > IP: [<ffffffff810c50c4>] iput+0x3e/0x195 >> > > > > > PGD 0 >> > > > > > Oops: 0000 [#1] SMP >> > > > > > CPU 6 >> > > > > > Pid: 3571, comm: qemu-dm Not tainted >> > 3.5.0-dom0 #1 >> > > > > >> > > > > First of all upgrade to latest 3.5.x Linux >> kernel >> > release >> > > .. so >> > > > at least >> > > > > 3.5.4. >> > > > > >> > > > > -- Pasi >> > > > > >> > > > > > /DQ77MK >> > > > > > RIP: e030:[<ffffffff810c50c4>] >> > [<ffffffff810c50c4>] >> > > > > iput+0x3e/0x195 >> > > > > > RSP: e02b:ffff8800389ffbf8 EFLAGS: >> 00010246 >> > > > > > RAX: 0000000000000001 RBX: >> ffff8800377b0720 >> > RCX: >> > > > ffff8800501c0000 >> > > > > > RDX: ffff8800501c0000 RSI: >> ffff8800377b0790 >> > RDI: >> > > > ffff8800377b0790 >> > > > > > RBP: 0000000000000000 R08: >> ffffffff815cdd00 >> > R09: >> > > > 0000000000000016 >> > > > > > R10: fefefefefefefeff R11: >> ffff8800377b0400 >> > R12: >> > > > 00000001000a3e0c >> > > > > > R13: 0000000000000000 R14: >> 00000001000a3e0c >> > R15: >> > > > ffff8800389ffc28 >> > > > > > FS: 00007f1af70a8700(0000) >> > GS:ffff880050180000(0000) >> > > > > > knlGS:0000000000000000 >> > > > > > CS: e033 DS: 0000 ES: 0000 CR0: >> > 000000008005003b >> > > > > > CR2: 0000000000000030 CR3: >> 000000000156d000 >> > CR4: >> > > > 0000000000002660 >> > > > > > DR0: 0000000000000000 DR1: >> 0000000000000000 >> > DR2: >> > > > 0000000000000000 >> > > > > > DR3: 0000000000000000 DR6: >> 00000000ffff0ff0 >> > DR7: >> > > > 0000000000000400 >> > > > > > Process qemu-dm (pid: 3571, threadinfo >> > > ffff8800389fe000, >> > > > task >> > > > > > ffff88003a721260) >> > > > > > Stack: >> > > > > > ffff88003a6d6400 ffff8800377b0000 >> > 00000001000a3e0c >> > > > > ffffffff8133ce8f >> > > > > > ffff8800377b0400 ffffffff8134b6cd >> > ffff8800389ffc28 >> > > > > ffff8800389ffc28 >> > > > > > ffff8800377b00f8 ffff8800377b0680 >> > ffff880038cdcd60 >> > > > > ffff8800377b0000 >> > > > > > Call Trace: >> > > > > > [<ffffffff8133ce8f>] ? >> > sk_release_kernel+0x23/0x39 >> > > > > > [<ffffffff8134b6cd>] ? >> > netdev_run_todo+0x1e9/0x206 >> > > > > > [<ffffffff8129798f>] ? >> > tun_chr_close+0x4c/0x7b >> > > > > > [<ffffffff810b39d3>] ? fput+0xe4/0x1c5 >> > > > > > [<ffffffff810b202c>] ? >> filp_close+0x61/0x68 >> > > > > > [<ffffffff81035e62>] ? >> > put_files_struct+0x62/0xb9 >> > > > > > [<ffffffff81036374>] ? >> do_exit+0x24a/0x74c >> > > > > > [<ffffffff81036906>] ? >> > do_group_exit+0x6b/0x9d >> > > > > > [<ffffffff8103ea0b>] ? >> > > get_signal_to_deliver+0x449/0x46e >> > > > > > [<ffffffff81009fa5>] ? >> do_signal+0x28/0x4c4 >> > > > > > [<ffffffff81027079>] ? >> > > pvclock_clocksource_read+0x48/0xbf >> > > > > > [<ffffffff8105b745>] ? >> ktime_get_ts+0x66/0xa8 >> > > > > > [<ffffffff810bfb18>] ? >> > > poll_select_copy_remaining+0xe0/0xf5 >> > > > > > [<ffffffff8100a48d>] ? >> > do_notify_resume+0x3b/0x74 >> > > > > > [<ffffffff81411a70>] ? >> int_signal+0x12/0x17 >> > > > > > Code: 00 00 00 40 74 02 0f 0b 48 8d 77 >> 70 48 >> > 8d bf 08 >> > > 01 00 >> > > > 00 e8 >> > > > > 8b 71 10 >> > > > > > 00 85 c0 0f 84 5d 01 00 00 48 8b 6b 18 >> f6 83 >> > 80 00 00 >> > > 00 08 >> > > > <4c> 8b >> > > > > 65 30 >> > > > > > 74 11 be 68 05 00 00 48 c7 c7 8e df 4f >> 81 e8 >> > bb d0 >> > > > > > RIP [<ffffffff810c50c4>] iput+0x3e/0x195 >> > > > > > RSP <ffff8800389ffbf8> >> > > > > > CR2: 0000000000000030 >> > > > > > ---[ end trace 67cc1654658fedcc ]--- >> > > > > > Fixing recursive fault but reboot is >> needed! >> > > > > > >> > > > > > I also tested Xen 4.2.0 and problem is >> the >> > same. So >> > > is this >> > > > a Xen >> > > > > bug or a >> > > > > > kernel bug? I am running vanilla >> > > [1][2][3][4][5]kernel.org kernel >> > > > 3.5.0 and >> > > > > my >> > > > > > hardware is Intel Core i7-3770 CPU and >> Intel >> > DQ77MK >> > > > motherboard >> > > > > with >> > > > > > latest bios. >> > > > > > >> > > > > > Best regards, >> > > > > > Valtteri Kiviniemi >> > > > > > >> > > > > > References >> > > > > > >> > > > > > Visible links >> > > > > > 1. [3][4][5][6]http://kernel.org/ >> > > > > >> > > > > > >> _______________________________________________ >> > > > > > Xen-devel mailing list >> > > > > > [4][5][6][7]Xen-devel@lists.xen.org >> > > > > > [5][6][7][8]http://lists.xen.org/xen-devel >> > > > > >> > > > > References >> > > > > >> > > > > Visible links >> > > > > 1. mailto:[7][8][9]pasik@iki.fi >> > > > > 2. [8][9][10]http://kernel.org/ >> > > > > 3. [9][10][11]http://kernel.org/ >> > > > > 4. mailto:[10][11][12]Xen-devel@lists.xen.org >> > > > > 5. [11][12][13]http://lists.xen.org/xen-devel >> > > > >> > > > References >> > > > >> > > > Visible links >> > > > 1. mailto:[13][14]pasik@iki.fi >> > > > 2. mailto:[14][15]pasik@iki.fi >> > > > 3. [15][16]http://kernel.org/ >> > > > 4. [16][17]http://kernel.org/ >> > > > 5. mailto:[17][18]Xen-devel@lists.xen.org >> > > > 6. [18][19]http://lists.xen.org/xen-devel >> > > > 7. mailto:[19][20]pasik@iki.fi >> > > > 8. [20][21]http://kernel.org/ >> > > > 9. [21][22]http://kernel.org/ >> > > > 10. mailto:[22][23]Xen-devel@lists.xen.org >> > > > 11. [23][24]http://lists.xen.org/xen-devel >> > > >> > > References >> > > >> > > Visible links >> > > 1. mailto:[25]pasik@iki.fi >> > > 2. mailto:[26]pasik@iki.fi >> > > 3. mailto:[27]pasik@iki.fi >> > > 4. [28]http://kernel.org/ >> > > 5. [29]http://kernel.org/ >> > > 6. mailto:[30]Xen-devel@lists.xen.org >> > > 7. [31]http://lists.xen.org/xen-devel >> > > 8. mailto:[32]pasik@iki.fi >> > > 9. [33]http://kernel.org/ >> > > 10. [34]http://kernel.org/ >> > > 11. mailto:[35]Xen-devel@lists.xen.org >> > > 12. [36]http://lists.xen.org/xen-devel >> > > 13. mailto:[37]pasik@iki.fi >> > > 14. mailto:[38]pasik@iki.fi >> > > 15. [39]http://kernel.org/ >> > > 16. [40]http://kernel.org/ >> > > 17. mailto:[41]Xen-devel@lists.xen.org >> > > 18. [42]http://lists.xen.org/xen-devel >> > > 19. mailto:[43]pasik@iki.fi >> > > 20. [44]http://kernel.org/ >> > > 21. [45]http://kernel.org/ >> > > 22. mailto:[46]Xen-devel@lists.xen.org >> > > 23. [47]http://lists.xen.org/xen-devel >> > >> > References >> > >> > Visible links >> > 1. mailto:pasik@iki.fi >> > 2. mailto:pasik@iki.fi >> > 3. mailto:pasik@iki.fi >> > 4. mailto:pasik@iki.fi >> > 5. http://kernel.org/ >> > 6. http://kernel.org/ >> > 7. mailto:Xen-devel@lists.xen.org >> > 8. http://lists.xen.org/xen-devel >> > 9. mailto:pasik@iki.fi >> > 10. http://kernel.org/ >> > 11. http://kernel.org/ >> > 12. mailto:Xen-devel@lists.xen.org >> > 13. http://lists.xen.org/xen-devel >> > 14. mailto:pasik@iki.fi >> > 15. mailto:pasik@iki.fi >> > 16. http://kernel.org/ >> > 17. http://kernel.org/ >> > 18. mailto:Xen-devel@lists.xen.org >> > 19. http://lists.xen.org/xen-devel >> > 20. mailto:pasik@iki.fi >> > 21. http://kernel.org/ >> > 22. http://kernel.org/ >> > 23. mailto:Xen-devel@lists.xen.org >> > 24. http://lists.xen.org/xen-devel >> > 25. mailto:pasik@iki.fi >> > 26. mailto:pasik@iki.fi >> > 27. mailto:pasik@iki.fi >> > 28. http://kernel.org/ >> > 29. http://kernel.org/ >> > 30. mailto:Xen-devel@lists.xen.org >> > 31. http://lists.xen.org/xen-devel >> > 32. mailto:pasik@iki.fi >> > 33. http://kernel.org/ >> > 34. http://kernel.org/ >> > 35. mailto:Xen-devel@lists.xen.org >> > 36. http://lists.xen.org/xen-devel >> > 37. mailto:pasik@iki.fi >> > 38. mailto:pasik@iki.fi >> > 39. http://kernel.org/ >> > 40. http://kernel.org/ >> > 41. mailto:Xen-devel@lists.xen.org >> > 42. http://lists.xen.org/xen-devel >> > 43. mailto:pasik@iki.fi >> > 44. http://kernel.org/ >> > 45. http://kernel.org/ >> > 46. mailto:Xen-devel@lists.xen.org >> > 47. http://lists.xen.org/xen-devel >> > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Pasi Kärkkäinen
2012-Oct-02 12:19 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
On Tue, Oct 02, 2012 at 03:11:07PM +0300, Valtteri Kiviniemi wrote:> Hi, > > Another update: > > I wanted to check that if a Linux HVM would boot with working VNC console, > so I tried to launch a Debian Squeeze installer on HVM. It refused to > start ant told me that vbd hotplug scripts were not working. After that > failure even the Windows domU would not anymore start which was previously > starting ok. > > The hotplug scripts also starts hanging on the processes. > > root 9401 0.1 0.1 17700 1640 ? S 15:05 0:00 /bin/bash > /etc/xen/scripts/xen-hotplug-cleanup > root 9441 0.1 0.1 17700 1644 ? S 15:05 0:00 /bin/bash > /etc/xen/scripts/xen-hotplug-cleanup > root 9481 0.1 0.1 17700 1640 ? S 15:05 0:00 /bin/bash > /etc/xen/scripts/xen-hotplug-cleanup > root 9560 0.1 0.1 17700 1640 ? S 15:05 0:00 /bin/bash > /etc/xen/scripts/xen-hotplug-cleanup > root 10738 0.1 0.1 17696 1636 ? S 15:05 0:00 /bin/bash > /etc/xen/scripts/xen-hotplug-cleanup > root 10747 0.1 0.1 17792 1736 ? S 15:05 0:00 /bin/bash > /etc/xen/scripts/block remove > root 11286 0.0 0.0 4080 324 ? S 15:06 0:00 sleep 1 > root 11290 0.0 0.0 4080 324 ? S 15:06 0:00 sleep 1 > root 11294 0.0 0.0 4080 324 ? S 15:06 0:00 sleep 1 > root 11298 0.0 0.0 4080 324 ? S 15:06 0:00 sleep 1 > root 11302 0.0 0.0 4080 320 ? S 15:06 0:00 sleep 1 > root 11306 0.0 0.0 4080 320 ? S 15:06 0:00 sleep 1 > > Then I did a xm destroy and I had again the kernel BUG on dmesg. So it > seems that the problem is not fixed by using 3.6.0. Udev version is 175-7. >So you have definitely something broken in your system, probably in your dom0 kernel. Try with Linux 3.5.4 or 3.4.x, and see how that goes. Any errors in dom0 dmesg? How about in /var/log/xen/* ? -- Pasi> > > 2012/10/1 Valtteri Kiviniemi <[1]kiviniemi.valtteri@gmail.com> > > Hi, > > CPU: Intel Core i7-3770 3.4GHz > [2]http://ark.intel.com/products/65719/ > > MB: Intel DQ77MK (latest bios updated) > [3]http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > > Memory: 32GB (4 x 8GB DDR3-1600MHz) > > Host is Debian wheezy/testing, Xen 4.0.4 and latest 3.6.0 kernel. > > Noticed also some errors in xm dmesg: > > root@xen-2:~# xm dmesg > > (XEN) Xen version 4.0.4 ([4]root@dataproof.fi) (gcc version 4.7.1 > (Debian 4.7.1-7) ) Sun Sep 30 20:28:26 EEST 2012 > (XEN) Latest ChangeSet: unavailable > (XEN) Bootloader: GNU GRUB 0.97 > (XEN) Command line: dom0_mem=1280M cpufreq=xen clocksource=hpet > (XEN) Video information: > (XEN) VGA is text mode 80x25, font 8x16 > (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds > (XEN) EDID info not retrieved because no DDC retrieval method detected > (XEN) Disc information: > (XEN) Found 4 MBR signatures > (XEN) Found 4 EDD information structures > (XEN) Xen-e820 RAM map: > (XEN) 0000000000000000 - 000000000009d800 (usable) > (XEN) 000000000009d800 - 00000000000a0000 (reserved) > (XEN) 00000000000e0000 - 0000000000100000 (reserved) > (XEN) 0000000000100000 - 0000000020000000 (usable) > (XEN) 0000000020000000 - 0000000020200000 (reserved) > (XEN) 0000000020200000 - 0000000040004000 (usable) > (XEN) 0000000040004000 - 0000000040005000 (reserved) > (XEN) 0000000040005000 - 00000000dbe44000 (usable) > (XEN) 00000000dbe44000 - 00000000dc2d7000 (reserved) > (XEN) 00000000dc2d7000 - 00000000dc2e7000 (ACPI data) > (XEN) 00000000dc2e7000 - 00000000dc40c000 (ACPI NVS) > (XEN) 00000000dc40c000 - 00000000dc6af000 (reserved) > (XEN) 00000000dc6af000 - 00000000dc6b0000 (usable) > (XEN) 00000000dc6b0000 - 00000000dc6f3000 (ACPI NVS) > (XEN) 00000000dc6f3000 - 00000000dd000000 (usable) > (XEN) 00000000dd800000 - 00000000dfa00000 (reserved) > (XEN) 00000000f8000000 - 00000000fc000000 (reserved) > (XEN) 00000000fec00000 - 00000000fec01000 (reserved) > (XEN) 00000000fed00000 - 00000000fed04000 (reserved) > (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > (XEN) 00000000ff000000 - 0000000100000000 (reserved) > (XEN) 0000000100000000 - 000000081e600000 (usable) > (XEN) ACPI: RSDP 000F0490, 0024 (r2 INTEL) > (XEN) ACPI: XSDT DC2DB080, 007C (r1 INTEL DQ77MK 32 AMI > 10013) > (XEN) ACPI: FACP DC2E51F0, 010C (r5 INTEL DQ77MK 32 AMI > 10013) > (XEN) ACPI Warning (tbfadt-0232): FADT (revision 5) is longer than ACPI > 2.0 version, truncating length 0x10C to 0xF4 [20070126] > (XEN) ACPI: DSDT DC2DB188, A061 (r2 INTEL DQ77MK 32 INTL > 20051117) > (XEN) ACPI: FACS DC40A080, 0040 > (XEN) ACPI: APIC DC2E5300, 0092 (r3 INTEL DQ77MK 32 AMI > 10013) > (XEN) ACPI: FPDT DC2E5398, 0044 (r1 INTEL DQ77MK 32 AMI > 10013) > (XEN) ACPI: TCPA DC2E53E0, 0032 (r2 INTEL DQ77MK 32 MSFT > 1000013) > (XEN) ACPI: MCFG DC2E5418, 003C (r1 INTEL DQ77MK 32 MSFT > 97) > (XEN) ACPI: HPET DC2E5458, 0038 (r1 INTEL DQ77MK 32 AMI. > 5) > (XEN) ACPI: SSDT DC2E5490, 036D (r1 INTEL DQ77MK 32 INTL > 20091112) > (XEN) ACPI: SSDT DC2E5800, 09AA (r1 INTEL DQ77MK 32 INTL > 20051117) > (XEN) ACPI: SSDT DC2E61B0, 0A92 (r1 INTEL DQ77MK 32 INTL > 20051117) > (XEN) ACPI: DMAR DC2E6C48, 00B8 (r1 INTEL DQ77MK 32 INTL > 1) > (XEN) ACPI: ASF! DC2E6D00, 00A5 (r32 INTEL DQ77MK 32 TFSM > F4240) > (XEN) System RAM: 32682MB (33467320kB) > (XEN) Domain heap initialised > (XEN) ACPI: 32/64X FACS address mismatch in FADT - > dc40a080/0000000000000000, using 32 > (XEN) Processor #0 7:10 APIC version 21 > (XEN) Processor #2 7:10 APIC version 21 > (XEN) Processor #4 7:10 APIC version 21 > (XEN) Processor #6 7:10 APIC version 21 > (XEN) Processor #1 7:10 APIC version 21 > (XEN) Processor #3 7:10 APIC version 21 > (XEN) Processor #5 7:10 APIC version 21 > (XEN) Processor #7 7:10 APIC version 21 > (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > (XEN) Switched to APIC driver x2apic_cluster. > (XEN) x2APIC mode enabled. > (XEN) Using scheduler: SMP Credit Scheduler (credit) > (XEN) Detected 3392.369 MHz processor. > (XEN) Initing memory sharing. > (XEN) VMX: Supported advanced features: > (XEN) - APIC MMIO access virtualisation > (XEN) - APIC TPR shadow > (XEN) - Extended Page Tables (EPT) > (XEN) - Virtual-Processor Identifiers (VPID) > (XEN) - Virtual NMI > (XEN) - MSR direct-access bitmap > (XEN) - Unrestricted Guest > (XEN) EPT supports 2MB super page. > (XEN) HVM: ASIDs enabled. > (XEN) HVM: VMX enabled > (XEN) HVM: Hardware Assisted Paging detected. > (XEN) Intel VT-d Snoop Control not enabled. > (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. > (XEN) Intel VT-d Queued Invalidation enabled. > (XEN) Intel VT-d Interrupt Remapping enabled. > (XEN) I/O virtualisation enabled > (XEN) - Dom0 mode: Relaxed > (XEN) Enabled directed EOI with ioapic_ack_old on! > (XEN) Total of 8 processors activated. > (XEN) ENABLING IO-APIC IRQs > (XEN) -> Using old ACK method > (XEN) TSC is reliable, synchronization unnecessary > (XEN) Platform timer appears to have unexpectedly wrapped 1 times. > (XEN) Platform timer is 14.318MHz HPET > (XEN) Allocated console ring of 16 KiB. > (XEN) Brought up 8 CPUs > (XEN) *** LOADING DOMAIN 0 *** > (XEN) Xen kernel: 64-bit, lsb, compat32 > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1ae7000 > (XEN) PHYSICAL MEMORY ARRANGEMENT: > (XEN) Dom0 alloc.: 0000000804000000->0000000806000000 (319488 pages > to be allocated) > (XEN) VIRTUAL MEMORY ARRANGEMENT: > (XEN) Loaded kernel: ffffffff81000000->ffffffff81ae7000 > (XEN) Init. ramdisk: ffffffff81ae7000->ffffffff81ae7000 > (XEN) Phys-Mach map: ffffffff81ae7000->ffffffff81d67000 > (XEN) Start info: ffffffff81d67000->ffffffff81d674b4 > (XEN) Page tables: ffffffff81d68000->ffffffff81d7b000 > (XEN) Boot stack: ffffffff81d7b000->ffffffff81d7c000 > (XEN) TOTAL: ffffffff80000000->ffffffff82000000 > (XEN) ENTRY ADDRESS: ffffffff815e3210 > (XEN) Dom0 has maximum 8 VCPUs > (XEN) [VT-D]iommu.c:718: BIOS did not enable IGD for VT properly. > Disabling IGD VT-d engine. > (XEN) Scrubbing Free RAM: done. > (XEN) Xen trace buffers: disabled > (XEN) Std. Loglevel: Errors and warnings > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) > (XEN) Xen is relinquishing VGA console. > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch > input to Xen) > (XEN) Freed 172kB init memory. > (XEN) traps.c:2333:d0 Domain attempted WRMSR 000000000000008b from > 00000012:00000000 to 00000000:00000000. > > - Valtteri > > 2012/10/1 Pasi Kärkkäinen <[5]pasik@iki.fi> > > On Mon, Oct 01, 2012 at 09:12:50PM +0300, Valtteri Kiviniemi wrote: > > Hi, > > > > Lowering memory or vcpu''s does not help, problem is the same. I > originally > > installed Xen 4.2.0 and the problem was same on that too. Then I > > downgraded back to 4.0.4 since I thought that this might be a bug > on > > 4.2.0. I have been previously running Windows Server 2008 R2 > succesfully > > on Xen 4.0.x on different hardware with this same config. > Hypervisor is > > 64bit and windows is 64bit. > > > > Any ideas what to try next? > > > > What kind of hardware is that? > > [6]xen.org automated testing regularly tests Windows VMs, and it works > OK there. > > -- Pasi > > Ps. qemu-dm.log is the following: > > > > domid: 10 > > config qemu network with xen bridge for tap10.0 xenbr0 > > Using file /dev/virtuals/ts in read-write mode > > Using file /media/iso/windows_server_2008_r2_sp1.iso in read-only > mode > > Watching /local/domain/0/device-model/10/logdirty/cmd > > Watching /local/domain/0/device-model/10/command > > qemu_map_cache_init nr_buckets = 10000 size 4194304 > > shared page at pfn feffd > > buffered io page at pfn feffb > > Guest uuid = 52f19e23-2955-c27d-a22c-60c5d8c60d5a > > Time offset set 0 > > populating video RAM at ff000000 > > mapping video RAM from ff000000 > > Register xen platform. > > Done register platform. > > platform_fixed_ioport: changed ro/rw state of ROM memory area. > now is rw > > state. > > xs_read(/local/domain/0/device-model/10/xen_extended_power_mgmt): > read > > error > > medium change watch on `hdc'' (index: 1): > > /media/iso/windows_server_2008_r2_sp1.iso > > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, > size: 0 > > Log-dirty: no command yet. > > xs_read(/local/domain/10/log-throttling): read error > > qemu: ignoring not-understood drive > `/local/domain/10/log-throttling'' > > medium change watch on `/local/domain/10/log-throttling'' - > unknown device, > > ignored > > cirrus vga map change while on lfb mode > > mapping vram to f0000000 - f0400000 > > platform_fixed_ioport: changed ro/rw state of ROM memory area. > now is rw > > state. > > platform_fixed_ioport: changed ro/rw state of ROM memory area. > now is ro > > state. > > > > 2012/10/1 Pasi Kärkkäinen <[1][7]pasik@iki.fi> > > > > On Mon, Oct 01, 2012 at 07:23:44PM +0300, Valtteri Kiviniemi > wrote: > > > Hi, > > > > > > I have tried other config files, but the problem is the > same. At > > the > > > moment I''m using a config file from another server where I > have a > > working > > > Windows Server 2008 R2 installation, so I dont think that > there is > > > anything wrong with my config: > > > > > > > Did you try with less vcpus, for example 2 ? > > how about with less memory, say 2 GB ? > > > > Did you try with later Xen versions? Is that a 32bit Xen, or > 64bit Xen > > hypervisor? > > > > -- Pasi > > > kernel = "/usr/lib/xen/boot/hvmloader" > > > builder = "hvm" > > > shadow_memory = "8" > > > memory = "4096" > > > name = "ts" > > > vcpus = "8" > > > cpus = ["0", "1", "2", "3", "4", "5", "6", "7"] > > > pae = "1" > > > acpi = "1" > > > apic = "1" > > > vfb = [ ''type=vnc, vnclisten=10.100.100.50, vncpasswd=xxx'' > ] > > > xen_extended_power_mgmt = "0" > > > vif = [ "type=ioemu, mac=00:16:3e:d7:d7:5d, bridge=xenbr0" > ] > > > disk = [ "phy:/dev/virtuals/ts,hda,w", > > > > "file:/media/iso/windows_server_2008_r2_sp1.iso,hdc:cdrom,r" ] > > > on_poweroff = "destroy" > > > on_reboot = "restart" > > > on_crash = "restart" > > > viridian = "1" > > > device_model = "/usr/lib/xen/bin/qemu-dm" > > > boot = "dc" > > > snapshot = "0" > > > vncconsole = "1" > > > sdl = "0" > > > opengl = "0" > > > vnc = "1" > > > nographic = "0" > > > stdvga = "0" > > > tsc_mode = "1" > > > monitor = "0" > > > localtime = "1" > > > usb = "0" > > > keymap = "fi" > > > xen_platform_pci = "1" > > > pci_msitranslate = "1" > > > pci_power_mgmt = "0" > > > > > > 2012/10/1 Pasi Kärkkäinen <[1][2][8]pasik@iki.fi> > > > > > > On Mon, Oct 01, 2012 at 06:46:08PM +0300, Valtteri > Kiviniemi > > wrote: > > > > Hi, > > > > > > > > Yes, I have viridian=1 on my domU config. > > > > > > > > > > Try with some known good domU configfile. > > > > > > -- Pasi > > > > 2012/10/1 Pasi Kärkkäinen > <[1][2][3][9]pasik@iki.fi> > > > > > > > > On Mon, Oct 01, 2012 at 05:06:53PM +0300, > Valtteri > > Kiviniemi > > > wrote: > > > > > Hi, > > > > > > > > > > I''m now using 3.6.0 and can''t reproduce that > crash > > anymore, > > > so it > > > > seems > > > > > that it was a kernel bug. > > > > > > > > > > > > > OK. > > > > > However I''m still getting black screen on > VNC > > > > > when trying to install Windows Server 2008 > R2. I can > > see the > > > > "windows is > > > > > loading files" screen but after the > installer starts > > the VNC > > > > display goes > > > > > black. > > > > > > > > > > Any ideas? > > > > > > > > > > > > > Do you have viridian=1 specified for the windows > vm? > > > > > > > > -- Pasi > > > > > > > > > - Valtteri > > > > > > > > > > 2012/10/1 Pasi Kärkkäinen > <[1][2][3][4][10]pasik@iki.fi> > > > > > > > > > > On Sun, Sep 30, 2012 at 11:18:03PM +0300, > Valtteri > > > Kiviniemi > > > > wrote: > > > > > > Hi, > > > > > > > > > > > > > > > > Hello, > > > > > > I''m trying to get Windows Server 2008 > R2 > > installation > > > > booting on > > > > > Xen > > > > > > 4.0.4. Using the following config: > > > > > > > > > > > > > > > > <snip> > > > > > > > > > > > > The domU will start booting just > fine, but > > after a > > > few > > > > minutes the > > > > > VNC > > > > > > screen goes black. After that when > typing "xm > > destroy > > > ts" it > > > > will > > > > > trigger > > > > > > a kernel BUG: > > > > > > > > > > > > BUG: unable to handle kernel NULL > pointer > > dereference > > > at > > > > > 0000000000000030 > > > > > > IP: [<ffffffff810c50c4>] > iput+0x3e/0x195 > > > > > > PGD 0 > > > > > > Oops: 0000 [#1] SMP > > > > > > CPU 6 > > > > > > Pid: 3571, comm: qemu-dm Not tainted > > 3.5.0-dom0 #1 > > > > > > > > > > First of all upgrade to latest 3.5.x Linux > kernel > > release > > > .. so > > > > at least > > > > > 3.5.4. > > > > > > > > > > -- Pasi > > > > > > > > > > > /DQ77MK > > > > > > RIP: e030:[<ffffffff810c50c4>] > > [<ffffffff810c50c4>] > > > > > iput+0x3e/0x195 > > > > > > RSP: e02b:ffff8800389ffbf8 EFLAGS: > 00010246 > > > > > > RAX: 0000000000000001 RBX: > ffff8800377b0720 > > RCX: > > > > ffff8800501c0000 > > > > > > RDX: ffff8800501c0000 RSI: > ffff8800377b0790 > > RDI: > > > > ffff8800377b0790 > > > > > > RBP: 0000000000000000 R08: > ffffffff815cdd00 > > R09: > > > > 0000000000000016 > > > > > > R10: fefefefefefefeff R11: > ffff8800377b0400 > > R12: > > > > 00000001000a3e0c > > > > > > R13: 0000000000000000 R14: > 00000001000a3e0c > > R15: > > > > ffff8800389ffc28 > > > > > > FS: 00007f1af70a8700(0000) > > GS:ffff880050180000(0000) > > > > > > knlGS:0000000000000000 > > > > > > CS: e033 DS: 0000 ES: 0000 CR0: > > 000000008005003b > > > > > > CR2: 0000000000000030 CR3: > 000000000156d000 > > CR4: > > > > 0000000000002660 > > > > > > DR0: 0000000000000000 DR1: > 0000000000000000 > > DR2: > > > > 0000000000000000 > > > > > > DR3: 0000000000000000 DR6: > 00000000ffff0ff0 > > DR7: > > > > 0000000000000400 > > > > > > Process qemu-dm (pid: 3571, > threadinfo > > > ffff8800389fe000, > > > > task > > > > > > ffff88003a721260) > > > > > > Stack: > > > > > > ffff88003a6d6400 ffff8800377b0000 > > 00000001000a3e0c > > > > > ffffffff8133ce8f > > > > > > ffff8800377b0400 ffffffff8134b6cd > > ffff8800389ffc28 > > > > > ffff8800389ffc28 > > > > > > ffff8800377b00f8 ffff8800377b0680 > > ffff880038cdcd60 > > > > > ffff8800377b0000 > > > > > > Call Trace: > > > > > > [<ffffffff8133ce8f>] ? > > sk_release_kernel+0x23/0x39 > > > > > > [<ffffffff8134b6cd>] ? > > netdev_run_todo+0x1e9/0x206 > > > > > > [<ffffffff8129798f>] ? > > tun_chr_close+0x4c/0x7b > > > > > > [<ffffffff810b39d3>] ? > fput+0xe4/0x1c5 > > > > > > [<ffffffff810b202c>] ? > filp_close+0x61/0x68 > > > > > > [<ffffffff81035e62>] ? > > put_files_struct+0x62/0xb9 > > > > > > [<ffffffff81036374>] ? > do_exit+0x24a/0x74c > > > > > > [<ffffffff81036906>] ? > > do_group_exit+0x6b/0x9d > > > > > > [<ffffffff8103ea0b>] ? > > > get_signal_to_deliver+0x449/0x46e > > > > > > [<ffffffff81009fa5>] ? > do_signal+0x28/0x4c4 > > > > > > [<ffffffff81027079>] ? > > > pvclock_clocksource_read+0x48/0xbf > > > > > > [<ffffffff8105b745>] ? > ktime_get_ts+0x66/0xa8 > > > > > > [<ffffffff810bfb18>] ? > > > poll_select_copy_remaining+0xe0/0xf5 > > > > > > [<ffffffff8100a48d>] ? > > do_notify_resume+0x3b/0x74 > > > > > > [<ffffffff81411a70>] ? > int_signal+0x12/0x17 > > > > > > Code: 00 00 00 40 74 02 0f 0b 48 8d > 77 70 48 > > 8d bf 08 > > > 01 00 > > > > 00 e8 > > > > > 8b 71 10 > > > > > > 00 85 c0 0f 84 5d 01 00 00 48 8b 6b > 18 f6 83 > > 80 00 00 > > > 00 08 > > > > <4c> 8b > > > > > 65 30 > > > > > > 74 11 be 68 05 00 00 48 c7 c7 8e df > 4f 81 e8 > > bb d0 > > > > > > RIP [<ffffffff810c50c4>] > iput+0x3e/0x195 > > > > > > RSP <ffff8800389ffbf8> > > > > > > CR2: 0000000000000030 > > > > > > ---[ end trace 67cc1654658fedcc ]--- > > > > > > Fixing recursive fault but reboot is > needed! > > > > > > > > > > > > I also tested Xen 4.2.0 and problem > is the > > same. So > > > is this > > > > a Xen > > > > > bug or a > > > > > > kernel bug? I am running vanilla > > > [1][2][3][4][5][11]kernel.org kernel > > > > 3.5.0 and > > > > > my > > > > > > hardware is Intel Core i7-3770 CPU > and Intel > > DQ77MK > > > > motherboard > > > > > with > > > > > > latest bios. > > > > > > > > > > > > Best regards, > > > > > > Valtteri Kiviniemi > > > > > > > > > > > > References > > > > > > > > > > > > Visible links > > > > > > 1. [3][4][5][6][12]http://kernel.org/ > > > > > > > > > > > > _______________________________________________ > > > > > > Xen-devel mailing list > > > > > > [4][5][6][7][13]Xen-devel@lists.xen.org > > > > > > > [5][6][7][8][14]http://lists.xen.org/xen-devel > > > > > > > > > > References > > > > > > > > > > Visible links > > > > > 1. mailto:[7][8][9][15]pasik@iki.fi > > > > > 2. [8][9][10][16]http://kernel.org/ > > > > > 3. [9][10][11][17]http://kernel.org/ > > > > > 4. > mailto:[10][11][12][18]Xen-devel@lists.xen.org > > > > > 5. > [11][12][13][19]http://lists.xen.org/xen-devel > > > > > > > > References > > > > > > > > Visible links > > > > 1. mailto:[13][14][20]pasik@iki.fi > > > > 2. mailto:[14][15][21]pasik@iki.fi > > > > 3. [15][16][22]http://kernel.org/ > > > > 4. [16][17][23]http://kernel.org/ > > > > 5. mailto:[17][18][24]Xen-devel@lists.xen.org > > > > 6. [18][19][25]http://lists.xen.org/xen-devel > > > > 7. mailto:[19][20][26]pasik@iki.fi > > > > 8. [20][21][27]http://kernel.org/ > > > > 9. [21][22][28]http://kernel.org/ > > > > 10. mailto:[22][23][29]Xen-devel@lists.xen.org > > > > 11. [23][24][30]http://lists.xen.org/xen-devel > > > > > > References > > > > > > Visible links > > > 1. mailto:[25][31]pasik@iki.fi > > > 2. mailto:[26][32]pasik@iki.fi > > > 3. mailto:[27][33]pasik@iki.fi > > > 4. [28][34]http://kernel.org/ > > > 5. [29][35]http://kernel.org/ > > > 6. mailto:[30][36]Xen-devel@lists.xen.org > > > 7. [31][37]http://lists.xen.org/xen-devel > > > 8. mailto:[32][38]pasik@iki.fi > > > 9. [33][39]http://kernel.org/ > > > 10. [34][40]http://kernel.org/ > > > 11. mailto:[35][41]Xen-devel@lists.xen.org > > > 12. [36][42]http://lists.xen.org/xen-devel > > > 13. mailto:[37][43]pasik@iki.fi > > > 14. mailto:[38][44]pasik@iki.fi > > > 15. [39][45]http://kernel.org/ > > > 16. [40][46]http://kernel.org/ > > > 17. mailto:[41][47]Xen-devel@lists.xen.org > > > 18. [42][48]http://lists.xen.org/xen-devel > > > 19. mailto:[43][49]pasik@iki.fi > > > 20. [44][50]http://kernel.org/ > > > 21. [45][51]http://kernel.org/ > > > 22. mailto:[46][52]Xen-devel@lists.xen.org > > > 23. [47][53]http://lists.xen.org/xen-devel > > > > References > > > > Visible links > > 1. mailto:[54]pasik@iki.fi > > 2. mailto:[55]pasik@iki.fi > > 3. mailto:[56]pasik@iki.fi > > 4. mailto:[57]pasik@iki.fi > > 5. [58]http://kernel.org/ > > 6. [59]http://kernel.org/ > > 7. mailto:[60]Xen-devel@lists.xen.org > > 8. [61]http://lists.xen.org/xen-devel > > 9. mailto:[62]pasik@iki.fi > > 10. [63]http://kernel.org/ > > 11. [64]http://kernel.org/ > > 12. mailto:[65]Xen-devel@lists.xen.org > > 13. [66]http://lists.xen.org/xen-devel > > 14. mailto:[67]pasik@iki.fi > > 15. mailto:[68]pasik@iki.fi > > 16. [69]http://kernel.org/ > > 17. [70]http://kernel.org/ > > 18. mailto:[71]Xen-devel@lists.xen.org > > 19. [72]http://lists.xen.org/xen-devel > > 20. mailto:[73]pasik@iki.fi > > 21. [74]http://kernel.org/ > > 22. [75]http://kernel.org/ > > 23. mailto:[76]Xen-devel@lists.xen.org > > 24. [77]http://lists.xen.org/xen-devel > > 25. mailto:[78]pasik@iki.fi > > 26. mailto:[79]pasik@iki.fi > > 27. mailto:[80]pasik@iki.fi > > 28. [81]http://kernel.org/ > > 29. [82]http://kernel.org/ > > 30. mailto:[83]Xen-devel@lists.xen.org > > 31. [84]http://lists.xen.org/xen-devel > > 32. mailto:[85]pasik@iki.fi > > 33. [86]http://kernel.org/ > > 34. [87]http://kernel.org/ > > 35. mailto:[88]Xen-devel@lists.xen.org > > 36. [89]http://lists.xen.org/xen-devel > > 37. mailto:[90]pasik@iki.fi > > 38. mailto:[91]pasik@iki.fi > > 39. [92]http://kernel.org/ > > 40. [93]http://kernel.org/ > > 41. mailto:[94]Xen-devel@lists.xen.org > > 42. [95]http://lists.xen.org/xen-devel > > 43. mailto:[96]pasik@iki.fi > > 44. [97]http://kernel.org/ > > 45. [98]http://kernel.org/ > > 46. mailto:[99]Xen-devel@lists.xen.org > > 47. [100]http://lists.xen.org/xen-devel > > References > > Visible links > 1. mailto:kiviniemi.valtteri@gmail.com > 2. http://ark.intel.com/products/65719/ > 3. http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > 4. mailto:root@dataproof.fi > 5. mailto:pasik@iki.fi > 6. http://xen.org/ > 7. mailto:pasik@iki.fi > 8. mailto:pasik@iki.fi > 9. mailto:pasik@iki.fi > 10. mailto:pasik@iki.fi > 11. http://kernel.org/ > 12. http://kernel.org/ > 13. mailto:Xen-devel@lists.xen.org > 14. http://lists.xen.org/xen-devel > 15. mailto:pasik@iki.fi > 16. http://kernel.org/ > 17. http://kernel.org/ > 18. mailto:Xen-devel@lists.xen.org > 19. http://lists.xen.org/xen-devel > 20. mailto:pasik@iki.fi > 21. mailto:pasik@iki.fi > 22. http://kernel.org/ > 23. http://kernel.org/ > 24. mailto:Xen-devel@lists.xen.org > 25. http://lists.xen.org/xen-devel > 26. mailto:pasik@iki.fi > 27. http://kernel.org/ > 28. http://kernel.org/ > 29. mailto:Xen-devel@lists.xen.org > 30. http://lists.xen.org/xen-devel > 31. mailto:pasik@iki.fi > 32. mailto:pasik@iki.fi > 33. mailto:pasik@iki.fi > 34. http://kernel.org/ > 35. http://kernel.org/ > 36. mailto:Xen-devel@lists.xen.org > 37. http://lists.xen.org/xen-devel > 38. mailto:pasik@iki.fi > 39. http://kernel.org/ > 40. http://kernel.org/ > 41. mailto:Xen-devel@lists.xen.org > 42. http://lists.xen.org/xen-devel > 43. mailto:pasik@iki.fi > 44. mailto:pasik@iki.fi > 45. http://kernel.org/ > 46. http://kernel.org/ > 47. mailto:Xen-devel@lists.xen.org > 48. http://lists.xen.org/xen-devel > 49. mailto:pasik@iki.fi > 50. http://kernel.org/ > 51. http://kernel.org/ > 52. mailto:Xen-devel@lists.xen.org > 53. http://lists.xen.org/xen-devel > 54. mailto:pasik@iki.fi > 55. mailto:pasik@iki.fi > 56. mailto:pasik@iki.fi > 57. mailto:pasik@iki.fi > 58. http://kernel.org/ > 59. http://kernel.org/ > 60. mailto:Xen-devel@lists.xen.org > 61. http://lists.xen.org/xen-devel > 62. mailto:pasik@iki.fi > 63. http://kernel.org/ > 64. http://kernel.org/ > 65. mailto:Xen-devel@lists.xen.org > 66. http://lists.xen.org/xen-devel > 67. mailto:pasik@iki.fi > 68. mailto:pasik@iki.fi > 69. http://kernel.org/ > 70. http://kernel.org/ > 71. mailto:Xen-devel@lists.xen.org > 72. http://lists.xen.org/xen-devel > 73. mailto:pasik@iki.fi > 74. http://kernel.org/ > 75. http://kernel.org/ > 76. mailto:Xen-devel@lists.xen.org > 77. http://lists.xen.org/xen-devel > 78. mailto:pasik@iki.fi > 79. mailto:pasik@iki.fi > 80. mailto:pasik@iki.fi > 81. http://kernel.org/ > 82. http://kernel.org/ > 83. mailto:Xen-devel@lists.xen.org > 84. http://lists.xen.org/xen-devel > 85. mailto:pasik@iki.fi > 86. http://kernel.org/ > 87. http://kernel.org/ > 88. mailto:Xen-devel@lists.xen.org > 89. http://lists.xen.org/xen-devel > 90. mailto:pasik@iki.fi > 91. mailto:pasik@iki.fi > 92. http://kernel.org/ > 93. http://kernel.org/ > 94. mailto:Xen-devel@lists.xen.org > 95. http://lists.xen.org/xen-devel > 96. mailto:pasik@iki.fi > 97. http://kernel.org/ > 98. http://kernel.org/ > 99. mailto:Xen-devel@lists.xen.org > 100. http://lists.xen.org/xen-devel
Valtteri Kiviniemi
2012-Oct-02 13:01 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
Hi, I already tried 3.2, 3.5, 3.5.0, 3.6.0-rc7 and 3.6.0, same problem all of those. My dom0 config is the same config that I''am using on other server where HVM is working, so I dont think that it is a config problem. I have triple checked everything and all should be ok. dom0 dmesg shows the same crash that I have previously posted here. /var/log/xen/ does not contain any specific errors. Could this be some kind of broblem with my motherboard bios being buggy or CPU not supported? I''m using the new intel Ivy Bridge processor which has integrated GPU, but that should not probably cause these kind of problems. Or maybe some ACPI problem? xm dmesg is showing some notices about ACPI. Is there any ACPI kernel parameters that I should try booting? This has to be somekind of problem with my hardware, or then maybe it could be a kernel problem too. I just really cant figure this out myself, I have tried everything. Lets take a quick summary of what has been tested, what hardware I''m using etc. Xen-versions tested: 4.2.0, 4.0.4 Kernel-versions tested: 3.2.0, 3.5.0, 3.5.4, 3.6.0-rc7, 3.6.0 Host OS: Debian testing/wheezy, udev version 175-7, 2.13-35, python version 2.7.3~rc2-2.1 Hardware: CPU: Intel Core i7-3770 3.4GHz MB: Intel DQ77MK (latest bios updated) Memory: 32GB (4 x 8GB DDR3-1600MHz) All relevant log files and configs: dom0 dmesg: http://nago.fi/dmesg.txt qemu-dm log: http://nago.fi/qemu-dm.txt xm dmesg log: http://nago.fi/xm-dmesg.txt domU config: http://nago.fi/domu-config.txt dom0 kernel config: http://nago.fi/dom0-config.txt I have also tried playing with every setting on that domU that I can think of and tried different configs etc. - Valtteri 2012/10/2 Pasi Kärkkäinen <pasik@iki.fi>> On Tue, Oct 02, 2012 at 03:11:07PM +0300, Valtteri Kiviniemi wrote: > > Hi, > > > > Another update: > > > > I wanted to check that if a Linux HVM would boot with working VNC > console, > > so I tried to launch a Debian Squeeze installer on HVM. It refused to > > start ant told me that vbd hotplug scripts were not working. After > that > > failure even the Windows domU would not anymore start which was > previously > > starting ok. > > > > The hotplug scripts also starts hanging on the processes. > > > > root 9401 0.1 0.1 17700 1640 ? S 15:05 0:00 > /bin/bash > > /etc/xen/scripts/xen-hotplug-cleanup > > root 9441 0.1 0.1 17700 1644 ? S 15:05 0:00 > /bin/bash > > /etc/xen/scripts/xen-hotplug-cleanup > > root 9481 0.1 0.1 17700 1640 ? S 15:05 0:00 > /bin/bash > > /etc/xen/scripts/xen-hotplug-cleanup > > root 9560 0.1 0.1 17700 1640 ? S 15:05 0:00 > /bin/bash > > /etc/xen/scripts/xen-hotplug-cleanup > > root 10738 0.1 0.1 17696 1636 ? S 15:05 0:00 > /bin/bash > > /etc/xen/scripts/xen-hotplug-cleanup > > root 10747 0.1 0.1 17792 1736 ? S 15:05 0:00 > /bin/bash > > /etc/xen/scripts/block remove > > root 11286 0.0 0.0 4080 324 ? S 15:06 0:00 > sleep 1 > > root 11290 0.0 0.0 4080 324 ? S 15:06 0:00 > sleep 1 > > root 11294 0.0 0.0 4080 324 ? S 15:06 0:00 > sleep 1 > > root 11298 0.0 0.0 4080 324 ? S 15:06 0:00 > sleep 1 > > root 11302 0.0 0.0 4080 320 ? S 15:06 0:00 > sleep 1 > > root 11306 0.0 0.0 4080 320 ? S 15:06 0:00 > sleep 1 > > > > Then I did a xm destroy and I had again the kernel BUG on dmesg. So it > > seems that the problem is not fixed by using 3.6.0. Udev version is > 175-7. > > > > So you have definitely something broken in your system, > probably in your dom0 kernel. Try with Linux 3.5.4 or 3.4.x, > and see how that goes. > > Any errors in dom0 dmesg? How about in /var/log/xen/* ? > > -- Pasi > > > > > > > 2012/10/1 Valtteri Kiviniemi <[1]kiviniemi.valtteri@gmail.com> > > > > Hi, > > > > CPU: Intel Core i7-3770 3.4GHz > > [2]http://ark.intel.com/products/65719/ > > > > MB: Intel DQ77MK (latest bios updated) > > [3] > http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > > > > Memory: 32GB (4 x 8GB DDR3-1600MHz) > > > > Host is Debian wheezy/testing, Xen 4.0.4 and latest 3.6.0 kernel. > > > > Noticed also some errors in xm dmesg: > > > > root@xen-2:~# xm dmesg > > > > (XEN) Xen version 4.0.4 ([4]root@dataproof.fi) (gcc version 4.7.1 > > (Debian 4.7.1-7) ) Sun Sep 30 20:28:26 EEST 2012 > > (XEN) Latest ChangeSet: unavailable > > (XEN) Bootloader: GNU GRUB 0.97 > > (XEN) Command line: dom0_mem=1280M cpufreq=xen clocksource=hpet > > (XEN) Video information: > > (XEN) VGA is text mode 80x25, font 8x16 > > (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds > > (XEN) EDID info not retrieved because no DDC retrieval method > detected > > (XEN) Disc information: > > (XEN) Found 4 MBR signatures > > (XEN) Found 4 EDD information structures > > (XEN) Xen-e820 RAM map: > > (XEN) 0000000000000000 - 000000000009d800 (usable) > > (XEN) 000000000009d800 - 00000000000a0000 (reserved) > > (XEN) 00000000000e0000 - 0000000000100000 (reserved) > > (XEN) 0000000000100000 - 0000000020000000 (usable) > > (XEN) 0000000020000000 - 0000000020200000 (reserved) > > (XEN) 0000000020200000 - 0000000040004000 (usable) > > (XEN) 0000000040004000 - 0000000040005000 (reserved) > > (XEN) 0000000040005000 - 00000000dbe44000 (usable) > > (XEN) 00000000dbe44000 - 00000000dc2d7000 (reserved) > > (XEN) 00000000dc2d7000 - 00000000dc2e7000 (ACPI data) > > (XEN) 00000000dc2e7000 - 00000000dc40c000 (ACPI NVS) > > (XEN) 00000000dc40c000 - 00000000dc6af000 (reserved) > > (XEN) 00000000dc6af000 - 00000000dc6b0000 (usable) > > (XEN) 00000000dc6b0000 - 00000000dc6f3000 (ACPI NVS) > > (XEN) 00000000dc6f3000 - 00000000dd000000 (usable) > > (XEN) 00000000dd800000 - 00000000dfa00000 (reserved) > > (XEN) 00000000f8000000 - 00000000fc000000 (reserved) > > (XEN) 00000000fec00000 - 00000000fec01000 (reserved) > > (XEN) 00000000fed00000 - 00000000fed04000 (reserved) > > (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) > > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > > (XEN) 00000000ff000000 - 0000000100000000 (reserved) > > (XEN) 0000000100000000 - 000000081e600000 (usable) > > (XEN) ACPI: RSDP 000F0490, 0024 (r2 INTEL) > > (XEN) ACPI: XSDT DC2DB080, 007C (r1 INTEL DQ77MK 32 AMI > > 10013) > > (XEN) ACPI: FACP DC2E51F0, 010C (r5 INTEL DQ77MK 32 AMI > > 10013) > > (XEN) ACPI Warning (tbfadt-0232): FADT (revision 5) is longer than > ACPI > > 2.0 version, truncating length 0x10C to 0xF4 [20070126] > > (XEN) ACPI: DSDT DC2DB188, A061 (r2 INTEL DQ77MK 32 INTL > > 20051117) > > (XEN) ACPI: FACS DC40A080, 0040 > > (XEN) ACPI: APIC DC2E5300, 0092 (r3 INTEL DQ77MK 32 AMI > > 10013) > > (XEN) ACPI: FPDT DC2E5398, 0044 (r1 INTEL DQ77MK 32 AMI > > 10013) > > (XEN) ACPI: TCPA DC2E53E0, 0032 (r2 INTEL DQ77MK 32 MSFT > > 1000013) > > (XEN) ACPI: MCFG DC2E5418, 003C (r1 INTEL DQ77MK 32 MSFT > > 97) > > (XEN) ACPI: HPET DC2E5458, 0038 (r1 INTEL DQ77MK 32 AMI. > > 5) > > (XEN) ACPI: SSDT DC2E5490, 036D (r1 INTEL DQ77MK 32 INTL > > 20091112) > > (XEN) ACPI: SSDT DC2E5800, 09AA (r1 INTEL DQ77MK 32 INTL > > 20051117) > > (XEN) ACPI: SSDT DC2E61B0, 0A92 (r1 INTEL DQ77MK 32 INTL > > 20051117) > > (XEN) ACPI: DMAR DC2E6C48, 00B8 (r1 INTEL DQ77MK 32 INTL > > 1) > > (XEN) ACPI: ASF! DC2E6D00, 00A5 (r32 INTEL DQ77MK 32 TFSM > > F4240) > > (XEN) System RAM: 32682MB (33467320kB) > > (XEN) Domain heap initialised > > (XEN) ACPI: 32/64X FACS address mismatch in FADT - > > dc40a080/0000000000000000, using 32 > > (XEN) Processor #0 7:10 APIC version 21 > > (XEN) Processor #2 7:10 APIC version 21 > > (XEN) Processor #4 7:10 APIC version 21 > > (XEN) Processor #6 7:10 APIC version 21 > > (XEN) Processor #1 7:10 APIC version 21 > > (XEN) Processor #3 7:10 APIC version 21 > > (XEN) Processor #5 7:10 APIC version 21 > > (XEN) Processor #7 7:10 APIC version 21 > > (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI 0-23 > > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > > (XEN) Switched to APIC driver x2apic_cluster. > > (XEN) x2APIC mode enabled. > > (XEN) Using scheduler: SMP Credit Scheduler (credit) > > (XEN) Detected 3392.369 MHz processor. > > (XEN) Initing memory sharing. > > (XEN) VMX: Supported advanced features: > > (XEN) - APIC MMIO access virtualisation > > (XEN) - APIC TPR shadow > > (XEN) - Extended Page Tables (EPT) > > (XEN) - Virtual-Processor Identifiers (VPID) > > (XEN) - Virtual NMI > > (XEN) - MSR direct-access bitmap > > (XEN) - Unrestricted Guest > > (XEN) EPT supports 2MB super page. > > (XEN) HVM: ASIDs enabled. > > (XEN) HVM: VMX enabled > > (XEN) HVM: Hardware Assisted Paging detected. > > (XEN) Intel VT-d Snoop Control not enabled. > > (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. > > (XEN) Intel VT-d Queued Invalidation enabled. > > (XEN) Intel VT-d Interrupt Remapping enabled. > > (XEN) I/O virtualisation enabled > > (XEN) - Dom0 mode: Relaxed > > (XEN) Enabled directed EOI with ioapic_ack_old on! > > (XEN) Total of 8 processors activated. > > (XEN) ENABLING IO-APIC IRQs > > (XEN) -> Using old ACK method > > (XEN) TSC is reliable, synchronization unnecessary > > (XEN) Platform timer appears to have unexpectedly wrapped 1 times. > > (XEN) Platform timer is 14.318MHz HPET > > (XEN) Allocated console ring of 16 KiB. > > (XEN) Brought up 8 CPUs > > (XEN) *** LOADING DOMAIN 0 *** > > (XEN) Xen kernel: 64-bit, lsb, compat32 > > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x1ae7000 > > (XEN) PHYSICAL MEMORY ARRANGEMENT: > > (XEN) Dom0 alloc.: 0000000804000000->0000000806000000 (319488 > pages > > to be allocated) > > (XEN) VIRTUAL MEMORY ARRANGEMENT: > > (XEN) Loaded kernel: ffffffff81000000->ffffffff81ae7000 > > (XEN) Init. ramdisk: ffffffff81ae7000->ffffffff81ae7000 > > (XEN) Phys-Mach map: ffffffff81ae7000->ffffffff81d67000 > > (XEN) Start info: ffffffff81d67000->ffffffff81d674b4 > > (XEN) Page tables: ffffffff81d68000->ffffffff81d7b000 > > (XEN) Boot stack: ffffffff81d7b000->ffffffff81d7c000 > > (XEN) TOTAL: ffffffff80000000->ffffffff82000000 > > (XEN) ENTRY ADDRESS: ffffffff815e3210 > > (XEN) Dom0 has maximum 8 VCPUs > > (XEN) [VT-D]iommu.c:718: BIOS did not enable IGD for VT properly. > > Disabling IGD VT-d engine. > > (XEN) Scrubbing Free RAM: done. > > (XEN) Xen trace buffers: disabled > > (XEN) Std. Loglevel: Errors and warnings > > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) > > (XEN) Xen is relinquishing VGA console. > > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to switch > > input to Xen) > > (XEN) Freed 172kB init memory. > > (XEN) traps.c:2333:d0 Domain attempted WRMSR 000000000000008b from > > 00000012:00000000 to 00000000:00000000. > > > > - Valtteri > > > > 2012/10/1 Pasi Kärkkäinen <[5]pasik@iki.fi> > > > > On Mon, Oct 01, 2012 at 09:12:50PM +0300, Valtteri Kiviniemi > wrote: > > > Hi, > > > > > > Lowering memory or vcpu''s does not help, problem is the > same. I > > originally > > > installed Xen 4.2.0 and the problem was same on that too. > Then I > > > downgraded back to 4.0.4 since I thought that this might be > a bug > > on > > > 4.2.0. I have been previously running Windows Server 2008 R2 > > succesfully > > > on Xen 4.0.x on different hardware with this same config. > > Hypervisor is > > > 64bit and windows is 64bit. > > > > > > Any ideas what to try next? > > > > > > > What kind of hardware is that? > > > > [6]xen.org automated testing regularly tests Windows VMs, and it > works > > OK there. > > > > -- Pasi > > > Ps. qemu-dm.log is the following: > > > > > > domid: 10 > > > config qemu network with xen bridge for tap10.0 xenbr0 > > > Using file /dev/virtuals/ts in read-write mode > > > Using file /media/iso/windows_server_2008_r2_sp1.iso in > read-only > > mode > > > Watching /local/domain/0/device-model/10/logdirty/cmd > > > Watching /local/domain/0/device-model/10/command > > > qemu_map_cache_init nr_buckets = 10000 size 4194304 > > > shared page at pfn feffd > > > buffered io page at pfn feffb > > > Guest uuid = 52f19e23-2955-c27d-a22c-60c5d8c60d5a > > > Time offset set 0 > > > populating video RAM at ff000000 > > > mapping video RAM from ff000000 > > > Register xen platform. > > > Done register platform. > > > platform_fixed_ioport: changed ro/rw state of ROM memory > area. > > now is rw > > > state. > > > > xs_read(/local/domain/0/device-model/10/xen_extended_power_mgmt): > > read > > > error > > > medium change watch on `hdc'' (index: 1): > > > /media/iso/windows_server_2008_r2_sp1.iso > > > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, > > size: 0 > > > Log-dirty: no command yet. > > > xs_read(/local/domain/10/log-throttling): read error > > > qemu: ignoring not-understood drive > > `/local/domain/10/log-throttling'' > > > medium change watch on `/local/domain/10/log-throttling'' - > > unknown device, > > > ignored > > > cirrus vga map change while on lfb mode > > > mapping vram to f0000000 - f0400000 > > > platform_fixed_ioport: changed ro/rw state of ROM memory > area. > > now is rw > > > state. > > > platform_fixed_ioport: changed ro/rw state of ROM memory > area. > > now is ro > > > state. > > > > > > 2012/10/1 Pasi Kärkkäinen <[1][7]pasik@iki.fi> > > > > > > On Mon, Oct 01, 2012 at 07:23:44PM +0300, Valtteri > Kiviniemi > > wrote: > > > > Hi, > > > > > > > > I have tried other config files, but the problem is > the > > same. At > > > the > > > > moment I''m using a config file from another server > where I > > have a > > > working > > > > Windows Server 2008 R2 installation, so I dont think > that > > there is > > > > anything wrong with my config: > > > > > > > > > > Did you try with less vcpus, for example 2 ? > > > how about with less memory, say 2 GB ? > > > > > > Did you try with later Xen versions? Is that a 32bit Xen, > or > > 64bit Xen > > > hypervisor? > > > > > > -- Pasi > > > > kernel = "/usr/lib/xen/boot/hvmloader" > > > > builder = "hvm" > > > > shadow_memory = "8" > > > > memory = "4096" > > > > name = "ts" > > > > vcpus = "8" > > > > cpus = ["0", "1", "2", "3", "4", "5", "6", "7"] > > > > pae = "1" > > > > acpi = "1" > > > > apic = "1" > > > > vfb = [ ''type=vnc, vnclisten=10.100.100.50, > vncpasswd=xxx'' > > ] > > > > xen_extended_power_mgmt = "0" > > > > vif = [ "type=ioemu, mac=00:16:3e:d7:d7:5d, > bridge=xenbr0" > > ] > > > > disk = [ "phy:/dev/virtuals/ts,hda,w", > > > > > > "file:/media/iso/windows_server_2008_r2_sp1.iso,hdc:cdrom,r" ] > > > > on_poweroff = "destroy" > > > > on_reboot = "restart" > > > > on_crash = "restart" > > > > viridian = "1" > > > > device_model = "/usr/lib/xen/bin/qemu-dm" > > > > boot = "dc" > > > > snapshot = "0" > > > > vncconsole = "1" > > > > sdl = "0" > > > > opengl = "0" > > > > vnc = "1" > > > > nographic = "0" > > > > stdvga = "0" > > > > tsc_mode = "1" > > > > monitor = "0" > > > > localtime = "1" > > > > usb = "0" > > > > keymap = "fi" > > > > xen_platform_pci = "1" > > > > pci_msitranslate = "1" > > > > pci_power_mgmt = "0" > > > > > > > > 2012/10/1 Pasi Kärkkäinen <[1][2][8]pasik@iki.fi> > > > > > > > > On Mon, Oct 01, 2012 at 06:46:08PM +0300, Valtteri > > Kiviniemi > > > wrote: > > > > > Hi, > > > > > > > > > > Yes, I have viridian=1 on my domU config. > > > > > > > > > > > > > Try with some known good domU configfile. > > > > > > > > -- Pasi > > > > > 2012/10/1 Pasi Kärkkäinen > > <[1][2][3][9]pasik@iki.fi> > > > > > > > > > > On Mon, Oct 01, 2012 at 05:06:53PM +0300, > > Valtteri > > > Kiviniemi > > > > wrote: > > > > > > Hi, > > > > > > > > > > > > I''m now using 3.6.0 and can''t reproduce > that > > crash > > > anymore, > > > > so it > > > > > seems > > > > > > that it was a kernel bug. > > > > > > > > > > > > > > > > OK. > > > > > > However I''m still getting black screen > on > > VNC > > > > > > when trying to install Windows Server > 2008 > > R2. I can > > > see the > > > > > "windows is > > > > > > loading files" screen but after the > > installer starts > > > the VNC > > > > > display goes > > > > > > black. > > > > > > > > > > > > Any ideas? > > > > > > > > > > > > > > > > Do you have viridian=1 specified for the > windows > > vm? > > > > > > > > > > -- Pasi > > > > > > > > > > > - Valtteri > > > > > > > > > > > > 2012/10/1 Pasi Kärkkäinen > > <[1][2][3][4][10]pasik@iki.fi> > > > > > > > > > > > > On Sun, Sep 30, 2012 at 11:18:03PM > +0300, > > Valtteri > > > > Kiviniemi > > > > > wrote: > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > Hello, > > > > > > > I''m trying to get Windows Server > 2008 > > R2 > > > installation > > > > > booting on > > > > > > Xen > > > > > > > 4.0.4. Using the following > config: > > > > > > > > > > > > > > > > > > > <snip> > > > > > > > > > > > > > > The domU will start booting just > > fine, but > > > after a > > > > few > > > > > minutes the > > > > > > VNC > > > > > > > screen goes black. After that > when > > typing "xm > > > destroy > > > > ts" it > > > > > will > > > > > > trigger > > > > > > > a kernel BUG: > > > > > > > > > > > > > > BUG: unable to handle kernel NULL > > pointer > > > dereference > > > > at > > > > > > 0000000000000030 > > > > > > > IP: [<ffffffff810c50c4>] > > iput+0x3e/0x195 > > > > > > > PGD 0 > > > > > > > Oops: 0000 [#1] SMP > > > > > > > CPU 6 > > > > > > > Pid: 3571, comm: qemu-dm Not > tainted > > > 3.5.0-dom0 #1 > > > > > > > > > > > > First of all upgrade to latest 3.5.x > Linux > > kernel > > > release > > > > .. so > > > > > at least > > > > > > 3.5.4. > > > > > > > > > > > > -- Pasi > > > > > > > > > > > > > /DQ77MK > > > > > > > RIP: e030:[<ffffffff810c50c4>] > > > [<ffffffff810c50c4>] > > > > > > iput+0x3e/0x195 > > > > > > > RSP: e02b:ffff8800389ffbf8 > EFLAGS: > > 00010246 > > > > > > > RAX: 0000000000000001 RBX: > > ffff8800377b0720 > > > RCX: > > > > > ffff8800501c0000 > > > > > > > RDX: ffff8800501c0000 RSI: > > ffff8800377b0790 > > > RDI: > > > > > ffff8800377b0790 > > > > > > > RBP: 0000000000000000 R08: > > ffffffff815cdd00 > > > R09: > > > > > 0000000000000016 > > > > > > > R10: fefefefefefefeff R11: > > ffff8800377b0400 > > > R12: > > > > > 00000001000a3e0c > > > > > > > R13: 0000000000000000 R14: > > 00000001000a3e0c > > > R15: > > > > > ffff8800389ffc28 > > > > > > > FS: 00007f1af70a8700(0000) > > > GS:ffff880050180000(0000) > > > > > > > knlGS:0000000000000000 > > > > > > > CS: e033 DS: 0000 ES: 0000 CR0: > > > 000000008005003b > > > > > > > CR2: 0000000000000030 CR3: > > 000000000156d000 > > > CR4: > > > > > 0000000000002660 > > > > > > > DR0: 0000000000000000 DR1: > > 0000000000000000 > > > DR2: > > > > > 0000000000000000 > > > > > > > DR3: 0000000000000000 DR6: > > 00000000ffff0ff0 > > > DR7: > > > > > 0000000000000400 > > > > > > > Process qemu-dm (pid: 3571, > > threadinfo > > > > ffff8800389fe000, > > > > > task > > > > > > > ffff88003a721260) > > > > > > > Stack: > > > > > > > ffff88003a6d6400 > ffff8800377b0000 > > > 00000001000a3e0c > > > > > > ffffffff8133ce8f > > > > > > > ffff8800377b0400 > ffffffff8134b6cd > > > ffff8800389ffc28 > > > > > > ffff8800389ffc28 > > > > > > > ffff8800377b00f8 > ffff8800377b0680 > > > ffff880038cdcd60 > > > > > > ffff8800377b0000 > > > > > > > Call Trace: > > > > > > > [<ffffffff8133ce8f>] ? > > > sk_release_kernel+0x23/0x39 > > > > > > > [<ffffffff8134b6cd>] ? > > > netdev_run_todo+0x1e9/0x206 > > > > > > > [<ffffffff8129798f>] ? > > > tun_chr_close+0x4c/0x7b > > > > > > > [<ffffffff810b39d3>] ? > > fput+0xe4/0x1c5 > > > > > > > [<ffffffff810b202c>] ? > > filp_close+0x61/0x68 > > > > > > > [<ffffffff81035e62>] ? > > > put_files_struct+0x62/0xb9 > > > > > > > [<ffffffff81036374>] ? > > do_exit+0x24a/0x74c > > > > > > > [<ffffffff81036906>] ? > > > do_group_exit+0x6b/0x9d > > > > > > > [<ffffffff8103ea0b>] ? > > > > get_signal_to_deliver+0x449/0x46e > > > > > > > [<ffffffff81009fa5>] ? > > do_signal+0x28/0x4c4 > > > > > > > [<ffffffff81027079>] ? > > > > pvclock_clocksource_read+0x48/0xbf > > > > > > > [<ffffffff8105b745>] ? > > ktime_get_ts+0x66/0xa8 > > > > > > > [<ffffffff810bfb18>] ? > > > > poll_select_copy_remaining+0xe0/0xf5 > > > > > > > [<ffffffff8100a48d>] ? > > > do_notify_resume+0x3b/0x74 > > > > > > > [<ffffffff81411a70>] ? > > int_signal+0x12/0x17 > > > > > > > Code: 00 00 00 40 74 02 0f 0b 48 > 8d > > 77 70 48 > > > 8d bf 08 > > > > 01 00 > > > > > 00 e8 > > > > > > 8b 71 10 > > > > > > > 00 85 c0 0f 84 5d 01 00 00 48 8b > 6b > > 18 f6 83 > > > 80 00 00 > > > > 00 08 > > > > > <4c> 8b > > > > > > 65 30 > > > > > > > 74 11 be 68 05 00 00 48 c7 c7 8e > df > > 4f 81 e8 > > > bb d0 > > > > > > > RIP [<ffffffff810c50c4>] > > iput+0x3e/0x195 > > > > > > > RSP <ffff8800389ffbf8> > > > > > > > CR2: 0000000000000030 > > > > > > > ---[ end trace 67cc1654658fedcc > ]--- > > > > > > > Fixing recursive fault but > reboot is > > needed! > > > > > > > > > > > > > > I also tested Xen 4.2.0 and > problem > > is the > > > same. So > > > > is this > > > > > a Xen > > > > > > bug or a > > > > > > > kernel bug? I am running vanilla > > > > [1][2][3][4][5][11]kernel.org kernel > > > > > 3.5.0 and > > > > > > my > > > > > > > hardware is Intel Core i7-3770 > CPU > > and Intel > > > DQ77MK > > > > > motherboard > > > > > > with > > > > > > > latest bios. > > > > > > > > > > > > > > Best regards, > > > > > > > Valtteri Kiviniemi > > > > > > > > > > > > > > References > > > > > > > > > > > > > > Visible links > > > > > > > 1. [3][4][5][6][12] > http://kernel.org/ > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > Xen-devel mailing list > > > > > > > [4][5][6][7][13] > Xen-devel@lists.xen.org > > > > > > > > > [5][6][7][8][14]http://lists.xen.org/xen-devel > > > > > > > > > > > > References > > > > > > > > > > > > Visible links > > > > > > 1. mailto:[7][8][9][15]pasik@iki.fi > > > > > > 2. [8][9][10][16]http://kernel.org/ > > > > > > 3. [9][10][11][17]http://kernel.org/ > > > > > > 4. > > mailto:[10][11][12][18]Xen-devel@lists.xen.org > > > > > > 5. > > [11][12][13][19]http://lists.xen.org/xen-devel > > > > > > > > > > References > > > > > > > > > > Visible links > > > > > 1. mailto:[13][14][20]pasik@iki.fi > > > > > 2. mailto:[14][15][21]pasik@iki.fi > > > > > 3. [15][16][22]http://kernel.org/ > > > > > 4. [16][17][23]http://kernel.org/ > > > > > 5. mailto:[17][18][24]Xen-devel@lists.xen.org > > > > > 6. [18][19][25]http://lists.xen.org/xen-devel > > > > > 7. mailto:[19][20][26]pasik@iki.fi > > > > > 8. [20][21][27]http://kernel.org/ > > > > > 9. [21][22][28]http://kernel.org/ > > > > > 10. mailto:[22][23][29]Xen-devel@lists.xen.org > > > > > 11. [23][24][30]http://lists.xen.org/xen-devel > > > > > > > > References > > > > > > > > Visible links > > > > 1. mailto:[25][31]pasik@iki.fi > > > > 2. mailto:[26][32]pasik@iki.fi > > > > 3. mailto:[27][33]pasik@iki.fi > > > > 4. [28][34]http://kernel.org/ > > > > 5. [29][35]http://kernel.org/ > > > > 6. mailto:[30][36]Xen-devel@lists.xen.org > > > > 7. [31][37]http://lists.xen.org/xen-devel > > > > 8. mailto:[32][38]pasik@iki.fi > > > > 9. [33][39]http://kernel.org/ > > > > 10. [34][40]http://kernel.org/ > > > > 11. mailto:[35][41]Xen-devel@lists.xen.org > > > > 12. [36][42]http://lists.xen.org/xen-devel > > > > 13. mailto:[37][43]pasik@iki.fi > > > > 14. mailto:[38][44]pasik@iki.fi > > > > 15. [39][45]http://kernel.org/ > > > > 16. [40][46]http://kernel.org/ > > > > 17. mailto:[41][47]Xen-devel@lists.xen.org > > > > 18. [42][48]http://lists.xen.org/xen-devel > > > > 19. mailto:[43][49]pasik@iki.fi > > > > 20. [44][50]http://kernel.org/ > > > > 21. [45][51]http://kernel.org/ > > > > 22. mailto:[46][52]Xen-devel@lists.xen.org > > > > 23. [47][53]http://lists.xen.org/xen-devel > > > > > > References > > > > > > Visible links > > > 1. mailto:[54]pasik@iki.fi > > > 2. mailto:[55]pasik@iki.fi > > > 3. mailto:[56]pasik@iki.fi > > > 4. mailto:[57]pasik@iki.fi > > > 5. [58]http://kernel.org/ > > > 6. [59]http://kernel.org/ > > > 7. mailto:[60]Xen-devel@lists.xen.org > > > 8. [61]http://lists.xen.org/xen-devel > > > 9. mailto:[62]pasik@iki.fi > > > 10. [63]http://kernel.org/ > > > 11. [64]http://kernel.org/ > > > 12. mailto:[65]Xen-devel@lists.xen.org > > > 13. [66]http://lists.xen.org/xen-devel > > > 14. mailto:[67]pasik@iki.fi > > > 15. mailto:[68]pasik@iki.fi > > > 16. [69]http://kernel.org/ > > > 17. [70]http://kernel.org/ > > > 18. mailto:[71]Xen-devel@lists.xen.org > > > 19. [72]http://lists.xen.org/xen-devel > > > 20. mailto:[73]pasik@iki.fi > > > 21. [74]http://kernel.org/ > > > 22. [75]http://kernel.org/ > > > 23. mailto:[76]Xen-devel@lists.xen.org > > > 24. [77]http://lists.xen.org/xen-devel > > > 25. mailto:[78]pasik@iki.fi > > > 26. mailto:[79]pasik@iki.fi > > > 27. mailto:[80]pasik@iki.fi > > > 28. [81]http://kernel.org/ > > > 29. [82]http://kernel.org/ > > > 30. mailto:[83]Xen-devel@lists.xen.org > > > 31. [84]http://lists.xen.org/xen-devel > > > 32. mailto:[85]pasik@iki.fi > > > 33. [86]http://kernel.org/ > > > 34. [87]http://kernel.org/ > > > 35. mailto:[88]Xen-devel@lists.xen.org > > > 36. [89]http://lists.xen.org/xen-devel > > > 37. mailto:[90]pasik@iki.fi > > > 38. mailto:[91]pasik@iki.fi > > > 39. [92]http://kernel.org/ > > > 40. [93]http://kernel.org/ > > > 41. mailto:[94]Xen-devel@lists.xen.org > > > 42. [95]http://lists.xen.org/xen-devel > > > 43. mailto:[96]pasik@iki.fi > > > 44. [97]http://kernel.org/ > > > 45. [98]http://kernel.org/ > > > 46. mailto:[99]Xen-devel@lists.xen.org > > > 47. [100]http://lists.xen.org/xen-devel > > > > References > > > > Visible links > > 1. mailto:kiviniemi.valtteri@gmail.com > > 2. http://ark.intel.com/products/65719/ > > 3. > http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > > 4. mailto:root@dataproof.fi > > 5. mailto:pasik@iki.fi > > 6. http://xen.org/ > > 7. mailto:pasik@iki.fi > > 8. mailto:pasik@iki.fi > > 9. mailto:pasik@iki.fi > > 10. mailto:pasik@iki.fi > > 11. http://kernel.org/ > > 12. http://kernel.org/ > > 13. mailto:Xen-devel@lists.xen.org > > 14. http://lists.xen.org/xen-devel > > 15. mailto:pasik@iki.fi > > 16. http://kernel.org/ > > 17. http://kernel.org/ > > 18. mailto:Xen-devel@lists.xen.org > > 19. http://lists.xen.org/xen-devel > > 20. mailto:pasik@iki.fi > > 21. mailto:pasik@iki.fi > > 22. http://kernel.org/ > > 23. http://kernel.org/ > > 24. mailto:Xen-devel@lists.xen.org > > 25. http://lists.xen.org/xen-devel > > 26. mailto:pasik@iki.fi > > 27. http://kernel.org/ > > 28. http://kernel.org/ > > 29. mailto:Xen-devel@lists.xen.org > > 30. http://lists.xen.org/xen-devel > > 31. mailto:pasik@iki.fi > > 32. mailto:pasik@iki.fi > > 33. mailto:pasik@iki.fi > > 34. http://kernel.org/ > > 35. http://kernel.org/ > > 36. mailto:Xen-devel@lists.xen.org > > 37. http://lists.xen.org/xen-devel > > 38. mailto:pasik@iki.fi > > 39. http://kernel.org/ > > 40. http://kernel.org/ > > 41. mailto:Xen-devel@lists.xen.org > > 42. http://lists.xen.org/xen-devel > > 43. mailto:pasik@iki.fi > > 44. mailto:pasik@iki.fi > > 45. http://kernel.org/ > > 46. http://kernel.org/ > > 47. mailto:Xen-devel@lists.xen.org > > 48. http://lists.xen.org/xen-devel > > 49. mailto:pasik@iki.fi > > 50. http://kernel.org/ > > 51. http://kernel.org/ > > 52. mailto:Xen-devel@lists.xen.org > > 53. http://lists.xen.org/xen-devel > > 54. mailto:pasik@iki.fi > > 55. mailto:pasik@iki.fi > > 56. mailto:pasik@iki.fi > > 57. mailto:pasik@iki.fi > > 58. http://kernel.org/ > > 59. http://kernel.org/ > > 60. mailto:Xen-devel@lists.xen.org > > 61. http://lists.xen.org/xen-devel > > 62. mailto:pasik@iki.fi > > 63. http://kernel.org/ > > 64. http://kernel.org/ > > 65. mailto:Xen-devel@lists.xen.org > > 66. http://lists.xen.org/xen-devel > > 67. mailto:pasik@iki.fi > > 68. mailto:pasik@iki.fi > > 69. http://kernel.org/ > > 70. http://kernel.org/ > > 71. mailto:Xen-devel@lists.xen.org > > 72. http://lists.xen.org/xen-devel > > 73. mailto:pasik@iki.fi > > 74. http://kernel.org/ > > 75. http://kernel.org/ > > 76. mailto:Xen-devel@lists.xen.org > > 77. http://lists.xen.org/xen-devel > > 78. mailto:pasik@iki.fi > > 79. mailto:pasik@iki.fi > > 80. mailto:pasik@iki.fi > > 81. http://kernel.org/ > > 82. http://kernel.org/ > > 83. mailto:Xen-devel@lists.xen.org > > 84. http://lists.xen.org/xen-devel > > 85. mailto:pasik@iki.fi > > 86. http://kernel.org/ > > 87. http://kernel.org/ > > 88. mailto:Xen-devel@lists.xen.org > > 89. http://lists.xen.org/xen-devel > > 90. mailto:pasik@iki.fi > > 91. mailto:pasik@iki.fi > > 92. http://kernel.org/ > > 93. http://kernel.org/ > > 94. mailto:Xen-devel@lists.xen.org > > 95. http://lists.xen.org/xen-devel > > 96. mailto:pasik@iki.fi > > 97. http://kernel.org/ > > 98. http://kernel.org/ > > 99. mailto:Xen-devel@lists.xen.org > > 100. http://lists.xen.org/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Pasi Kärkkäinen
2012-Oct-02 13:14 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
On Tue, Oct 02, 2012 at 04:01:04PM +0300, Valtteri Kiviniemi wrote:> Hi, > > I already tried 3.2, 3.5, 3.5.0, 3.6.0-rc7 and 3.6.0, same problem all of > those. My dom0 config is the same config that I''am using on other server > where HVM is working, so I dont think that it is a config problem. I have > triple checked everything and all should be ok. dom0 dmesg shows the same > crash that I have previously posted here. /var/log/xen/ does not contain > any specific errors. > > Could this be some kind of broblem with my motherboard bios being buggy or > CPU not supported? I''m using the new intel Ivy Bridge processor which has > integrated GPU, but that should not probably cause these kind of problems. > Or maybe some ACPI problem? xm dmesg is showing some notices about ACPI. > Is there any ACPI kernel parameters that I should try booting? This has to > be somekind of problem with my hardware, or then maybe it could be a > kernel problem too. I just really cant figure this out myself, I have > tried everything. >Hmm.. I have some distant memories of seeing a patch that fixes a bug on recent Ivy Bridge systems, but I can''t find a link right now. Maybe you''re affected by that.. Also: Did you already post the crash log, with all the debug/verbose options enabled for both Xen and dom0 kernel? -- Pasi> Lets take a quick summary of what has been tested, what hardware I''m using > etc. > > Xen-versions tested: 4.2.0, 4.0.4 > Kernel-versions tested: 3.2.0, 3.5.0, 3.5.4, 3.6.0-rc7, 3.6.0 > > Host OS: Debian testing/wheezy, udev version 175-7, 2.13-35, python > version 2.7.3~rc2-2.1 > > Hardware: > > CPU: Intel Core i7-3770 3.4GHz > MB: Intel DQ77MK (latest bios updated) > Memory: 32GB (4 x 8GB DDR3-1600MHz) > > All relevant log files and configs: > > dom0 dmesg: [1]http://nago.fi/dmesg.txt > qemu-dm log: [2]http://nago.fi/qemu-dm.txt > xm dmesg log: [3]http://nago.fi/xm-dmesg.txt > domU config: [4]http://nago.fi/domu-config.txt > dom0 kernel config: [5]http://nago.fi/dom0-config.txt > > I have also tried playing with every setting on that domU that I can think > of and tried different configs etc. > > - Valtteri > > 2012/10/2 Pasi Kärkkäinen <[6]pasik@iki.fi> > > On Tue, Oct 02, 2012 at 03:11:07PM +0300, Valtteri Kiviniemi wrote: > > Hi, > > > > Another update: > > > > I wanted to check that if a Linux HVM would boot with working VNC > console, > > so I tried to launch a Debian Squeeze installer on HVM. It refused > to > > start ant told me that vbd hotplug scripts were not working. After > that > > failure even the Windows domU would not anymore start which was > previously > > starting ok. > > > > The hotplug scripts also starts hanging on the processes. > > > > root 9401 0.1 0.1 17700 1640 ? S 15:05 0:00 > /bin/bash > > /etc/xen/scripts/xen-hotplug-cleanup > > root 9441 0.1 0.1 17700 1644 ? S 15:05 0:00 > /bin/bash > > /etc/xen/scripts/xen-hotplug-cleanup > > root 9481 0.1 0.1 17700 1640 ? S 15:05 0:00 > /bin/bash > > /etc/xen/scripts/xen-hotplug-cleanup > > root 9560 0.1 0.1 17700 1640 ? S 15:05 0:00 > /bin/bash > > /etc/xen/scripts/xen-hotplug-cleanup > > root 10738 0.1 0.1 17696 1636 ? S 15:05 0:00 > /bin/bash > > /etc/xen/scripts/xen-hotplug-cleanup > > root 10747 0.1 0.1 17792 1736 ? S 15:05 0:00 > /bin/bash > > /etc/xen/scripts/block remove > > root 11286 0.0 0.0 4080 324 ? S 15:06 0:00 > sleep 1 > > root 11290 0.0 0.0 4080 324 ? S 15:06 0:00 > sleep 1 > > root 11294 0.0 0.0 4080 324 ? S 15:06 0:00 > sleep 1 > > root 11298 0.0 0.0 4080 324 ? S 15:06 0:00 > sleep 1 > > root 11302 0.0 0.0 4080 320 ? S 15:06 0:00 > sleep 1 > > root 11306 0.0 0.0 4080 320 ? S 15:06 0:00 > sleep 1 > > > > Then I did a xm destroy and I had again the kernel BUG on dmesg. So > it > > seems that the problem is not fixed by using 3.6.0. Udev version is > 175-7. > > > > So you have definitely something broken in your system, > probably in your dom0 kernel. Try with Linux 3.5.4 or 3.4.x, > and see how that goes. > > Any errors in dom0 dmesg? How about in /var/log/xen/* ? > > -- Pasi > > > > > > > 2012/10/1 Valtteri Kiviniemi <[1][7]kiviniemi.valtteri@gmail.com> > > > > Hi, > > > > CPU: Intel Core i7-3770 3.4GHz > > [2][8]http://ark.intel.com/products/65719/ > > > > MB: Intel DQ77MK (latest bios updated) > > > [3][9]http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > > > > Memory: 32GB (4 x 8GB DDR3-1600MHz) > > > > Host is Debian wheezy/testing, Xen 4.0.4 and latest 3.6.0 kernel. > > > > Noticed also some errors in xm dmesg: > > > > root@xen-2:~# xm dmesg > > > > (XEN) Xen version 4.0.4 ([4][10]root@dataproof.fi) (gcc version > 4.7.1 > > (Debian 4.7.1-7) ) Sun Sep 30 20:28:26 EEST 2012 > > (XEN) Latest ChangeSet: unavailable > > (XEN) Bootloader: GNU GRUB 0.97 > > (XEN) Command line: dom0_mem=1280M cpufreq=xen clocksource=hpet > > (XEN) Video information: > > (XEN) VGA is text mode 80x25, font 8x16 > > (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds > > (XEN) EDID info not retrieved because no DDC retrieval method > detected > > (XEN) Disc information: > > (XEN) Found 4 MBR signatures > > (XEN) Found 4 EDD information structures > > (XEN) Xen-e820 RAM map: > > (XEN) 0000000000000000 - 000000000009d800 (usable) > > (XEN) 000000000009d800 - 00000000000a0000 (reserved) > > (XEN) 00000000000e0000 - 0000000000100000 (reserved) > > (XEN) 0000000000100000 - 0000000020000000 (usable) > > (XEN) 0000000020000000 - 0000000020200000 (reserved) > > (XEN) 0000000020200000 - 0000000040004000 (usable) > > (XEN) 0000000040004000 - 0000000040005000 (reserved) > > (XEN) 0000000040005000 - 00000000dbe44000 (usable) > > (XEN) 00000000dbe44000 - 00000000dc2d7000 (reserved) > > (XEN) 00000000dc2d7000 - 00000000dc2e7000 (ACPI data) > > (XEN) 00000000dc2e7000 - 00000000dc40c000 (ACPI NVS) > > (XEN) 00000000dc40c000 - 00000000dc6af000 (reserved) > > (XEN) 00000000dc6af000 - 00000000dc6b0000 (usable) > > (XEN) 00000000dc6b0000 - 00000000dc6f3000 (ACPI NVS) > > (XEN) 00000000dc6f3000 - 00000000dd000000 (usable) > > (XEN) 00000000dd800000 - 00000000dfa00000 (reserved) > > (XEN) 00000000f8000000 - 00000000fc000000 (reserved) > > (XEN) 00000000fec00000 - 00000000fec01000 (reserved) > > (XEN) 00000000fed00000 - 00000000fed04000 (reserved) > > (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) > > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > > (XEN) 00000000ff000000 - 0000000100000000 (reserved) > > (XEN) 0000000100000000 - 000000081e600000 (usable) > > (XEN) ACPI: RSDP 000F0490, 0024 (r2 INTEL) > > (XEN) ACPI: XSDT DC2DB080, 007C (r1 INTEL DQ77MK 32 AMI > > 10013) > > (XEN) ACPI: FACP DC2E51F0, 010C (r5 INTEL DQ77MK 32 AMI > > 10013) > > (XEN) ACPI Warning (tbfadt-0232): FADT (revision 5) is longer > than ACPI > > 2.0 version, truncating length 0x10C to 0xF4 [20070126] > > (XEN) ACPI: DSDT DC2DB188, A061 (r2 INTEL DQ77MK 32 INTL > > 20051117) > > (XEN) ACPI: FACS DC40A080, 0040 > > (XEN) ACPI: APIC DC2E5300, 0092 (r3 INTEL DQ77MK 32 AMI > > 10013) > > (XEN) ACPI: FPDT DC2E5398, 0044 (r1 INTEL DQ77MK 32 AMI > > 10013) > > (XEN) ACPI: TCPA DC2E53E0, 0032 (r2 INTEL DQ77MK 32 MSFT > > 1000013) > > (XEN) ACPI: MCFG DC2E5418, 003C (r1 INTEL DQ77MK 32 MSFT > > 97) > > (XEN) ACPI: HPET DC2E5458, 0038 (r1 INTEL DQ77MK 32 AMI. > > 5) > > (XEN) ACPI: SSDT DC2E5490, 036D (r1 INTEL DQ77MK 32 INTL > > 20091112) > > (XEN) ACPI: SSDT DC2E5800, 09AA (r1 INTEL DQ77MK 32 INTL > > 20051117) > > (XEN) ACPI: SSDT DC2E61B0, 0A92 (r1 INTEL DQ77MK 32 INTL > > 20051117) > > (XEN) ACPI: DMAR DC2E6C48, 00B8 (r1 INTEL DQ77MK 32 INTL > > 1) > > (XEN) ACPI: ASF! DC2E6D00, 00A5 (r32 INTEL DQ77MK 32 > TFSM > > F4240) > > (XEN) System RAM: 32682MB (33467320kB) > > (XEN) Domain heap initialised > > (XEN) ACPI: 32/64X FACS address mismatch in FADT - > > dc40a080/0000000000000000, using 32 > > (XEN) Processor #0 7:10 APIC version 21 > > (XEN) Processor #2 7:10 APIC version 21 > > (XEN) Processor #4 7:10 APIC version 21 > > (XEN) Processor #6 7:10 APIC version 21 > > (XEN) Processor #1 7:10 APIC version 21 > > (XEN) Processor #3 7:10 APIC version 21 > > (XEN) Processor #5 7:10 APIC version 21 > > (XEN) Processor #7 7:10 APIC version 21 > > (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, GSI > 0-23 > > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > > (XEN) Switched to APIC driver x2apic_cluster. > > (XEN) x2APIC mode enabled. > > (XEN) Using scheduler: SMP Credit Scheduler (credit) > > (XEN) Detected 3392.369 MHz processor. > > (XEN) Initing memory sharing. > > (XEN) VMX: Supported advanced features: > > (XEN) - APIC MMIO access virtualisation > > (XEN) - APIC TPR shadow > > (XEN) - Extended Page Tables (EPT) > > (XEN) - Virtual-Processor Identifiers (VPID) > > (XEN) - Virtual NMI > > (XEN) - MSR direct-access bitmap > > (XEN) - Unrestricted Guest > > (XEN) EPT supports 2MB super page. > > (XEN) HVM: ASIDs enabled. > > (XEN) HVM: VMX enabled > > (XEN) HVM: Hardware Assisted Paging detected. > > (XEN) Intel VT-d Snoop Control not enabled. > > (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. > > (XEN) Intel VT-d Queued Invalidation enabled. > > (XEN) Intel VT-d Interrupt Remapping enabled. > > (XEN) I/O virtualisation enabled > > (XEN) - Dom0 mode: Relaxed > > (XEN) Enabled directed EOI with ioapic_ack_old on! > > (XEN) Total of 8 processors activated. > > (XEN) ENABLING IO-APIC IRQs > > (XEN) -> Using old ACK method > > (XEN) TSC is reliable, synchronization unnecessary > > (XEN) Platform timer appears to have unexpectedly wrapped 1 > times. > > (XEN) Platform timer is 14.318MHz HPET > > (XEN) Allocated console ring of 16 KiB. > > (XEN) Brought up 8 CPUs > > (XEN) *** LOADING DOMAIN 0 *** > > (XEN) Xen kernel: 64-bit, lsb, compat32 > > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> > 0x1ae7000 > > (XEN) PHYSICAL MEMORY ARRANGEMENT: > > (XEN) Dom0 alloc.: 0000000804000000->0000000806000000 (319488 > pages > > to be allocated) > > (XEN) VIRTUAL MEMORY ARRANGEMENT: > > (XEN) Loaded kernel: ffffffff81000000->ffffffff81ae7000 > > (XEN) Init. ramdisk: ffffffff81ae7000->ffffffff81ae7000 > > (XEN) Phys-Mach map: ffffffff81ae7000->ffffffff81d67000 > > (XEN) Start info: ffffffff81d67000->ffffffff81d674b4 > > (XEN) Page tables: ffffffff81d68000->ffffffff81d7b000 > > (XEN) Boot stack: ffffffff81d7b000->ffffffff81d7c000 > > (XEN) TOTAL: ffffffff80000000->ffffffff82000000 > > (XEN) ENTRY ADDRESS: ffffffff815e3210 > > (XEN) Dom0 has maximum 8 VCPUs > > (XEN) [VT-D]iommu.c:718: BIOS did not enable IGD for VT properly. > > Disabling IGD VT-d engine. > > (XEN) Scrubbing Free RAM: done. > > (XEN) Xen trace buffers: disabled > > (XEN) Std. Loglevel: Errors and warnings > > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings) > > (XEN) Xen is relinquishing VGA console. > > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to > switch > > input to Xen) > > (XEN) Freed 172kB init memory. > > (XEN) traps.c:2333:d0 Domain attempted WRMSR 000000000000008b > from > > 00000012:00000000 to 00000000:00000000. > > > > - Valtteri > > > > 2012/10/1 Pasi Kärkkäinen <[5][11]pasik@iki.fi> > > > > On Mon, Oct 01, 2012 at 09:12:50PM +0300, Valtteri Kiviniemi > wrote: > > > Hi, > > > > > > Lowering memory or vcpu''s does not help, problem is the > same. I > > originally > > > installed Xen 4.2.0 and the problem was same on that too. > Then I > > > downgraded back to 4.0.4 since I thought that this might > be a bug > > on > > > 4.2.0. I have been previously running Windows Server 2008 > R2 > > succesfully > > > on Xen 4.0.x on different hardware with this same config. > > Hypervisor is > > > 64bit and windows is 64bit. > > > > > > Any ideas what to try next? > > > > > > > What kind of hardware is that? > > > > [6][12]xen.org automated testing regularly tests Windows VMs, > and it works > > OK there. > > > > -- Pasi > > > Ps. qemu-dm.log is the following: > > > > > > domid: 10 > > > config qemu network with xen bridge for tap10.0 xenbr0 > > > Using file /dev/virtuals/ts in read-write mode > > > Using file /media/iso/windows_server_2008_r2_sp1.iso in > read-only > > mode > > > Watching /local/domain/0/device-model/10/logdirty/cmd > > > Watching /local/domain/0/device-model/10/command > > > qemu_map_cache_init nr_buckets = 10000 size 4194304 > > > shared page at pfn feffd > > > buffered io page at pfn feffb > > > Guest uuid = 52f19e23-2955-c27d-a22c-60c5d8c60d5a > > > Time offset set 0 > > > populating video RAM at ff000000 > > > mapping video RAM from ff000000 > > > Register xen platform. > > > Done register platform. > > > platform_fixed_ioport: changed ro/rw state of ROM memory > area. > > now is rw > > > state. > > > > xs_read(/local/domain/0/device-model/10/xen_extended_power_mgmt): > > read > > > error > > > medium change watch on `hdc'' (index: 1): > > > /media/iso/windows_server_2008_r2_sp1.iso > > > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: > 0, > > size: 0 > > > Log-dirty: no command yet. > > > xs_read(/local/domain/10/log-throttling): read error > > > qemu: ignoring not-understood drive > > `/local/domain/10/log-throttling'' > > > medium change watch on `/local/domain/10/log-throttling'' - > > unknown device, > > > ignored > > > cirrus vga map change while on lfb mode > > > mapping vram to f0000000 - f0400000 > > > platform_fixed_ioport: changed ro/rw state of ROM memory > area. > > now is rw > > > state. > > > platform_fixed_ioport: changed ro/rw state of ROM memory > area. > > now is ro > > > state. > > > > > > 2012/10/1 Pasi Kärkkäinen <[1][7][13]pasik@iki.fi> > > > > > > On Mon, Oct 01, 2012 at 07:23:44PM +0300, Valtteri > Kiviniemi > > wrote: > > > > Hi, > > > > > > > > I have tried other config files, but the problem is > the > > same. At > > > the > > > > moment I''m using a config file from another server > where I > > have a > > > working > > > > Windows Server 2008 R2 installation, so I dont > think that > > there is > > > > anything wrong with my config: > > > > > > > > > > Did you try with less vcpus, for example 2 ? > > > how about with less memory, say 2 GB ? > > > > > > Did you try with later Xen versions? Is that a 32bit > Xen, or > > 64bit Xen > > > hypervisor? > > > > > > -- Pasi > > > > kernel = "/usr/lib/xen/boot/hvmloader" > > > > builder = "hvm" > > > > shadow_memory = "8" > > > > memory = "4096" > > > > name = "ts" > > > > vcpus = "8" > > > > cpus = ["0", "1", "2", "3", "4", "5", "6", "7"] > > > > pae = "1" > > > > acpi = "1" > > > > apic = "1" > > > > vfb = [ ''type=vnc, vnclisten=10.100.100.50, > vncpasswd=xxx'' > > ] > > > > xen_extended_power_mgmt = "0" > > > > vif = [ "type=ioemu, mac=00:16:3e:d7:d7:5d, > bridge=xenbr0" > > ] > > > > disk = [ "phy:/dev/virtuals/ts,hda,w", > > > > > > "file:/media/iso/windows_server_2008_r2_sp1.iso,hdc:cdrom,r" ] > > > > on_poweroff = "destroy" > > > > on_reboot = "restart" > > > > on_crash = "restart" > > > > viridian = "1" > > > > device_model = "/usr/lib/xen/bin/qemu-dm" > > > > boot = "dc" > > > > snapshot = "0" > > > > vncconsole = "1" > > > > sdl = "0" > > > > opengl = "0" > > > > vnc = "1" > > > > nographic = "0" > > > > stdvga = "0" > > > > tsc_mode = "1" > > > > monitor = "0" > > > > localtime = "1" > > > > usb = "0" > > > > keymap = "fi" > > > > xen_platform_pci = "1" > > > > pci_msitranslate = "1" > > > > pci_power_mgmt = "0" > > > > > > > > 2012/10/1 Pasi Kärkkäinen > <[1][2][8][14]pasik@iki.fi> > > > > > > > > On Mon, Oct 01, 2012 at 06:46:08PM +0300, > Valtteri > > Kiviniemi > > > wrote: > > > > > Hi, > > > > > > > > > > Yes, I have viridian=1 on my domU config. > > > > > > > > > > > > > Try with some known good domU configfile. > > > > > > > > -- Pasi > > > > > 2012/10/1 Pasi Kärkkäinen > > <[1][2][3][9][15]pasik@iki.fi> > > > > > > > > > > On Mon, Oct 01, 2012 at 05:06:53PM +0300, > > Valtteri > > > Kiviniemi > > > > wrote: > > > > > > Hi, > > > > > > > > > > > > I''m now using 3.6.0 and can''t > reproduce that > > crash > > > anymore, > > > > so it > > > > > seems > > > > > > that it was a kernel bug. > > > > > > > > > > > > > > > > OK. > > > > > > However I''m still getting black > screen on > > VNC > > > > > > when trying to install Windows Server > 2008 > > R2. I can > > > see the > > > > > "windows is > > > > > > loading files" screen but after the > > installer starts > > > the VNC > > > > > display goes > > > > > > black. > > > > > > > > > > > > Any ideas? > > > > > > > > > > > > > > > > Do you have viridian=1 specified for the > windows > > vm? > > > > > > > > > > -- Pasi > > > > > > > > > > > - Valtteri > > > > > > > > > > > > 2012/10/1 Pasi Kärkkäinen > > <[1][2][3][4][10][16]pasik@iki.fi> > > > > > > > > > > > > On Sun, Sep 30, 2012 at 11:18:03PM > +0300, > > Valtteri > > > > Kiviniemi > > > > > wrote: > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > Hello, > > > > > > > I''m trying to get Windows > Server 2008 > > R2 > > > installation > > > > > booting on > > > > > > Xen > > > > > > > 4.0.4. Using the following > config: > > > > > > > > > > > > > > > > > > > <snip> > > > > > > > > > > > > > > The domU will start booting > just > > fine, but > > > after a > > > > few > > > > > minutes the > > > > > > VNC > > > > > > > screen goes black. After that > when > > typing "xm > > > destroy > > > > ts" it > > > > > will > > > > > > trigger > > > > > > > a kernel BUG: > > > > > > > > > > > > > > BUG: unable to handle kernel > NULL > > pointer > > > dereference > > > > at > > > > > > 0000000000000030 > > > > > > > IP: [<ffffffff810c50c4>] > > iput+0x3e/0x195 > > > > > > > PGD 0 > > > > > > > Oops: 0000 [#1] SMP > > > > > > > CPU 6 > > > > > > > Pid: 3571, comm: qemu-dm Not > tainted > > > 3.5.0-dom0 #1 > > > > > > > > > > > > First of all upgrade to latest > 3.5.x Linux > > kernel > > > release > > > > .. so > > > > > at least > > > > > > 3.5.4. > > > > > > > > > > > > -- Pasi > > > > > > > > > > > > > /DQ77MK > > > > > > > RIP: e030:[<ffffffff810c50c4>] > > > [<ffffffff810c50c4>] > > > > > > iput+0x3e/0x195 > > > > > > > RSP: e02b:ffff8800389ffbf8 > EFLAGS: > > 00010246 > > > > > > > RAX: 0000000000000001 RBX: > > ffff8800377b0720 > > > RCX: > > > > > ffff8800501c0000 > > > > > > > RDX: ffff8800501c0000 RSI: > > ffff8800377b0790 > > > RDI: > > > > > ffff8800377b0790 > > > > > > > RBP: 0000000000000000 R08: > > ffffffff815cdd00 > > > R09: > > > > > 0000000000000016 > > > > > > > R10: fefefefefefefeff R11: > > ffff8800377b0400 > > > R12: > > > > > 00000001000a3e0c > > > > > > > R13: 0000000000000000 R14: > > 00000001000a3e0c > > > R15: > > > > > ffff8800389ffc28 > > > > > > > FS: 00007f1af70a8700(0000) > > > GS:ffff880050180000(0000) > > > > > > > knlGS:0000000000000000 > > > > > > > CS: e033 DS: 0000 ES: 0000 > CR0: > > > 000000008005003b > > > > > > > CR2: 0000000000000030 CR3: > > 000000000156d000 > > > CR4: > > > > > 0000000000002660 > > > > > > > DR0: 0000000000000000 DR1: > > 0000000000000000 > > > DR2: > > > > > 0000000000000000 > > > > > > > DR3: 0000000000000000 DR6: > > 00000000ffff0ff0 > > > DR7: > > > > > 0000000000000400 > > > > > > > Process qemu-dm (pid: 3571, > > threadinfo > > > > ffff8800389fe000, > > > > > task > > > > > > > ffff88003a721260) > > > > > > > Stack: > > > > > > > ffff88003a6d6400 > ffff8800377b0000 > > > 00000001000a3e0c > > > > > > ffffffff8133ce8f > > > > > > > ffff8800377b0400 > ffffffff8134b6cd > > > ffff8800389ffc28 > > > > > > ffff8800389ffc28 > > > > > > > ffff8800377b00f8 > ffff8800377b0680 > > > ffff880038cdcd60 > > > > > > ffff8800377b0000 > > > > > > > Call Trace: > > > > > > > [<ffffffff8133ce8f>] ? > > > sk_release_kernel+0x23/0x39 > > > > > > > [<ffffffff8134b6cd>] ? > > > netdev_run_todo+0x1e9/0x206 > > > > > > > [<ffffffff8129798f>] ? > > > tun_chr_close+0x4c/0x7b > > > > > > > [<ffffffff810b39d3>] ? > > fput+0xe4/0x1c5 > > > > > > > [<ffffffff810b202c>] ? > > filp_close+0x61/0x68 > > > > > > > [<ffffffff81035e62>] ? > > > put_files_struct+0x62/0xb9 > > > > > > > [<ffffffff81036374>] ? > > do_exit+0x24a/0x74c > > > > > > > [<ffffffff81036906>] ? > > > do_group_exit+0x6b/0x9d > > > > > > > [<ffffffff8103ea0b>] ? > > > > get_signal_to_deliver+0x449/0x46e > > > > > > > [<ffffffff81009fa5>] ? > > do_signal+0x28/0x4c4 > > > > > > > [<ffffffff81027079>] ? > > > > pvclock_clocksource_read+0x48/0xbf > > > > > > > [<ffffffff8105b745>] ? > > ktime_get_ts+0x66/0xa8 > > > > > > > [<ffffffff810bfb18>] ? > > > > poll_select_copy_remaining+0xe0/0xf5 > > > > > > > [<ffffffff8100a48d>] ? > > > do_notify_resume+0x3b/0x74 > > > > > > > [<ffffffff81411a70>] ? > > int_signal+0x12/0x17 > > > > > > > Code: 00 00 00 40 74 02 0f 0b > 48 8d > > 77 70 48 > > > 8d bf 08 > > > > 01 00 > > > > > 00 e8 > > > > > > 8b 71 10 > > > > > > > 00 85 c0 0f 84 5d 01 00 00 48 > 8b 6b > > 18 f6 83 > > > 80 00 00 > > > > 00 08 > > > > > <4c> 8b > > > > > > 65 30 > > > > > > > 74 11 be 68 05 00 00 48 c7 c7 > 8e df > > 4f 81 e8 > > > bb d0 > > > > > > > RIP [<ffffffff810c50c4>] > > iput+0x3e/0x195 > > > > > > > RSP <ffff8800389ffbf8> > > > > > > > CR2: 0000000000000030 > > > > > > > ---[ end trace > 67cc1654658fedcc ]--- > > > > > > > Fixing recursive fault but > reboot is > > needed! > > > > > > > > > > > > > > I also tested Xen 4.2.0 and > problem > > is the > > > same. So > > > > is this > > > > > a Xen > > > > > > bug or a > > > > > > > kernel bug? I am running > vanilla > > > > [1][2][3][4][5][11][17]kernel.org kernel > > > > > 3.5.0 and > > > > > > my > > > > > > > hardware is Intel Core i7-3770 > CPU > > and Intel > > > DQ77MK > > > > > motherboard > > > > > > with > > > > > > > latest bios. > > > > > > > > > > > > > > Best regards, > > > > > > > Valtteri Kiviniemi > > > > > > > > > > > > > > References > > > > > > > > > > > > > > Visible links > > > > > > > 1. > [3][4][5][6][12][18]http://kernel.org/ > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > Xen-devel mailing list > > > > > > > > [4][5][6][7][13][19]Xen-devel@lists.xen.org > > > > > > > > > [5][6][7][8][14][20]http://lists.xen.org/xen-devel > > > > > > > > > > > > References > > > > > > > > > > > > Visible links > > > > > > 1. > mailto:[7][8][9][15][21]pasik@iki.fi > > > > > > 2. > [8][9][10][16][22]http://kernel.org/ > > > > > > 3. > [9][10][11][17][23]http://kernel.org/ > > > > > > 4. > > mailto:[10][11][12][18][24]Xen-devel@lists.xen.org > > > > > > 5. > > [11][12][13][19][25]http://lists.xen.org/xen-devel > > > > > > > > > > References > > > > > > > > > > Visible links > > > > > 1. mailto:[13][14][20][26]pasik@iki.fi > > > > > 2. mailto:[14][15][21][27]pasik@iki.fi > > > > > 3. [15][16][22][28]http://kernel.org/ > > > > > 4. [16][17][23][29]http://kernel.org/ > > > > > 5. > mailto:[17][18][24][30]Xen-devel@lists.xen.org > > > > > 6. > [18][19][25][31]http://lists.xen.org/xen-devel > > > > > 7. mailto:[19][20][26][32]pasik@iki.fi > > > > > 8. [20][21][27][33]http://kernel.org/ > > > > > 9. [21][22][28][34]http://kernel.org/ > > > > > 10. > mailto:[22][23][29][35]Xen-devel@lists.xen.org > > > > > 11. > [23][24][30][36]http://lists.xen.org/xen-devel > > > > > > > > References > > > > > > > > Visible links > > > > 1. mailto:[25][31][37]pasik@iki.fi > > > > 2. mailto:[26][32][38]pasik@iki.fi > > > > 3. mailto:[27][33][39]pasik@iki.fi > > > > 4. [28][34][40]http://kernel.org/ > > > > 5. [29][35][41]http://kernel.org/ > > > > 6. mailto:[30][36][42]Xen-devel@lists.xen.org > > > > 7. [31][37][43]http://lists.xen.org/xen-devel > > > > 8. mailto:[32][38][44]pasik@iki.fi > > > > 9. [33][39][45]http://kernel.org/ > > > > 10. [34][40][46]http://kernel.org/ > > > > 11. mailto:[35][41][47]Xen-devel@lists.xen.org > > > > 12. [36][42][48]http://lists.xen.org/xen-devel > > > > 13. mailto:[37][43][49]pasik@iki.fi > > > > 14. mailto:[38][44][50]pasik@iki.fi > > > > 15. [39][45][51]http://kernel.org/ > > > > 16. [40][46][52]http://kernel.org/ > > > > 17. mailto:[41][47][53]Xen-devel@lists.xen.org > > > > 18. [42][48][54]http://lists.xen.org/xen-devel > > > > 19. mailto:[43][49][55]pasik@iki.fi > > > > 20. [44][50][56]http://kernel.org/ > > > > 21. [45][51][57]http://kernel.org/ > > > > 22. mailto:[46][52][58]Xen-devel@lists.xen.org > > > > 23. [47][53][59]http://lists.xen.org/xen-devel > > > > > > References > > > > > > Visible links > > > 1. mailto:[54][60]pasik@iki.fi > > > 2. mailto:[55][61]pasik@iki.fi > > > 3. mailto:[56][62]pasik@iki.fi > > > 4. mailto:[57][63]pasik@iki.fi > > > 5. [58][64]http://kernel.org/ > > > 6. [59][65]http://kernel.org/ > > > 7. mailto:[60][66]Xen-devel@lists.xen.org > > > 8. [61][67]http://lists.xen.org/xen-devel > > > 9. mailto:[62][68]pasik@iki.fi > > > 10. [63][69]http://kernel.org/ > > > 11. [64][70]http://kernel.org/ > > > 12. mailto:[65][71]Xen-devel@lists.xen.org > > > 13. [66][72]http://lists.xen.org/xen-devel > > > 14. mailto:[67][73]pasik@iki.fi > > > 15. mailto:[68][74]pasik@iki.fi > > > 16. [69][75]http://kernel.org/ > > > 17. [70][76]http://kernel.org/ > > > 18. mailto:[71][77]Xen-devel@lists.xen.org > > > 19. [72][78]http://lists.xen.org/xen-devel > > > 20. mailto:[73][79]pasik@iki.fi > > > 21. [74][80]http://kernel.org/ > > > 22. [75][81]http://kernel.org/ > > > 23. mailto:[76][82]Xen-devel@lists.xen.org > > > 24. [77][83]http://lists.xen.org/xen-devel > > > 25. mailto:[78][84]pasik@iki.fi > > > 26. mailto:[79][85]pasik@iki.fi > > > 27. mailto:[80][86]pasik@iki.fi > > > 28. [81][87]http://kernel.org/ > > > 29. [82][88]http://kernel.org/ > > > 30. mailto:[83][89]Xen-devel@lists.xen.org > > > 31. [84][90]http://lists.xen.org/xen-devel > > > 32. mailto:[85][91]pasik@iki.fi > > > 33. [86][92]http://kernel.org/ > > > 34. [87][93]http://kernel.org/ > > > 35. mailto:[88][94]Xen-devel@lists.xen.org > > > 36. [89][95]http://lists.xen.org/xen-devel > > > 37. mailto:[90][96]pasik@iki.fi > > > 38. mailto:[91][97]pasik@iki.fi > > > 39. [92][98]http://kernel.org/ > > > 40. [93][99]http://kernel.org/ > > > 41. mailto:[94][100]Xen-devel@lists.xen.org > > > 42. [95][101]http://lists.xen.org/xen-devel > > > 43. mailto:[96][102]pasik@iki.fi > > > 44. [97][103]http://kernel.org/ > > > 45. [98][104]http://kernel.org/ > > > 46. mailto:[99][105]Xen-devel@lists.xen.org > > > 47. [100][106]http://lists.xen.org/xen-devel > > > > References > > > > Visible links > > 1. mailto:[107]kiviniemi.valtteri@gmail.com > > 2. [108]http://ark.intel.com/products/65719/ > > 3. > [109]http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > > 4. mailto:[110]root@dataproof.fi > > 5. mailto:[111]pasik@iki.fi > > 6. [112]http://xen.org/ > > 7. mailto:[113]pasik@iki.fi > > 8. mailto:[114]pasik@iki.fi > > 9. mailto:[115]pasik@iki.fi > > 10. mailto:[116]pasik@iki.fi > > 11. [117]http://kernel.org/ > > 12. [118]http://kernel.org/ > > 13. mailto:[119]Xen-devel@lists.xen.org > > 14. [120]http://lists.xen.org/xen-devel > > 15. mailto:[121]pasik@iki.fi > > 16. [122]http://kernel.org/ > > 17. [123]http://kernel.org/ > > 18. mailto:[124]Xen-devel@lists.xen.org > > 19. [125]http://lists.xen.org/xen-devel > > 20. mailto:[126]pasik@iki.fi > > 21. mailto:[127]pasik@iki.fi > > 22. [128]http://kernel.org/ > > 23. [129]http://kernel.org/ > > 24. mailto:[130]Xen-devel@lists.xen.org > > 25. [131]http://lists.xen.org/xen-devel > > 26. mailto:[132]pasik@iki.fi > > 27. [133]http://kernel.org/ > > 28. [134]http://kernel.org/ > > 29. mailto:[135]Xen-devel@lists.xen.org > > 30. [136]http://lists.xen.org/xen-devel > > 31. mailto:[137]pasik@iki.fi > > 32. mailto:[138]pasik@iki.fi > > 33. mailto:[139]pasik@iki.fi > > 34. [140]http://kernel.org/ > > 35. [141]http://kernel.org/ > > 36. mailto:[142]Xen-devel@lists.xen.org > > 37. [143]http://lists.xen.org/xen-devel > > 38. mailto:[144]pasik@iki.fi > > 39. [145]http://kernel.org/ > > 40. [146]http://kernel.org/ > > 41. mailto:[147]Xen-devel@lists.xen.org > > 42. [148]http://lists.xen.org/xen-devel > > 43. mailto:[149]pasik@iki.fi > > 44. mailto:[150]pasik@iki.fi > > 45. [151]http://kernel.org/ > > 46. [152]http://kernel.org/ > > 47. mailto:[153]Xen-devel@lists.xen.org > > 48. [154]http://lists.xen.org/xen-devel > > 49. mailto:[155]pasik@iki.fi > > 50. [156]http://kernel.org/ > > 51. [157]http://kernel.org/ > > 52. mailto:[158]Xen-devel@lists.xen.org > > 53. [159]http://lists.xen.org/xen-devel > > 54. mailto:[160]pasik@iki.fi > > 55. mailto:[161]pasik@iki.fi > > 56. mailto:[162]pasik@iki.fi > > 57. mailto:[163]pasik@iki.fi > > 58. [164]http://kernel.org/ > > 59. [165]http://kernel.org/ > > 60. mailto:[166]Xen-devel@lists.xen.org > > 61. [167]http://lists.xen.org/xen-devel > > 62. mailto:[168]pasik@iki.fi > > 63. [169]http://kernel.org/ > > 64. [170]http://kernel.org/ > > 65. mailto:[171]Xen-devel@lists.xen.org > > 66. [172]http://lists.xen.org/xen-devel > > 67. mailto:[173]pasik@iki.fi > > 68. mailto:[174]pasik@iki.fi > > 69. [175]http://kernel.org/ > > 70. [176]http://kernel.org/ > > 71. mailto:[177]Xen-devel@lists.xen.org > > 72. [178]http://lists.xen.org/xen-devel > > 73. mailto:[179]pasik@iki.fi > > 74. [180]http://kernel.org/ > > 75. [181]http://kernel.org/ > > 76. mailto:[182]Xen-devel@lists.xen.org > > 77. [183]http://lists.xen.org/xen-devel > > 78. mailto:[184]pasik@iki.fi > > 79. mailto:[185]pasik@iki.fi > > 80. mailto:[186]pasik@iki.fi > > 81. [187]http://kernel.org/ > > 82. [188]http://kernel.org/ > > 83. mailto:[189]Xen-devel@lists.xen.org > > 84. [190]http://lists.xen.org/xen-devel > > 85. mailto:[191]pasik@iki.fi > > 86. [192]http://kernel.org/ > > 87. [193]http://kernel.org/ > > 88. mailto:[194]Xen-devel@lists.xen.org > > 89. [195]http://lists.xen.org/xen-devel > > 90. mailto:[196]pasik@iki.fi > > 91. mailto:[197]pasik@iki.fi > > 92. [198]http://kernel.org/ > > 93. [199]http://kernel.org/ > > 94. mailto:[200]Xen-devel@lists.xen.org > > 95. [201]http://lists.xen.org/xen-devel > > 96. mailto:[202]pasik@iki.fi > > 97. [203]http://kernel.org/ > > 98. [204]http://kernel.org/ > > 99. mailto:[205]Xen-devel@lists.xen.org > > 100. [206]http://lists.xen.org/xen-devel > > References > > Visible links > 1. http://nago.fi/dmesg.txt > 2. http://nago.fi/qemu-dm.txt > 3. http://nago.fi/xm-dmesg.txt > 4. http://nago.fi/domu-config.txt > 5. http://nago.fi/dom0-config.txt > 6. mailto:pasik@iki.fi > 7. mailto:kiviniemi.valtteri@gmail.com > 8. http://ark.intel.com/products/65719/ > 9. http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > 10. mailto:root@dataproof.fi > 11. mailto:pasik@iki.fi > 12. http://xen.org/ > 13. mailto:pasik@iki.fi > 14. mailto:pasik@iki.fi > 15. mailto:pasik@iki.fi > 16. mailto:pasik@iki.fi > 17. http://kernel.org/ > 18. http://kernel.org/ > 19. mailto:Xen-devel@lists.xen.org > 20. http://lists.xen.org/xen-devel > 21. mailto:pasik@iki.fi > 22. http://kernel.org/ > 23. http://kernel.org/ > 24. mailto:Xen-devel@lists.xen.org > 25. http://lists.xen.org/xen-devel > 26. mailto:pasik@iki.fi > 27. mailto:pasik@iki.fi > 28. http://kernel.org/ > 29. http://kernel.org/ > 30. mailto:Xen-devel@lists.xen.org > 31. http://lists.xen.org/xen-devel > 32. mailto:pasik@iki.fi > 33. http://kernel.org/ > 34. http://kernel.org/ > 35. mailto:Xen-devel@lists.xen.org > 36. http://lists.xen.org/xen-devel > 37. mailto:pasik@iki.fi > 38. mailto:pasik@iki.fi > 39. mailto:pasik@iki.fi > 40. http://kernel.org/ > 41. http://kernel.org/ > 42. mailto:Xen-devel@lists.xen.org > 43. http://lists.xen.org/xen-devel > 44. mailto:pasik@iki.fi > 45. http://kernel.org/ > 46. http://kernel.org/ > 47. mailto:Xen-devel@lists.xen.org > 48. http://lists.xen.org/xen-devel > 49. mailto:pasik@iki.fi > 50. mailto:pasik@iki.fi > 51. http://kernel.org/ > 52. http://kernel.org/ > 53. mailto:Xen-devel@lists.xen.org > 54. http://lists.xen.org/xen-devel > 55. mailto:pasik@iki.fi > 56. http://kernel.org/ > 57. http://kernel.org/ > 58. mailto:Xen-devel@lists.xen.org > 59. http://lists.xen.org/xen-devel > 60. mailto:pasik@iki.fi > 61. mailto:pasik@iki.fi > 62. mailto:pasik@iki.fi > 63. mailto:pasik@iki.fi > 64. http://kernel.org/ > 65. http://kernel.org/ > 66. mailto:Xen-devel@lists.xen.org > 67. http://lists.xen.org/xen-devel > 68. mailto:pasik@iki.fi > 69. http://kernel.org/ > 70. http://kernel.org/ > 71. mailto:Xen-devel@lists.xen.org > 72. http://lists.xen.org/xen-devel > 73. mailto:pasik@iki.fi > 74. mailto:pasik@iki.fi > 75. http://kernel.org/ > 76. http://kernel.org/ > 77. mailto:Xen-devel@lists.xen.org > 78. http://lists.xen.org/xen-devel > 79. mailto:pasik@iki.fi > 80. http://kernel.org/ > 81. http://kernel.org/ > 82. mailto:Xen-devel@lists.xen.org > 83. http://lists.xen.org/xen-devel > 84. mailto:pasik@iki.fi > 85. mailto:pasik@iki.fi > 86. mailto:pasik@iki.fi > 87. http://kernel.org/ > 88. http://kernel.org/ > 89. mailto:Xen-devel@lists.xen.org > 90. http://lists.xen.org/xen-devel > 91. mailto:pasik@iki.fi > 92. http://kernel.org/ > 93. http://kernel.org/ > 94. mailto:Xen-devel@lists.xen.org > 95. http://lists.xen.org/xen-devel > 96. mailto:pasik@iki.fi > 97. mailto:pasik@iki.fi > 98. http://kernel.org/ > 99. http://kernel.org/ > 100. mailto:Xen-devel@lists.xen.org > 101. http://lists.xen.org/xen-devel > 102. mailto:pasik@iki.fi > 103. http://kernel.org/ > 104. http://kernel.org/ > 105. mailto:Xen-devel@lists.xen.org > 106. http://lists.xen.org/xen-devel > 107. mailto:kiviniemi.valtteri@gmail.com > 108. http://ark.intel.com/products/65719/ > 109. http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > 110. mailto:root@dataproof.fi > 111. mailto:pasik@iki.fi > 112. http://xen.org/ > 113. mailto:pasik@iki.fi > 114. mailto:pasik@iki.fi > 115. mailto:pasik@iki.fi > 116. mailto:pasik@iki.fi > 117. http://kernel.org/ > 118. http://kernel.org/ > 119. mailto:Xen-devel@lists.xen.org > 120. http://lists.xen.org/xen-devel > 121. mailto:pasik@iki.fi > 122. http://kernel.org/ > 123. http://kernel.org/ > 124. mailto:Xen-devel@lists.xen.org > 125. http://lists.xen.org/xen-devel > 126. mailto:pasik@iki.fi > 127. mailto:pasik@iki.fi > 128. http://kernel.org/ > 129. http://kernel.org/ > 130. mailto:Xen-devel@lists.xen.org > 131. http://lists.xen.org/xen-devel > 132. mailto:pasik@iki.fi > 133. http://kernel.org/ > 134. http://kernel.org/ > 135. mailto:Xen-devel@lists.xen.org > 136. http://lists.xen.org/xen-devel > 137. mailto:pasik@iki.fi > 138. mailto:pasik@iki.fi > 139. mailto:pasik@iki.fi > 140. http://kernel.org/ > 141. http://kernel.org/ > 142. mailto:Xen-devel@lists.xen.org > 143. http://lists.xen.org/xen-devel > 144. mailto:pasik@iki.fi > 145. http://kernel.org/ > 146. http://kernel.org/ > 147. mailto:Xen-devel@lists.xen.org > 148. http://lists.xen.org/xen-devel > 149. mailto:pasik@iki.fi > 150. mailto:pasik@iki.fi > 151. http://kernel.org/ > 152. http://kernel.org/ > 153. mailto:Xen-devel@lists.xen.org > 154. http://lists.xen.org/xen-devel > 155. mailto:pasik@iki.fi > 156. http://kernel.org/ > 157. http://kernel.org/ > 158. mailto:Xen-devel@lists.xen.org > 159. http://lists.xen.org/xen-devel > 160. mailto:pasik@iki.fi > 161. mailto:pasik@iki.fi > 162. mailto:pasik@iki.fi > 163. mailto:pasik@iki.fi > 164. http://kernel.org/ > 165. http://kernel.org/ > 166. mailto:Xen-devel@lists.xen.org > 167. http://lists.xen.org/xen-devel > 168. mailto:pasik@iki.fi > 169. http://kernel.org/ > 170. http://kernel.org/ > 171. mailto:Xen-devel@lists.xen.org > 172. http://lists.xen.org/xen-devel > 173. mailto:pasik@iki.fi > 174. mailto:pasik@iki.fi > 175. http://kernel.org/ > 176. http://kernel.org/ > 177. mailto:Xen-devel@lists.xen.org > 178. http://lists.xen.org/xen-devel > 179. mailto:pasik@iki.fi > 180. http://kernel.org/ > 181. http://kernel.org/ > 182. mailto:Xen-devel@lists.xen.org > 183. http://lists.xen.org/xen-devel > 184. mailto:pasik@iki.fi > 185. mailto:pasik@iki.fi > 186. mailto:pasik@iki.fi > 187. http://kernel.org/ > 188. http://kernel.org/ > 189. mailto:Xen-devel@lists.xen.org > 190. http://lists.xen.org/xen-devel > 191. mailto:pasik@iki.fi > 192. http://kernel.org/ > 193. http://kernel.org/ > 194. mailto:Xen-devel@lists.xen.org > 195. http://lists.xen.org/xen-devel > 196. mailto:pasik@iki.fi > 197. mailto:pasik@iki.fi > 198. http://kernel.org/ > 199. http://kernel.org/ > 200. mailto:Xen-devel@lists.xen.org > 201. http://lists.xen.org/xen-devel > 202. mailto:pasik@iki.fi > 203. http://kernel.org/ > 204. http://kernel.org/ > 205. mailto:Xen-devel@lists.xen.org > 206. http://lists.xen.org/xen-devel
Valtteri Kiviniemi
2012-Oct-02 13:46 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
Hi, I have not enabled debug on Xen or dom0 kernel. Could you tell me the parameters for Xen coompilation needed to enable debugging? And If you would also happen to know what are the options needed to enable kernel debugging in menuconfig? Well I can probably manage to get the kernel debugging enabled myself, but if you happen to know them please share so maybe I can get everything enabled at the first try :) Thanks! - Valtteri 2012/10/2 Pasi Kärkkäinen <pasik@iki.fi>> On Tue, Oct 02, 2012 at 04:01:04PM +0300, Valtteri Kiviniemi wrote: > > Hi, > > > > I already tried 3.2, 3.5, 3.5.0, 3.6.0-rc7 and 3.6.0, same problem > all of > > those. My dom0 config is the same config that I''am using on other > server > > where HVM is working, so I dont think that it is a config problem. I > have > > triple checked everything and all should be ok. dom0 dmesg shows the > same > > crash that I have previously posted here. /var/log/xen/ does not > contain > > any specific errors. > > > > Could this be some kind of broblem with my motherboard bios being > buggy or > > CPU not supported? I''m using the new intel Ivy Bridge processor which > has > > integrated GPU, but that should not probably cause these kind of > problems. > > Or maybe some ACPI problem? xm dmesg is showing some notices about > ACPI. > > Is there any ACPI kernel parameters that I should try booting? This > has to > > be somekind of problem with my hardware, or then maybe it could be a > > kernel problem too. I just really cant figure this out myself, I have > > tried everything. > > > > Hmm.. I have some distant memories of seeing a patch that fixes a bug > on recent Ivy Bridge systems, but I can''t find a link right now. > Maybe you''re affected by that.. > > Also: Did you already post the crash log, with all the debug/verbose > options enabled for both Xen and dom0 kernel? > > -- Pasi > > > Lets take a quick summary of what has been tested, what hardware I''m > using > > etc. > > > > Xen-versions tested: 4.2.0, 4.0.4 > > Kernel-versions tested: 3.2.0, 3.5.0, 3.5.4, 3.6.0-rc7, 3.6.0 > > > > Host OS: Debian testing/wheezy, udev version 175-7, 2.13-35, python > > version 2.7.3~rc2-2.1 > > > > Hardware: > > > > CPU: Intel Core i7-3770 3.4GHz > > MB: Intel DQ77MK (latest bios updated) > > Memory: 32GB (4 x 8GB DDR3-1600MHz) > > > > All relevant log files and configs: > > > > dom0 dmesg: [1]http://nago.fi/dmesg.txt > > qemu-dm log: [2]http://nago.fi/qemu-dm.txt > > xm dmesg log: [3]http://nago.fi/xm-dmesg.txt > > domU config: [4]http://nago.fi/domu-config.txt > > dom0 kernel config: [5]http://nago.fi/dom0-config.txt > > > > I have also tried playing with every setting on that domU that I can > think > > of and tried different configs etc. > > > > - Valtteri > > > > 2012/10/2 Pasi Kärkkäinen <[6]pasik@iki.fi> > > > > On Tue, Oct 02, 2012 at 03:11:07PM +0300, Valtteri Kiviniemi wrote: > > > Hi, > > > > > > Another update: > > > > > > I wanted to check that if a Linux HVM would boot with working > VNC > > console, > > > so I tried to launch a Debian Squeeze installer on HVM. It > refused > > to > > > start ant told me that vbd hotplug scripts were not working. > After > > that > > > failure even the Windows domU would not anymore start which was > > previously > > > starting ok. > > > > > > The hotplug scripts also starts hanging on the processes. > > > > > > root 9401 0.1 0.1 17700 1640 ? S 15:05 > 0:00 > > /bin/bash > > > /etc/xen/scripts/xen-hotplug-cleanup > > > root 9441 0.1 0.1 17700 1644 ? S 15:05 > 0:00 > > /bin/bash > > > /etc/xen/scripts/xen-hotplug-cleanup > > > root 9481 0.1 0.1 17700 1640 ? S 15:05 > 0:00 > > /bin/bash > > > /etc/xen/scripts/xen-hotplug-cleanup > > > root 9560 0.1 0.1 17700 1640 ? S 15:05 > 0:00 > > /bin/bash > > > /etc/xen/scripts/xen-hotplug-cleanup > > > root 10738 0.1 0.1 17696 1636 ? S 15:05 > 0:00 > > /bin/bash > > > /etc/xen/scripts/xen-hotplug-cleanup > > > root 10747 0.1 0.1 17792 1736 ? S 15:05 > 0:00 > > /bin/bash > > > /etc/xen/scripts/block remove > > > root 11286 0.0 0.0 4080 324 ? S 15:06 > 0:00 > > sleep 1 > > > root 11290 0.0 0.0 4080 324 ? S 15:06 > 0:00 > > sleep 1 > > > root 11294 0.0 0.0 4080 324 ? S 15:06 > 0:00 > > sleep 1 > > > root 11298 0.0 0.0 4080 324 ? S 15:06 > 0:00 > > sleep 1 > > > root 11302 0.0 0.0 4080 320 ? S 15:06 > 0:00 > > sleep 1 > > > root 11306 0.0 0.0 4080 320 ? S 15:06 > 0:00 > > sleep 1 > > > > > > Then I did a xm destroy and I had again the kernel BUG on > dmesg. So > > it > > > seems that the problem is not fixed by using 3.6.0. Udev > version is > > 175-7. > > > > > > > So you have definitely something broken in your system, > > probably in your dom0 kernel. Try with Linux 3.5.4 or 3.4.x, > > and see how that goes. > > > > Any errors in dom0 dmesg? How about in /var/log/xen/* ? > > > > -- Pasi > > > > > > > > > > > 2012/10/1 Valtteri Kiviniemi <[1][7] > kiviniemi.valtteri@gmail.com> > > > > > > Hi, > > > > > > CPU: Intel Core i7-3770 3.4GHz > > > [2][8]http://ark.intel.com/products/65719/ > > > > > > MB: Intel DQ77MK (latest bios updated) > > > > > [3][9] > http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > > > > > > Memory: 32GB (4 x 8GB DDR3-1600MHz) > > > > > > Host is Debian wheezy/testing, Xen 4.0.4 and latest 3.6.0 > kernel. > > > > > > Noticed also some errors in xm dmesg: > > > > > > root@xen-2:~# xm dmesg > > > > > > (XEN) Xen version 4.0.4 ([4][10]root@dataproof.fi) (gcc > version > > 4.7.1 > > > (Debian 4.7.1-7) ) Sun Sep 30 20:28:26 EEST 2012 > > > (XEN) Latest ChangeSet: unavailable > > > (XEN) Bootloader: GNU GRUB 0.97 > > > (XEN) Command line: dom0_mem=1280M cpufreq=xen > clocksource=hpet > > > (XEN) Video information: > > > (XEN) VGA is text mode 80x25, font 8x16 > > > (XEN) VBE/DDC methods: none; EDID transfer time: 0 seconds > > > (XEN) EDID info not retrieved because no DDC retrieval > method > > detected > > > (XEN) Disc information: > > > (XEN) Found 4 MBR signatures > > > (XEN) Found 4 EDD information structures > > > (XEN) Xen-e820 RAM map: > > > (XEN) 0000000000000000 - 000000000009d800 (usable) > > > (XEN) 000000000009d800 - 00000000000a0000 (reserved) > > > (XEN) 00000000000e0000 - 0000000000100000 (reserved) > > > (XEN) 0000000000100000 - 0000000020000000 (usable) > > > (XEN) 0000000020000000 - 0000000020200000 (reserved) > > > (XEN) 0000000020200000 - 0000000040004000 (usable) > > > (XEN) 0000000040004000 - 0000000040005000 (reserved) > > > (XEN) 0000000040005000 - 00000000dbe44000 (usable) > > > (XEN) 00000000dbe44000 - 00000000dc2d7000 (reserved) > > > (XEN) 00000000dc2d7000 - 00000000dc2e7000 (ACPI data) > > > (XEN) 00000000dc2e7000 - 00000000dc40c000 (ACPI NVS) > > > (XEN) 00000000dc40c000 - 00000000dc6af000 (reserved) > > > (XEN) 00000000dc6af000 - 00000000dc6b0000 (usable) > > > (XEN) 00000000dc6b0000 - 00000000dc6f3000 (ACPI NVS) > > > (XEN) 00000000dc6f3000 - 00000000dd000000 (usable) > > > (XEN) 00000000dd800000 - 00000000dfa00000 (reserved) > > > (XEN) 00000000f8000000 - 00000000fc000000 (reserved) > > > (XEN) 00000000fec00000 - 00000000fec01000 (reserved) > > > (XEN) 00000000fed00000 - 00000000fed04000 (reserved) > > > (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) > > > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > > > (XEN) 00000000ff000000 - 0000000100000000 (reserved) > > > (XEN) 0000000100000000 - 000000081e600000 (usable) > > > (XEN) ACPI: RSDP 000F0490, 0024 (r2 INTEL) > > > (XEN) ACPI: XSDT DC2DB080, 007C (r1 INTEL DQ77MK 32 > AMI > > > 10013) > > > (XEN) ACPI: FACP DC2E51F0, 010C (r5 INTEL DQ77MK 32 > AMI > > > 10013) > > > (XEN) ACPI Warning (tbfadt-0232): FADT (revision 5) is longer > > than ACPI > > > 2.0 version, truncating length 0x10C to 0xF4 [20070126] > > > (XEN) ACPI: DSDT DC2DB188, A061 (r2 INTEL DQ77MK 32 > INTL > > > 20051117) > > > (XEN) ACPI: FACS DC40A080, 0040 > > > (XEN) ACPI: APIC DC2E5300, 0092 (r3 INTEL DQ77MK 32 > AMI > > > 10013) > > > (XEN) ACPI: FPDT DC2E5398, 0044 (r1 INTEL DQ77MK 32 > AMI > > > 10013) > > > (XEN) ACPI: TCPA DC2E53E0, 0032 (r2 INTEL DQ77MK 32 > MSFT > > > 1000013) > > > (XEN) ACPI: MCFG DC2E5418, 003C (r1 INTEL DQ77MK 32 > MSFT > > > 97) > > > (XEN) ACPI: HPET DC2E5458, 0038 (r1 INTEL DQ77MK 32 > AMI. > > > 5) > > > (XEN) ACPI: SSDT DC2E5490, 036D (r1 INTEL DQ77MK 32 > INTL > > > 20091112) > > > (XEN) ACPI: SSDT DC2E5800, 09AA (r1 INTEL DQ77MK 32 > INTL > > > 20051117) > > > (XEN) ACPI: SSDT DC2E61B0, 0A92 (r1 INTEL DQ77MK 32 > INTL > > > 20051117) > > > (XEN) ACPI: DMAR DC2E6C48, 00B8 (r1 INTEL DQ77MK 32 > INTL > > > 1) > > > (XEN) ACPI: ASF! DC2E6D00, 00A5 (r32 INTEL DQ77MK 32 > > TFSM > > > F4240) > > > (XEN) System RAM: 32682MB (33467320kB) > > > (XEN) Domain heap initialised > > > (XEN) ACPI: 32/64X FACS address mismatch in FADT - > > > dc40a080/0000000000000000, using 32 > > > (XEN) Processor #0 7:10 APIC version 21 > > > (XEN) Processor #2 7:10 APIC version 21 > > > (XEN) Processor #4 7:10 APIC version 21 > > > (XEN) Processor #6 7:10 APIC version 21 > > > (XEN) Processor #1 7:10 APIC version 21 > > > (XEN) Processor #3 7:10 APIC version 21 > > > (XEN) Processor #5 7:10 APIC version 21 > > > (XEN) Processor #7 7:10 APIC version 21 > > > (XEN) IOAPIC[0]: apic_id 2, version 32, address 0xfec00000, > GSI > > 0-23 > > > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > > > (XEN) Switched to APIC driver x2apic_cluster. > > > (XEN) x2APIC mode enabled. > > > (XEN) Using scheduler: SMP Credit Scheduler (credit) > > > (XEN) Detected 3392.369 MHz processor. > > > (XEN) Initing memory sharing. > > > (XEN) VMX: Supported advanced features: > > > (XEN) - APIC MMIO access virtualisation > > > (XEN) - APIC TPR shadow > > > (XEN) - Extended Page Tables (EPT) > > > (XEN) - Virtual-Processor Identifiers (VPID) > > > (XEN) - Virtual NMI > > > (XEN) - MSR direct-access bitmap > > > (XEN) - Unrestricted Guest > > > (XEN) EPT supports 2MB super page. > > > (XEN) HVM: ASIDs enabled. > > > (XEN) HVM: VMX enabled > > > (XEN) HVM: Hardware Assisted Paging detected. > > > (XEN) Intel VT-d Snoop Control not enabled. > > > (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. > > > (XEN) Intel VT-d Queued Invalidation enabled. > > > (XEN) Intel VT-d Interrupt Remapping enabled. > > > (XEN) I/O virtualisation enabled > > > (XEN) - Dom0 mode: Relaxed > > > (XEN) Enabled directed EOI with ioapic_ack_old on! > > > (XEN) Total of 8 processors activated. > > > (XEN) ENABLING IO-APIC IRQs > > > (XEN) -> Using old ACK method > > > (XEN) TSC is reliable, synchronization unnecessary > > > (XEN) Platform timer appears to have unexpectedly wrapped 1 > > times. > > > (XEN) Platform timer is 14.318MHz HPET > > > (XEN) Allocated console ring of 16 KiB. > > > (XEN) Brought up 8 CPUs > > > (XEN) *** LOADING DOMAIN 0 *** > > > (XEN) Xen kernel: 64-bit, lsb, compat32 > > > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> > > 0x1ae7000 > > > (XEN) PHYSICAL MEMORY ARRANGEMENT: > > > (XEN) Dom0 alloc.: 0000000804000000->0000000806000000 > (319488 > > pages > > > to be allocated) > > > (XEN) VIRTUAL MEMORY ARRANGEMENT: > > > (XEN) Loaded kernel: ffffffff81000000->ffffffff81ae7000 > > > (XEN) Init. ramdisk: ffffffff81ae7000->ffffffff81ae7000 > > > (XEN) Phys-Mach map: ffffffff81ae7000->ffffffff81d67000 > > > (XEN) Start info: ffffffff81d67000->ffffffff81d674b4 > > > (XEN) Page tables: ffffffff81d68000->ffffffff81d7b000 > > > (XEN) Boot stack: ffffffff81d7b000->ffffffff81d7c000 > > > (XEN) TOTAL: ffffffff80000000->ffffffff82000000 > > > (XEN) ENTRY ADDRESS: ffffffff815e3210 > > > (XEN) Dom0 has maximum 8 VCPUs > > > (XEN) [VT-D]iommu.c:718: BIOS did not enable IGD for VT > properly. > > > Disabling IGD VT-d engine. > > > (XEN) Scrubbing Free RAM: done. > > > (XEN) Xen trace buffers: disabled > > > (XEN) Std. Loglevel: Errors and warnings > > > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and > warnings) > > > (XEN) Xen is relinquishing VGA console. > > > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times to > > switch > > > input to Xen) > > > (XEN) Freed 172kB init memory. > > > (XEN) traps.c:2333:d0 Domain attempted WRMSR 000000000000008b > > from > > > 00000012:00000000 to 00000000:00000000. > > > > > > - Valtteri > > > > > > 2012/10/1 Pasi Kärkkäinen <[5][11]pasik@iki.fi> > > > > > > On Mon, Oct 01, 2012 at 09:12:50PM +0300, Valtteri > Kiviniemi > > wrote: > > > > Hi, > > > > > > > > Lowering memory or vcpu''s does not help, problem is > the > > same. I > > > originally > > > > installed Xen 4.2.0 and the problem was same on that > too. > > Then I > > > > downgraded back to 4.0.4 since I thought that this > might > > be a bug > > > on > > > > 4.2.0. I have been previously running Windows Server > 2008 > > R2 > > > succesfully > > > > on Xen 4.0.x on different hardware with this same > config. > > > Hypervisor is > > > > 64bit and windows is 64bit. > > > > > > > > Any ideas what to try next? > > > > > > > > > > What kind of hardware is that? > > > > > > [6][12]xen.org automated testing regularly tests Windows > VMs, > > and it works > > > OK there. > > > > > > -- Pasi > > > > Ps. qemu-dm.log is the following: > > > > > > > > domid: 10 > > > > config qemu network with xen bridge for tap10.0 > xenbr0 > > > > Using file /dev/virtuals/ts in read-write mode > > > > Using file /media/iso/windows_server_2008_r2_sp1.iso > in > > read-only > > > mode > > > > Watching /local/domain/0/device-model/10/logdirty/cmd > > > > Watching /local/domain/0/device-model/10/command > > > > qemu_map_cache_init nr_buckets = 10000 size 4194304 > > > > shared page at pfn feffd > > > > buffered io page at pfn feffb > > > > Guest uuid = 52f19e23-2955-c27d-a22c-60c5d8c60d5a > > > > Time offset set 0 > > > > populating video RAM at ff000000 > > > > mapping video RAM from ff000000 > > > > Register xen platform. > > > > Done register platform. > > > > platform_fixed_ioport: changed ro/rw state of ROM > memory > > area. > > > now is rw > > > > state. > > > > > > xs_read(/local/domain/0/device-model/10/xen_extended_power_mgmt): > > > read > > > > error > > > > medium change watch on `hdc'' (index: 1): > > > > /media/iso/windows_server_2008_r2_sp1.iso > > > > I/O request not ready: 0, ptr: 0, port: 0, data: 0, > count: > > 0, > > > size: 0 > > > > Log-dirty: no command yet. > > > > xs_read(/local/domain/10/log-throttling): read error > > > > qemu: ignoring not-understood drive > > > `/local/domain/10/log-throttling'' > > > > medium change watch on > `/local/domain/10/log-throttling'' - > > > unknown device, > > > > ignored > > > > cirrus vga map change while on lfb mode > > > > mapping vram to f0000000 - f0400000 > > > > platform_fixed_ioport: changed ro/rw state of ROM > memory > > area. > > > now is rw > > > > state. > > > > platform_fixed_ioport: changed ro/rw state of ROM > memory > > area. > > > now is ro > > > > state. > > > > > > > > 2012/10/1 Pasi Kärkkäinen <[1][7][13]pasik@iki.fi> > > > > > > > > On Mon, Oct 01, 2012 at 07:23:44PM +0300, Valtteri > > Kiviniemi > > > wrote: > > > > > Hi, > > > > > > > > > > I have tried other config files, but the > problem is > > the > > > same. At > > > > the > > > > > moment I''m using a config file from another > server > > where I > > > have a > > > > working > > > > > Windows Server 2008 R2 installation, so I dont > > think that > > > there is > > > > > anything wrong with my config: > > > > > > > > > > > > > Did you try with less vcpus, for example 2 ? > > > > how about with less memory, say 2 GB ? > > > > > > > > Did you try with later Xen versions? Is that a 32bit > > Xen, or > > > 64bit Xen > > > > hypervisor? > > > > > > > > -- Pasi > > > > > kernel = "/usr/lib/xen/boot/hvmloader" > > > > > builder = "hvm" > > > > > shadow_memory = "8" > > > > > memory = "4096" > > > > > name = "ts" > > > > > vcpus = "8" > > > > > cpus = ["0", "1", "2", "3", "4", "5", "6", "7"] > > > > > pae = "1" > > > > > acpi = "1" > > > > > apic = "1" > > > > > vfb = [ ''type=vnc, vnclisten=10.100.100.50, > > vncpasswd=xxx'' > > > ] > > > > > xen_extended_power_mgmt = "0" > > > > > vif = [ "type=ioemu, mac=00:16:3e:d7:d7:5d, > > bridge=xenbr0" > > > ] > > > > > disk = [ "phy:/dev/virtuals/ts,hda,w", > > > > > > > > > "file:/media/iso/windows_server_2008_r2_sp1.iso,hdc:cdrom,r" ] > > > > > on_poweroff = "destroy" > > > > > on_reboot = "restart" > > > > > on_crash = "restart" > > > > > viridian = "1" > > > > > device_model = "/usr/lib/xen/bin/qemu-dm" > > > > > boot = "dc" > > > > > snapshot = "0" > > > > > vncconsole = "1" > > > > > sdl = "0" > > > > > opengl = "0" > > > > > vnc = "1" > > > > > nographic = "0" > > > > > stdvga = "0" > > > > > tsc_mode = "1" > > > > > monitor = "0" > > > > > localtime = "1" > > > > > usb = "0" > > > > > keymap = "fi" > > > > > xen_platform_pci = "1" > > > > > pci_msitranslate = "1" > > > > > pci_power_mgmt = "0" > > > > > > > > > > 2012/10/1 Pasi Kärkkäinen > > <[1][2][8][14]pasik@iki.fi> > > > > > > > > > > On Mon, Oct 01, 2012 at 06:46:08PM +0300, > > Valtteri > > > Kiviniemi > > > > wrote: > > > > > > Hi, > > > > > > > > > > > > Yes, I have viridian=1 on my domU > config. > > > > > > > > > > > > > > > > Try with some known good domU configfile. > > > > > > > > > > -- Pasi > > > > > > 2012/10/1 Pasi Kärkkäinen > > > <[1][2][3][9][15]pasik@iki.fi> > > > > > > > > > > > > On Mon, Oct 01, 2012 at 05:06:53PM > +0300, > > > Valtteri > > > > Kiviniemi > > > > > wrote: > > > > > > > Hi, > > > > > > > > > > > > > > I''m now using 3.6.0 and can''t > > reproduce that > > > crash > > > > anymore, > > > > > so it > > > > > > seems > > > > > > > that it was a kernel bug. > > > > > > > > > > > > > > > > > > > OK. > > > > > > > However I''m still getting black > > screen on > > > VNC > > > > > > > when trying to install Windows > Server > > 2008 > > > R2. I can > > > > see the > > > > > > "windows is > > > > > > > loading files" screen but after > the > > > installer starts > > > > the VNC > > > > > > display goes > > > > > > > black. > > > > > > > > > > > > > > Any ideas? > > > > > > > > > > > > > > > > > > > Do you have viridian=1 specified for > the > > windows > > > vm? > > > > > > > > > > > > -- Pasi > > > > > > > > > > > > > - Valtteri > > > > > > > > > > > > > > 2012/10/1 Pasi Kärkkäinen > > > <[1][2][3][4][10][16]pasik@iki.fi> > > > > > > > > > > > > > > On Sun, Sep 30, 2012 at > 11:18:03PM > > +0300, > > > Valtteri > > > > > Kiviniemi > > > > > > wrote: > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > > > Hello, > > > > > > > > I''m trying to get Windows > > Server 2008 > > > R2 > > > > installation > > > > > > booting on > > > > > > > Xen > > > > > > > > 4.0.4. Using the following > > config: > > > > > > > > > > > > > > > > > > > > > > <snip> > > > > > > > > > > > > > > > > The domU will start > booting > > just > > > fine, but > > > > after a > > > > > few > > > > > > minutes the > > > > > > > VNC > > > > > > > > screen goes black. After > that > > when > > > typing "xm > > > > destroy > > > > > ts" it > > > > > > will > > > > > > > trigger > > > > > > > > a kernel BUG: > > > > > > > > > > > > > > > > BUG: unable to handle > kernel > > NULL > > > pointer > > > > dereference > > > > > at > > > > > > > 0000000000000030 > > > > > > > > IP: [<ffffffff810c50c4>] > > > iput+0x3e/0x195 > > > > > > > > PGD 0 > > > > > > > > Oops: 0000 [#1] SMP > > > > > > > > CPU 6 > > > > > > > > Pid: 3571, comm: qemu-dm > Not > > tainted > > > > 3.5.0-dom0 #1 > > > > > > > > > > > > > > First of all upgrade to latest > > 3.5.x Linux > > > kernel > > > > release > > > > > .. so > > > > > > at least > > > > > > > 3.5.4. > > > > > > > > > > > > > > -- Pasi > > > > > > > > > > > > > > > /DQ77MK > > > > > > > > RIP: > e030:[<ffffffff810c50c4>] > > > > [<ffffffff810c50c4>] > > > > > > > iput+0x3e/0x195 > > > > > > > > RSP: e02b:ffff8800389ffbf8 > > EFLAGS: > > > 00010246 > > > > > > > > RAX: 0000000000000001 RBX: > > > ffff8800377b0720 > > > > RCX: > > > > > > ffff8800501c0000 > > > > > > > > RDX: ffff8800501c0000 RSI: > > > ffff8800377b0790 > > > > RDI: > > > > > > ffff8800377b0790 > > > > > > > > RBP: 0000000000000000 R08: > > > ffffffff815cdd00 > > > > R09: > > > > > > 0000000000000016 > > > > > > > > R10: fefefefefefefeff R11: > > > ffff8800377b0400 > > > > R12: > > > > > > 00000001000a3e0c > > > > > > > > R13: 0000000000000000 R14: > > > 00000001000a3e0c > > > > R15: > > > > > > ffff8800389ffc28 > > > > > > > > FS: > 00007f1af70a8700(0000) > > > > GS:ffff880050180000(0000) > > > > > > > > knlGS:0000000000000000 > > > > > > > > CS: e033 DS: 0000 ES: > 0000 > > CR0: > > > > 000000008005003b > > > > > > > > CR2: 0000000000000030 CR3: > > > 000000000156d000 > > > > CR4: > > > > > > 0000000000002660 > > > > > > > > DR0: 0000000000000000 DR1: > > > 0000000000000000 > > > > DR2: > > > > > > 0000000000000000 > > > > > > > > DR3: 0000000000000000 DR6: > > > 00000000ffff0ff0 > > > > DR7: > > > > > > 0000000000000400 > > > > > > > > Process qemu-dm (pid: > 3571, > > > threadinfo > > > > > ffff8800389fe000, > > > > > > task > > > > > > > > ffff88003a721260) > > > > > > > > Stack: > > > > > > > > ffff88003a6d6400 > > ffff8800377b0000 > > > > 00000001000a3e0c > > > > > > > ffffffff8133ce8f > > > > > > > > ffff8800377b0400 > > ffffffff8134b6cd > > > > ffff8800389ffc28 > > > > > > > ffff8800389ffc28 > > > > > > > > ffff8800377b00f8 > > ffff8800377b0680 > > > > ffff880038cdcd60 > > > > > > > ffff8800377b0000 > > > > > > > > Call Trace: > > > > > > > > [<ffffffff8133ce8f>] ? > > > > sk_release_kernel+0x23/0x39 > > > > > > > > [<ffffffff8134b6cd>] ? > > > > netdev_run_todo+0x1e9/0x206 > > > > > > > > [<ffffffff8129798f>] ? > > > > tun_chr_close+0x4c/0x7b > > > > > > > > [<ffffffff810b39d3>] ? > > > fput+0xe4/0x1c5 > > > > > > > > [<ffffffff810b202c>] ? > > > filp_close+0x61/0x68 > > > > > > > > [<ffffffff81035e62>] ? > > > > put_files_struct+0x62/0xb9 > > > > > > > > [<ffffffff81036374>] ? > > > do_exit+0x24a/0x74c > > > > > > > > [<ffffffff81036906>] ? > > > > do_group_exit+0x6b/0x9d > > > > > > > > [<ffffffff8103ea0b>] ? > > > > > get_signal_to_deliver+0x449/0x46e > > > > > > > > [<ffffffff81009fa5>] ? > > > do_signal+0x28/0x4c4 > > > > > > > > [<ffffffff81027079>] ? > > > > > pvclock_clocksource_read+0x48/0xbf > > > > > > > > [<ffffffff8105b745>] ? > > > ktime_get_ts+0x66/0xa8 > > > > > > > > [<ffffffff810bfb18>] ? > > > > > poll_select_copy_remaining+0xe0/0xf5 > > > > > > > > [<ffffffff8100a48d>] ? > > > > do_notify_resume+0x3b/0x74 > > > > > > > > [<ffffffff81411a70>] ? > > > int_signal+0x12/0x17 > > > > > > > > Code: 00 00 00 40 74 02 > 0f 0b > > 48 8d > > > 77 70 48 > > > > 8d bf 08 > > > > > 01 00 > > > > > > 00 e8 > > > > > > > 8b 71 10 > > > > > > > > 00 85 c0 0f 84 5d 01 00 > 00 48 > > 8b 6b > > > 18 f6 83 > > > > 80 00 00 > > > > > 00 08 > > > > > > <4c> 8b > > > > > > > 65 30 > > > > > > > > 74 11 be 68 05 00 00 48 > c7 c7 > > 8e df > > > 4f 81 e8 > > > > bb d0 > > > > > > > > RIP [<ffffffff810c50c4>] > > > iput+0x3e/0x195 > > > > > > > > RSP <ffff8800389ffbf8> > > > > > > > > CR2: 0000000000000030 > > > > > > > > ---[ end trace > > 67cc1654658fedcc ]--- > > > > > > > > Fixing recursive fault but > > reboot is > > > needed! > > > > > > > > > > > > > > > > I also tested Xen 4.2.0 > and > > problem > > > is the > > > > same. So > > > > > is this > > > > > > a Xen > > > > > > > bug or a > > > > > > > > kernel bug? I am running > > vanilla > > > > > [1][2][3][4][5][11][17]kernel.org kernel > > > > > > 3.5.0 and > > > > > > > my > > > > > > > > hardware is Intel Core > i7-3770 > > CPU > > > and Intel > > > > DQ77MK > > > > > > motherboard > > > > > > > with > > > > > > > > latest bios. > > > > > > > > > > > > > > > > Best regards, > > > > > > > > Valtteri Kiviniemi > > > > > > > > > > > > > > > > References > > > > > > > > > > > > > > > > Visible links > > > > > > > > 1. > > [3][4][5][6][12][18]http://kernel.org/ > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > Xen-devel mailing list > > > > > > > > > > [4][5][6][7][13][19]Xen-devel@lists.xen.org > > > > > > > > > > > [5][6][7][8][14][20]http://lists.xen.org/xen-devel > > > > > > > > > > > > > > References > > > > > > > > > > > > > > Visible links > > > > > > > 1. > > mailto:[7][8][9][15][21]pasik@iki.fi > > > > > > > 2. > > [8][9][10][16][22]http://kernel.org/ > > > > > > > 3. > > [9][10][11][17][23]http://kernel.org/ > > > > > > > 4. > > > mailto:[10][11][12][18][24]Xen-devel@lists.xen.org > > > > > > > 5. > > > [11][12][13][19][25]http://lists.xen.org/xen-devel > > > > > > > > > > > > References > > > > > > > > > > > > Visible links > > > > > > 1. mailto:[13][14][20][26]pasik@iki.fi > > > > > > 2. mailto:[14][15][21][27]pasik@iki.fi > > > > > > 3. [15][16][22][28]http://kernel.org/ > > > > > > 4. [16][17][23][29]http://kernel.org/ > > > > > > 5. > > mailto:[17][18][24][30]Xen-devel@lists.xen.org > > > > > > 6. > > [18][19][25][31]http://lists.xen.org/xen-devel > > > > > > 7. mailto:[19][20][26][32]pasik@iki.fi > > > > > > 8. [20][21][27][33]http://kernel.org/ > > > > > > 9. [21][22][28][34]http://kernel.org/ > > > > > > 10. > > mailto:[22][23][29][35]Xen-devel@lists.xen.org > > > > > > 11. > > [23][24][30][36]http://lists.xen.org/xen-devel > > > > > > > > > > References > > > > > > > > > > Visible links > > > > > 1. mailto:[25][31][37]pasik@iki.fi > > > > > 2. mailto:[26][32][38]pasik@iki.fi > > > > > 3. mailto:[27][33][39]pasik@iki.fi > > > > > 4. [28][34][40]http://kernel.org/ > > > > > 5. [29][35][41]http://kernel.org/ > > > > > 6. mailto:[30][36][42]Xen-devel@lists.xen.org > > > > > 7. [31][37][43]http://lists.xen.org/xen-devel > > > > > 8. mailto:[32][38][44]pasik@iki.fi > > > > > 9. [33][39][45]http://kernel.org/ > > > > > 10. [34][40][46]http://kernel.org/ > > > > > 11. mailto:[35][41][47]Xen-devel@lists.xen.org > > > > > 12. [36][42][48]http://lists.xen.org/xen-devel > > > > > 13. mailto:[37][43][49]pasik@iki.fi > > > > > 14. mailto:[38][44][50]pasik@iki.fi > > > > > 15. [39][45][51]http://kernel.org/ > > > > > 16. [40][46][52]http://kernel.org/ > > > > > 17. mailto:[41][47][53]Xen-devel@lists.xen.org > > > > > 18. [42][48][54]http://lists.xen.org/xen-devel > > > > > 19. mailto:[43][49][55]pasik@iki.fi > > > > > 20. [44][50][56]http://kernel.org/ > > > > > 21. [45][51][57]http://kernel.org/ > > > > > 22. mailto:[46][52][58]Xen-devel@lists.xen.org > > > > > 23. [47][53][59]http://lists.xen.org/xen-devel > > > > > > > > References > > > > > > > > Visible links > > > > 1. mailto:[54][60]pasik@iki.fi > > > > 2. mailto:[55][61]pasik@iki.fi > > > > 3. mailto:[56][62]pasik@iki.fi > > > > 4. mailto:[57][63]pasik@iki.fi > > > > 5. [58][64]http://kernel.org/ > > > > 6. [59][65]http://kernel.org/ > > > > 7. mailto:[60][66]Xen-devel@lists.xen.org > > > > 8. [61][67]http://lists.xen.org/xen-devel > > > > 9. mailto:[62][68]pasik@iki.fi > > > > 10. [63][69]http://kernel.org/ > > > > 11. [64][70]http://kernel.org/ > > > > 12. mailto:[65][71]Xen-devel@lists.xen.org > > > > 13. [66][72]http://lists.xen.org/xen-devel > > > > 14. mailto:[67][73]pasik@iki.fi > > > > 15. mailto:[68][74]pasik@iki.fi > > > > 16. [69][75]http://kernel.org/ > > > > 17. [70][76]http://kernel.org/ > > > > 18. mailto:[71][77]Xen-devel@lists.xen.org > > > > 19. [72][78]http://lists.xen.org/xen-devel > > > > 20. mailto:[73][79]pasik@iki.fi > > > > 21. [74][80]http://kernel.org/ > > > > 22. [75][81]http://kernel.org/ > > > > 23. mailto:[76][82]Xen-devel@lists.xen.org > > > > 24. [77][83]http://lists.xen.org/xen-devel > > > > 25. mailto:[78][84]pasik@iki.fi > > > > 26. mailto:[79][85]pasik@iki.fi > > > > 27. mailto:[80][86]pasik@iki.fi > > > > 28. [81][87]http://kernel.org/ > > > > 29. [82][88]http://kernel.org/ > > > > 30. mailto:[83][89]Xen-devel@lists.xen.org > > > > 31. [84][90]http://lists.xen.org/xen-devel > > > > 32. mailto:[85][91]pasik@iki.fi > > > > 33. [86][92]http://kernel.org/ > > > > 34. [87][93]http://kernel.org/ > > > > 35. mailto:[88][94]Xen-devel@lists.xen.org > > > > 36. [89][95]http://lists.xen.org/xen-devel > > > > 37. mailto:[90][96]pasik@iki.fi > > > > 38. mailto:[91][97]pasik@iki.fi > > > > 39. [92][98]http://kernel.org/ > > > > 40. [93][99]http://kernel.org/ > > > > 41. mailto:[94][100]Xen-devel@lists.xen.org > > > > 42. [95][101]http://lists.xen.org/xen-devel > > > > 43. mailto:[96][102]pasik@iki.fi > > > > 44. [97][103]http://kernel.org/ > > > > 45. [98][104]http://kernel.org/ > > > > 46. mailto:[99][105]Xen-devel@lists.xen.org > > > > 47. [100][106]http://lists.xen.org/xen-devel > > > > > > References > > > > > > Visible links > > > 1. mailto:[107]kiviniemi.valtteri@gmail.com > > > 2. [108]http://ark.intel.com/products/65719/ > > > 3. > > [109] > http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > > > 4. mailto:[110]root@dataproof.fi > > > 5. mailto:[111]pasik@iki.fi > > > 6. [112]http://xen.org/ > > > 7. mailto:[113]pasik@iki.fi > > > 8. mailto:[114]pasik@iki.fi > > > 9. mailto:[115]pasik@iki.fi > > > 10. mailto:[116]pasik@iki.fi > > > 11. [117]http://kernel.org/ > > > 12. [118]http://kernel.org/ > > > 13. mailto:[119]Xen-devel@lists.xen.org > > > 14. [120]http://lists.xen.org/xen-devel > > > 15. mailto:[121]pasik@iki.fi > > > 16. [122]http://kernel.org/ > > > 17. [123]http://kernel.org/ > > > 18. mailto:[124]Xen-devel@lists.xen.org > > > 19. [125]http://lists.xen.org/xen-devel > > > 20. mailto:[126]pasik@iki.fi > > > 21. mailto:[127]pasik@iki.fi > > > 22. [128]http://kernel.org/ > > > 23. [129]http://kernel.org/ > > > 24. mailto:[130]Xen-devel@lists.xen.org > > > 25. [131]http://lists.xen.org/xen-devel > > > 26. mailto:[132]pasik@iki.fi > > > 27. [133]http://kernel.org/ > > > 28. [134]http://kernel.org/ > > > 29. mailto:[135]Xen-devel@lists.xen.org > > > 30. [136]http://lists.xen.org/xen-devel > > > 31. mailto:[137]pasik@iki.fi > > > 32. mailto:[138]pasik@iki.fi > > > 33. mailto:[139]pasik@iki.fi > > > 34. [140]http://kernel.org/ > > > 35. [141]http://kernel.org/ > > > 36. mailto:[142]Xen-devel@lists.xen.org > > > 37. [143]http://lists.xen.org/xen-devel > > > 38. mailto:[144]pasik@iki.fi > > > 39. [145]http://kernel.org/ > > > 40. [146]http://kernel.org/ > > > 41. mailto:[147]Xen-devel@lists.xen.org > > > 42. [148]http://lists.xen.org/xen-devel > > > 43. mailto:[149]pasik@iki.fi > > > 44. mailto:[150]pasik@iki.fi > > > 45. [151]http://kernel.org/ > > > 46. [152]http://kernel.org/ > > > 47. mailto:[153]Xen-devel@lists.xen.org > > > 48. [154]http://lists.xen.org/xen-devel > > > 49. mailto:[155]pasik@iki.fi > > > 50. [156]http://kernel.org/ > > > 51. [157]http://kernel.org/ > > > 52. mailto:[158]Xen-devel@lists.xen.org > > > 53. [159]http://lists.xen.org/xen-devel > > > 54. mailto:[160]pasik@iki.fi > > > 55. mailto:[161]pasik@iki.fi > > > 56. mailto:[162]pasik@iki.fi > > > 57. mailto:[163]pasik@iki.fi > > > 58. [164]http://kernel.org/ > > > 59. [165]http://kernel.org/ > > > 60. mailto:[166]Xen-devel@lists.xen.org > > > 61. [167]http://lists.xen.org/xen-devel > > > 62. mailto:[168]pasik@iki.fi > > > 63. [169]http://kernel.org/ > > > 64. [170]http://kernel.org/ > > > 65. mailto:[171]Xen-devel@lists.xen.org > > > 66. [172]http://lists.xen.org/xen-devel > > > 67. mailto:[173]pasik@iki.fi > > > 68. mailto:[174]pasik@iki.fi > > > 69. [175]http://kernel.org/ > > > 70. [176]http://kernel.org/ > > > 71. mailto:[177]Xen-devel@lists.xen.org > > > 72. [178]http://lists.xen.org/xen-devel > > > 73. mailto:[179]pasik@iki.fi > > > 74. [180]http://kernel.org/ > > > 75. [181]http://kernel.org/ > > > 76. mailto:[182]Xen-devel@lists.xen.org > > > 77. [183]http://lists.xen.org/xen-devel > > > 78. mailto:[184]pasik@iki.fi > > > 79. mailto:[185]pasik@iki.fi > > > 80. mailto:[186]pasik@iki.fi > > > 81. [187]http://kernel.org/ > > > 82. [188]http://kernel.org/ > > > 83. mailto:[189]Xen-devel@lists.xen.org > > > 84. [190]http://lists.xen.org/xen-devel > > > 85. mailto:[191]pasik@iki.fi > > > 86. [192]http://kernel.org/ > > > 87. [193]http://kernel.org/ > > > 88. mailto:[194]Xen-devel@lists.xen.org > > > 89. [195]http://lists.xen.org/xen-devel > > > 90. mailto:[196]pasik@iki.fi > > > 91. mailto:[197]pasik@iki.fi > > > 92. [198]http://kernel.org/ > > > 93. [199]http://kernel.org/ > > > 94. mailto:[200]Xen-devel@lists.xen.org > > > 95. [201]http://lists.xen.org/xen-devel > > > 96. mailto:[202]pasik@iki.fi > > > 97. [203]http://kernel.org/ > > > 98. [204]http://kernel.org/ > > > 99. mailto:[205]Xen-devel@lists.xen.org > > > 100. [206]http://lists.xen.org/xen-devel > > > > References > > > > Visible links > > 1. http://nago.fi/dmesg.txt > > 2. http://nago.fi/qemu-dm.txt > > 3. http://nago.fi/xm-dmesg.txt > > 4. http://nago.fi/domu-config.txt > > 5. http://nago.fi/dom0-config.txt > > 6. mailto:pasik@iki.fi > > 7. mailto:kiviniemi.valtteri@gmail.com > > 8. http://ark.intel.com/products/65719/ > > 9. > http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > > 10. mailto:root@dataproof.fi > > 11. mailto:pasik@iki.fi > > 12. http://xen.org/ > > 13. mailto:pasik@iki.fi > > 14. mailto:pasik@iki.fi > > 15. mailto:pasik@iki.fi > > 16. mailto:pasik@iki.fi > > 17. http://kernel.org/ > > 18. http://kernel.org/ > > 19. mailto:Xen-devel@lists.xen.org > > 20. http://lists.xen.org/xen-devel > > 21. mailto:pasik@iki.fi > > 22. http://kernel.org/ > > 23. http://kernel.org/ > > 24. mailto:Xen-devel@lists.xen.org > > 25. http://lists.xen.org/xen-devel > > 26. mailto:pasik@iki.fi > > 27. mailto:pasik@iki.fi > > 28. http://kernel.org/ > > 29. http://kernel.org/ > > 30. mailto:Xen-devel@lists.xen.org > > 31. http://lists.xen.org/xen-devel > > 32. mailto:pasik@iki.fi > > 33. http://kernel.org/ > > 34. http://kernel.org/ > > 35. mailto:Xen-devel@lists.xen.org > > 36. http://lists.xen.org/xen-devel > > 37. mailto:pasik@iki.fi > > 38. mailto:pasik@iki.fi > > 39. mailto:pasik@iki.fi > > 40. http://kernel.org/ > > 41. http://kernel.org/ > > 42. mailto:Xen-devel@lists.xen.org > > 43. http://lists.xen.org/xen-devel > > 44. mailto:pasik@iki.fi > > 45. http://kernel.org/ > > 46. http://kernel.org/ > > 47. mailto:Xen-devel@lists.xen.org > > 48. http://lists.xen.org/xen-devel > > 49. mailto:pasik@iki.fi > > 50. mailto:pasik@iki.fi > > 51. http://kernel.org/ > > 52. http://kernel.org/ > > 53. mailto:Xen-devel@lists.xen.org > > 54. http://lists.xen.org/xen-devel > > 55. mailto:pasik@iki.fi > > 56. http://kernel.org/ > > 57. http://kernel.org/ > > 58. mailto:Xen-devel@lists.xen.org > > 59. http://lists.xen.org/xen-devel > > 60. mailto:pasik@iki.fi > > 61. mailto:pasik@iki.fi > > 62. mailto:pasik@iki.fi > > 63. mailto:pasik@iki.fi > > 64. http://kernel.org/ > > 65. http://kernel.org/ > > 66. mailto:Xen-devel@lists.xen.org > > 67. http://lists.xen.org/xen-devel > > 68. mailto:pasik@iki.fi > > 69. http://kernel.org/ > > 70. http://kernel.org/ > > 71. mailto:Xen-devel@lists.xen.org > > 72. http://lists.xen.org/xen-devel > > 73. mailto:pasik@iki.fi > > 74. mailto:pasik@iki.fi > > 75. http://kernel.org/ > > 76. http://kernel.org/ > > 77. mailto:Xen-devel@lists.xen.org > > 78. http://lists.xen.org/xen-devel > > 79. mailto:pasik@iki.fi > > 80. http://kernel.org/ > > 81. http://kernel.org/ > > 82. mailto:Xen-devel@lists.xen.org > > 83. http://lists.xen.org/xen-devel > > 84. mailto:pasik@iki.fi > > 85. mailto:pasik@iki.fi > > 86. mailto:pasik@iki.fi > > 87. http://kernel.org/ > > 88. http://kernel.org/ > > 89. mailto:Xen-devel@lists.xen.org > > 90. http://lists.xen.org/xen-devel > > 91. mailto:pasik@iki.fi > > 92. http://kernel.org/ > > 93. http://kernel.org/ > > 94. mailto:Xen-devel@lists.xen.org > > 95. http://lists.xen.org/xen-devel > > 96. mailto:pasik@iki.fi > > 97. mailto:pasik@iki.fi > > 98. http://kernel.org/ > > 99. http://kernel.org/ > > 100. mailto:Xen-devel@lists.xen.org > > 101. http://lists.xen.org/xen-devel > > 102. mailto:pasik@iki.fi > > 103. http://kernel.org/ > > 104. http://kernel.org/ > > 105. mailto:Xen-devel@lists.xen.org > > 106. http://lists.xen.org/xen-devel > > 107. mailto:kiviniemi.valtteri@gmail.com > > 108. http://ark.intel.com/products/65719/ > > 109. > http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > > 110. mailto:root@dataproof.fi > > 111. mailto:pasik@iki.fi > > 112. http://xen.org/ > > 113. mailto:pasik@iki.fi > > 114. mailto:pasik@iki.fi > > 115. mailto:pasik@iki.fi > > 116. mailto:pasik@iki.fi > > 117. http://kernel.org/ > > 118. http://kernel.org/ > > 119. mailto:Xen-devel@lists.xen.org > > 120. http://lists.xen.org/xen-devel > > 121. mailto:pasik@iki.fi > > 122. http://kernel.org/ > > 123. http://kernel.org/ > > 124. mailto:Xen-devel@lists.xen.org > > 125. http://lists.xen.org/xen-devel > > 126. mailto:pasik@iki.fi > > 127. mailto:pasik@iki.fi > > 128. http://kernel.org/ > > 129. http://kernel.org/ > > 130. mailto:Xen-devel@lists.xen.org > > 131. http://lists.xen.org/xen-devel > > 132. mailto:pasik@iki.fi > > 133. http://kernel.org/ > > 134. http://kernel.org/ > > 135. mailto:Xen-devel@lists.xen.org > > 136. http://lists.xen.org/xen-devel > > 137. mailto:pasik@iki.fi > > 138. mailto:pasik@iki.fi > > 139. mailto:pasik@iki.fi > > 140. http://kernel.org/ > > 141. http://kernel.org/ > > 142. mailto:Xen-devel@lists.xen.org > > 143. http://lists.xen.org/xen-devel > > 144. mailto:pasik@iki.fi > > 145. http://kernel.org/ > > 146. http://kernel.org/ > > 147. mailto:Xen-devel@lists.xen.org > > 148. http://lists.xen.org/xen-devel > > 149. mailto:pasik@iki.fi > > 150. mailto:pasik@iki.fi > > 151. http://kernel.org/ > > 152. http://kernel.org/ > > 153. mailto:Xen-devel@lists.xen.org > > 154. http://lists.xen.org/xen-devel > > 155. mailto:pasik@iki.fi > > 156. http://kernel.org/ > > 157. http://kernel.org/ > > 158. mailto:Xen-devel@lists.xen.org > > 159. http://lists.xen.org/xen-devel > > 160. mailto:pasik@iki.fi > > 161. mailto:pasik@iki.fi > > 162. mailto:pasik@iki.fi > > 163. mailto:pasik@iki.fi > > 164. http://kernel.org/ > > 165. http://kernel.org/ > > 166. mailto:Xen-devel@lists.xen.org > > 167. http://lists.xen.org/xen-devel > > 168. mailto:pasik@iki.fi > > 169. http://kernel.org/ > > 170. http://kernel.org/ > > 171. mailto:Xen-devel@lists.xen.org > > 172. http://lists.xen.org/xen-devel > > 173. mailto:pasik@iki.fi > > 174. mailto:pasik@iki.fi > > 175. http://kernel.org/ > > 176. http://kernel.org/ > > 177. mailto:Xen-devel@lists.xen.org > > 178. http://lists.xen.org/xen-devel > > 179. mailto:pasik@iki.fi > > 180. http://kernel.org/ > > 181. http://kernel.org/ > > 182. mailto:Xen-devel@lists.xen.org > > 183. http://lists.xen.org/xen-devel > > 184. mailto:pasik@iki.fi > > 185. mailto:pasik@iki.fi > > 186. mailto:pasik@iki.fi > > 187. http://kernel.org/ > > 188. http://kernel.org/ > > 189. mailto:Xen-devel@lists.xen.org > > 190. http://lists.xen.org/xen-devel > > 191. mailto:pasik@iki.fi > > 192. http://kernel.org/ > > 193. http://kernel.org/ > > 194. mailto:Xen-devel@lists.xen.org > > 195. http://lists.xen.org/xen-devel > > 196. mailto:pasik@iki.fi > > 197. mailto:pasik@iki.fi > > 198. http://kernel.org/ > > 199. http://kernel.org/ > > 200. mailto:Xen-devel@lists.xen.org > > 201. http://lists.xen.org/xen-devel > > 202. mailto:pasik@iki.fi > > 203. http://kernel.org/ > > 204. http://kernel.org/ > > 205. mailto:Xen-devel@lists.xen.org > > 206. http://lists.xen.org/xen-devel >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Pasi Kärkkäinen
2012-Oct-02 13:54 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
On Tue, Oct 02, 2012 at 04:46:37PM +0300, Valtteri Kiviniemi wrote:> Hi, > > I have not enabled debug on Xen or dom0 kernel. Could you tell me the > parameters for Xen coompilation needed to enable debugging? And If you > would also happen to know what are the options needed to enable kernel > debugging in menuconfig? Well I can probably manage to get the kernel > debugging enabled myself, but if you happen to know them please share so > maybe I can get everything enabled at the first try :) >I didn''t mean compilation options, just the xen/kernel cmdline options, please use these: xen.gz loglvl=all guest_loglvl=all sync_console lapic=debug apic_verbosity=debug apic=debug iommu=off vmlinuz console=hvc0 earlyprintk=xen nomodeset initcall_debug debug loglevel=10 Plus your serial console settings for xen.gz, of course. -- Pasi> Thanks! > > - Valtteri > > 2012/10/2 Pasi Kärkkäinen <[1]pasik@iki.fi> > > On Tue, Oct 02, 2012 at 04:01:04PM +0300, Valtteri Kiviniemi wrote: > > Hi, > > > > I already tried 3.2, 3.5, 3.5.0, 3.6.0-rc7 and 3.6.0, same problem > all of > > those. My dom0 config is the same config that I''am using on other > server > > where HVM is working, so I dont think that it is a config problem. > I have > > triple checked everything and all should be ok. dom0 dmesg shows > the same > > crash that I have previously posted here. /var/log/xen/ does not > contain > > any specific errors. > > > > Could this be some kind of broblem with my motherboard bios being > buggy or > > CPU not supported? I''m using the new intel Ivy Bridge processor > which has > > integrated GPU, but that should not probably cause these kind of > problems. > > Or maybe some ACPI problem? xm dmesg is showing some notices about > ACPI. > > Is there any ACPI kernel parameters that I should try booting? This > has to > > be somekind of problem with my hardware, or then maybe it could be > a > > kernel problem too. I just really cant figure this out myself, I > have > > tried everything. > > > > Hmm.. I have some distant memories of seeing a patch that fixes a bug > on recent Ivy Bridge systems, but I can''t find a link right now. > Maybe you''re affected by that.. > > Also: Did you already post the crash log, with all the debug/verbose > options enabled for both Xen and dom0 kernel? > > -- Pasi > > Lets take a quick summary of what has been tested, what hardware > I''m using > > etc. > > > > Xen-versions tested: 4.2.0, 4.0.4 > > Kernel-versions tested: 3.2.0, 3.5.0, 3.5.4, 3.6.0-rc7, 3.6.0 > > > > Host OS: Debian testing/wheezy, udev version 175-7, 2.13-35, python > > version 2.7.3~rc2-2.1 > > > > Hardware: > > > > CPU: Intel Core i7-3770 3.4GHz > > MB: Intel DQ77MK (latest bios updated) > > Memory: 32GB (4 x 8GB DDR3-1600MHz) > > > > All relevant log files and configs: > > > > dom0 dmesg: [1][2]http://nago.fi/dmesg.txt > > qemu-dm log: [2][3]http://nago.fi/qemu-dm.txt > > xm dmesg log: [3][4]http://nago.fi/xm-dmesg.txt > > domU config: [4][5]http://nago.fi/domu-config.txt > > dom0 kernel config: [5][6]http://nago.fi/dom0-config.txt > > > > I have also tried playing with every setting on that domU that I > can think > > of and tried different configs etc. > > > > - Valtteri > > > > 2012/10/2 Pasi Kärkkäinen <[6][7]pasik@iki.fi> > > > > On Tue, Oct 02, 2012 at 03:11:07PM +0300, Valtteri Kiviniemi > wrote: > > > Hi, > > > > > > Another update: > > > > > > I wanted to check that if a Linux HVM would boot with > working VNC > > console, > > > so I tried to launch a Debian Squeeze installer on HVM. It > refused > > to > > > start ant told me that vbd hotplug scripts were not working. > After > > that > > > failure even the Windows domU would not anymore start which > was > > previously > > > starting ok. > > > > > > The hotplug scripts also starts hanging on the processes. > > > > > > root 9401 0.1 0.1 17700 1640 ? S 15:05 > 0:00 > > /bin/bash > > > /etc/xen/scripts/xen-hotplug-cleanup > > > root 9441 0.1 0.1 17700 1644 ? S 15:05 > 0:00 > > /bin/bash > > > /etc/xen/scripts/xen-hotplug-cleanup > > > root 9481 0.1 0.1 17700 1640 ? S 15:05 > 0:00 > > /bin/bash > > > /etc/xen/scripts/xen-hotplug-cleanup > > > root 9560 0.1 0.1 17700 1640 ? S 15:05 > 0:00 > > /bin/bash > > > /etc/xen/scripts/xen-hotplug-cleanup > > > root 10738 0.1 0.1 17696 1636 ? S 15:05 > 0:00 > > /bin/bash > > > /etc/xen/scripts/xen-hotplug-cleanup > > > root 10747 0.1 0.1 17792 1736 ? S 15:05 > 0:00 > > /bin/bash > > > /etc/xen/scripts/block remove > > > root 11286 0.0 0.0 4080 324 ? S 15:06 > 0:00 > > sleep 1 > > > root 11290 0.0 0.0 4080 324 ? S 15:06 > 0:00 > > sleep 1 > > > root 11294 0.0 0.0 4080 324 ? S 15:06 > 0:00 > > sleep 1 > > > root 11298 0.0 0.0 4080 324 ? S 15:06 > 0:00 > > sleep 1 > > > root 11302 0.0 0.0 4080 320 ? S 15:06 > 0:00 > > sleep 1 > > > root 11306 0.0 0.0 4080 320 ? S 15:06 > 0:00 > > sleep 1 > > > > > > Then I did a xm destroy and I had again the kernel BUG on > dmesg. So > > it > > > seems that the problem is not fixed by using 3.6.0. Udev > version is > > 175-7. > > > > > > > So you have definitely something broken in your system, > > probably in your dom0 kernel. Try with Linux 3.5.4 or 3.4.x, > > and see how that goes. > > > > Any errors in dom0 dmesg? How about in /var/log/xen/* ? > > > > -- Pasi > > > > > > > > > > > 2012/10/1 Valtteri Kiviniemi > <[1][7][8]kiviniemi.valtteri@gmail.com> > > > > > > Hi, > > > > > > CPU: Intel Core i7-3770 3.4GHz > > > [2][8][9]http://ark.intel.com/products/65719/ > > > > > > MB: Intel DQ77MK (latest bios updated) > > > > > > [3][9][10]http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > > > > > > Memory: 32GB (4 x 8GB DDR3-1600MHz) > > > > > > Host is Debian wheezy/testing, Xen 4.0.4 and latest 3.6.0 > kernel. > > > > > > Noticed also some errors in xm dmesg: > > > > > > root@xen-2:~# xm dmesg > > > > > > (XEN) Xen version 4.0.4 ([4][10][11]root@dataproof.fi) > (gcc version > > 4.7.1 > > > (Debian 4.7.1-7) ) Sun Sep 30 20:28:26 EEST 2012 > > > (XEN) Latest ChangeSet: unavailable > > > (XEN) Bootloader: GNU GRUB 0.97 > > > (XEN) Command line: dom0_mem=1280M cpufreq=xen > clocksource=hpet > > > (XEN) Video information: > > > (XEN) VGA is text mode 80x25, font 8x16 > > > (XEN) VBE/DDC methods: none; EDID transfer time: 0 > seconds > > > (XEN) EDID info not retrieved because no DDC retrieval > method > > detected > > > (XEN) Disc information: > > > (XEN) Found 4 MBR signatures > > > (XEN) Found 4 EDD information structures > > > (XEN) Xen-e820 RAM map: > > > (XEN) 0000000000000000 - 000000000009d800 (usable) > > > (XEN) 000000000009d800 - 00000000000a0000 (reserved) > > > (XEN) 00000000000e0000 - 0000000000100000 (reserved) > > > (XEN) 0000000000100000 - 0000000020000000 (usable) > > > (XEN) 0000000020000000 - 0000000020200000 (reserved) > > > (XEN) 0000000020200000 - 0000000040004000 (usable) > > > (XEN) 0000000040004000 - 0000000040005000 (reserved) > > > (XEN) 0000000040005000 - 00000000dbe44000 (usable) > > > (XEN) 00000000dbe44000 - 00000000dc2d7000 (reserved) > > > (XEN) 00000000dc2d7000 - 00000000dc2e7000 (ACPI data) > > > (XEN) 00000000dc2e7000 - 00000000dc40c000 (ACPI NVS) > > > (XEN) 00000000dc40c000 - 00000000dc6af000 (reserved) > > > (XEN) 00000000dc6af000 - 00000000dc6b0000 (usable) > > > (XEN) 00000000dc6b0000 - 00000000dc6f3000 (ACPI NVS) > > > (XEN) 00000000dc6f3000 - 00000000dd000000 (usable) > > > (XEN) 00000000dd800000 - 00000000dfa00000 (reserved) > > > (XEN) 00000000f8000000 - 00000000fc000000 (reserved) > > > (XEN) 00000000fec00000 - 00000000fec01000 (reserved) > > > (XEN) 00000000fed00000 - 00000000fed04000 (reserved) > > > (XEN) 00000000fed1c000 - 00000000fed20000 (reserved) > > > (XEN) 00000000fee00000 - 00000000fee01000 (reserved) > > > (XEN) 00000000ff000000 - 0000000100000000 (reserved) > > > (XEN) 0000000100000000 - 000000081e600000 (usable) > > > (XEN) ACPI: RSDP 000F0490, 0024 (r2 INTEL) > > > (XEN) ACPI: XSDT DC2DB080, 007C (r1 INTEL DQ77MK > 32 AMI > > > 10013) > > > (XEN) ACPI: FACP DC2E51F0, 010C (r5 INTEL DQ77MK > 32 AMI > > > 10013) > > > (XEN) ACPI Warning (tbfadt-0232): FADT (revision 5) is > longer > > than ACPI > > > 2.0 version, truncating length 0x10C to 0xF4 [20070126] > > > (XEN) ACPI: DSDT DC2DB188, A061 (r2 INTEL DQ77MK > 32 INTL > > > 20051117) > > > (XEN) ACPI: FACS DC40A080, 0040 > > > (XEN) ACPI: APIC DC2E5300, 0092 (r3 INTEL DQ77MK > 32 AMI > > > 10013) > > > (XEN) ACPI: FPDT DC2E5398, 0044 (r1 INTEL DQ77MK > 32 AMI > > > 10013) > > > (XEN) ACPI: TCPA DC2E53E0, 0032 (r2 INTEL DQ77MK > 32 MSFT > > > 1000013) > > > (XEN) ACPI: MCFG DC2E5418, 003C (r1 INTEL DQ77MK > 32 MSFT > > > 97) > > > (XEN) ACPI: HPET DC2E5458, 0038 (r1 INTEL DQ77MK > 32 AMI. > > > 5) > > > (XEN) ACPI: SSDT DC2E5490, 036D (r1 INTEL DQ77MK > 32 INTL > > > 20091112) > > > (XEN) ACPI: SSDT DC2E5800, 09AA (r1 INTEL DQ77MK > 32 INTL > > > 20051117) > > > (XEN) ACPI: SSDT DC2E61B0, 0A92 (r1 INTEL DQ77MK > 32 INTL > > > 20051117) > > > (XEN) ACPI: DMAR DC2E6C48, 00B8 (r1 INTEL DQ77MK > 32 INTL > > > 1) > > > (XEN) ACPI: ASF! DC2E6D00, 00A5 (r32 INTEL DQ77MK > 32 > > TFSM > > > F4240) > > > (XEN) System RAM: 32682MB (33467320kB) > > > (XEN) Domain heap initialised > > > (XEN) ACPI: 32/64X FACS address mismatch in FADT - > > > dc40a080/0000000000000000, using 32 > > > (XEN) Processor #0 7:10 APIC version 21 > > > (XEN) Processor #2 7:10 APIC version 21 > > > (XEN) Processor #4 7:10 APIC version 21 > > > (XEN) Processor #6 7:10 APIC version 21 > > > (XEN) Processor #1 7:10 APIC version 21 > > > (XEN) Processor #3 7:10 APIC version 21 > > > (XEN) Processor #5 7:10 APIC version 21 > > > (XEN) Processor #7 7:10 APIC version 21 > > > (XEN) IOAPIC[0]: apic_id 2, version 32, address > 0xfec00000, GSI > > 0-23 > > > (XEN) Enabling APIC mode: Flat. Using 1 I/O APICs > > > (XEN) Switched to APIC driver x2apic_cluster. > > > (XEN) x2APIC mode enabled. > > > (XEN) Using scheduler: SMP Credit Scheduler (credit) > > > (XEN) Detected 3392.369 MHz processor. > > > (XEN) Initing memory sharing. > > > (XEN) VMX: Supported advanced features: > > > (XEN) - APIC MMIO access virtualisation > > > (XEN) - APIC TPR shadow > > > (XEN) - Extended Page Tables (EPT) > > > (XEN) - Virtual-Processor Identifiers (VPID) > > > (XEN) - Virtual NMI > > > (XEN) - MSR direct-access bitmap > > > (XEN) - Unrestricted Guest > > > (XEN) EPT supports 2MB super page. > > > (XEN) HVM: ASIDs enabled. > > > (XEN) HVM: VMX enabled > > > (XEN) HVM: Hardware Assisted Paging detected. > > > (XEN) Intel VT-d Snoop Control not enabled. > > > (XEN) Intel VT-d Dom0 DMA Passthrough not enabled. > > > (XEN) Intel VT-d Queued Invalidation enabled. > > > (XEN) Intel VT-d Interrupt Remapping enabled. > > > (XEN) I/O virtualisation enabled > > > (XEN) - Dom0 mode: Relaxed > > > (XEN) Enabled directed EOI with ioapic_ack_old on! > > > (XEN) Total of 8 processors activated. > > > (XEN) ENABLING IO-APIC IRQs > > > (XEN) -> Using old ACK method > > > (XEN) TSC is reliable, synchronization unnecessary > > > (XEN) Platform timer appears to have unexpectedly wrapped > 1 > > times. > > > (XEN) Platform timer is 14.318MHz HPET > > > (XEN) Allocated console ring of 16 KiB. > > > (XEN) Brought up 8 CPUs > > > (XEN) *** LOADING DOMAIN 0 *** > > > (XEN) Xen kernel: 64-bit, lsb, compat32 > > > (XEN) Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> > > 0x1ae7000 > > > (XEN) PHYSICAL MEMORY ARRANGEMENT: > > > (XEN) Dom0 alloc.: 0000000804000000->0000000806000000 > (319488 > > pages > > > to be allocated) > > > (XEN) VIRTUAL MEMORY ARRANGEMENT: > > > (XEN) Loaded kernel: ffffffff81000000->ffffffff81ae7000 > > > (XEN) Init. ramdisk: ffffffff81ae7000->ffffffff81ae7000 > > > (XEN) Phys-Mach map: ffffffff81ae7000->ffffffff81d67000 > > > (XEN) Start info: ffffffff81d67000->ffffffff81d674b4 > > > (XEN) Page tables: ffffffff81d68000->ffffffff81d7b000 > > > (XEN) Boot stack: ffffffff81d7b000->ffffffff81d7c000 > > > (XEN) TOTAL: ffffffff80000000->ffffffff82000000 > > > (XEN) ENTRY ADDRESS: ffffffff815e3210 > > > (XEN) Dom0 has maximum 8 VCPUs > > > (XEN) [VT-D]iommu.c:718: BIOS did not enable IGD for VT > properly. > > > Disabling IGD VT-d engine. > > > (XEN) Scrubbing Free RAM: done. > > > (XEN) Xen trace buffers: disabled > > > (XEN) Std. Loglevel: Errors and warnings > > > (XEN) Guest Loglevel: Nothing (Rate-limited: Errors and > warnings) > > > (XEN) Xen is relinquishing VGA console. > > > (XEN) *** Serial input -> DOM0 (type ''CTRL-a'' three times > to > > switch > > > input to Xen) > > > (XEN) Freed 172kB init memory. > > > (XEN) traps.c:2333:d0 Domain attempted WRMSR > 000000000000008b > > from > > > 00000012:00000000 to 00000000:00000000. > > > > > > - Valtteri > > > > > > 2012/10/1 Pasi Kärkkäinen <[5][11][12]pasik@iki.fi> > > > > > > On Mon, Oct 01, 2012 at 09:12:50PM +0300, Valtteri > Kiviniemi > > wrote: > > > > Hi, > > > > > > > > Lowering memory or vcpu''s does not help, problem is > the > > same. I > > > originally > > > > installed Xen 4.2.0 and the problem was same on > that too. > > Then I > > > > downgraded back to 4.0.4 since I thought that this > might > > be a bug > > > on > > > > 4.2.0. I have been previously running Windows > Server 2008 > > R2 > > > succesfully > > > > on Xen 4.0.x on different hardware with this same > config. > > > Hypervisor is > > > > 64bit and windows is 64bit. > > > > > > > > Any ideas what to try next? > > > > > > > > > > What kind of hardware is that? > > > > > > [6][12][13]xen.org automated testing regularly tests > Windows VMs, > > and it works > > > OK there. > > > > > > -- Pasi > > > > Ps. qemu-dm.log is the following: > > > > > > > > domid: 10 > > > > config qemu network with xen bridge for tap10.0 > xenbr0 > > > > Using file /dev/virtuals/ts in read-write mode > > > > Using file > /media/iso/windows_server_2008_r2_sp1.iso in > > read-only > > > mode > > > > Watching > /local/domain/0/device-model/10/logdirty/cmd > > > > Watching /local/domain/0/device-model/10/command > > > > qemu_map_cache_init nr_buckets = 10000 size 4194304 > > > > shared page at pfn feffd > > > > buffered io page at pfn feffb > > > > Guest uuid = 52f19e23-2955-c27d-a22c-60c5d8c60d5a > > > > Time offset set 0 > > > > populating video RAM at ff000000 > > > > mapping video RAM from ff000000 > > > > Register xen platform. > > > > Done register platform. > > > > platform_fixed_ioport: changed ro/rw state of ROM > memory > > area. > > > now is rw > > > > state. > > > > > > > xs_read(/local/domain/0/device-model/10/xen_extended_power_mgmt): > > > read > > > > error > > > > medium change watch on `hdc'' (index: 1): > > > > /media/iso/windows_server_2008_r2_sp1.iso > > > > I/O request not ready: 0, ptr: 0, port: 0, data: 0, > count: > > 0, > > > size: 0 > > > > Log-dirty: no command yet. > > > > xs_read(/local/domain/10/log-throttling): read > error > > > > qemu: ignoring not-understood drive > > > `/local/domain/10/log-throttling'' > > > > medium change watch on > `/local/domain/10/log-throttling'' - > > > unknown device, > > > > ignored > > > > cirrus vga map change while on lfb mode > > > > mapping vram to f0000000 - f0400000 > > > > platform_fixed_ioport: changed ro/rw state of ROM > memory > > area. > > > now is rw > > > > state. > > > > platform_fixed_ioport: changed ro/rw state of ROM > memory > > area. > > > now is ro > > > > state. > > > > > > > > 2012/10/1 Pasi Kärkkäinen > <[1][7][13][14]pasik@iki.fi> > > > > > > > > On Mon, Oct 01, 2012 at 07:23:44PM +0300, > Valtteri > > Kiviniemi > > > wrote: > > > > > Hi, > > > > > > > > > > I have tried other config files, but the > problem is > > the > > > same. At > > > > the > > > > > moment I''m using a config file from another > server > > where I > > > have a > > > > working > > > > > Windows Server 2008 R2 installation, so I > dont > > think that > > > there is > > > > > anything wrong with my config: > > > > > > > > > > > > > Did you try with less vcpus, for example 2 ? > > > > how about with less memory, say 2 GB ? > > > > > > > > Did you try with later Xen versions? Is that a > 32bit > > Xen, or > > > 64bit Xen > > > > hypervisor? > > > > > > > > -- Pasi > > > > > kernel = "/usr/lib/xen/boot/hvmloader" > > > > > builder = "hvm" > > > > > shadow_memory = "8" > > > > > memory = "4096" > > > > > name = "ts" > > > > > vcpus = "8" > > > > > cpus = ["0", "1", "2", "3", "4", "5", "6", > "7"] > > > > > pae = "1" > > > > > acpi = "1" > > > > > apic = "1" > > > > > vfb = [ ''type=vnc, vnclisten=10.100.100.50, > > vncpasswd=xxx'' > > > ] > > > > > xen_extended_power_mgmt = "0" > > > > > vif = [ "type=ioemu, mac=00:16:3e:d7:d7:5d, > > bridge=xenbr0" > > > ] > > > > > disk = [ "phy:/dev/virtuals/ts,hda,w", > > > > > > > > > "file:/media/iso/windows_server_2008_r2_sp1.iso,hdc:cdrom,r" ] > > > > > on_poweroff = "destroy" > > > > > on_reboot = "restart" > > > > > on_crash = "restart" > > > > > viridian = "1" > > > > > device_model = "/usr/lib/xen/bin/qemu-dm" > > > > > boot = "dc" > > > > > snapshot = "0" > > > > > vncconsole = "1" > > > > > sdl = "0" > > > > > opengl = "0" > > > > > vnc = "1" > > > > > nographic = "0" > > > > > stdvga = "0" > > > > > tsc_mode = "1" > > > > > monitor = "0" > > > > > localtime = "1" > > > > > usb = "0" > > > > > keymap = "fi" > > > > > xen_platform_pci = "1" > > > > > pci_msitranslate = "1" > > > > > pci_power_mgmt = "0" > > > > > > > > > > 2012/10/1 Pasi Kärkkäinen > > <[1][2][8][14][15]pasik@iki.fi> > > > > > > > > > > On Mon, Oct 01, 2012 at 06:46:08PM +0300, > > Valtteri > > > Kiviniemi > > > > wrote: > > > > > > Hi, > > > > > > > > > > > > Yes, I have viridian=1 on my domU > config. > > > > > > > > > > > > > > > > Try with some known good domU configfile. > > > > > > > > > > -- Pasi > > > > > > 2012/10/1 Pasi Kärkkäinen > > > <[1][2][3][9][15][16]pasik@iki.fi> > > > > > > > > > > > > On Mon, Oct 01, 2012 at 05:06:53PM > +0300, > > > Valtteri > > > > Kiviniemi > > > > > wrote: > > > > > > > Hi, > > > > > > > > > > > > > > I''m now using 3.6.0 and can''t > > reproduce that > > > crash > > > > anymore, > > > > > so it > > > > > > seems > > > > > > > that it was a kernel bug. > > > > > > > > > > > > > > > > > > > OK. > > > > > > > However I''m still getting > black > > screen on > > > VNC > > > > > > > when trying to install Windows > Server > > 2008 > > > R2. I can > > > > see the > > > > > > "windows is > > > > > > > loading files" screen but > after the > > > installer starts > > > > the VNC > > > > > > display goes > > > > > > > black. > > > > > > > > > > > > > > Any ideas? > > > > > > > > > > > > > > > > > > > Do you have viridian=1 specified > for the > > windows > > > vm? > > > > > > > > > > > > -- Pasi > > > > > > > > > > > > > - Valtteri > > > > > > > > > > > > > > 2012/10/1 Pasi Kärkkäinen > > > <[1][2][3][4][10][16][17]pasik@iki.fi> > > > > > > > > > > > > > > On Sun, Sep 30, 2012 at > 11:18:03PM > > +0300, > > > Valtteri > > > > > Kiviniemi > > > > > > wrote: > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > > > Hello, > > > > > > > > I''m trying to get > Windows > > Server 2008 > > > R2 > > > > installation > > > > > > booting on > > > > > > > Xen > > > > > > > > 4.0.4. Using the > following > > config: > > > > > > > > > > > > > > > > > > > > > > <snip> > > > > > > > > > > > > > > > > The domU will start > booting > > just > > > fine, but > > > > after a > > > > > few > > > > > > minutes the > > > > > > > VNC > > > > > > > > screen goes black. > After that > > when > > > typing "xm > > > > destroy > > > > > ts" it > > > > > > will > > > > > > > trigger > > > > > > > > a kernel BUG: > > > > > > > > > > > > > > > > BUG: unable to handle > kernel > > NULL > > > pointer > > > > dereference > > > > > at > > > > > > > 0000000000000030 > > > > > > > > IP: > [<ffffffff810c50c4>] > > > iput+0x3e/0x195 > > > > > > > > PGD 0 > > > > > > > > Oops: 0000 [#1] SMP > > > > > > > > CPU 6 > > > > > > > > Pid: 3571, comm: > qemu-dm Not > > tainted > > > > 3.5.0-dom0 #1 > > > > > > > > > > > > > > First of all upgrade to > latest > > 3.5.x Linux > > > kernel > > > > release > > > > > .. so > > > > > > at least > > > > > > > 3.5.4. > > > > > > > > > > > > > > -- Pasi > > > > > > > > > > > > > > > /DQ77MK > > > > > > > > RIP: > e030:[<ffffffff810c50c4>] > > > > [<ffffffff810c50c4>] > > > > > > > iput+0x3e/0x195 > > > > > > > > RSP: > e02b:ffff8800389ffbf8 > > EFLAGS: > > > 00010246 > > > > > > > > RAX: 0000000000000001 > RBX: > > > ffff8800377b0720 > > > > RCX: > > > > > > ffff8800501c0000 > > > > > > > > RDX: ffff8800501c0000 > RSI: > > > ffff8800377b0790 > > > > RDI: > > > > > > ffff8800377b0790 > > > > > > > > RBP: 0000000000000000 > R08: > > > ffffffff815cdd00 > > > > R09: > > > > > > 0000000000000016 > > > > > > > > R10: fefefefefefefeff > R11: > > > ffff8800377b0400 > > > > R12: > > > > > > 00000001000a3e0c > > > > > > > > R13: 0000000000000000 > R14: > > > 00000001000a3e0c > > > > R15: > > > > > > ffff8800389ffc28 > > > > > > > > FS: > 00007f1af70a8700(0000) > > > > GS:ffff880050180000(0000) > > > > > > > > knlGS:0000000000000000 > > > > > > > > CS: e033 DS: 0000 ES: > 0000 > > CR0: > > > > 000000008005003b > > > > > > > > CR2: 0000000000000030 > CR3: > > > 000000000156d000 > > > > CR4: > > > > > > 0000000000002660 > > > > > > > > DR0: 0000000000000000 > DR1: > > > 0000000000000000 > > > > DR2: > > > > > > 0000000000000000 > > > > > > > > DR3: 0000000000000000 > DR6: > > > 00000000ffff0ff0 > > > > DR7: > > > > > > 0000000000000400 > > > > > > > > Process qemu-dm (pid: > 3571, > > > threadinfo > > > > > ffff8800389fe000, > > > > > > task > > > > > > > > ffff88003a721260) > > > > > > > > Stack: > > > > > > > > ffff88003a6d6400 > > ffff8800377b0000 > > > > 00000001000a3e0c > > > > > > > ffffffff8133ce8f > > > > > > > > ffff8800377b0400 > > ffffffff8134b6cd > > > > ffff8800389ffc28 > > > > > > > ffff8800389ffc28 > > > > > > > > ffff8800377b00f8 > > ffff8800377b0680 > > > > ffff880038cdcd60 > > > > > > > ffff8800377b0000 > > > > > > > > Call Trace: > > > > > > > > [<ffffffff8133ce8f>] ? > > > > sk_release_kernel+0x23/0x39 > > > > > > > > [<ffffffff8134b6cd>] ? > > > > netdev_run_todo+0x1e9/0x206 > > > > > > > > [<ffffffff8129798f>] ? > > > > tun_chr_close+0x4c/0x7b > > > > > > > > [<ffffffff810b39d3>] ? > > > fput+0xe4/0x1c5 > > > > > > > > [<ffffffff810b202c>] ? > > > filp_close+0x61/0x68 > > > > > > > > [<ffffffff81035e62>] ? > > > > put_files_struct+0x62/0xb9 > > > > > > > > [<ffffffff81036374>] ? > > > do_exit+0x24a/0x74c > > > > > > > > [<ffffffff81036906>] ? > > > > do_group_exit+0x6b/0x9d > > > > > > > > [<ffffffff8103ea0b>] ? > > > > > get_signal_to_deliver+0x449/0x46e > > > > > > > > [<ffffffff81009fa5>] ? > > > do_signal+0x28/0x4c4 > > > > > > > > [<ffffffff81027079>] ? > > > > > pvclock_clocksource_read+0x48/0xbf > > > > > > > > [<ffffffff8105b745>] ? > > > ktime_get_ts+0x66/0xa8 > > > > > > > > [<ffffffff810bfb18>] ? > > > > > poll_select_copy_remaining+0xe0/0xf5 > > > > > > > > [<ffffffff8100a48d>] ? > > > > do_notify_resume+0x3b/0x74 > > > > > > > > [<ffffffff81411a70>] ? > > > int_signal+0x12/0x17 > > > > > > > > Code: 00 00 00 40 74 02 > 0f 0b > > 48 8d > > > 77 70 48 > > > > 8d bf 08 > > > > > 01 00 > > > > > > 00 e8 > > > > > > > 8b 71 10 > > > > > > > > 00 85 c0 0f 84 5d 01 00 > 00 48 > > 8b 6b > > > 18 f6 83 > > > > 80 00 00 > > > > > 00 08 > > > > > > <4c> 8b > > > > > > > 65 30 > > > > > > > > 74 11 be 68 05 00 00 48 > c7 c7 > > 8e df > > > 4f 81 e8 > > > > bb d0 > > > > > > > > RIP > [<ffffffff810c50c4>] > > > iput+0x3e/0x195 > > > > > > > > RSP <ffff8800389ffbf8> > > > > > > > > CR2: 0000000000000030 > > > > > > > > ---[ end trace > > 67cc1654658fedcc ]--- > > > > > > > > Fixing recursive fault > but > > reboot is > > > needed! > > > > > > > > > > > > > > > > I also tested Xen 4.2.0 > and > > problem > > > is the > > > > same. So > > > > > is this > > > > > > a Xen > > > > > > > bug or a > > > > > > > > kernel bug? I am > running > > vanilla > > > > > [1][2][3][4][5][11][17][18]kernel.org > kernel > > > > > > 3.5.0 and > > > > > > > my > > > > > > > > hardware is Intel Core > i7-3770 > > CPU > > > and Intel > > > > DQ77MK > > > > > > motherboard > > > > > > > with > > > > > > > > latest bios. > > > > > > > > > > > > > > > > Best regards, > > > > > > > > Valtteri Kiviniemi > > > > > > > > > > > > > > > > References > > > > > > > > > > > > > > > > Visible links > > > > > > > > 1. > > [3][4][5][6][12][18][19]http://kernel.org/ > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > Xen-devel mailing list > > > > > > > > > > [4][5][6][7][13][19][20]Xen-devel@lists.xen.org > > > > > > > > > > > [5][6][7][8][14][20][21]http://lists.xen.org/xen-devel > > > > > > > > > > > > > > References > > > > > > > > > > > > > > Visible links > > > > > > > 1. > > mailto:[7][8][9][15][21][22]pasik@iki.fi > > > > > > > 2. > > [8][9][10][16][22][23]http://kernel.org/ > > > > > > > 3. > > [9][10][11][17][23][24]http://kernel.org/ > > > > > > > 4. > > > mailto:[10][11][12][18][24][25]Xen-devel@lists.xen.org > > > > > > > 5. > > > [11][12][13][19][25][26]http://lists.xen.org/xen-devel > > > > > > > > > > > > References > > > > > > > > > > > > Visible links > > > > > > 1. > mailto:[13][14][20][26][27]pasik@iki.fi > > > > > > 2. > mailto:[14][15][21][27][28]pasik@iki.fi > > > > > > 3. > [15][16][22][28][29]http://kernel.org/ > > > > > > 4. > [16][17][23][29][30]http://kernel.org/ > > > > > > 5. > > mailto:[17][18][24][30][31]Xen-devel@lists.xen.org > > > > > > 6. > > [18][19][25][31][32]http://lists.xen.org/xen-devel > > > > > > 7. > mailto:[19][20][26][32][33]pasik@iki.fi > > > > > > 8. > [20][21][27][33][34]http://kernel.org/ > > > > > > 9. > [21][22][28][34][35]http://kernel.org/ > > > > > > 10. > > mailto:[22][23][29][35][36]Xen-devel@lists.xen.org > > > > > > 11. > > [23][24][30][36][37]http://lists.xen.org/xen-devel > > > > > > > > > > References > > > > > > > > > > Visible links > > > > > 1. mailto:[25][31][37][38]pasik@iki.fi > > > > > 2. mailto:[26][32][38][39]pasik@iki.fi > > > > > 3. mailto:[27][33][39][40]pasik@iki.fi > > > > > 4. [28][34][40][41]http://kernel.org/ > > > > > 5. [29][35][41][42]http://kernel.org/ > > > > > 6. > mailto:[30][36][42][43]Xen-devel@lists.xen.org > > > > > 7. > [31][37][43][44]http://lists.xen.org/xen-devel > > > > > 8. mailto:[32][38][44][45]pasik@iki.fi > > > > > 9. [33][39][45][46]http://kernel.org/ > > > > > 10. [34][40][46][47]http://kernel.org/ > > > > > 11. > mailto:[35][41][47][48]Xen-devel@lists.xen.org > > > > > 12. > [36][42][48][49]http://lists.xen.org/xen-devel > > > > > 13. mailto:[37][43][49][50]pasik@iki.fi > > > > > 14. mailto:[38][44][50][51]pasik@iki.fi > > > > > 15. [39][45][51][52]http://kernel.org/ > > > > > 16. [40][46][52][53]http://kernel.org/ > > > > > 17. > mailto:[41][47][53][54]Xen-devel@lists.xen.org > > > > > 18. > [42][48][54][55]http://lists.xen.org/xen-devel > > > > > 19. mailto:[43][49][55][56]pasik@iki.fi > > > > > 20. [44][50][56][57]http://kernel.org/ > > > > > 21. [45][51][57][58]http://kernel.org/ > > > > > 22. > mailto:[46][52][58][59]Xen-devel@lists.xen.org > > > > > 23. > [47][53][59][60]http://lists.xen.org/xen-devel > > > > > > > > References > > > > > > > > Visible links > > > > 1. mailto:[54][60][61]pasik@iki.fi > > > > 2. mailto:[55][61][62]pasik@iki.fi > > > > 3. mailto:[56][62][63]pasik@iki.fi > > > > 4. mailto:[57][63][64]pasik@iki.fi > > > > 5. [58][64][65]http://kernel.org/ > > > > 6. [59][65][66]http://kernel.org/ > > > > 7. mailto:[60][66][67]Xen-devel@lists.xen.org > > > > 8. [61][67][68]http://lists.xen.org/xen-devel > > > > 9. mailto:[62][68][69]pasik@iki.fi > > > > 10. [63][69][70]http://kernel.org/ > > > > 11. [64][70][71]http://kernel.org/ > > > > 12. mailto:[65][71][72]Xen-devel@lists.xen.org > > > > 13. [66][72][73]http://lists.xen.org/xen-devel > > > > 14. mailto:[67][73][74]pasik@iki.fi > > > > 15. mailto:[68][74][75]pasik@iki.fi > > > > 16. [69][75][76]http://kernel.org/ > > > > 17. [70][76][77]http://kernel.org/ > > > > 18. mailto:[71][77][78]Xen-devel@lists.xen.org > > > > 19. [72][78][79]http://lists.xen.org/xen-devel > > > > 20. mailto:[73][79][80]pasik@iki.fi > > > > 21. [74][80][81]http://kernel.org/ > > > > 22. [75][81][82]http://kernel.org/ > > > > 23. mailto:[76][82][83]Xen-devel@lists.xen.org > > > > 24. [77][83][84]http://lists.xen.org/xen-devel > > > > 25. mailto:[78][84][85]pasik@iki.fi > > > > 26. mailto:[79][85][86]pasik@iki.fi > > > > 27. mailto:[80][86][87]pasik@iki.fi > > > > 28. [81][87][88]http://kernel.org/ > > > > 29. [82][88][89]http://kernel.org/ > > > > 30. mailto:[83][89][90]Xen-devel@lists.xen.org > > > > 31. [84][90][91]http://lists.xen.org/xen-devel > > > > 32. mailto:[85][91][92]pasik@iki.fi > > > > 33. [86][92][93]http://kernel.org/ > > > > 34. [87][93][94]http://kernel.org/ > > > > 35. mailto:[88][94][95]Xen-devel@lists.xen.org > > > > 36. [89][95][96]http://lists.xen.org/xen-devel > > > > 37. mailto:[90][96][97]pasik@iki.fi > > > > 38. mailto:[91][97][98]pasik@iki.fi > > > > 39. [92][98][99]http://kernel.org/ > > > > 40. [93][99][100]http://kernel.org/ > > > > 41. mailto:[94][100][101]Xen-devel@lists.xen.org > > > > 42. [95][101][102]http://lists.xen.org/xen-devel > > > > 43. mailto:[96][102][103]pasik@iki.fi > > > > 44. [97][103][104]http://kernel.org/ > > > > 45. [98][104][105]http://kernel.org/ > > > > 46. mailto:[99][105][106]Xen-devel@lists.xen.org > > > > 47. [100][106][107]http://lists.xen.org/xen-devel > > > > > > References > > > > > > Visible links > > > 1. mailto:[107][108]kiviniemi.valtteri@gmail.com > > > 2. [108][109]http://ark.intel.com/products/65719/ > > > 3. > > > [109][110]http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > > > 4. mailto:[110][111]root@dataproof.fi > > > 5. mailto:[111][112]pasik@iki.fi > > > 6. [112][113]http://xen.org/ > > > 7. mailto:[113][114]pasik@iki.fi > > > 8. mailto:[114][115]pasik@iki.fi > > > 9. mailto:[115][116]pasik@iki.fi > > > 10. mailto:[116][117]pasik@iki.fi > > > 11. [117][118]http://kernel.org/ > > > 12. [118][119]http://kernel.org/ > > > 13. mailto:[119][120]Xen-devel@lists.xen.org > > > 14. [120][121]http://lists.xen.org/xen-devel > > > 15. mailto:[121][122]pasik@iki.fi > > > 16. [122][123]http://kernel.org/ > > > 17. [123][124]http://kernel.org/ > > > 18. mailto:[124][125]Xen-devel@lists.xen.org > > > 19. [125][126]http://lists.xen.org/xen-devel > > > 20. mailto:[126][127]pasik@iki.fi > > > 21. mailto:[127][128]pasik@iki.fi > > > 22. [128][129]http://kernel.org/ > > > 23. [129][130]http://kernel.org/ > > > 24. mailto:[130][131]Xen-devel@lists.xen.org > > > 25. [131][132]http://lists.xen.org/xen-devel > > > 26. mailto:[132][133]pasik@iki.fi > > > 27. [133][134]http://kernel.org/ > > > 28. [134][135]http://kernel.org/ > > > 29. mailto:[135][136]Xen-devel@lists.xen.org > > > 30. [136][137]http://lists.xen.org/xen-devel > > > 31. mailto:[137][138]pasik@iki.fi > > > 32. mailto:[138][139]pasik@iki.fi > > > 33. mailto:[139][140]pasik@iki.fi > > > 34. [140][141]http://kernel.org/ > > > 35. [141][142]http://kernel.org/ > > > 36. mailto:[142][143]Xen-devel@lists.xen.org > > > 37. [143][144]http://lists.xen.org/xen-devel > > > 38. mailto:[144][145]pasik@iki.fi > > > 39. [145][146]http://kernel.org/ > > > 40. [146][147]http://kernel.org/ > > > 41. mailto:[147][148]Xen-devel@lists.xen.org > > > 42. [148][149]http://lists.xen.org/xen-devel > > > 43. mailto:[149][150]pasik@iki.fi > > > 44. mailto:[150][151]pasik@iki.fi > > > 45. [151][152]http://kernel.org/ > > > 46. [152][153]http://kernel.org/ > > > 47. mailto:[153][154]Xen-devel@lists.xen.org > > > 48. [154][155]http://lists.xen.org/xen-devel > > > 49. mailto:[155][156]pasik@iki.fi > > > 50. [156][157]http://kernel.org/ > > > 51. [157][158]http://kernel.org/ > > > 52. mailto:[158][159]Xen-devel@lists.xen.org > > > 53. [159][160]http://lists.xen.org/xen-devel > > > 54. mailto:[160][161]pasik@iki.fi > > > 55. mailto:[161][162]pasik@iki.fi > > > 56. mailto:[162][163]pasik@iki.fi > > > 57. mailto:[163][164]pasik@iki.fi > > > 58. [164][165]http://kernel.org/ > > > 59. [165][166]http://kernel.org/ > > > 60. mailto:[166][167]Xen-devel@lists.xen.org > > > 61. [167][168]http://lists.xen.org/xen-devel > > > 62. mailto:[168][169]pasik@iki.fi > > > 63. [169][170]http://kernel.org/ > > > 64. [170][171]http://kernel.org/ > > > 65. mailto:[171][172]Xen-devel@lists.xen.org > > > 66. [172][173]http://lists.xen.org/xen-devel > > > 67. mailto:[173][174]pasik@iki.fi > > > 68. mailto:[174][175]pasik@iki.fi > > > 69. [175][176]http://kernel.org/ > > > 70. [176][177]http://kernel.org/ > > > 71. mailto:[177][178]Xen-devel@lists.xen.org > > > 72. [178][179]http://lists.xen.org/xen-devel > > > 73. mailto:[179][180]pasik@iki.fi > > > 74. [180][181]http://kernel.org/ > > > 75. [181][182]http://kernel.org/ > > > 76. mailto:[182][183]Xen-devel@lists.xen.org > > > 77. [183][184]http://lists.xen.org/xen-devel > > > 78. mailto:[184][185]pasik@iki.fi > > > 79. mailto:[185][186]pasik@iki.fi > > > 80. mailto:[186][187]pasik@iki.fi > > > 81. [187][188]http://kernel.org/ > > > 82. [188][189]http://kernel.org/ > > > 83. mailto:[189][190]Xen-devel@lists.xen.org > > > 84. [190][191]http://lists.xen.org/xen-devel > > > 85. mailto:[191][192]pasik@iki.fi > > > 86. [192][193]http://kernel.org/ > > > 87. [193][194]http://kernel.org/ > > > 88. mailto:[194][195]Xen-devel@lists.xen.org > > > 89. [195][196]http://lists.xen.org/xen-devel > > > 90. mailto:[196][197]pasik@iki.fi > > > 91. mailto:[197][198]pasik@iki.fi > > > 92. [198][199]http://kernel.org/ > > > 93. [199][200]http://kernel.org/ > > > 94. mailto:[200][201]Xen-devel@lists.xen.org > > > 95. [201][202]http://lists.xen.org/xen-devel > > > 96. mailto:[202][203]pasik@iki.fi > > > 97. [203][204]http://kernel.org/ > > > 98. [204][205]http://kernel.org/ > > > 99. mailto:[205][206]Xen-devel@lists.xen.org > > > 100. [206][207]http://lists.xen.org/xen-devel > > > > References > > > > Visible links > > 1. [208]http://nago.fi/dmesg.txt > > 2. [209]http://nago.fi/qemu-dm.txt > > 3. [210]http://nago.fi/xm-dmesg.txt > > 4. [211]http://nago.fi/domu-config.txt > > 5. [212]http://nago.fi/dom0-config.txt > > 6. mailto:[213]pasik@iki.fi > > 7. mailto:[214]kiviniemi.valtteri@gmail.com > > 8. [215]http://ark.intel.com/products/65719/ > > 9. > [216]http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > > 10. mailto:[217]root@dataproof.fi > > 11. mailto:[218]pasik@iki.fi > > 12. [219]http://xen.org/ > > 13. mailto:[220]pasik@iki.fi > > 14. mailto:[221]pasik@iki.fi > > 15. mailto:[222]pasik@iki.fi > > 16. mailto:[223]pasik@iki.fi > > 17. [224]http://kernel.org/ > > 18. [225]http://kernel.org/ > > 19. mailto:[226]Xen-devel@lists.xen.org > > 20. [227]http://lists.xen.org/xen-devel > > 21. mailto:[228]pasik@iki.fi > > 22. [229]http://kernel.org/ > > 23. [230]http://kernel.org/ > > 24. mailto:[231]Xen-devel@lists.xen.org > > 25. [232]http://lists.xen.org/xen-devel > > 26. mailto:[233]pasik@iki.fi > > 27. mailto:[234]pasik@iki.fi > > 28. [235]http://kernel.org/ > > 29. [236]http://kernel.org/ > > 30. mailto:[237]Xen-devel@lists.xen.org > > 31. [238]http://lists.xen.org/xen-devel > > 32. mailto:[239]pasik@iki.fi > > 33. [240]http://kernel.org/ > > 34. [241]http://kernel.org/ > > 35. mailto:[242]Xen-devel@lists.xen.org > > 36. [243]http://lists.xen.org/xen-devel > > 37. mailto:[244]pasik@iki.fi > > 38. mailto:[245]pasik@iki.fi > > 39. mailto:[246]pasik@iki.fi > > 40. [247]http://kernel.org/ > > 41. [248]http://kernel.org/ > > 42. mailto:[249]Xen-devel@lists.xen.org > > 43. [250]http://lists.xen.org/xen-devel > > 44. mailto:[251]pasik@iki.fi > > 45. [252]http://kernel.org/ > > 46. [253]http://kernel.org/ > > 47. mailto:[254]Xen-devel@lists.xen.org > > 48. [255]http://lists.xen.org/xen-devel > > 49. mailto:[256]pasik@iki.fi > > 50. mailto:[257]pasik@iki.fi > > 51. [258]http://kernel.org/ > > 52. [259]http://kernel.org/ > > 53. mailto:[260]Xen-devel@lists.xen.org > > 54. [261]http://lists.xen.org/xen-devel > > 55. mailto:[262]pasik@iki.fi > > 56. [263]http://kernel.org/ > > 57. [264]http://kernel.org/ > > 58. mailto:[265]Xen-devel@lists.xen.org > > 59. [266]http://lists.xen.org/xen-devel > > 60. mailto:[267]pasik@iki.fi > > 61. mailto:[268]pasik@iki.fi > > 62. mailto:[269]pasik@iki.fi > > 63. mailto:[270]pasik@iki.fi > > 64. [271]http://kernel.org/ > > 65. [272]http://kernel.org/ > > 66. mailto:[273]Xen-devel@lists.xen.org > > 67. [274]http://lists.xen.org/xen-devel > > 68. mailto:[275]pasik@iki.fi > > 69. [276]http://kernel.org/ > > 70. [277]http://kernel.org/ > > 71. mailto:[278]Xen-devel@lists.xen.org > > 72. [279]http://lists.xen.org/xen-devel > > 73. mailto:[280]pasik@iki.fi > > 74. mailto:[281]pasik@iki.fi > > 75. [282]http://kernel.org/ > > 76. [283]http://kernel.org/ > > 77. mailto:[284]Xen-devel@lists.xen.org > > 78. [285]http://lists.xen.org/xen-devel > > 79. mailto:[286]pasik@iki.fi > > 80. [287]http://kernel.org/ > > 81. [288]http://kernel.org/ > > 82. mailto:[289]Xen-devel@lists.xen.org > > 83. [290]http://lists.xen.org/xen-devel > > 84. mailto:[291]pasik@iki.fi > > 85. mailto:[292]pasik@iki.fi > > 86. mailto:[293]pasik@iki.fi > > 87. [294]http://kernel.org/ > > 88. [295]http://kernel.org/ > > 89. mailto:[296]Xen-devel@lists.xen.org > > 90. [297]http://lists.xen.org/xen-devel > > 91. mailto:[298]pasik@iki.fi > > 92. [299]http://kernel.org/ > > 93. [300]http://kernel.org/ > > 94. mailto:[301]Xen-devel@lists.xen.org > > 95. [302]http://lists.xen.org/xen-devel > > 96. mailto:[303]pasik@iki.fi > > 97. mailto:[304]pasik@iki.fi > > 98. [305]http://kernel.org/ > > 99. [306]http://kernel.org/ > > 100. mailto:[307]Xen-devel@lists.xen.org > > 101. [308]http://lists.xen.org/xen-devel > > 102. mailto:[309]pasik@iki.fi > > 103. [310]http://kernel.org/ > > 104. [311]http://kernel.org/ > > 105. mailto:[312]Xen-devel@lists.xen.org > > 106. [313]http://lists.xen.org/xen-devel > > 107. mailto:[314]kiviniemi.valtteri@gmail.com > > 108. [315]http://ark.intel.com/products/65719/ > > 109. > [316]http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > > 110. mailto:[317]root@dataproof.fi > > 111. mailto:[318]pasik@iki.fi > > 112. [319]http://xen.org/ > > 113. mailto:[320]pasik@iki.fi > > 114. mailto:[321]pasik@iki.fi > > 115. mailto:[322]pasik@iki.fi > > 116. mailto:[323]pasik@iki.fi > > 117. [324]http://kernel.org/ > > 118. [325]http://kernel.org/ > > 119. mailto:[326]Xen-devel@lists.xen.org > > 120. [327]http://lists.xen.org/xen-devel > > 121. mailto:[328]pasik@iki.fi > > 122. [329]http://kernel.org/ > > 123. [330]http://kernel.org/ > > 124. mailto:[331]Xen-devel@lists.xen.org > > 125. [332]http://lists.xen.org/xen-devel > > 126. mailto:[333]pasik@iki.fi > > 127. mailto:[334]pasik@iki.fi > > 128. [335]http://kernel.org/ > > 129. [336]http://kernel.org/ > > 130. mailto:[337]Xen-devel@lists.xen.org > > 131. [338]http://lists.xen.org/xen-devel > > 132. mailto:[339]pasik@iki.fi > > 133. [340]http://kernel.org/ > > 134. [341]http://kernel.org/ > > 135. mailto:[342]Xen-devel@lists.xen.org > > 136. [343]http://lists.xen.org/xen-devel > > 137. mailto:[344]pasik@iki.fi > > 138. mailto:[345]pasik@iki.fi > > 139. mailto:[346]pasik@iki.fi > > 140. [347]http://kernel.org/ > > 141. [348]http://kernel.org/ > > 142. mailto:[349]Xen-devel@lists.xen.org > > 143. [350]http://lists.xen.org/xen-devel > > 144. mailto:[351]pasik@iki.fi > > 145. [352]http://kernel.org/ > > 146. [353]http://kernel.org/ > > 147. mailto:[354]Xen-devel@lists.xen.org > > 148. [355]http://lists.xen.org/xen-devel > > 149. mailto:[356]pasik@iki.fi > > 150. mailto:[357]pasik@iki.fi > > 151. [358]http://kernel.org/ > > 152. [359]http://kernel.org/ > > 153. mailto:[360]Xen-devel@lists.xen.org > > 154. [361]http://lists.xen.org/xen-devel > > 155. mailto:[362]pasik@iki.fi > > 156. [363]http://kernel.org/ > > 157. [364]http://kernel.org/ > > 158. mailto:[365]Xen-devel@lists.xen.org > > 159. [366]http://lists.xen.org/xen-devel > > 160. mailto:[367]pasik@iki.fi > > 161. mailto:[368]pasik@iki.fi > > 162. mailto:[369]pasik@iki.fi > > 163. mailto:[370]pasik@iki.fi > > 164. [371]http://kernel.org/ > > 165. [372]http://kernel.org/ > > 166. mailto:[373]Xen-devel@lists.xen.org > > 167. [374]http://lists.xen.org/xen-devel > > 168. mailto:[375]pasik@iki.fi > > 169. [376]http://kernel.org/ > > 170. [377]http://kernel.org/ > > 171. mailto:[378]Xen-devel@lists.xen.org > > 172. [379]http://lists.xen.org/xen-devel > > 173. mailto:[380]pasik@iki.fi > > 174. mailto:[381]pasik@iki.fi > > 175. [382]http://kernel.org/ > > 176. [383]http://kernel.org/ > > 177. mailto:[384]Xen-devel@lists.xen.org > > 178. [385]http://lists.xen.org/xen-devel > > 179. mailto:[386]pasik@iki.fi > > 180. [387]http://kernel.org/ > > 181. [388]http://kernel.org/ > > 182. mailto:[389]Xen-devel@lists.xen.org > > 183. [390]http://lists.xen.org/xen-devel > > 184. mailto:[391]pasik@iki.fi > > 185. mailto:[392]pasik@iki.fi > > 186. mailto:[393]pasik@iki.fi > > 187. [394]http://kernel.org/ > > 188. [395]http://kernel.org/ > > 189. mailto:[396]Xen-devel@lists.xen.org > > 190. [397]http://lists.xen.org/xen-devel > > 191. mailto:[398]pasik@iki.fi > > 192. [399]http://kernel.org/ > > 193. [400]http://kernel.org/ > > 194. mailto:[401]Xen-devel@lists.xen.org > > 195. [402]http://lists.xen.org/xen-devel > > 196. mailto:[403]pasik@iki.fi > > 197. mailto:[404]pasik@iki.fi > > 198. [405]http://kernel.org/ > > 199. [406]http://kernel.org/ > > 200. mailto:[407]Xen-devel@lists.xen.org > > 201. [408]http://lists.xen.org/xen-devel > > 202. mailto:[409]pasik@iki.fi > > 203. [410]http://kernel.org/ > > 204. [411]http://kernel.org/ > > 205. mailto:[412]Xen-devel@lists.xen.org > > 206. [413]http://lists.xen.org/xen-devel > > References > > Visible links > 1. mailto:pasik@iki.fi > 2. http://nago.fi/dmesg.txt > 3. http://nago.fi/qemu-dm.txt > 4. http://nago.fi/xm-dmesg.txt > 5. http://nago.fi/domu-config.txt > 6. http://nago.fi/dom0-config.txt > 7. mailto:pasik@iki.fi > 8. mailto:kiviniemi.valtteri@gmail.com > 9. http://ark.intel.com/products/65719/ > 10. http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > 11. mailto:root@dataproof.fi > 12. mailto:pasik@iki.fi > 13. http://xen.org/ > 14. mailto:pasik@iki.fi > 15. mailto:pasik@iki.fi > 16. mailto:pasik@iki.fi > 17. mailto:pasik@iki.fi > 18. http://kernel.org/ > 19. http://kernel.org/ > 20. mailto:Xen-devel@lists.xen.org > 21. http://lists.xen.org/xen-devel > 22. mailto:pasik@iki.fi > 23. http://kernel.org/ > 24. http://kernel.org/ > 25. mailto:Xen-devel@lists.xen.org > 26. http://lists.xen.org/xen-devel > 27. mailto:pasik@iki.fi > 28. mailto:pasik@iki.fi > 29. http://kernel.org/ > 30. http://kernel.org/ > 31. mailto:Xen-devel@lists.xen.org > 32. http://lists.xen.org/xen-devel > 33. mailto:pasik@iki.fi > 34. http://kernel.org/ > 35. http://kernel.org/ > 36. mailto:Xen-devel@lists.xen.org > 37. http://lists.xen.org/xen-devel > 38. mailto:pasik@iki.fi > 39. mailto:pasik@iki.fi > 40. mailto:pasik@iki.fi > 41. http://kernel.org/ > 42. http://kernel.org/ > 43. mailto:Xen-devel@lists.xen.org > 44. http://lists.xen.org/xen-devel > 45. mailto:pasik@iki.fi > 46. http://kernel.org/ > 47. http://kernel.org/ > 48. mailto:Xen-devel@lists.xen.org > 49. http://lists.xen.org/xen-devel > 50. mailto:pasik@iki.fi > 51. mailto:pasik@iki.fi > 52. http://kernel.org/ > 53. http://kernel.org/ > 54. mailto:Xen-devel@lists.xen.org > 55. http://lists.xen.org/xen-devel > 56. mailto:pasik@iki.fi > 57. http://kernel.org/ > 58. http://kernel.org/ > 59. mailto:Xen-devel@lists.xen.org > 60. http://lists.xen.org/xen-devel > 61. mailto:pasik@iki.fi > 62. mailto:pasik@iki.fi > 63. mailto:pasik@iki.fi > 64. mailto:pasik@iki.fi > 65. http://kernel.org/ > 66. http://kernel.org/ > 67. mailto:Xen-devel@lists.xen.org > 68. http://lists.xen.org/xen-devel > 69. mailto:pasik@iki.fi > 70. http://kernel.org/ > 71. http://kernel.org/ > 72. mailto:Xen-devel@lists.xen.org > 73. http://lists.xen.org/xen-devel > 74. mailto:pasik@iki.fi > 75. mailto:pasik@iki.fi > 76. http://kernel.org/ > 77. http://kernel.org/ > 78. mailto:Xen-devel@lists.xen.org > 79. http://lists.xen.org/xen-devel > 80. mailto:pasik@iki.fi > 81. http://kernel.org/ > 82. http://kernel.org/ > 83. mailto:Xen-devel@lists.xen.org > 84. http://lists.xen.org/xen-devel > 85. mailto:pasik@iki.fi > 86. mailto:pasik@iki.fi > 87. mailto:pasik@iki.fi > 88. http://kernel.org/ > 89. http://kernel.org/ > 90. mailto:Xen-devel@lists.xen.org > 91. http://lists.xen.org/xen-devel > 92. mailto:pasik@iki.fi > 93. http://kernel.org/ > 94. http://kernel.org/ > 95. mailto:Xen-devel@lists.xen.org > 96. http://lists.xen.org/xen-devel > 97. mailto:pasik@iki.fi > 98. mailto:pasik@iki.fi > 99. http://kernel.org/ > 100. http://kernel.org/ > 101. mailto:Xen-devel@lists.xen.org > 102. http://lists.xen.org/xen-devel > 103. mailto:pasik@iki.fi > 104. http://kernel.org/ > 105. http://kernel.org/ > 106. mailto:Xen-devel@lists.xen.org > 107. http://lists.xen.org/xen-devel > 108. mailto:kiviniemi.valtteri@gmail.com > 109. http://ark.intel.com/products/65719/ > 110. http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > 111. mailto:root@dataproof.fi > 112. mailto:pasik@iki.fi > 113. http://xen.org/ > 114. mailto:pasik@iki.fi > 115. mailto:pasik@iki.fi > 116. mailto:pasik@iki.fi > 117. mailto:pasik@iki.fi > 118. http://kernel.org/ > 119. http://kernel.org/ > 120. mailto:Xen-devel@lists.xen.org > 121. http://lists.xen.org/xen-devel > 122. mailto:pasik@iki.fi > 123. http://kernel.org/ > 124. http://kernel.org/ > 125. mailto:Xen-devel@lists.xen.org > 126. http://lists.xen.org/xen-devel > 127. mailto:pasik@iki.fi > 128. mailto:pasik@iki.fi > 129. http://kernel.org/ > 130. http://kernel.org/ > 131. mailto:Xen-devel@lists.xen.org > 132. http://lists.xen.org/xen-devel > 133. mailto:pasik@iki.fi > 134. http://kernel.org/ > 135. http://kernel.org/ > 136. mailto:Xen-devel@lists.xen.org > 137. http://lists.xen.org/xen-devel > 138. mailto:pasik@iki.fi > 139. mailto:pasik@iki.fi > 140. mailto:pasik@iki.fi > 141. http://kernel.org/ > 142. http://kernel.org/ > 143. mailto:Xen-devel@lists.xen.org > 144. http://lists.xen.org/xen-devel > 145. mailto:pasik@iki.fi > 146. http://kernel.org/ > 147. http://kernel.org/ > 148. mailto:Xen-devel@lists.xen.org > 149. http://lists.xen.org/xen-devel > 150. mailto:pasik@iki.fi > 151. mailto:pasik@iki.fi > 152. http://kernel.org/ > 153. http://kernel.org/ > 154. mailto:Xen-devel@lists.xen.org > 155. http://lists.xen.org/xen-devel > 156. mailto:pasik@iki.fi > 157. http://kernel.org/ > 158. http://kernel.org/ > 159. mailto:Xen-devel@lists.xen.org > 160. http://lists.xen.org/xen-devel > 161. mailto:pasik@iki.fi > 162. mailto:pasik@iki.fi > 163. mailto:pasik@iki.fi > 164. mailto:pasik@iki.fi > 165. http://kernel.org/ > 166. http://kernel.org/ > 167. mailto:Xen-devel@lists.xen.org > 168. http://lists.xen.org/xen-devel > 169. mailto:pasik@iki.fi > 170. http://kernel.org/ > 171. http://kernel.org/ > 172. mailto:Xen-devel@lists.xen.org > 173. http://lists.xen.org/xen-devel > 174. mailto:pasik@iki.fi > 175. mailto:pasik@iki.fi > 176. http://kernel.org/ > 177. http://kernel.org/ > 178. mailto:Xen-devel@lists.xen.org > 179. http://lists.xen.org/xen-devel > 180. mailto:pasik@iki.fi > 181. http://kernel.org/ > 182. http://kernel.org/ > 183. mailto:Xen-devel@lists.xen.org > 184. http://lists.xen.org/xen-devel > 185. mailto:pasik@iki.fi > 186. mailto:pasik@iki.fi > 187. mailto:pasik@iki.fi > 188. http://kernel.org/ > 189. http://kernel.org/ > 190. mailto:Xen-devel@lists.xen.org > 191. http://lists.xen.org/xen-devel > 192. mailto:pasik@iki.fi > 193. http://kernel.org/ > 194. http://kernel.org/ > 195. mailto:Xen-devel@lists.xen.org > 196. http://lists.xen.org/xen-devel > 197. mailto:pasik@iki.fi > 198. mailto:pasik@iki.fi > 199. http://kernel.org/ > 200. http://kernel.org/ > 201. mailto:Xen-devel@lists.xen.org > 202. http://lists.xen.org/xen-devel > 203. mailto:pasik@iki.fi > 204. http://kernel.org/ > 205. http://kernel.org/ > 206. mailto:Xen-devel@lists.xen.org > 207. http://lists.xen.org/xen-devel > 208. http://nago.fi/dmesg.txt > 209. http://nago.fi/qemu-dm.txt > 210. http://nago.fi/xm-dmesg.txt > 211. http://nago.fi/domu-config.txt > 212. http://nago.fi/dom0-config.txt > 213. mailto:pasik@iki.fi > 214. mailto:kiviniemi.valtteri@gmail.com > 215. http://ark.intel.com/products/65719/ > 216. http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > 217. mailto:root@dataproof.fi > 218. mailto:pasik@iki.fi > 219. http://xen.org/ > 220. mailto:pasik@iki.fi > 221. mailto:pasik@iki.fi > 222. mailto:pasik@iki.fi > 223. mailto:pasik@iki.fi > 224. http://kernel.org/ > 225. http://kernel.org/ > 226. mailto:Xen-devel@lists.xen.org > 227. http://lists.xen.org/xen-devel > 228. mailto:pasik@iki.fi > 229. http://kernel.org/ > 230. http://kernel.org/ > 231. mailto:Xen-devel@lists.xen.org > 232. http://lists.xen.org/xen-devel > 233. mailto:pasik@iki.fi > 234. mailto:pasik@iki.fi > 235. http://kernel.org/ > 236. http://kernel.org/ > 237. mailto:Xen-devel@lists.xen.org > 238. http://lists.xen.org/xen-devel > 239. mailto:pasik@iki.fi > 240. http://kernel.org/ > 241. http://kernel.org/ > 242. mailto:Xen-devel@lists.xen.org > 243. http://lists.xen.org/xen-devel > 244. mailto:pasik@iki.fi > 245. mailto:pasik@iki.fi > 246. mailto:pasik@iki.fi > 247. http://kernel.org/ > 248. http://kernel.org/ > 249. mailto:Xen-devel@lists.xen.org > 250. http://lists.xen.org/xen-devel > 251. mailto:pasik@iki.fi > 252. http://kernel.org/ > 253. http://kernel.org/ > 254. mailto:Xen-devel@lists.xen.org > 255. http://lists.xen.org/xen-devel > 256. mailto:pasik@iki.fi > 257. mailto:pasik@iki.fi > 258. http://kernel.org/ > 259. http://kernel.org/ > 260. mailto:Xen-devel@lists.xen.org > 261. http://lists.xen.org/xen-devel > 262. mailto:pasik@iki.fi > 263. http://kernel.org/ > 264. http://kernel.org/ > 265. mailto:Xen-devel@lists.xen.org > 266. http://lists.xen.org/xen-devel > 267. mailto:pasik@iki.fi > 268. mailto:pasik@iki.fi > 269. mailto:pasik@iki.fi > 270. mailto:pasik@iki.fi > 271. http://kernel.org/ > 272. http://kernel.org/ > 273. mailto:Xen-devel@lists.xen.org > 274. http://lists.xen.org/xen-devel > 275. mailto:pasik@iki.fi > 276. http://kernel.org/ > 277. http://kernel.org/ > 278. mailto:Xen-devel@lists.xen.org > 279. http://lists.xen.org/xen-devel > 280. mailto:pasik@iki.fi > 281. mailto:pasik@iki.fi > 282. http://kernel.org/ > 283. http://kernel.org/ > 284. mailto:Xen-devel@lists.xen.org > 285. http://lists.xen.org/xen-devel > 286. mailto:pasik@iki.fi > 287. http://kernel.org/ > 288. http://kernel.org/ > 289. mailto:Xen-devel@lists.xen.org > 290. http://lists.xen.org/xen-devel > 291. mailto:pasik@iki.fi > 292. mailto:pasik@iki.fi > 293. mailto:pasik@iki.fi > 294. http://kernel.org/ > 295. http://kernel.org/ > 296. mailto:Xen-devel@lists.xen.org > 297. http://lists.xen.org/xen-devel > 298. mailto:pasik@iki.fi > 299. http://kernel.org/ > 300. http://kernel.org/ > 301. mailto:Xen-devel@lists.xen.org > 302. http://lists.xen.org/xen-devel > 303. mailto:pasik@iki.fi > 304. mailto:pasik@iki.fi > 305. http://kernel.org/ > 306. http://kernel.org/ > 307. mailto:Xen-devel@lists.xen.org > 308. http://lists.xen.org/xen-devel > 309. mailto:pasik@iki.fi > 310. http://kernel.org/ > 311. http://kernel.org/ > 312. mailto:Xen-devel@lists.xen.org > 313. http://lists.xen.org/xen-devel > 314. mailto:kiviniemi.valtteri@gmail.com > 315. http://ark.intel.com/products/65719/ > 316. http://www.intel.com/content/www/us/en/motherboards/desktop-motherboards/desktop-board-dq77mk.html > 317. mailto:root@dataproof.fi > 318. mailto:pasik@iki.fi > 319. http://xen.org/ > 320. mailto:pasik@iki.fi > 321. mailto:pasik@iki.fi > 322. mailto:pasik@iki.fi > 323. mailto:pasik@iki.fi > 324. http://kernel.org/ > 325. http://kernel.org/ > 326. mailto:Xen-devel@lists.xen.org > 327. http://lists.xen.org/xen-devel > 328. mailto:pasik@iki.fi > 329. http://kernel.org/ > 330. http://kernel.org/ > 331. mailto:Xen-devel@lists.xen.org > 332. http://lists.xen.org/xen-devel > 333. mailto:pasik@iki.fi > 334. mailto:pasik@iki.fi > 335. http://kernel.org/ > 336. http://kernel.org/ > 337. mailto:Xen-devel@lists.xen.org > 338. http://lists.xen.org/xen-devel > 339. mailto:pasik@iki.fi > 340. http://kernel.org/ > 341. http://kernel.org/ > 342. mailto:Xen-devel@lists.xen.org > 343. http://lists.xen.org/xen-devel > 344. mailto:pasik@iki.fi > 345. mailto:pasik@iki.fi > 346. mailto:pasik@iki.fi > 347. http://kernel.org/ > 348. http://kernel.org/ > 349. mailto:Xen-devel@lists.xen.org > 350. http://lists.xen.org/xen-devel > 351. mailto:pasik@iki.fi > 352. http://kernel.org/ > 353. http://kernel.org/ > 354. mailto:Xen-devel@lists.xen.org > 355. http://lists.xen.org/xen-devel > 356. mailto:pasik@iki.fi > 357. mailto:pasik@iki.fi > 358. http://kernel.org/ > 359. http://kernel.org/ > 360. mailto:Xen-devel@lists.xen.org > 361. http://lists.xen.org/xen-devel > 362. mailto:pasik@iki.fi > 363. http://kernel.org/ > 364. http://kernel.org/ > 365. mailto:Xen-devel@lists.xen.org > 366. http://lists.xen.org/xen-devel > 367. mailto:pasik@iki.fi > 368. mailto:pasik@iki.fi > 369. mailto:pasik@iki.fi > 370. mailto:pasik@iki.fi > 371. http://kernel.org/ > 372. http://kernel.org/ > 373. mailto:Xen-devel@lists.xen.org > 374. http://lists.xen.org/xen-devel > 375. mailto:pasik@iki.fi > 376. http://kernel.org/ > 377. http://kernel.org/ > 378. mailto:Xen-devel@lists.xen.org > 379. http://lists.xen.org/xen-devel > 380. mailto:pasik@iki.fi > 381. mailto:pasik@iki.fi > 382. http://kernel.org/ > 383. http://kernel.org/ > 384. mailto:Xen-devel@lists.xen.org > 385. http://lists.xen.org/xen-devel > 386. mailto:pasik@iki.fi > 387. http://kernel.org/ > 388. http://kernel.org/ > 389. mailto:Xen-devel@lists.xen.org > 390. http://lists.xen.org/xen-devel > 391. mailto:pasik@iki.fi > 392. mailto:pasik@iki.fi > 393. mailto:pasik@iki.fi > 394. http://kernel.org/ > 395. http://kernel.org/ > 396. mailto:Xen-devel@lists.xen.org > 397. http://lists.xen.org/xen-devel > 398. mailto:pasik@iki.fi > 399. http://kernel.org/ > 400. http://kernel.org/ > 401. mailto:Xen-devel@lists.xen.org > 402. http://lists.xen.org/xen-devel > 403. mailto:pasik@iki.fi > 404. mailto:pasik@iki.fi > 405. http://kernel.org/ > 406. http://kernel.org/ > 407. mailto:Xen-devel@lists.xen.org > 408. http://lists.xen.org/xen-devel > 409. mailto:pasik@iki.fi > 410. http://kernel.org/ > 411. http://kernel.org/ > 412. mailto:Xen-devel@lists.xen.org > 413. http://lists.xen.org/xen-devel
Konrad Rzeszutek Wilk
2012-Oct-02 14:20 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
On Tue, Oct 2, 2012 at 9:01 AM, Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com> wrote:> Hi, > > I already tried 3.2, 3.5, 3.5.0, 3.6.0-rc7 and 3.6.0, same problem all of > those. My dom0 config is the same config that I''am using on other server > where HVM is working, so I dont think that it is a config problem. I have > triple checked everything and all should be ok. dom0 dmesg shows the same > crash that I have previously posted here. /var/log/xen/ does not contain any > specific errors. > > Could this be some kind of broblem with my motherboard bios being buggy or > CPU not supported? I''m using the new intel Ivy Bridge processor which has > integrated GPU, but that should not probably cause these kind of problems. > Or maybe some ACPI problem? xm dmesg is showing some notices about ACPI. Is > there any ACPI kernel parameters that I should try booting? This has to be > somekind of problem with my hardware, or then maybe it could be a kernel > problem too. I just really cant figure this out myself, I have tried > everything. > > Lets take a quick summary of what has been tested, what hardware I''m using > etc. > > Xen-versions tested: 4.2.0, 4.0.4 > Kernel-versions tested: 3.2.0, 3.5.0, 3.5.4, 3.6.0-rc7, 3.6.0 > > Host OS: Debian testing/wheezy, udev version 175-7, 2.13-35, python version > 2.7.3~rc2-2.1 > > Hardware: > > CPU: Intel Core i7-3770 3.4GHz > MB: Intel DQ77MK (latest bios updated) > Memory: 32GB (4 x 8GB DDR3-1600MHz) > > All relevant log files and configs: > > dom0 dmesg: http://nago.fi/dmesg.txt > qemu-dm log: http://nago.fi/qemu-dm.txt > xm dmesg log: http://nago.fi/xm-dmesg.txt > domU config: http://nago.fi/domu-config.txt > dom0 kernel config: http://nago.fi/dom0-config.txt > > I have also tried playing with every setting on that domU that I can think > of and tried different configs etc.This is troubling. You seem to trigger the QEMU closing the tunX (your Windows''s guest network interface) which then crashes somehow. Just to make sure that this is the case - can you try launching your guest without network and seeing what happens?
Valtteri Kiviniemi
2012-Oct-02 14:37 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
Hi, Tried boogin with vif-parameters commented out, result is the same: Error: Device 768 (vbd) could not be connected. Hotplug scripts not working. But what is more troubling with these issues I''m having is the fact that this "hotpluf scripts not working" came out of nowhere. I was able to boot my Windows domU just fine earlier with only problem being that the VNC output was just black screen after Windows installer had started. Then I tried to create a Linux HVM (debian squeeze) and then I got that "Hotplug scripts not working" error. And after trying to start Windows domU again it says that same "Hotplug scripts not working" error. If I reboot the machine and start my Windows domU it will start again just fine, but the VNC output is just black screen. Then again, if I start the Linux HVM domU I will again get that "Hotplug scripts not working" error and then the Windows domU wont start either again and tells the same "Hotplug scripts not working" error. So this is pretty confusing and troubling indeed. I will reboot the machine later and put those boot parameters that Pasi mentioned. - Valtteri 2012/10/2 Konrad Rzeszutek Wilk <konrad@kernel.org>> On Tue, Oct 2, 2012 at 9:01 AM, Valtteri Kiviniemi > <kiviniemi.valtteri@gmail.com> wrote: > > Hi, > > > > I already tried 3.2, 3.5, 3.5.0, 3.6.0-rc7 and 3.6.0, same problem all of > > those. My dom0 config is the same config that I''am using on other server > > where HVM is working, so I dont think that it is a config problem. I have > > triple checked everything and all should be ok. dom0 dmesg shows the same > > crash that I have previously posted here. /var/log/xen/ does not contain > any > > specific errors. > > > > Could this be some kind of broblem with my motherboard bios being buggy > or > > CPU not supported? I''m using the new intel Ivy Bridge processor which has > > integrated GPU, but that should not probably cause these kind of > problems. > > Or maybe some ACPI problem? xm dmesg is showing some notices about ACPI. > Is > > there any ACPI kernel parameters that I should try booting? This has to > be > > somekind of problem with my hardware, or then maybe it could be a kernel > > problem too. I just really cant figure this out myself, I have tried > > everything. > > > > Lets take a quick summary of what has been tested, what hardware I''m > using > > etc. > > > > Xen-versions tested: 4.2.0, 4.0.4 > > Kernel-versions tested: 3.2.0, 3.5.0, 3.5.4, 3.6.0-rc7, 3.6.0 > > > > Host OS: Debian testing/wheezy, udev version 175-7, 2.13-35, python > version > > 2.7.3~rc2-2.1 > > > > Hardware: > > > > CPU: Intel Core i7-3770 3.4GHz > > MB: Intel DQ77MK (latest bios updated) > > Memory: 32GB (4 x 8GB DDR3-1600MHz) > > > > All relevant log files and configs: > > > > dom0 dmesg: http://nago.fi/dmesg.txt > > qemu-dm log: http://nago.fi/qemu-dm.txt > > xm dmesg log: http://nago.fi/xm-dmesg.txt > > domU config: http://nago.fi/domu-config.txt > > dom0 kernel config: http://nago.fi/dom0-config.txt > > > > I have also tried playing with every setting on that domU that I can > think > > of and tried different configs etc. > > This is troubling. You seem to trigger the QEMU closing the tunX (your > Windows''s guest network interface) which then crashes somehow. > Just to make sure that this is the case - can you try launching your > guest without network and seeing what happens? >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Pasi Kärkkäinen
2012-Oct-02 14:42 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
On Tue, Oct 02, 2012 at 05:37:08PM +0300, Valtteri Kiviniemi wrote:> Hi, > > Tried boogin with vif-parameters commented out, result is the same: > > Error: Device 768 (vbd) could not be connected. Hotplug scripts not > working. > > But what is more troubling with these issues I''m having is the fact that > this "hotpluf scripts not working" came out of nowhere. I was able to boot > my Windows domU just fine earlier with only problem being that the VNC > output was just black screen after Windows installer had started. Then I > tried to create a Linux HVM (debian squeeze) and then I got that "Hotplug > scripts not working" error. And after trying to start Windows domU again > it says that same "Hotplug scripts not working" error. > > If I reboot the machine and start my Windows domU it will start again just > fine, but the VNC output is just black screen. Then again, if I start the > Linux HVM domU I will again get that "Hotplug scripts not working" error > and then the Windows domU wont start either again and tells the same > "Hotplug scripts not working" error. > > So this is pretty confusing and troubling indeed. > > I will reboot the machine later and put those boot parameters that Pasi > mentioned. >My parameters were meant for the case where your server crashes, to be able to get a proper boot and crash logs to analyze it. -- Pasi> - Valtteri > > 2012/10/2 Konrad Rzeszutek Wilk <[1]konrad@kernel.org> > > On Tue, Oct 2, 2012 at 9:01 AM, Valtteri Kiviniemi > <[2]kiviniemi.valtteri@gmail.com> wrote: > > Hi, > > > > I already tried 3.2, 3.5, 3.5.0, 3.6.0-rc7 and 3.6.0, same problem all > of > > those. My dom0 config is the same config that I''am using on other > server > > where HVM is working, so I dont think that it is a config problem. I > have > > triple checked everything and all should be ok. dom0 dmesg shows the > same > > crash that I have previously posted here. /var/log/xen/ does not > contain any > > specific errors. > > > > Could this be some kind of broblem with my motherboard bios being > buggy or > > CPU not supported? I''m using the new intel Ivy Bridge processor which > has > > integrated GPU, but that should not probably cause these kind of > problems. > > Or maybe some ACPI problem? xm dmesg is showing some notices about > ACPI. Is > > there any ACPI kernel parameters that I should try booting? This has > to be > > somekind of problem with my hardware, or then maybe it could be a > kernel > > problem too. I just really cant figure this out myself, I have tried > > everything. > > > > Lets take a quick summary of what has been tested, what hardware I''m > using > > etc. > > > > Xen-versions tested: 4.2.0, 4.0.4 > > Kernel-versions tested: 3.2.0, 3.5.0, 3.5.4, 3.6.0-rc7, 3.6.0 > > > > Host OS: Debian testing/wheezy, udev version 175-7, 2.13-35, python > version > > 2.7.3~rc2-2.1 > > > > Hardware: > > > > CPU: Intel Core i7-3770 3.4GHz > > MB: Intel DQ77MK (latest bios updated) > > Memory: 32GB (4 x 8GB DDR3-1600MHz) > > > > All relevant log files and configs: > > > > dom0 dmesg: [3]http://nago.fi/dmesg.txt > > qemu-dm log: [4]http://nago.fi/qemu-dm.txt > > xm dmesg log: [5]http://nago.fi/xm-dmesg.txt > > domU config: [6]http://nago.fi/domu-config.txt > > dom0 kernel config: [7]http://nago.fi/dom0-config.txt > > > > I have also tried playing with every setting on that domU that I can > think > > of and tried different configs etc. > > This is troubling. You seem to trigger the QEMU closing the tunX (your > Windows''s guest network interface) which then crashes somehow. > Just to make sure that this is the case - can you try launching your > guest without network and seeing what happens? > > References > > Visible links > 1. mailto:konrad@kernel.org > 2. mailto:kiviniemi.valtteri@gmail.com > 3. http://nago.fi/dmesg.txt > 4. http://nago.fi/qemu-dm.txt > 5. http://nago.fi/xm-dmesg.txt > 6. http://nago.fi/domu-config.txt > 7. http://nago.fi/dom0-config.txt
Valtteri Kiviniemi
2012-Oct-02 14:55 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
Hi, Yes, I understood for what the parameters were for. I''ts been a long time since I last had major problems with Xen (maybe 3.1 or something, been using Xen since version 2) and I had a shady recollection that Xen was required to be build debugging enabled in order to get any usable debugging data. But anyway, I cant reproduce that kernel crash everytime, it just happens sometimes. Major problem is the black screen on VNC and second problem seems to be that everytime i try to run Linux in HVM mode it somehow breaks the hotplug scripts. - Valtteri 2012/10/2 Pasi Kärkkäinen <pasik@iki.fi>> On Tue, Oct 02, 2012 at 05:37:08PM +0300, Valtteri Kiviniemi wrote: > > Hi, > > > > Tried boogin with vif-parameters commented out, result is the same: > > > > Error: Device 768 (vbd) could not be connected. Hotplug scripts not > > working. > > > > But what is more troubling with these issues I''m having is the fact > that > > this "hotpluf scripts not working" came out of nowhere. I was able to > boot > > my Windows domU just fine earlier with only problem being that the VNC > > output was just black screen after Windows installer had started. > Then I > > tried to create a Linux HVM (debian squeeze) and then I got that > "Hotplug > > scripts not working" error. And after trying to start Windows domU > again > > it says that same "Hotplug scripts not working" error. > > > > If I reboot the machine and start my Windows domU it will start again > just > > fine, but the VNC output is just black screen. Then again, if I start > the > > Linux HVM domU I will again get that "Hotplug scripts not working" > error > > and then the Windows domU wont start either again and tells the same > > "Hotplug scripts not working" error. > > > > So this is pretty confusing and troubling indeed. > > > > I will reboot the machine later and put those boot parameters that > Pasi > > mentioned. > > > > My parameters were meant for the case where your server crashes, > to be able to get a proper boot and crash logs to analyze it. > > -- Pasi > > > > - Valtteri > > > > 2012/10/2 Konrad Rzeszutek Wilk <[1]konrad@kernel.org> > > > > On Tue, Oct 2, 2012 at 9:01 AM, Valtteri Kiviniemi > > <[2]kiviniemi.valtteri@gmail.com> wrote: > > > Hi, > > > > > > I already tried 3.2, 3.5, 3.5.0, 3.6.0-rc7 and 3.6.0, same > problem all > > of > > > those. My dom0 config is the same config that I''am using on other > > server > > > where HVM is working, so I dont think that it is a config > problem. I > > have > > > triple checked everything and all should be ok. dom0 dmesg shows > the > > same > > > crash that I have previously posted here. /var/log/xen/ does not > > contain any > > > specific errors. > > > > > > Could this be some kind of broblem with my motherboard bios being > > buggy or > > > CPU not supported? I''m using the new intel Ivy Bridge processor > which > > has > > > integrated GPU, but that should not probably cause these kind of > > problems. > > > Or maybe some ACPI problem? xm dmesg is showing some notices about > > ACPI. Is > > > there any ACPI kernel parameters that I should try booting? This > has > > to be > > > somekind of problem with my hardware, or then maybe it could be a > > kernel > > > problem too. I just really cant figure this out myself, I have > tried > > > everything. > > > > > > Lets take a quick summary of what has been tested, what hardware > I''m > > using > > > etc. > > > > > > Xen-versions tested: 4.2.0, 4.0.4 > > > Kernel-versions tested: 3.2.0, 3.5.0, 3.5.4, 3.6.0-rc7, 3.6.0 > > > > > > Host OS: Debian testing/wheezy, udev version 175-7, 2.13-35, > python > > version > > > 2.7.3~rc2-2.1 > > > > > > Hardware: > > > > > > CPU: Intel Core i7-3770 3.4GHz > > > MB: Intel DQ77MK (latest bios updated) > > > Memory: 32GB (4 x 8GB DDR3-1600MHz) > > > > > > All relevant log files and configs: > > > > > > dom0 dmesg: [3]http://nago.fi/dmesg.txt > > > qemu-dm log: [4]http://nago.fi/qemu-dm.txt > > > xm dmesg log: [5]http://nago.fi/xm-dmesg.txt > > > domU config: [6]http://nago.fi/domu-config.txt > > > dom0 kernel config: [7]http://nago.fi/dom0-config.txt > > > > > > I have also tried playing with every setting on that domU that I > can > > think > > > of and tried different configs etc. > > > > This is troubling. You seem to trigger the QEMU closing the tunX > (your > > Windows''s guest network interface) which then crashes somehow. > > Just to make sure that this is the case - can you try launching your > > guest without network and seeing what happens? > > > > References > > > > Visible links > > 1. mailto:konrad@kernel.org > > 2. mailto:kiviniemi.valtteri@gmail.com > > 3. http://nago.fi/dmesg.txt > > 4. http://nago.fi/qemu-dm.txt > > 5. http://nago.fi/xm-dmesg.txt > > 6. http://nago.fi/domu-config.txt > > 7. http://nago.fi/dom0-config.txt >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Konrad Rzeszutek Wilk
2012-Oct-02 18:56 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
On Tue, Oct 2, 2012 at 10:55 AM, Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com> wrote:> Hi, > > Yes, I understood for what the parameters were for. I''ts been a long time > since I last had major problems with Xen (maybe 3.1 or something, been using > Xen since version 2) and I had a shady recollection that Xen was required to > be build debugging enabled in order to get any usable debugging data. > > But anyway, I cant reproduce that kernel crash everytime, it just happens > sometimes. Major problem is the black screen on VNC and second problem seems > to be that everytime i try to run Linux in HVM mode it somehow breaks the > hotplug scripts. >So do you have all backends loaded? Is xen-netback and xen-blkback running? Do you also have tun loaded?
Valtteri Kiviniemi
2012-Oct-02 20:23 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
Hi, Yes, they are all loaded and I''m running Linux PV-virtuals at the same time with no problems. Only HVM is not working. I have single socket corei7 processor and NUMA enabled on dom0 kernel, so I will try tomorrow to compile dom0 kernel without NUMA, since its not needed and it could probably cause some kind of memory related problems. I will also try Debian squeezes package Xen and test if it is working with my hardware. - Valtteri 2012/10/2 Konrad Rzeszutek Wilk <konrad@kernel.org>> On Tue, Oct 2, 2012 at 10:55 AM, Valtteri Kiviniemi > <kiviniemi.valtteri@gmail.com> wrote: > > Hi, > > > > Yes, I understood for what the parameters were for. I''ts been a long time > > since I last had major problems with Xen (maybe 3.1 or something, been > using > > Xen since version 2) and I had a shady recollection that Xen was > required to > > be build debugging enabled in order to get any usable debugging data. > > > > But anyway, I cant reproduce that kernel crash everytime, it just happens > > sometimes. Major problem is the black screen on VNC and second problem > seems > > to be that everytime i try to run Linux in HVM mode it somehow breaks the > > hotplug scripts. > > > > So do you have all backends loaded? Is xen-netback and xen-blkback running? > Do you also have tun loaded? >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Valtteri Kiviniemi
2012-Oct-03 09:21 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
Hi, I disabled NUMA and upgraded to Xen 4.2.0. Windows domU starts now fine and I cant anymore reproduce the hotplug problems. VNC output is still just black screen and it actually crashes the the whole VNC client when after a few seconds. RealVNC just shuts itself down and tightvnc crashes. - Valtteri 2012/10/2 Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com>> Hi, > > Yes, they are all loaded and I''m running Linux PV-virtuals at the same > time with no problems. Only HVM is not working. I have single socket corei7 > processor and NUMA enabled on dom0 kernel, so I will try tomorrow to > compile dom0 kernel without NUMA, since its not needed and it could > probably cause some kind of memory related problems. > > I will also try Debian squeezes package Xen and test if it is working with > my hardware. > > - Valtteri > > > 2012/10/2 Konrad Rzeszutek Wilk <konrad@kernel.org> > >> On Tue, Oct 2, 2012 at 10:55 AM, Valtteri Kiviniemi >> <kiviniemi.valtteri@gmail.com> wrote: >> > Hi, >> > >> > Yes, I understood for what the parameters were for. I''ts been a long >> time >> > since I last had major problems with Xen (maybe 3.1 or something, been >> using >> > Xen since version 2) and I had a shady recollection that Xen was >> required to >> > be build debugging enabled in order to get any usable debugging data. >> > >> > But anyway, I cant reproduce that kernel crash everytime, it just >> happens >> > sometimes. Major problem is the black screen on VNC and second problem >> seems >> > to be that everytime i try to run Linux in HVM mode it somehow breaks >> the >> > hotplug scripts. >> > >> >> So do you have all backends loaded? Is xen-netback and xen-blkback >> running? >> Do you also have tun loaded? >> > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Valtteri Kiviniemi
2012-Oct-03 10:36 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
Hi, I enabled debugging, no new information available. DomU starts, VNC has black screen. No crashes so far. - Valtteri 2012/10/3 Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com>> Hi, > > I disabled NUMA and upgraded to Xen 4.2.0. Windows domU starts now fine > and I cant anymore reproduce the hotplug problems. VNC output is still just > black screen and it actually crashes the the whole VNC client when after a > few seconds. RealVNC just shuts itself down and tightvnc crashes. > > - Valtteri > > > > 2012/10/2 Valtteri Kiviniemi <kiviniemi.valtteri@gmail.com> > >> Hi, >> >> Yes, they are all loaded and I''m running Linux PV-virtuals at the same >> time with no problems. Only HVM is not working. I have single socket corei7 >> processor and NUMA enabled on dom0 kernel, so I will try tomorrow to >> compile dom0 kernel without NUMA, since its not needed and it could >> probably cause some kind of memory related problems. >> >> I will also try Debian squeezes package Xen and test if it is working >> with my hardware. >> >> - Valtteri >> >> >> 2012/10/2 Konrad Rzeszutek Wilk <konrad@kernel.org> >> >>> On Tue, Oct 2, 2012 at 10:55 AM, Valtteri Kiviniemi >>> <kiviniemi.valtteri@gmail.com> wrote: >>> > Hi, >>> > >>> > Yes, I understood for what the parameters were for. I''ts been a long >>> time >>> > since I last had major problems with Xen (maybe 3.1 or something, been >>> using >>> > Xen since version 2) and I had a shady recollection that Xen was >>> required to >>> > be build debugging enabled in order to get any usable debugging data. >>> > >>> > But anyway, I cant reproduce that kernel crash everytime, it just >>> happens >>> > sometimes. Major problem is the black screen on VNC and second problem >>> seems >>> > to be that everytime i try to run Linux in HVM mode it somehow breaks >>> the >>> > hotplug scripts. >>> > >>> >>> So do you have all backends loaded? Is xen-netback and xen-blkback >>> running? >>> Do you also have tun loaded? >>> >> >> >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Pasi Kärkkäinen
2012-Oct-03 11:45 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
On Wed, Oct 03, 2012 at 12:21:47PM +0300, Valtteri Kiviniemi wrote:> Hi, > > I disabled NUMA and upgraded to Xen 4.2.0. Windows domU starts now fine > and I cant anymore reproduce the hotplug problems. VNC output is still > just black screen and it actually crashes the the whole VNC client when > after a few seconds. RealVNC just shuts itself down and tightvnc crashes. >Valtteri: Can you actually paste the names of the .config options you disabled and got the dom0 kernel working without crashes? Maybe Konrad can comment if the current upstream dom0 kernel is supposed to work with NUMA support enabled / compiled in? -- Pasi> - Valtteri > > 2012/10/2 Valtteri Kiviniemi <[1]kiviniemi.valtteri@gmail.com> > > Hi, > > Yes, they are all loaded and I''m running Linux PV-virtuals at the same > time with no problems. Only HVM is not working. I have single socket > corei7 processor and NUMA enabled on dom0 kernel, so I will try tomorrow > to compile dom0 kernel without NUMA, since its not needed and it could > probably cause some kind of memory related problems. > > I will also try Debian squeezes package Xen and test if it is working > with my hardware. > > - Valtteri > > 2012/10/2 Konrad Rzeszutek Wilk <[2]konrad@kernel.org> > > On Tue, Oct 2, 2012 at 10:55 AM, Valtteri Kiviniemi > <[3]kiviniemi.valtteri@gmail.com> wrote: > > Hi, > > > > Yes, I understood for what the parameters were for. I''ts been a long > time > > since I last had major problems with Xen (maybe 3.1 or something, > been using > > Xen since version 2) and I had a shady recollection that Xen was > required to > > be build debugging enabled in order to get any usable debugging > data. > > > > But anyway, I cant reproduce that kernel crash everytime, it just > happens > > sometimes. Major problem is the black screen on VNC and second > problem seems > > to be that everytime i try to run Linux in HVM mode it somehow > breaks the > > hotplug scripts. > > > > So do you have all backends loaded? Is xen-netback and xen-blkback > running? > Do you also have tun loaded? > > References > > Visible links > 1. mailto:kiviniemi.valtteri@gmail.com > 2. mailto:konrad@kernel.org > 3. mailto:kiviniemi.valtteri@gmail.com
Valtteri Kiviniemi
2012-Oct-03 12:09 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
Hi, Yes, of course. I disabled these options: Processor type and features: [*] Numa Memory Allocation and Scheduler Support [*] ACPI NUMA detection Power management and ACPI options ---> ACPI (Advanced Configuration and Power Interface) Support -*- NUMA support Any Ideas howto debug the VNC problem any further? - Valtteri 2012/10/3 Pasi Kärkkäinen <pasik@iki.fi>> On Wed, Oct 03, 2012 at 12:21:47PM +0300, Valtteri Kiviniemi wrote: > > Hi, > > > > I disabled NUMA and upgraded to Xen 4.2.0. Windows domU starts now > fine > > and I cant anymore reproduce the hotplug problems. VNC output is still > > just black screen and it actually crashes the the whole VNC client > when > > after a few seconds. RealVNC just shuts itself down and tightvnc > crashes. > > > > > Valtteri: Can you actually paste the names of the .config options you > disabled > and got the dom0 kernel working without crashes? > > Maybe Konrad can comment if the current upstream dom0 kernel is supposed > to work > with NUMA support enabled / compiled in? > > -- Pasi > > > - Valtteri > > > > 2012/10/2 Valtteri Kiviniemi <[1]kiviniemi.valtteri@gmail.com> > > > > Hi, > > > > Yes, they are all loaded and I''m running Linux PV-virtuals at the > same > > time with no problems. Only HVM is not working. I have single socket > > corei7 processor and NUMA enabled on dom0 kernel, so I will try > tomorrow > > to compile dom0 kernel without NUMA, since its not needed and it > could > > probably cause some kind of memory related problems. > > > > I will also try Debian squeezes package Xen and test if it is > working > > with my hardware. > > > > - Valtteri > > > > 2012/10/2 Konrad Rzeszutek Wilk <[2]konrad@kernel.org> > > > > On Tue, Oct 2, 2012 at 10:55 AM, Valtteri Kiviniemi > > <[3]kiviniemi.valtteri@gmail.com> wrote: > > > Hi, > > > > > > Yes, I understood for what the parameters were for. I''ts been a > long > > time > > > since I last had major problems with Xen (maybe 3.1 or > something, > > been using > > > Xen since version 2) and I had a shady recollection that Xen was > > required to > > > be build debugging enabled in order to get any usable debugging > > data. > > > > > > But anyway, I cant reproduce that kernel crash everytime, it > just > > happens > > > sometimes. Major problem is the black screen on VNC and second > > problem seems > > > to be that everytime i try to run Linux in HVM mode it somehow > > breaks the > > > hotplug scripts. > > > > > > > So do you have all backends loaded? Is xen-netback and xen-blkback > > running? > > Do you also have tun loaded? > > > > References > > > > Visible links > > 1. mailto:kiviniemi.valtteri@gmail.com > > 2. mailto:konrad@kernel.org > > 3. mailto:kiviniemi.valtteri@gmail.com >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Pasi Kärkkäinen
2012-Oct-03 12:48 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
On Wed, Oct 03, 2012 at 03:09:07PM +0300, Valtteri Kiviniemi wrote:> Hi, > > Yes, of course. I disabled these options: > > Processor type and features: > [*] Numa Memory Allocation and Scheduler Support > [*] ACPI NUMA detection > > Power management and ACPI options ---> > ACPI (Advanced Configuration and Power Interface) Support > -*- NUMA support >Ok. Good to know.> Any Ideas howto debug the VNC problem any further? >Maybe start a new thread about the VNC problem.. it seems to be a separate issue. -- Pasi> - Valtteri > > 2012/10/3 Pasi Kärkkäinen <[1]pasik@iki.fi> > > On Wed, Oct 03, 2012 at 12:21:47PM +0300, Valtteri Kiviniemi wrote: > > Hi, > > > > I disabled NUMA and upgraded to Xen 4.2.0. Windows domU starts now > fine > > and I cant anymore reproduce the hotplug problems. VNC output is > still > > just black screen and it actually crashes the the whole VNC client > when > > after a few seconds. RealVNC just shuts itself down and tightvnc > crashes. > > > > Valtteri: Can you actually paste the names of the .config options you > disabled > and got the dom0 kernel working without crashes? > > Maybe Konrad can comment if the current upstream dom0 kernel is supposed > to work > with NUMA support enabled / compiled in? > > -- Pasi > > > - Valtteri > > > > 2012/10/2 Valtteri Kiviniemi <[1][2]kiviniemi.valtteri@gmail.com> > > > > Hi, > > > > Yes, they are all loaded and I''m running Linux PV-virtuals at the > same > > time with no problems. Only HVM is not working. I have single > socket > > corei7 processor and NUMA enabled on dom0 kernel, so I will try > tomorrow > > to compile dom0 kernel without NUMA, since its not needed and it > could > > probably cause some kind of memory related problems. > > > > I will also try Debian squeezes package Xen and test if it is > working > > with my hardware. > > > > - Valtteri > > > > 2012/10/2 Konrad Rzeszutek Wilk <[2][3]konrad@kernel.org> > > > > On Tue, Oct 2, 2012 at 10:55 AM, Valtteri Kiviniemi > > <[3][4]kiviniemi.valtteri@gmail.com> wrote: > > > Hi, > > > > > > Yes, I understood for what the parameters were for. I''ts been > a long > > time > > > since I last had major problems with Xen (maybe 3.1 or > something, > > been using > > > Xen since version 2) and I had a shady recollection that Xen > was > > required to > > > be build debugging enabled in order to get any usable > debugging > > data. > > > > > > But anyway, I cant reproduce that kernel crash everytime, it > just > > happens > > > sometimes. Major problem is the black screen on VNC and > second > > problem seems > > > to be that everytime i try to run Linux in HVM mode it > somehow > > breaks the > > > hotplug scripts. > > > > > > > So do you have all backends loaded? Is xen-netback and > xen-blkback > > running? > > Do you also have tun loaded? > > > > References > > > > Visible links > > 1. mailto:[5]kiviniemi.valtteri@gmail.com > > 2. mailto:[6]konrad@kernel.org > > 3. mailto:[7]kiviniemi.valtteri@gmail.com > > References > > Visible links > 1. mailto:pasik@iki.fi > 2. mailto:kiviniemi.valtteri@gmail.com > 3. mailto:konrad@kernel.org > 4. mailto:kiviniemi.valtteri@gmail.com > 5. mailto:kiviniemi.valtteri@gmail.com > 6. mailto:konrad@kernel.org > 7. mailto:kiviniemi.valtteri@gmail.com
Valtteri Kiviniemi
2012-Oct-03 12:49 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
Hi, Ok, will do that. thanks. - Valtteri 2012/10/3 Pasi Kärkkäinen <pasik@iki.fi>> On Wed, Oct 03, 2012 at 03:09:07PM +0300, Valtteri Kiviniemi wrote: > > Hi, > > > > Yes, of course. I disabled these options: > > > > Processor type and features: > > [*] Numa Memory Allocation and Scheduler Support > > [*] ACPI NUMA detection > > > > Power management and ACPI options ---> > > ACPI (Advanced Configuration and Power Interface) Support > > -*- NUMA support > > > > Ok. Good to know. > > > Any Ideas howto debug the VNC problem any further? > > > > Maybe start a new thread about the VNC problem.. it seems to be a separate > issue. > > -- Pasi > > > - Valtteri > > > > 2012/10/3 Pasi Kärkkäinen <[1]pasik@iki.fi> > > > > On Wed, Oct 03, 2012 at 12:21:47PM +0300, Valtteri Kiviniemi wrote: > > > Hi, > > > > > > I disabled NUMA and upgraded to Xen 4.2.0. Windows domU starts > now > > fine > > > and I cant anymore reproduce the hotplug problems. VNC output > is > > still > > > just black screen and it actually crashes the the whole VNC > client > > when > > > after a few seconds. RealVNC just shuts itself down and > tightvnc > > crashes. > > > > > > > Valtteri: Can you actually paste the names of the .config options > you > > disabled > > and got the dom0 kernel working without crashes? > > > > Maybe Konrad can comment if the current upstream dom0 kernel is > supposed > > to work > > with NUMA support enabled / compiled in? > > > > -- Pasi > > > > > - Valtteri > > > > > > 2012/10/2 Valtteri Kiviniemi <[1][2] > kiviniemi.valtteri@gmail.com> > > > > > > Hi, > > > > > > Yes, they are all loaded and I''m running Linux PV-virtuals > at the > > same > > > time with no problems. Only HVM is not working. I have single > > socket > > > corei7 processor and NUMA enabled on dom0 kernel, so I will > try > > tomorrow > > > to compile dom0 kernel without NUMA, since its not needed > and it > > could > > > probably cause some kind of memory related problems. > > > > > > I will also try Debian squeezes package Xen and test if it is > > working > > > with my hardware. > > > > > > - Valtteri > > > > > > 2012/10/2 Konrad Rzeszutek Wilk <[2][3]konrad@kernel.org> > > > > > > On Tue, Oct 2, 2012 at 10:55 AM, Valtteri Kiviniemi > > > <[3][4]kiviniemi.valtteri@gmail.com> wrote: > > > > Hi, > > > > > > > > Yes, I understood for what the parameters were for. I''ts > been > > a long > > > time > > > > since I last had major problems with Xen (maybe 3.1 or > > something, > > > been using > > > > Xen since version 2) and I had a shady recollection that > Xen > > was > > > required to > > > > be build debugging enabled in order to get any usable > > debugging > > > data. > > > > > > > > But anyway, I cant reproduce that kernel crash > everytime, it > > just > > > happens > > > > sometimes. Major problem is the black screen on VNC and > > second > > > problem seems > > > > to be that everytime i try to run Linux in HVM mode it > > somehow > > > breaks the > > > > hotplug scripts. > > > > > > > > > > So do you have all backends loaded? Is xen-netback and > > xen-blkback > > > running? > > > Do you also have tun loaded? > > > > > > References > > > > > > Visible links > > > 1. mailto:[5]kiviniemi.valtteri@gmail.com > > > 2. mailto:[6]konrad@kernel.org > > > 3. mailto:[7]kiviniemi.valtteri@gmail.com > > > > References > > > > Visible links > > 1. mailto:pasik@iki.fi > > 2. mailto:kiviniemi.valtteri@gmail.com > > 3. mailto:konrad@kernel.org > > 4. mailto:kiviniemi.valtteri@gmail.com > > 5. mailto:kiviniemi.valtteri@gmail.com > > 6. mailto:konrad@kernel.org > > 7. mailto:kiviniemi.valtteri@gmail.com >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
Konrad Rzeszutek Wilk
2012-Oct-03 13:25 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
On Wed, Oct 3, 2012 at 7:45 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote:> On Wed, Oct 03, 2012 at 12:21:47PM +0300, Valtteri Kiviniemi wrote: >> Hi, >> >> I disabled NUMA and upgraded to Xen 4.2.0. Windows domU starts now fine >> and I cant anymore reproduce the hotplug problems. VNC output is still >> just black screen and it actually crashes the the whole VNC client when >> after a few seconds. RealVNC just shuts itself down and tightvnc crashes. >> > > > Valtteri: Can you actually paste the names of the .config options you disabled > and got the dom0 kernel working without crashes? > > Maybe Konrad can comment if the current upstream dom0 kernel is supposed to work > with NUMA support enabled / compiled in?There is a patch to actually disable it since we do not provide any NUMA information to the guest. And the dom0 has access to extra information (ACPI, Northbridge, etc) so it might think to create a NUMA topology and get it wrong. But his dmesg did not have anything obvious related to NUMA, so I am perplexed that turning that off would have made such a difference. Valterri - if you just pass ''numa=off'' on the Linux command line with the old kernel (the one that had the NUMA enabled) does that make it the iput issue go away? You VNC issue .. does it work if you launch PV guests? Or is it only for HVM guests?
Valtteri Kiviniemi
2012-Oct-03 13:41 UTC
Re: Xen 4.0.4, kernel 3.5.0 HVM crash and kernel BUG
2012/10/3 Konrad Rzeszutek Wilk <konrad@kernel.org>> On Wed, Oct 3, 2012 at 7:45 AM, Pasi Kärkkäinen <pasik@iki.fi> wrote: > > On Wed, Oct 03, 2012 at 12:21:47PM +0300, Valtteri Kiviniemi wrote: > >> Hi, > >> > >> I disabled NUMA and upgraded to Xen 4.2.0. Windows domU starts now > fine > >> and I cant anymore reproduce the hotplug problems. VNC output is > still > >> just black screen and it actually crashes the the whole VNC client > when > >> after a few seconds. RealVNC just shuts itself down and tightvnc > crashes. > >> > > > > > > Valtteri: Can you actually paste the names of the .config options you > disabled > > and got the dom0 kernel working without crashes? > > > > Maybe Konrad can comment if the current upstream dom0 kernel is supposed > to work > > with NUMA support enabled / compiled in? > > There is a patch to actually disable it since we do not provide any > NUMA information > to the guest. And the dom0 has access to extra information (ACPI, > Northbridge, etc) > so it might think to create a NUMA topology and get it wrong. > > But his dmesg did not have anything obvious related to NUMA, so I am > perplexed that > turning that off would have made such a difference. > > Valterri - if you just pass ''numa=off'' on the Linux command line with > the old kernel > (the one that had the NUMA enabled) does that make it the iput issue go > away? > > > You VNC issue .. does it work if you launch PV guests? Or is it only > for HVM guests? >Hi, Well it might be that disabling NUMA did not fix the problem since the crash is sometimes hard to reproduce. Sometimes it will crash everytime and sometimes I have to restart the domU 30 times before it causes that crash. But I have been testing this whole day and I have not been able to reproduce the crash anymore. I also upgraded from Xen 4.0.4 to Xen 4.2.0 so that combined for the NUMA disabling might have also affect, but I did also get the same crash on Xen 4.2.0 previously, so it probably does not affect. At the moment I cannot test enabling the NUMA since now when I got it working (at least it think that it works now) I want to figure out the VNC problem, since the VNC problem is very critical to me. I''m probably ordering another computer with the same hardware later this month and then I can use it as my primary test/dev server and try to test the NUMA again. At the moment I dont have any PV guests that I could test the VNC with. But maybe I could try installing one. I also started a new thread about the VNC problem, so I think that we should continue the VNC discussion on that thread. - Valtteri _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel