similar to: DomU boot from NFS server

Hello, I''ve installed a OpenSolaris dom0 snv_44 on a x4100 server, and booted a 32-bit xen kernel. I''m trying to create a OpenSolaris DOMU (snv_44) by following the howto described at http://www.opensolaris.org/os/community/xen/howto/create-osox-domu/. I did not manage to create a diskless environment by using SUNWCXall. I''ve created SUNWCreq instead and add the

Hi. trying to get a domU (dom1) up using nfs root. never done this before ;-). I have dom0 up (2.6.12-xen0) and i have an external nfs server with a nice root disk populated. i get this after xm create -c dom1 vmid=1 . . . IP-Config: Complete: device=eth0, addr=172.31.205.229, mask=255.255.255.0, gw=172.31.205.2, host=vm%d, domain=, nis-domain=(none),

Dear All: I am using Xen 3.3 on a Fedora 8 machine and failed to start a guest domain from an exported NFS directory. The step I follow is as follows NFS server: 192.168.1.1 NFS client: 192.168.1.201 1: I copy the guest.img, which can be corrected booted on NFS client to the NFS server. 2: On the NFS server mount guest.img /xen/guest; such that if I do a ls /xen/guest, I can see all the

> I have my disk file stored on a NFS server. > I have tried these two approaches: > > A) Mounting the NFS directory in RW mode on a local directory > and specifying in my config file the complete path of my disk file. > > xm create configFile returned with this error: > Error: Error creating domain: vbd: Segment not found: > uname=file:/MountPoint/diskfile

Hello. =) I''m having a bit of trouble with my nfs xen installation and have spent much time trying to research/figure out this problem with no luck, so I''m hoping someone might be able to help me here. =) I''ve successfully installed xen 3.02 on Linux RH4 on my Sun single proc opteron v20z server. I''ve installed what I believe to be a base Linux OS on a

I have been googling and searching the archive , haven''t got anything helpful. Would appreciate any help. Got the follow error when trying to start a domain using NFS root IP-Config: Incomplete network configuration information. Looking up port of RPC 100003/2 on 10.10.24.141 <http://10.10.24.141> RPC: sendmsg returned error 101 portmap: RPC call returned error 101 Root-NFS:

I have been trying to boot Xen guest (Fedora Core 6 - linux version 2.6.18) from NFS server but I kept encountering a problem despite using ramdisk or not. Key items in my config file are as follows: ================================================= kernel = "/root/Xen/xen-3.1.0-src/linux-2.6.18-xenU2/vmlinuz" # Optional ramdisk. # ramdisk = "/boot/initrd-2.6.18-xenU2.img"

Hi, I wanted to ask it on elli_dbergs''s thread ''problem with xm create'', but it seems that my message was never gonna be published (waited for 24 hours til i figured it was taking way too much time). So i''m working with Xen unstable, installed dom0 over Ubuntu 8.10, no problem so far apparently, reboot on Xen, then I go to /etc/xen to get some example config

I''m starting to go nuts I have tried this several ways and can''t get my doamin to boot up, I am using Fedora 5 as dom0 and trying to boot up ubuntu 5.10. I am using a file but my dom0 is using lvm and I am not in the ubuntu installation, here are my output of my domain file and error......I have edited the fstab on my ubuntu installation to match the domain file, any help would

Hello, I guess it possible distro specific issue but is it resolvable? I have one node(testing purpose) ganeti 2.0.1 cluster installed over Debian5 Lenny. Almost everything from distro repositories. Only ganeti 2.0.1 and ganeti-debootstrap are from sources. I have it successful run with vmlinuz-2.6.26-2-xen-686 and initrd.img-2.6.26-2-xen-686 from repositories. Both Dom0 and DomU are use the

Hi all, i've problem with mounting logical volumes over NFS. On NFS server, i have following logical volume [root at nfs_server ~]# lvdisplay --- Logical volume --- LV Name /dev/escience/vv_25 VGnfs_servernfs_servernfs_servernfs_servernfs_server escience LV UUID iMhNq7-iC7L-VTDO-Xcwv-a6yv-sEAD-EZWASV LV Write Access read/write LV Status

Hi, every one: I had problem creating domU on diskless device by using xen-unstable. Following, please find out details. BTW, the same configuration works fine on device with hard disk (1) Xen, dom0 kernel and dom0 root file system are loaded/mounted over via eth0 (2) DomU root file system is created in a file-backed virtual block device(VBD). The file-backed VBD locates at some directory on

Package: xen-utils-4.0 Version: 4.0.1-1 Severity: wishlist [resending from another address since my ISP seems to be queueing emails for up to 25 hours and counting...] I did some experiments with the xen remus HA system. With overlord3:~$ debdiff xen_4.0.1-1.dsc xen_4.0.1-1lindi1.dsc diff -Nru xen-4.0.1/debian/rules.real xen-4.0.1/debian/rules.real --- xen-4.0.1/debian/rules.real 2010-08-02

hi fellow XEN-users: I have been trying hard to get this problem fixed, hope I can get some help here. Thanks in advance for your time. I have a typical dom0 + domU XEN setup. after I start xend and network-bridge, I get the default network setup, , peth0 -------- bridge ------------------------------------------------------- |

Using the 2.0.6 demo cd image, I booted the supplied freebsd image and rsync''d the file system to an NFS server. However I don not seem to be able to succesfully boot from it the system just hangs here: xn0: bpf attached xn0: Ethernet address: aa:00:00:61:1c:d4 lo0: bpf I have modified /sbin/start_freebsd.sh and /etc/xen/freebsd.py to generate the following configuration: xendemo:~#

I recently started having this issue after enabling nat networking for my domU. The domU is booting the 2.6.32.27 kernel with an initrd i generated and was using before just fine. Output is as follows. Any help would be appreciated. Here is the output I get: 0.161289] xvde1: detected capacity change from 0 to 10486808576 > [ 0.260033] XENBUS: Device with no driver: device/console/0

Hi all, I have a question on /etc/inittab for DomU booted with xencons parameter. I saw the following error messages when I appended xencons=ttyS to DomU boot option. INIT: Id "1" respawning too fast: disabled for 5 minutes INIT: Id "2" respawning too fast: disabled for 5 minutes INIT: Id "4" respawning too fast: disabled for 5 minutes INIT: Id

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 trying to install a fai installation server in a DomU for DomUs, but i have some problems with nfs. The DomUs says, that they can''t reach the NFS Server =========== Begin: Retrying nfs mount ... IP-Config: eth0 hardware address 00:16:3e:7a:25:7c mtu 1500 DHCP IP-Config: eth0 guessed broadcast address 172.16.0.255 IP-Config: eth0 complete (from 172.16.0.151): address:

Package: xen-utils-4.0 Version: 4.0.1-1 Severity: wishlist I did some experiments with the xen remus HA system. With overlord3:~$ debdiff xen_4.0.1-1.dsc xen_4.0.1-1lindi1.dsc diff -Nru xen-4.0.1/debian/rules.real xen-4.0.1/debian/rules.real --- xen-4.0.1/debian/rules.real 2010-08-02 16:10:13.000000000 +0300 +++ xen-4.0.1/debian/rules.real 2011-01-05 00:32:41.000000000 +0200 @@ -159,6 +159,7 @@