similar to: [SOLVED] ibm x440 xen not boot (rootfs not found)

Fresh Ubuntu 13.10 server build with all the latest patches, installed Xen 4.3 and XCP-XAPI. Got Xenbr0 working properly and created an LVM storage repository and a CIFS ISO repository. I can create VM''s no problem at all but whenever I try to start them I get the following error from the log. Only Windows VM. The error comes up almost instantly when trying to start it. Not sure where to

Howdy. We've got a couple IBM x440 (Summit) 8-way Xeon systems that I've been trying to get netbooting for a while. Since we use Kickstart and SystemImager to load OSes on our systems, a system has to be able to netboot before it can be made available to folks for project use. System BIOS is the current one, v1.08. They're booting from a planar BroadCom Tigon3 adapter. BIOS

Hi, I am a Masters student from Carnegie Mellon University. I am looking for a research topics for an Advanced OS & DS course we have. I wanted to know what is the current support for NUMA on Xen ? Does it support the IBM x440 and AMD64 Opteron ? Also, does the Xen scheduler do NUMA aware scheduling so it does not degrade the VM performace ? My group is currently looking into Scheduling

Hi all I just ran these tests on my network and came up with these results. I found it interesting and thought I would share. In all test the same 2.5 Gig logfile was used for transfer (2719312019 Nov 12 11:42 maillog.back) (2.5G Nov 12 11:42 maillog.back) The transfer was done over two Gigabit nic's one onboard broadcom on IBM X440 server, Other Intel on standard selfbuilt dual P3 880

bgColor="oldlace"<BR><DIV>&nbsp;</DIV> <BR><BR>width="92%" bgColor="lemonchiffon" <BR><DIV><FONT style="FONT-SIZE: 2px" size=1>&#173;</FONT></DIV> <BR><DIV><FONT style="FONT-SIZE: 1px" size=1>&#xAD;&#xAD;</FONT></DIV>

With the traditional qemu tree fixed to not use PROT_WRITE anymore in the mmap() call for this region, and with the upstream qemu tree not being capable of handling passthrough, yet, there''s no need to treat Dom specially here anymore. This continues to leave unaddressed the case where PV guests map the MSI-X table page(s) before setting up the first MSI-X interrupt (see the original c/s

Anyone using the IBM x445 machine as a xen host? Mike _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

bgColor="ghostwhite" width="98%" bgColor="honeydew" bgColor="ghostwhite" - &Beta;a??&#x61;<FONT style="FONT-SIZE: 3px" size=1>&#xAD;</FONT>?<FONT style="FONT-SIZE: 1px" color=#fefcfc size=1>&#28;</FONT>&#x20;&#1080;&#x43D;<FONT style="FONT-SIZE: 1px"

Hello, I''m getting many "Error getting mfn" on a xen4.1.3 with dom0 3.4.11 x86_32. I thought it could be related to xen/mmu: Release just the MFN list, not MFN list and part of pagetables. http://git.kernel.org/?p=linux/kernel/git/konrad/xen.git;a=commit;h=785f62314984ea3af9dd830b020289ba2509ae69 (XEN) Freed 212kB init memory. (XEN) mm.c:908:d0 Error getting mfn 2009b (pfn

Hi Peter, Removal of VMI(VMware's para-virtualization technique) is scheduled for 2.6.37, I was wondering what would be the right time frame for submitting a patch which does that. Does the x86-tip tree have any next branch where we can park this patch ? Below is the patch for your reference which just removes VMI specific bits, applies on top of x86-tip. There is also an opportunity to

Hi Peter, Removal of VMI(VMware's para-virtualization technique) is scheduled for 2.6.37, I was wondering what would be the right time frame for submitting a patch which does that. Does the x86-tip tree have any next branch where we can park this patch ? Below is the patch for your reference which just removes VMI specific bits, applies on top of x86-tip. There is also an opportunity to

Hi, i have big trouble with a Debian Lenny dom0 and latest kernel 2.6.32.19 with xen-4.0.1rc5. Due some reason the system freezes from time to time. I used kernel 2.6.31.9 with xen-3.4.2 before. The machine doesn''t write anything to serial console so there are no errors or something like that. Perhaps there is something to see from the logs ... Hardware Board: Intel DQ45CB CPU: