similar to: Problem: IP-Config: Unable to set interface netmask (-22)

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

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

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

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

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,

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; -*- > >

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)

Hi, Running lastest Xen dev (3.0) supplied by Fedorea C4, I get this same problem as already reported but whatever information I''ve found on this list is not working: Starting udev: [FAILED] Any new hints on how to fix it? Regards, -- xm create -c vsi Using config file "/etc/xen/vsi". Started domain vsi, console on port 9604 ************ REMOTE CONSOLE: CTRL-] TO QUIT

After upgrading to a recent snapshot (6831) I am unable to boot a guest - I get the following messages when booting the guest domain: Xen_blk: Initialising virtual block device driver Xen_blk: Timeout connecting to device! ... VFS: Cannot open root device "sda1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount

Does anyone know how anaconda partitioning enumerates disk partitions when specified in kickstart? I quickly browsed through the anaconda installer source on github but didn't see the relevant bits. I'm using the centOS 6.10 anaconda installer. Somehow I am ending up with my swap partition on sda1, /boot on sda2, and root on sda3. for $REASONS I want /boot to be the partition #1 (sda1)

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.

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

Processing commands for control at bugs.debian.org: > # reassigning all open bugs reported against versioned xen packages that are no longer in the archive to src:xen > reassign 399073 src:xen 3.0.3-0-2 Bug #399073 [xen-hypervisor-3.0.3-1-i386] xen-hypervisor-3.0.3-1-i386: dom0 crashes with a domU that define more than 6 vdb Warning: Unknown package 'xen-hypervisor-3.0.3-1-i386' Bug

I was playing with suspending and resuming Xen domains. Suspend and restore seems to work. However, when I reconnected with ''xm console'', I got the following error message on screen. Should I be concerned? [root@ROUGE xen]# xm console FedoraCore2 ************ REMOTE CONSOLE: CTRL-] TO QUIT ******** xen_blk: Unexpected blkif status disconnected in state connected blkfront:

Hi there guys. I''m trying to setup an Ubuntu 9.04 DomU, it boot fine, but does finishes to load completelly, this is what I get. I''m using xen 4 Linux netwarrior 2.6.31.13 #7 SMP Wed Jun 30 18:09:49 ART 2010 x86_64 AMD Athlon(tm) II X4 630 Processor AuthenticAMD GNU/Linu * Skip starting firewall: ufw (not enabled)... [ OK ] * Configuring network

On 08.02.19 15:08, James B. Byrne via CentOS wrote: > # ifconfig eth1:192008001 > eth1:192008001 Link encap:Ethernet HWaddr 00:25:90:61:74:C1 > inet addr:192.168.8.1 Bcast:192.168.8.255 > Mask:255.255.255.128 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > Interrupt:17 Memory:feae0000-feb00000 > > Which shows that the network mask is

When xen_emul_unplug=never is specified on kernel command line reading files from /sys/hypervisor is broken (returns -EBUSY). It is caused by xen_bus dependency on platform_pci and platform_pci isn''t initialized when xen_emul_unplug=never is specified. Fix it by allowing platform_pcii to ignore xen_emul_unplug=never, and do not intialize xen_[blk|net]front instead. Signed-off-by: Igor