similar to: Anyone able to NFS boot on xen 4.x ?

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:

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

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

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 Everyone, In order to prevent DomU from entering promiscuous mode, is it just a matter of adding these 2 rules when the vif is created? # Accept packets leaving the bridge going to the domU only if # the destination IP for that packet matches an authorized IPv4 # address for that domU. iptables -A FORWARD -m physdev --physdev-out vif1.0 \ --destination 216.146.46.43 -j ACCEPT

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

In a prior message I documented my woes in getting an NFS_ROOT xen going. I haven''t resolved those yet, want to try a different tack at this: If the group were to recommend a path of least resistance to showing migration/live migration, which configuration would it be? Joe. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

> 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 have been struggling through the task of moving our infrastructure over to Xen VMs. We were initially using Ubuntu packages for both dom0 and our domUs, but experienced extreme instability so we moved to CentOS, which has been much more reliable for dom0. Since we already had a bunch of Ubuntu VMs, we left them using the Ubuntu 2.4.24-19-xen kernel, but this has turned out to be

Hi Everyone, In my HVM guest''s config file, I have given my guest 3 interface. I have called them fw1, fw2 and fw3. I have joined each interface to a bridge on the Dom0. This does appear when I do a "brctl show". However, there are 3 other interfaces also added called tapx.0,tapx.1 and tapx.2 (Where x is the domain ID for the guest). Furthermore, I am only able to run

Hi, I am trying out Xen for the first time and I am having a few problems with getting it working. The computer is a quad core Intel Xeon with VT enabled, 8gb of RAM and 2 x 15,000rpm SAS drives in RAID1. I have installed CentOS 5 64bit and installed Xen 3.3.0 via yum. I have successfully booted in to dom0. Here is my grub.conf on dom0: > # grub.conf generated by anaconda > # > #

Hi All, Could anybody tell me the creating of pv domain on nas. I mean to say that root file sytem should be at nas location. Useful links will be most welcome. Thanks, Trilok _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hi, I have a same question posted by punamia , when I am trying to create domain using xen-2.0 built on Fedora 2/ Pentium PC with IDE drive: "Kernel panic: No init found. Try passing init= option to kernel". Below is console dump. Any suggestions ? Thanks Console Dump: Linux version 2.6.8.1-xenU (root@localhost.localdomain) (gcc version 3.3.3 20040412 (Red Hat Linux

Hi Everyone, Is there any way to restrict Disk usages per DomU? It would be to stop customers from hogging all the available disk time and slow everyone else down. Apperently, Cloudmin can do this, but that costs money... Any ideas would be appreciated Thanks _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com

Hi, I have an ASUS P6T Deluxe and I''m trying to use VT-d with Xen. I have also tried it with ESXi and Parallels Workstation Extreme - none of them work correctly. >From reading the xen-user and xen-devel list archives, I see that this motherboard has problems with malformed DMAR tables. Is there anything I can do to fix/workaround this or am I completely stuck? I did notice

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

Hello, While using xen 4.1-testing.hg (r23202) I noticed that the ''vifname'' config value is not handled by xl, but is handled by xm. Is there a workaround or patch for this? My firewall and scripts depend on static vifnames. XM works good - it adds multiple interfaces to multiple bridges and configures them appropriately. But with xl it differs -- here only tap devices are

Hello, While using xen 4.1-testing.hg (r23202) I noticed that the ''vifname'' config value is not handled by xl, but is handled by xm. Is there a workaround or patch for this? My firewall and scripts depend on static vifnames. XM works good - it adds multiple interfaces to multiple bridges and configures them appropriately. But with xl it differs -- here only tap devices are

Anybody else noticed this: debug: package provider yum: Executing ''/usr/bin/yum -d 0 -e 0 list available portmap'' err: //nfs_server/Package[portmap]: Failed to retrieve current state of resource: Could not get latest version: Execution of ''/usr/bin/ yum -d 0 -e 0 list availaSearching 100% | =========================| 16 kB 00:03 Error: No

Hi! DomUs can be backed up just fine, and there''s no problem to restore files as long as the DomU boots. Now I wonder how to recover hard (desaster recovery)... Backing up the disk images or partitions (from Dom0) seems to be not an option, because there are changes to them all the time, so incremental backups would always save them, and all saves would be inconsistent. Now the idea