search for: hochholdinger

Hi, for a RTlinux application I need to install a 2.4.0 kernel. prevoisly, my kernel 2.4.10 was supporting the ext3 fs and all my fs were under ext3. as 2.4.0 doesn't support ext3 I've got a problem to boot cause /proc is recognise as a ext3 fs and my kernel doesnt know how to mount it. what can I do and how to change back /proc to an ext2 fs thanks Fred

Hi, i''m prepering to upgrade my servers from xen 3.0.3 32-bit to 3.2.1 64-bit. The old system: Debian 4.0 i386 with included hypervisor 3.0.3 (pae) and dom0 kernel. The new systen: Debian lenny amd64 with the included hypervisor 3.2.1 and dom0 kernel from Debian 4.0 amd64. My domUs have a self compiled kernel out of the dom0 kernel of the old system (mainly the dom0 kernel but

We have a Xen 3.0 / Linux kernel 2.6.15 machine with the domU''s configured for shared /home directories. One of the domU''s is an NFS server, exporting /home, and the other domU''s all mount this. It all functions fine, but it''s pretty slow. I tried untarring a recent Linux kernel tarball. On the NFS server domU this takes about 25 seconds. I didn''t

...ap the entry for this host is ypmatch -k hosts-ids netgroup hosts-ids (horch,,fzi) Since every other service using NIS runs fine, I think the problem lies on samba, (possibly I have to set any flag so that samba tries to lookup the short host-name, but I have found none) Gruss Ulli -- \ Ulli Hochholdinger E-Mail: hochhold@fzi.de \ / ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ / \ Sometimes I think the surest sign that intelligent life exists elsewhere \ / in the universe is that none of it has tried to contact us. (Calvin) /

Hi, I think the API Reference for libvirt disappeared from libvirt.org: browsing to http://libvirt.org/html/libvirt-libvirt.html delivers no content. The content is still available via google cache http://webcache.googleusercontent.com/search?q=cache:libvirt.org/html/libvirt-libvirt.html So, is this removed on purpose? Or is this some bluff from my browser (but I checked this from different

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

I''m running xen on SLES10SP2. It''s been much more stable than SP1, but I still occasionally have issues. For example, one of my servers (8 CPU/32GB RAM) has five sles pv domUs and five fully virtualized windows 2k3 domUs. It had been up for almost 60 days. Yesterday afternoon one of the sles domU''s stopped responding. I went to check on it and I couldn''t using

...boot-stage. For debugging purpose I logged Kernel-Dump with minicom over Serial Console: System is: Dell Poweredge R710 2x Intel XEON X5650 96GB RAM Perc H200 SAS Controller 3x SAS-Drive I see a possible conjunction with Bug #600241 but acpi=off doesn't solve this problem. Regards, Ulli Hochholdinger Hier comes the Dump: (XEN) Xen version 4.0.1 (Debian 4.0.1-1) (waldi at debian.org) (gcc version 4.4.5 20100824 (prerelease) (Debian 4.4.4-11) ) Fri Sep 3 15:38:12 UTC 2010 (XEN) Console output is synchronous. (XEN) Bootloader: GRUB 1.98+20100804-7 (XEN) Command line: placeholder dom0_mem=512M l...

hi, first of all, you guys make great work to use xen under debian. I use etch to set up a xen server for later production use and so i try to use as much debian packages without manual adaptations to later use security updates when etch is released. As i have a machine with 16G of ram i need the pae versions of the hypervisor and the linux kernel. But there is only the pae version of the

Hi, you have to limit dom0 memory on two places, xen hypervisor option and xend config. In this example below I limit memory to 256MB: /boot/grub/menu.lst 87c87 < # xenhopt= --- > # xenhopt=dom0_mem=256M /etc/xen/xend-config.sxp 120c120 < (dom0-min-mem 196) --- > (dom0-min-mem 256) After changing /boot/grub/menu.lst you have to run update-grub and reboot the machine. After

Hi, have you tried to set dom0 memory to a fixed value? Perhaps the explanation in this bug could help: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414040 The message "Error: Device 5696 (vbd) could not be connected. Backend device not found." can occur if the device is (still) in use. I've found this sometimes if a domU was not normally shutdown. Possible solutions: + kill

Hello, I was also hit by this problem. Perhaps it is related to the xen-netback module in the dom0 kernel? Have a look at: http://www.gossamer-threads.com/lists/xen/devel/275548 -- greetings eMHa -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part. URL:

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

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-1 Severity: normal My 32Bit Dom0-crashes with error "Out of SW-IOMMU space for 65536 bytes" after doing moderate I/O on the local storage, which is a software-raid1 over 3 harddrives, connected to the builtin Perc H200 controller with ext3-fs. The error is reproduceable with "dd if=/dev/zero of=bigfile bs=1024 count=1000000"