similar to: bonding, ethtool and live migration

hi, i''ve a little problem here with raid1 inside domU. My setup is, two block devices (gnbd) attached to domU (sda1, sdb1) and build raid1 inside domU. All works fine (mdadm --remove, block-detach, resize, block-attach, mdadm -add) except the part where i want to grow my raid to the new size (mdadm --grow .. --size=max). Sometimes (when not much fs load is done in domU) it works and

QEMU needs CONFIG_TUN to enable networking. Signed-off-by: Edwin Zhai <edwin.zhai@intel.com> Signed-off-by: Arun Sharma <arun.sharma@intel.com> --- 1.56/linux-2.6.11-xen-sparse/arch/xen/configs/xen0_defconfig_x86_32 2005-04-13 15:38:59 -07:00 +++ edited/xen0_defconfig_x86_32 2005-05-02 13:18:14 -07:00 @@ -598,7 +598,7 @@ # CONFIG_DUMMY is not set # CONFIG_BONDING is not set #

It turns hard to make XEN 3.0 running on my middle-sized server. Now when XEN 3.0 is released I first successfully put it on several PCs and then decided to probe it on SMP and PAE enabled Dell PowerEdge 6800 server. And experienced intermittent hangs just after dom0 comes up. The [login:] prompt comes up and the server hangs completely for a while and in some 2-10 minutes releases just to let me

I am looking for a kernel boot option that specifies "nonetwork" I have found in searching the nousb - nopcmcia etc.... but I have not found one for nonetwork. Is there one and what is it called? Thanks, Jerry

I hope the CentOS people don't mind me cross-posting for their input. I've just done a clean, text-mode minimal WBEL4 install on an IBM Netfinity 4500, essentially the same hardware as an xSeries 340. The install went fine but now the box will boot, run through the initrd init sequence, perform its switchroot then hang here... SELinux: Initializing. SELinux: Starting in permissive mode

Author: ultrotter Date: 2006-02-19 18:38:10 +0000 (Sun, 19 Feb 2006) New Revision: 26 Added: trunk/debian/patches/30xenchangeset.dpatch Modified: trunk/debian/patches/00list trunk/debian/patches/10sysconfig.dpatch trunk/debian/rules Log: Add 10sysconfig.dpatch description Add 30xenchangeset.dpatch to make the xen changeset configurable Force the xen changeset to be the correct one

Hi I have a new ASUS A6Tc laptop with 1.6 GHz AMD Turion dual core processor. I get a strange error: <4>0000:00:0b.0 OHCI: BIOS handoff failed (BIOS bug ?) 000007b4 <4>0000:00:0b.1 EHCI: BIOS handoff failed (BIOS bug ?) 01010001 This only occurs when booting into the xen kernel, not without xen. Can someone tell me why and how it can be fixed? Art

Hi, I was noticing that our debian/rules did: ... debian/stamps/build: mkdir -p $(@D) rm -rf debian/install $(MAKE) all DESTDIR=$(CURDIR)/debian/install KERNELS= GCC=$(CC) CC=$(CC) HOSTCC=$(CC) touch $@ install: debian/stamps/build rm -rf debian/install $(MAKE) dist DESTDIR=$(CURDIR)/debian/install KERNELS= XEN_PYTHON_NATIVE_INSTALL=1 CC=$(CC)

Ok, here's what iam trying on,, a compaq proliant 8500 server with 8 xeon 550mhz processors, 6 gig ram,, i just installed centos 4.1 on a proliant 3000 dual 550's and 2 gig ram and went smooth as silk, just got the 8500 and it seems to be in good order, but when i tried (twice) to install centos 4.1 it stalls shortly after a screen of stuff installing and the last two items are something

I will install CentOS 4.3 and downloaded the driver disk from Dell for RedHat Enterprise Linux 4: Description: Dell PowerEdge RAID Controller 5 Device Driver for Red Hat Enterprise Linux 4.0, X86 & X86_64 I saw a few minutes ago that the driver disk is extracted within /tmp/ramfs/DD-01. Therfore I know that the network is working correct. I will try to extract the module and insmod/modprobe

Hi All, I''ve tried upgrading from 3.0.1 to 3.0.2 on a couple of test servers and had the same strange results on both... In both cases I had a running 3.0.1server, then downloaded the 3.0.2 source. Next, I extracted the files and executed "make XEN_TARGET_X86_PAE=y world". Upon completion I executed "dist/install.sh", changed the grub.conf and rebooted. Once the

Hi everyone, My email server is running CentOS 3 and I can't upgrade it to CentOS 4 using the CD's. At first I thought it was the old Megaraid card (that's no longer supported), so I replaced that with a new card. I've tried ISO's from CentOS 4, 4.1 and now 4.2 which I've tested and booted in other machines. Just not this one. I've never had a problem like this

Hi, I have a KVM host running ubuntu 18.04 with libguestfs-tools version 1.36.13-1ubuntu3.3 installed from the Ubuntu's repo and when I try to use virt-cat for example on a VM it fails with: libguestfs: error: appliance closed the connection unexpectedly. > libguestfs: error: guestfs_launch failed. After doing "export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1" and running the

Hi Raj, I also meet the same python problem when create VMX in FC3-x86_64 xen0. But python error doesn''t happen in RHEL4U1-x86_64 xen0. Are your two computers all SLES9? Thanks, Yongkang You(Kangkang) > >All. > >I am running Xen on an ES7000 system with 4 procs and 4 GB memory. >I am running Suse Sles-9 (32-bit) on the machine. > >I have compiled Xen (the tip on

I''m currently using the xen-3.0-testing.hg version with the XEN_TARGET_X86_PAE=y complied dom0/hypervisor. I have an HP dl585 with 28GB but the hypervisor boots and says "(XEN) WARNING: Only the first 16 GB of the physical memory map can be accessed...". Xentop shows 16GB. When I boot a RHEL4 2.6.9 hugemem kernel, I can see all 28GB. Any suggestions? Toby

Author: tha-guest Date: 2006-02-18 22:55:21 +0000 (Sat, 18 Feb 2006) New Revision: 24 Removed: trunk/debian/patches/30rename-pae-hypervisor.dpatch Log: Guido found a better way to have the pae hypervisor installed with another name without patching upstream and it seems to work as good as the patched upstream version, so I removed my patch from svn again. There seems to be no need to just

I have recently built a single-T1 Asterisk box using an HP DL120G6 with a Digium TE122 card. I was finding that I was getting missed interrupts on the TE122, causing the driver to report that it was increasing latency. It kept doing this until the T1 did not work reliably. I tried my usual procedure of disabling the USB subsystem in the BIOS (or so I thought), but I found that the USB drivers

I''m trying to start a number of lvm-backend domUs on a Dell Poweredge 2850 (i''ve got nousb on the grub command line, and no usb in the kernel). Some domUs are created and started successfully. However, quite a few of my domUs don''t start properly. I get the correct Started Domain messages... but then the domain doesn''t "go anywhere", meaning

Hello, I successfuly run Centos 5.1 domU in Centos 5.1 dom0. But I still have some minor issues/errors/warnings while booting I'd like to fix and here are my questions: 1. How to disable loading usb host controler module: [...from dmesg... ] Loading uhci-hcd.ko module USB Universal Host Controller Interface driver v3.0 insmod: error inserting '/lib/uhci-hcd.ko': -1 No such

Author: tha-guest Date: 2006-02-18 16:38:52 +0000 (Sat, 18 Feb 2006) New Revision: 19 Modified: trunk/debian/control trunk/debian/patches/00list trunk/debian/rules trunk/debian/xen-hypervisor-pae.install trunk/debian/xen-hypervisor.install Log: - changed debian/rules to build a pae hypervisor on i386 (has to be done after the "make dist" for the non-pae stuff) - changed