similar to: Fwd: Re: Problems running Debian as Guest System on SLES10 Dom0

---------- Forwarded Message ---------- Subject: Re: [Xen-users] Xen 3.1, Fedora 8 and PCI passthrough Date: Sunday 24 February 2008 From: jim burns <jim_burn@bellsouth.net> To: deshantm@gmail.com On Friday 22 February 2008 09:34:17 pm Todd Deshane wrote: > The configuration in both python and SXP format is covered in the xen user > manual [0]. > > Fedora still does make a

I have installed Ubuntu Intrepid Server on bare metal and successfully ran:- # apt-get install ubuntu-xen-server.     It installed several packages on system . Now i can see files /boot/xen-3.3.gz, /etc/init.d/xend, /etc/init.d/xendomains, but no xenified kernel gets in. Attempt  to use vmlinuz-2.6.27-7-server, obviously , fails with system panic.    I do remember recompiling  procedure for Xen

Hi, I''m trying to build non sles10 domU under sles10 dom0. I''ve downloaded centos and debian images from www.jailtime.org fixed the config file and try to start domU. After creating domU from images I get Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) I''m running without problems two sles10 domU machines. After using google allot :-)

I am having issues with guest OSes running on SLES10 (Sun 4200) hosts. Periodically, the guest OS system drops off the network. From the general network it is not pingable, consequently, ssh fails. If however, I log into the SLES10 server that is hosting the guest OS and ssh to the guest OS, then it becomes immediately pingable and accessible to the rest of the network. Almost like the

Hi, After some hard trying to use lustre on our debian servers with an up2date kernel I decided to buy sles10 to make everything more comftable: I installed (rpm -i) the new kernelbinaries from 1.6.2/sles10-i686 to a sles10 test box (AMD64). When i try to install the modules form 1.6.2/sles10-i686 it says : sles2:/usr/src/lustre # rpm -i

Thank you Mark and Todd! (mark''s reply in a seperate email I did have the xen kernel installed, but wasn''t aware i needed to boot into that kernel manually at GRUB (which totally makes sense). This part was just missing from the instructions i was following. now it looks like it is working. Thanks again. /andrew On Sat, Apr 30, 2011 at 6:15 PM, Todd Deshane

I start sles10 use kernel-xen, but there''re not NIC eh0, and only have xenbr0, but the xenbr0 cannot get IP address via DHCP, (in normal sles10, the eth0 can get IP via DHCP), how can I connect to Internet in kerne-xen via xenbr0? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

I''ve just set up a small lustre installation on mixed SLES10 32-bit and SLES10 SP1 64-bit. 32-bit would give ksym errors upon installation of modules rpm, while 64-bit SP1 it was only warnings. I did a little research on the ksym package and it seemed to me it was only needed if you were trying to install a module compiled for a different kernel version. Since CFS is providing a

I''ve just uneventfully installed SLES10 as an HVM DomU (after finding out, the hard way, that OpenSUSE 10.3 won''t install on Intel VT). This almost went without a hitch, but I''ve been banging my head against a brick wall for a few hours trying to get VNC working. I can get a remote desktop, but a few seconds after I log in to the remote desktop, the screen goes

Hi, We have configured several xen guest OSes on a server running SLES10. The physical server is a Sun 4200 with 3 NICs installed, configured, and working. Each of the xen guest OSes have three virtual nics, configured for RAC, Interconnect, and public IPs as follows; eth0 - public (routable and registered in DNS) eth1 - private (not routable, uses a seperate network subnet for

Hi, I thought about changing the RPM package the guys of Redhat created, because I wanted an Init Script for SLES10 built-in. I started documenting the steps I took. Maybe it''s useful for someone else, although in German.. but the basic steps should be useable. My little Installating puppet Howto: http://wiki.njh.eu/Konfigurationsmanagement#Installation_3 The Init Script for SLES10:

Hi, in SLES10 YaST insists in "xorg-x11" being installed, even if the display is redirected to a remote host. So I thought: Can''t I do it simpler? I''m still new to XEN, but I started like this: mount the SLES10 DVD to /mnt, and use this configuration file: ----- disk = [ ''phy:/dev/system/as1,hda,w'', ''phy:/dev/hda,hdb,r'' ] memory

---------- Forwarded Message ---------- Subject: UNS: Re: [Xen-users] Re: [Xen-devel] windows pv drivers released at www.halsign.com Date: Saturday 16 February 2008 From: jim burns <jim_burn@bellsouth.net> To: jim burns <jim_burn@bellsouth.net> On Saturday 16 February 2008 07:05:55 am you wrote: > Checking the install instructions: ( >

Original Dom0 setup had been done per Todd Deshane''s instruction:- http://deshantm.livejournal.com/29959.html Functionality of SNV89 PV and HVM DomUs tested fine as well as F8 and WinXP HVM guests. Once again, all done as advised at http://deshantm.livejournal.com/29959.html Next i attempted to follow :- https://help.ubuntu.com/8.04/serverguide/C/libvirt.html #

Thanks for the reply. Sorry I didn't provide more details, but, yes, these are HVM domains. I use PV domains whenever possible, but in the case of Windows XP, that isn't possible, so I have to use HVM. I haven't tried suspending to OCFS2 with a PV domain, but I may give that a shot. Still, I think it's strange that it works perfectly fine to my ext3 and reiser filesystems, but

After recent Samba updates to one of our SLES10 SP1 systems users who open and save Excel 2007 files end up with the Read-only attribute set on the file. I had this same problem with the 3.0.28 update and the only solution I found was to roll back to the previous version. My understanding was that 3.0.32 should fix this. Did I miss something? Are there smb.conf changes that need to be made

We are trying to install a 32-bit SLES9-SP4 paravirtual machine on a 64-bit SLES10-SP1 Dom0 host from scratch. We have two problems: 1. The YaST2 VM creation tool fails to create a vm if a network card is selected. 2. The initial vm boots from the SLES9-SP4 iso file, but then complains it can''t find the installation source. Here is the /etc/xen/vm/file (after manually editing for a

Hi,All, how can I install suse sles10 as para Dom-U on RHEL5, I have update xen to 3.2. In python-virtinst readme,there is only support Fedora/Red Hat Enterprise Linux. README of python-virtinst: virtinst is a module to help in starting installations of Fedora/Red Hat Enterprise Linux related distributions inside of virtual machines. It supports both paravirt guests (for which only FC and

Hello friends! In this week, i had a problem with Xen version 3.0.2_09749-0.7 on SLES10 for x86, when the initrd-xen file was loaded. On console, various messages about "No space left on device" appears later that the "/dev" was monted on a tmpfs filesystem (for udev). The only sollution for this problem at that moment, was remove the "dom0_mem=192M" and the

Hello, my apologies for not being sure whom to tell this problem, but it is very strange. Let me tell the story: I''m using XEN (3.0.2) with SLES10 (x86_64, SunFire X4100). On one machine I have three virtual machines ("DomU") that are very identically configured (SLES10 x86_64 also). There is also a SLES9 (i386) acting as a multi-homed NFS server. I can mount and access a