similar to: xen_blk: Timeout connecting to device

Hi all, I tried to boot up a VM using two options (a) reading boot information from a config file (b) adding boot information directly to the command line. However, I got "IP-Config: Unable to set interface netmask (-22)" problem when using option (b). For (a), I don''t have such problem. The boot information for both (a) and (b) is same. Could you please let me know what I am

Running udev 070 on debian unstable. Looks like the hotplug stuff doesn''t work. I''ll see if I can use the suggested udev rules instead. Tim:> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

> Hi all, > I tried to boot up a VM using two options (a) reading boot > information from a config file (b) adding boot information > directly to the command line. However, I got "IP-Config: > Unable to set interface netmask (-22)" problem when using > option (b). For (a), I don''t have such problem. The boot > information for both (a) and (b) is same.

I cannot boot domU: # xm create inhouse Using config file "inhouse". Started domain inhouse # xm list Name ID Mem(MiB) CPU VCPUs State Time(s) Domain-0 0 123 0 1 r----- 27.4 inhouse 8 2048 0 1 ------ 11.4 # xm console inhouse Linux version 2.6.12.6-xenU ( root@xen1) (gcc version 4.0.2 20050901 (prerelease)

nic@wuwei:/usr/src/xen/xen-unstable.hg$ sudo xm create breezy -c Using config file "/etc/xen/breezy". Started domain breezy Linux version 2.6.12-xenU (nic@wuwei) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #3 SMP Thu Oct 13 14:56:20 NZDT 2005 kernel direct mapping tables upto 10000000 @ 568000-5ea000 Built 1 zonelists Kernel command line: root=/dev/sda1 ro 4 lockd.udpport=32768

This happens randomly, more often than not the next xm create will succeed. Don''t think kernel config is related as I use almost identical setup on my UP machine, but I use the work around for dev designations on all the vm configs. With that setup I get 100% success on creation of domU''s with changeset: 7353:29db5bded574, this changeset would not boot dom0 on the SMP machine.

hello. i just installed xen from source (using mke world then make install) booted into linux using the xen-2.0.7.gz kernel and then triewd to run ttylinux from the instructions in the user manual. i used this command. xm create /store/xmexample1 -c my xonfigfile ( xmexample1) is this. > # -*- mode: python; -*- > >

Hi. I spawned a thread last week about the failure of bridged networking and I have gotten a little further. Turns out that I _do_ have network connectivity from inside the domains, but I cannot get the network to come up when I boot. I have to login and start up the network manually. E.g. after installing Debian Sarge according to the debootstrap method outlined in the users manual, I created a

I am trying to get PV drivers running on both Centos 5.1 and Centos 5.3 HVMs, my DomU is Centos 5.2 with Xen 3.31. For 5.1 I install the kmod-xenpv RPM but for 5.3 the drivers seem to be built-in. For the network drivers to work I had to unload the Realtek NIC driver and renamed its .ko files to stop it loading. Adding the Xen-Vnif alias to modprobe.conf then got the PV NICs working nicely (Much

I tried today''s unstable on some IBM hardware and get this IRQ message at boot when xenU tries to probe the virtual block device: Xen virtual console successfully installed as tty1 Event-channel device installed. xen_blk: Initialising virtual block device driver Trying to free free IRQ261 vbd: probe of

I get the following warning when running xend start, and a similar warning sometimes when doing xm commands: /usr/lib/python/xen/xend/XendNode.py:26: RuntimeWarning: Python C API version mismatch for module xen.lowlevel.xc: This Python has API version 1012, module xen.lowlevel.xc has version 1011. import xen.lowlevel.xc /usr/lib/python/xen/xend/xenstore/xstransact.py:10: RuntimeWarning:

i saw a screen shot of knoppix beeing run under xen but for some reason i can''t do that. here if the config file i use. > kernel = "/boot/vmlinuz-2.6-xenU" > memory = 64 > name = "ttylinux" > nics = 1 > ip = "1.2.3.4" > disk = [''phy:hdc,hdd,r''] > root = "/dev/hdd ro" hdc is my cdrom and it was unmounted at

We''ve been noticing a lot of these errors when booting VMs since we moved to 3.0.3 - I''ve traced this to the hotplug scripts in Dom0 taking >10s to run to completion and specifically the vif-bridge script taking >=9s to plug the vif into the s/w bridge on occasion - was wondering if anyone has any insight into why it might take this long. I added some instrumentation to

Hi, i have seen a post with the same title, but didn''t help a lot -it mentioned, that the image was for LVM, which i don''t think is my case. I downloaded the debian31 image from http://jailtime.org. Initially, i had some problems and changed the configuration file a little. Here it is now: ----------- kernel = "/boot/vmlinuz-2.6-xenU" memory = 256 name =

Running on a up-to-date CentOS 5.6 x86_64 machine: [heller at ravel ~]$ uname -a Linux ravel.60villagedrive 2.6.18-238.19.1.el5 #1 SMP Fri Jul 15 07:31:24 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux with a TYAN Computer Corp S4881 motherboard, which has a nVidia 4 channel SATA controller. It also has a Marvell Technology Group Ltd. 88SX7042 PCI-e 4-port SATA-II (rev 02). This machine has a 120G

Hi, I have got xen compiled and installed properly.Domain 0 is created on the Xen port of Linux-2.6.11.10.But I am unable to boot the host domains. This is what one of my XenU config file contains [root@xion /]# cat /etc/xen/ttylinux kernel = "/boot/vmlinuz-2.6.11.10-xenU" memory = 64 name = "ttylinux" nics = 1 vif = [ ''mac=bb:00:00:00:00:11,

Hi, I''m trying to run Xen 3.0 on my amd64 UP machine. So far xen0 is working fine but there is a problem with mounting rootfs on xenU kernel. Is there something else that needs to be compiled into xenU 3.0 kernel? $ grep XEN kernel-xenU-x86_64-3.0.config CONFIG_XEN=y CONFIG_ARCH_XEN=y # XEN # CONFIG_XEN_PRIVILEGED_GUEST is not set # CONFIG_XEN_PHYSDEV_ACCESS is not set

Instead of using part_to_dev to find such devices we open the device's directory under /sys/block/<dev_name> and look for entries starting with <dev_name>, eg. /sys/block/sda/sda1. --- daemon/listfs.ml | 41 ++++++++++++++++++++++------------------- 1 file changed, 22 insertions(+), 19 deletions(-) diff --git a/daemon/listfs.ml b/daemon/listfs.ml index 56ebadeda..eced55bce 100644

Instead of using part_to_dev to find such devices we open the device's directory under /sys/block/<device> and look for entries starting with <device>, eg. /sys/block/sda/sda1. --- daemon/listfs.ml | 40 +++++++++++++++++++++------------------- 1 file changed, 21 insertions(+), 19 deletions(-) diff --git a/daemon/listfs.ml b/daemon/listfs.ml index 56ebadeda..55ace8e9c 100644 ---

Dear All, I now have my Dom0 working nicely running Ubuntu Jaunty. I am now trying to boot Images I had been using without problem under my previous Xen installation (Gentoo). For the Dom0 host kernel I am using the debian package linux-image-2.6.26-2-xen-686_2.6.26-15_i386.deb. The DomU kernel is one I compiled myself a while ago (sometime last year and has always worked on Gentoo and I think