search for: gordon_mcfadden

Hi, I''ve run linux off an on for several years. Recently I''ve been using windows (simply for ease), but have gotten so fed up with stability and what not. I had read good things about xen, so I installed suse and was hoping to not give up the 10% of things that I need windows for. I''ve still got windows on a partition and was wondering if I could boot that, but wanted

Hi I am pretty new to this, and this may be an easy one, but I have not found the answer in the docs. The kernels produced from a build seem to have the same name for both the dom0 and domU instances. I get one kernel named vmlnuz-2.16.6-xen Is this expected? Although the dom0 boots, I ma having a crappy time getting a virtualized OS to boot and am trying to see if this is the

I call this one the "Manager is watching" bug since it *only* happens during demonstrations. Really. I am not kidding. Caused me some, er, awkward moments not once, but twice. Actually, the reason may be more prosaic. Here is the situation. I am using FC4 on an EM64T host with the Xen mods - VT enabled. I have two VMs. VM1 is Win XP (32 bit), VM2 is RHEL4U1 (32 bits)

I am hoping I can get a little light she on a problem I am having trying to bring up a guest domain. I suspect that the problem is in my supplied file system First the environment. VT enabled dual core EM64T processor, Asus Mb (I can get the exact chipset infor if relevant) 2 Gig of DRAM SATA drives. I have build and booted the domain 0 using 3.0.2-2 version of xen. This seems ok.