similar to: Q: HOWTO manually boot SLES10 installation

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

Xen Host Server OS: SLES10 Kernel: 2.6.16.21-0.8-xen x86_64 Hardware: Sun 4200 Memory: 12Gb Guest Domains (2 total) RHEL4-U3 2.6.16-xen x86_64 2Gb Swap 4Gb RAM 2 Nics bridged to seperate physical Nics (Public and Private) Systems come up normal and we are able to mount filer space to the guest domains and do work. However, at some point, the guest

> Hello Everyone, > > Since rebooting my Centos 6.10 Openvz server "daisy" yesterday, I am > getting horrible system performance.? /var/log/messages is full of > HDIO_GET_IDENTITY failed for /dev/sdb.? The latest entries look like this: > > Apr 22 08:51:32 daisy kernel: [141224.655699] CT: 1005: stopped > Apr 22 08:55:04 daisy ata_id[21513]: HDIO_GET_IDENTITY

Correct, 3ware 9670SE SATA-II Raid PCIe [root at daisy dev]# lspci 00:00.0 Memory controller: NVIDIA Corporation CK804 Memory Controller (rev a3) 00:01.0 ISA bridge: NVIDIA Corporation CK804 ISA Bridge (rev a3) 00:01.1 SMBus: NVIDIA Corporation CK804 SMBus (rev a2) 00:02.0 USB controller: NVIDIA Corporation CK804 USB Controller (rev a2) 00:02.1 USB controller: NVIDIA Corporation CK804 USB

>> Hello Everyone, >> >> Since rebooting my Centos 6.10 Openvz server "daisy" yesterday, I am >> getting horrible system performance.? /var/log/messages is full of >> HDIO_GET_IDENTITY failed for /dev/sdb.? The latest entries look like >> this: >> >> Apr 22 08:51:32 daisy kernel: [141224.655699] CT: 1005: stopped >> Apr 22 08:55:04

Hello Everyone, Since rebooting my Centos 6.10 Openvz server "daisy" yesterday, I am getting horrible system performance.? /var/log/messages is full of HDIO_GET_IDENTITY failed for /dev/sdb.? The latest entries look like this: Apr 22 08:51:32 daisy kernel: [141224.655699] CT: 1005: stopped Apr 22 08:55:04 daisy ata_id[21513]: HDIO_GET_IDENTITY failed for '/dev/sdb' Apr 22

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, how can I install a openSuSE 10.3 PV-guest on a LVM-drive of a openSuSE 10.3 host with Xen 3.10? On 10.2 with Xen 3.0.3 the openSuSE-YaST-module for managing VMs could install the system also on block-devices, unfortunately this is not possible anymore with OSS 10.3 :-( What I have tried: - I created two LVM-partitions, one for "/" one for swap. - Installing an OSS 10.2 PV-guest

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 :-)

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

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

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 I have been using pygrub for most of the needs. Was trying out some stuff on SLES 10 SP1. It seems that it does not have pygrub!! On the other hand,they have domUloader.py which requires bootargs="--entry=hda:/boot/vmlinuz...., path to ramdisk. It is quite strange to be asking for the path of the kernel and the ramdisk to be supplied in the conf file!!. Am I missing something

Hi I have been using pygrub for most of the needs. Was trying out some stuff on SLES 10 SP1. It seems that it does not have pygrub!! On the other hand,they have domUloader.py which requires bootargs="--entry=hda:/boot/vmlinuz...., path to ramdisk. It is quite strange to be asking for the path of the kernel and the ramdisk to be supplied in the conf file!!. Am I missing something

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

---------- Forwarded Message ---------- Subject: Re: [Xen-users] Problems running Debian as Guest System on SLES10 Dom0 Date: Tuesday 29 January 2008 From: jim burns <jim_burn@bellsouth.net> To: deshantm@gmail.com On Tuesday 29 January 2008 11:21:09 am Todd Deshane wrote: > Why doesn''t sles 10 have pygrub? pygrub comes with Xen. Old problem that was covered in this list a

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