similar to: Xen and LVM snapshots on FC4

Hi i''m trying to run Xen on my amd64. Installed is Debian 3.1 sarge i386 and Xen 2.0.7, my whole enviroment is 32 bit. When i''m running a xenU domain and use /var/xen/samba as a ext2 fs file ( file:/var/xen/samba,hda1,w ) everything goes according to plan. If i use my LVM partition ( phy:/dev/xen/samba-ha,hda1,w ) it gives during boot: -------- ... NET:

Hi all, it is possible create a 32 bits xen guest in a 64 bits xen server? I need get guest running with DirectAdmin (32 bits) and the problem is: if i use a 64 bits kernel for the guest, the Directadmin instalation fails because the 64 bits arch , if i create the guest with a 32 kernel it fails on boot: XENBUS: Device with no driver: device/vkbd/0 XENBUS: Device with no driver:

Hello, we''re using several test- and development-servers as virtual Xen-machines running on one host. Unfortunately our main application needs much memory. Its not a problem at a first view, because usually only very few instances are running at the same time. But if I understand Xen correctly, its only possible to distribute the physical memory of the machine, not the whole

Howdy folks, I''m trying to boot Xen 3.0 on a Centos 4(.2) system with root on a software raid1 volume. When booting the Xen kernel, ''raidautorun'' in the /init nash script fails to assemble either the root md or the raid5 md containing my LVM volumes. If I move root to /dev/hda1, the system boots fine. raidautorun still fails to assemble the md devices, but mdadm

Any help about this error on domU ? request_module: runaway loop modprobe net-pf-16-proto-9 request_module: runaway loop modprobe net-pf-16-proto-9 request_module: runaway loop modprobe net-pf-16-proto-9 request_module: runaway loop modprobe net-pf-16-proto-9 request_module: runaway loop modprobe net-pf-16-proto-9 I am using xen_changeset : Sat Apr 1 14:59:12 2006 +0100

Any help about this error on domU ? request_module: runaway loop modprobe net-pf-16-proto-9 request_module: runaway loop modprobe net-pf-16-proto-9 request_module: runaway loop modprobe net-pf-16-proto-9 request_module: runaway loop modprobe net-pf-16-proto-9 request_module: runaway loop modprobe net-pf-16-proto-9 I am using xen_changeset : Sat Apr 1 14:59:12 2006 +0100

Hi *, when I try to start this config kernel = "/boot/vmlinuz-2.6.11-xenU" memory = 128 name = "Virtual1" vif = [ ''mac=aa:00:00:00:00:11, bridge=xen-br0'' ] disk = [ ''phy:vg00/domu01_lv,sda1,w'' ] root = "/dev/sda1 ro" extra = "4" I get this errors in xend.log (tried two times): [2005-05-23 13:37:22 xend] INFO

There would seem to be a potential deadlock in the netfront accelerator plugin support. When the configured accelerator changes in xenstore, netfront tries to load the new plugin using request_module(). It does this from a workqueue work item. request_module() will invoke modprobe which in some circumstances (I''m not sure exactly what - I''ve not managed to reproduce it myself)

Moi! I upgraded Xen-2.0.1 to Xen-2.0.5 (testing) and everything compiled cleanly. I''m still able to boot dom0 and start domUs but networking doesn''t work anymore. xen-br0 appears in dom0, but vif-interfaces now only when ifconfig -a is used. Interface appears in domU and all seems to be fine, except no any data doesn''t move in any direction. I can''t even ping

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I''m running htb on an 2.4.20 with the linux-2.4.20-ptrace.patch and now the messages in my syslog changed. specially, what is net-pf-14? I didn''t change anything else, just applied the patch and installed the kernel Mar 20 15:33:54 stovokor kernel: HTB: quantum of class 10001 is big. Consider r2q change.<4>HTB: quantum

This adds basic support for driving sensor chips off the nvidia i2c buses, along with basic support for reading the internal GPU sensor on supported chipsets. It's heavily cribbed off nvclock. Having scanned a large number of bioses, I'm pretty convinced that the appropriate i2c bus is always number 2 in the list on <g80 - I'm not sure about later cards yet. There's still a lot

i have patched the kernel and recompiled the kernel with the ext3 support, however, when i boot up, i get this error below, what have i missed ? request_module[block-major-3]: Root fs not mounted VFS: Cannot open root device "hda6" or 03:06 Please append a correct "root=" boot option Kernel panic: VFS: Unable to mount root fs on 03:06

Hi everyone, I got the error: NET4: Unix domain sockets 1.0/smp for linux NET4.0 ds: no socket drivers loaded request_module[block-major-8]: root fs not mounted VFS: Cannot open root device ""or 08:03 Please append a correct "root"boot option The strange thing is that it tries to mount from harddisk. This I got somewhere else: "the kernel looks like it is trying to

Hi, I''d like to test the stability of live migration during heavy load of domU. scenario: - both dom0s and domU are running on Debian Sarge. - script on dom0 triggers live-migration to the other dom0 - domU is running I/O tests, e.g. bonnie++ - domUs root- (ext3) and swap fs is stored on two partitions in a san - san is connected using fibre channel cards to both dom0s - san in dom0

All, When starting guest domain (installed with "yum -c ...Base"), I''m getting this error 5 times and then my guest domain always hung: "request_module: runaway loop modeprobe net-pf-1" Anyone seen this before? Thanks, Dicson _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Move away from the deprecated API and return the shiny new ERRPTR where useful. Signed-off-by: Wolfram Sang <wsa+renesas at sang-engineering.com> --- drivers/gpu/drm/nouveau/nvkm/subdev/therm/ic.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nvkm/subdev/therm/ic.c b/drivers/gpu/drm/nouveau/nvkm/subdev/therm/ic.c index

I have setup Centos-3.1 on a Dell Optiplex GX1 this week. It has to replace an old Compaq Deskpro I used as a firewall/router running the no longer supported RedHat 7.1. I have the NAT firewall up and running, and it works OK. However, there is one thing bugging me. I cannot use any client software that queries a nameserver. I tried to use "dig", "host" and

I'm currently using the latest stable release and that computer does not have an internet connection so I can't use the update manager/s and have to rely on a windows machine. I know I can download wine over at http://www.winehq.org/site/download however trying to install the *.deb file coughs up a dependency issue. something about binfmt-support. and to be clear, I am doing a bit of

I have just build an arm chroot and I imagine others might be interested on how to do it. First you need to install qemu. Follow the instructions on http://wiki.debian.org/QemuUserEmulation. I had some problems compiling for x86_64, so I just edited qemu's configure to compile for i686. Now run debootstrap: debootstrap --foreign --arch arm sid your_chroot_dir http://ftp.debian.org/debian