similar to: How can I connect to Internet in sles10-xen

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 some problem setup networking on a opensuse 10.3, x86_64, xen 3.1.0. I have four suse 10.3, x86_64 PVM hosts running on it, they are connected via a bridge to get network. I can connect from external hosts, to the virtual machine, and from the virtual machines to the internet, no problem. But I cannot reach the dom0 from within the domU''s or vice versa. Also the domU''s

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

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, 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,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

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, 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

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

Hi, we are using a SLES10 Patchlevel 3 with 12 Nodes hosting tomcat application servers. The cluster was running some time (about 200 days) without problems. Recently we needed to shutdown the cluster for maintenance and experianced very long times for the umount of the filesystem. It took something like 45 minutes each node and filesystem (12 x 45 minutes shutdown time). As a result the planned

Hi, I''ve set up identical (what I think) machines using SLES 10 x86_64, but a new one of those is saying frequently in /var/log/messages: kernel: bond0: received packet with own address as source address A short summary of ifconfig looks like this: bond0 Link encap:Ethernet HWaddr 00:14:4F:2A:12:9C inet addr:132.199.176.78 Bcast:132.199.255.255 Mask:255.255.0.0 eth0

My head hurts from trying to figure this out for the past several hours . . . I want to determine what provider to use based on a fact (thanks for the suse version fact btw) but I ain''t gettin it: What''s wrong? Am I going down the completely wrong path? Is there a better way? # suse-yum.pp case $suse_repo_name { #sled10-i586: {Package{ provider => rug}} sled10-i586:

Hi, I''m running SLES10 SP1 with xen 3.0.4 and windows 2003 server as guest. Is it possible to assign ips from different networks to Dom0 and Guest, e. g. 172.27.10.1/24 for Dom0 and 172.27.15.1/24 for Guest? I tried it, but I can''t reach the Guest. If it''s possible, what should I have to configure? Thanks! Nicole _______________________________________________

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

Hi, I have a problem with augeas, puppet and Suse 10 SP2. Augeas works when I use the augtool to edit files. But I would like to use it in combination with puppet. My class looks something like this: augeas {"sysctl.conf": provider => "augeas", context => "/files/etc/sysctl.conf", changes => [ "set

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

Hi folks, I''ve been trying to work out this situation for a few days now without much success and dug all over the archives for similar issues, none of which seem to relate exactly. I installed Debian Etch and the Xen (3.03) kernels / binaries on a Dell server. It works fantastic with all the default configurations with one strange flaw - as soon as the /etc/xen/scripts/network-bridge

My very first xen DomU can not ping anything on my network. Well that is not entirely true, it can ping itself. I did not touch any of the scripts in /etc/xen so xen should be using bridging. My pc is running xen-unstable and uses a 3Com PCI 3c905B Just after the ''xen start'' on Dom0 brctl shows: bash-3.00# brctl show xenbr0 bridge name bridge id STP