similar to: State of memdisk-acpi

From 8be8951015673d6279d7d49b0138645194317dc2 Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Wed, 9 Dec 2009 19:11:38 +0000 Subject: [PATCH] doc: document mBFT and "safe hook" --- doc/memdisk.txt | 40 ++++++++++++++++++++++++++++++++++++++++ 1 files changed, 40 insertions(+), 0 deletions(-) diff --git a/doc/memdisk.txt b/doc/memdisk.txt

Hello I am trying to boot ubuntu 9.04 with iommu=1 iommu=passthrough noreboot and i keep getting a panic i have vt and vt-d enabled in my bios here is the serial console capture __ __ _____ _ _ _ \ \/ /___ _ __ |___ /| || | / | \ // _ \ ''_ \ |_ \| || |_ | | / \ __/ | | | ___) |__ _|| | /_/\_\___|_| |_| |____(_) |_|(_)_|

Two additions to MEMDISK to support OS drivers. The "safe hook" structure ("Safe Master Boot Record INT 13h Hook Routines") is a means for an OS driver to follow a chain of INT 13h hooks, examining the hooks'' vendors and assuming responsibility for hook functionality along the way. For MEMDISK, we guarantee an additional field which holds the physical address for the

Hello, I was hoping someone might be able to tell me why IOMMU does not seem to be found on my system. At the very least is there any way I can get more debug information in addition to adding iommu=verbose to the command line? Xen 4.0.0 MSI 890FXA-GD70 (I spoke with an MSI representative who confirmed that this motherboard does support IOMMU) AMD Phenom II 1090T x6 # dmesg __ __

Package: xen-hypervisor-4.0-i386 Version: 4.0.1-5.8 Severity: normal Tags: upstream *** Please type your report below this line *** -- System Information: Debian Release: 6.0.7 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-xen-686 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8,

Hello, With kernel 2.6.32.21 (from Jeremy) : - System size : 3945 kB, gzip compressed kernel size 4051553 Bytes -> works well - System size : 3968 kB, gzip compressed kernel size 4074976 Bytes -> fault (see below) I''ve attached the 2 configurations files and xen boot error. __ __ _ _ ___ _ \ \/ /___ _ __ | || | / _ \ / | \ // _ \

UPDATE: This bug does not reproduce in version: 4.1.4-3 since the domU creation is shadowed by another new bug [1]. Below is my hypervisor log or "xm dmesg" output since the 706543 bug also affects my system: # xm dme (XEN) Xen version 4.1.4 (Debian 4.1.4-3) (waldi at debian.org) (gcc version 4.7.2 (Debian 4.7.2-5) ) Fri Apr 19 11:34:20 UTC 2013 (XEN) Bootloader: GRUB 1.99-27+deb7u1

Hi, I am having great difficulties in getting pci passthrough with VTd to work, surely I am doing something stupid but I cannot see what. "tangram" (https://www.blogger.com/profile/06588030231546523539) has been a huge help, but despite his efforts I am still stuck. Hardware: Intel S3200SHV motherboard BIOS : S3200X38.86B.00.00.0052 CPU : Intel Core 2

Hi. I'm working on replacing a PXELINUX/MEMDISK loaded DOS based installation image with a PXELINUX/MEMDISK loaded WinPE ISO image. So far everything seems to work well (appending "bigraw" to memdisk solved booting problems on several machines), but I kind of miss the option of using getargs.com to get/set environment variables from the memdisk command line. Is there any way to

Below, attached, and available at the 'ifmemdsk' branch at: http://git.zytor.com/?p=users/sha0/syslinux.git;a=commitdiff;h=a975c12919bbd48739fede4ebfe099d98b87192e Review welcome! - Shao Miller ----- From a975c12919bbd48739fede4ebfe099d98b87192e Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Sat, 6 Aug 2011 05:24:46 -0400 Subject: [PATCH]

Hello, I''ve done an update from xen 3.2 to 3.3. Since 3.3 I can not use my TV-Card anymore. The error message is "Error: pci: 0000:10:0a.0: non-page-aligned MMIO BAR found." lspci shows the card as 10:0a.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) Any hints ? Thanks in advance Christoph xm dmesg: (XEN) Xen version 3.3.1-rc1-pre (root@artus.own) (gcc

Dear Users, Debian Etch 2.6.18.8-xen from xensource.com with Xen 3.3.0 on AMD64: After i want to start the HVM i get: VmError: fail to assign device(1:0.0): maybe it has already been assigned to other domain, or maybe it doesn''t exist. [2008-10-25 19:59:30 2460] DEBUG (__init__:1072) XendDomainInfo.destroy: domid=5 [2008-10-25 19:59:30 2460] DEBUG (__init__:1072)

Hello all, I have a problem getting a working VNC console for HVM guests on Xen 4.1. When I start the DomU with xm create everything is fine the DomU runs and in xm list it has the running state but when I try to connect to the VNC console to install an operating system (Ubuntu and Debian I have tested) the VNC viewer only shows a black screen. So I searched in the logs and found a log entry

Hi, I am having some issues with xen hypervisor crashing because it could not find one of the cores in my processor. This is not consistent. It happens once in every two or three boots. Is this is xen bug or is it something related to BIOS. If it is a xen bug, has it been addressed and could you point me to the right patch. Here is the xen boot message. title CentOS (2.6.18-274.7.1.el5xen)

I''m having trouble actually seeing a PCI device in my VMs. I''ve resolved several of my issues using previous posts and using the VTdHowTo wiki page. I have both VT and VTd BIOS options enabled. I have pciback hiding the devices and xm can list and assign the devices to VMs. I don''t see the PCI devices in my VMs though. I have tried a windows and a Linux vm, without

Hi, I have some problems to configure the xen I''ve installed (3.3.1). The computer is a Intel Core 2 Duo, I''m using Ubuntu 8.10 and have linux in my dom0 and winxp pro in my domU. I have two cores and I''d like to set the affinity of dom0 to cpu0 and domU to cpu1 but I haven''t find the way of making this permanent. I''ve set cpus=1 in the domU config

When booting a recently compiled Xen 4.2 on Ubuntu 12.04, dom0 crashes. I''ve included a serial console log below. I''ve used: Xen 4.2 unstable rev. 25483, compiled on the same machine. I had to apply the AT_EMPTY_PATH patch from http://lists.gnu.org/archive/html/qemu-devel/2012-02/msg03460.html to get it to compile. Linux 3.2.0-25, which is the default kernel in Ubuntu''s

Hey guys, I am posting this again....because i didnt get any replay. Please I am doing my thesis and I am stack installing a guest machine from Yocto, a unix like machine. It boots successfully on the same host without xen. thank you again, Nas On Tue, Jun 4, 2013 at 5:37 PM, nesredin mahmud <nasmitlinux@gmail.com>wrote: > hello everyone, > > I am experiencing DomU booting

Not sure I did the xen log correctly. I have this in /etc/default/grub now: GRUB_CMDLINE_XEN_DEFAULT="loglvl=all" And now here is xen dmesg: root at xen-3:~# xl dmesg (XEN) Xen version 4.3.0 (Debian 4.3.0-3+b1) (buildd-binet at buildd.debian.org) (gcc (Debian 4.8.2-8) 4.8.2) debug=n Wed Dec 4 07:43:54 UTC 2013 (XEN) Bootloader: GRUB 2.00-22 (XEN) Command line: placeholder

Package: xen-hypervisor-3.2-1-amd64 Version: 3.2.1-2 Severity: normal After giving xen a shoot with the fresh lenny packages, an annoying bug comes up right after trying to boot into the new system. I'll provide further informations if needed. Please see serial debug output below and here http://plzk.de/xen-lenny (maxlines got extended for comfortable reading) XEN) Xen version 3.2-1