similar to: upgrading from 3.0.1 to 3.0.2

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

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)

hi, i''m having here the problem with bonding and crcchecksum. So as i read the mailing list the solution is to run ethtool -K eth0 tx off inside domU. So my domU is reachable. All is fine. But after i migrate (live) the domU to another machine the complete domU stopped. Und I also had one time this ugly Zombie thing in xm list and couldn''t reboot the machine (only power

Hello! This morning I tried to upgrade Samba from 3.0.1 to 3.0.2 final on our 3 servers and users were not able to login. All servers run RedHat 7.3, we use LDAP as backend. Two servers work as PDC (each in different VLAN), one server is BDC. I had only few minutes to test it from Windows XP clients (we use Windows 98, 2000 and XP clients in our company) because we have hundreds of users

Hello, I want to implement a diskless xen hypervisor. The way I suppose it will work is xen booted over pxe and getting iscsi san storage to store vm images. Is solution like that usable ? _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi! We are using Samba 3 in SuSE-linux 8.2 with ldap. After upgrading from 3.0.1 to 3.0.2 we got following problem: When users log-in homes-share is not allways reachable, so automatic homedrive-mapping and roaming profiles doesn't work. This doesn't happen everytime, but quite often. And after login users can map their homedrives manually. Users have following attributes in LDAP

Hello! I have problems with installation of Xen 3.1 in OpenSUSE 10.2. I have unpacked the xen 3.1 tarball and installed software using #sh ./install.sh Then I have modified /boot/grub/menu.lst and now it looks like: title openSUSE 10.2 root(hd0,2) kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda3 vga=0x314 resume=/dev/sda2 initrd /boot/initrd-2.6.18.2-34-default title

Hi, I noticed some issues with the ssh transport mode where the virt-v2v would fail because of issue with libssh2. I see a lot of following errors before the conversion terminates: > commandrvf: /usr/sbin/update-initramfs -v -c -k 4.9.0-4-amd64 > read failed: would block (libssh2 error code: -37, sftp error code: 0) > /usr/sbin/mkinitramfs: 265: /usr/sbin/mkinitramfs: dirname: Exec

Oye 3 days on this now, my head hurts. I have spent what seems like 40 hours in the last 3 or 4 days reading, and I realize xen is in the middle of this transition of getting into mainline kernel, issues with dom0 etc etc. Ok, so i have come across a few howtos/tutorials on installing xen dom0 kernel, using git to download a patched? kernel tree, and getting xen source from mercurial. Below is my

I have released rsync 3.0.2. This is a security release to fix a potential buffer overflow in the extended attribute support. For more details, see the rsync security advisory page: http://rsync.samba.org/security.html There is a patch there that can be applied to 2.6.9 (if you were using the xattrs.patch), 3.0.0, or 3.0.1. Those running a writable rsync daemon can opt to refuse the

I have released rsync 3.0.2. This is a security release to fix a potential buffer overflow in the extended attribute support. For more details, see the rsync security advisory page: http://rsync.samba.org/security.html There is a patch there that can be applied to 2.6.9 (if you were using the xattrs.patch), 3.0.0, or 3.0.1. Those running a writable rsync daemon can opt to refuse the

Hello, attached is a little guide (in mediawiki notation) how to cleanly install xen 3.1.0 on debian etch amd64. Suggestions welcome! Regards, Bjoern _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

i just ran install.sh from the xen 3.0.2 pre-built distribution. in /boot it put vmlinuz-2.6.16-xen vmlinuz-2.6-xen -> vmlinuz-2.6.16-xen what happened to the xen0 and xenU kernels? also in /boot from xen 3.0.1 is vmlinuz-2.6-xen0 -> vmlinuz-2.6.12.6-xen0 vmlinuz-2.6-xenU -> vmlinuz-2.6.12.6-xenU which is what i expected from xen 3.0.2. don

I am having problems with the configuration of samba 3.0.1 on a Solaris 2.6 box. This box has no previous samba versions installed. When I try to configure samba I get the following error. # cd samba-3.0.1/source #./configure -with-ads 2>&1 |tree config.new.log fails with the following error:- checking for LDAP support... auto checking ldap.h usability... no checking ldap.h

Hi. I am trying to make initrd for xen0 but I am not successful. I receive error: #yaird error: Could not read output for /sbin/modprobe -v -n --show-depends --set-version 2.6.16.33-xen0 evdev (fatal). If I do that just for xen kernel (not xen0) it goes without any problem. I guest I have to use initrd for xen0 otherwise it does not want to boot. Similarly, xen kernel without initrd will not

OK, I have just pushed out klibc-0.130; it significantly updates the run-init program (again... PLEASE TEST IN A SAFE ENVIRONMENT) based on, but not identical to, Alexander's suggestions; it also adds s390/x patches from Arnd Bergmann. -hpa

Hi All, I am not able to boot Xen . My "/boot/grub/menu.lst" has this entry title Xen 3.3.2-rc5 / Debian GNU/Linux, kernel 2.6.18.8-xen root (hd0,0) kernel /boot/xen-3.3.2-rc5.gz module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro console=tty0 module /boot/initrd.img-2.6.18.8-xen savedefault I am getting following error : ERROR

Hi All, I am not able to boot Xen . My "/boot/grub/menu.lst" has this entry title Xen 3.3.2-rc5 / Debian GNU/Linux, kernel 2.6.18.8-xen root (hd0,0) kernel /boot/xen-3.3.2-rc5.gz module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro console=tty0 module /boot/initrd.img-2.6.18.8-xen savedefault I am getting following error : ERROR

Hi All, I am not able to boot Xen . My "/boot/grub/menu.lst" has this entry title Xen 3.3.2-rc5 / Debian GNU/Linux, kernel 2.6.18.8-xen root (hd0,0) kernel /boot/xen-3.3.2-rc5.gz module /boot/vmlinuz-2.6.18.8-xen root=/dev/sda1 ro console=tty0 module /boot/initrd.img-2.6.18.8-xen savedefault I am getting following error : ERROR