similar to: Installing CentOS 5.1 as DomU

I have posted in http://vireso.blogspot.com my notes about installing Centos5 (from DVD image) into DomU on OpenSolaris Xen (xen-nv66-2007-06-24). Using OpenSolaris for Dom0 gives such advantage as zfs zvols for "phy" devices in DomUs, so zfs snapshot & zfs send gives you incredible fast and convenient full/incremental backup/restore of full DomUs.

Hello everyone! Well i want to know, if there is a way to specify a physical nic (like eth0 or eth1) to a domU and how can i do it. The server has two nics, what i want to do is assign physical nic (eth0) to the dom0 and assign physical nic (eht1) to the domU. I appreciate your help. Regards Ivan ____________________________________________________________________________________ Be a

Hi all, I am running Scientific Linux 5.1 (rhel 5.1 compatible) 64bit on a 2x4core system with 16 gb ram with 3 Scientific Linux 4.6 (rhel 4.6 compatible) guests an one Scientific Linux 5.1 guest. I do not run ntp on the guests but only on dom0. One specific Scientific Linux 4 domU always looses time synchronization with dom0. All the others SL4 and the SL5 domUs remain synchronized. There

Hello list! I''ve noticed this problem a couple of times now.. so I''m wondering if it''s a known bug? Symptoms: After "long" dom0 uptime (174 days when it happened now, was something similar on previous times too) cannot start new pv domUs anymore.. pygrub runs and boots the kernel, but kernel newer gets to actually running initrd and the console output

Hi guys ... I have a problem ... here is my settup luci xen0 xen1 [root at xen1 ~]# clustat Cluster Status for XEN_Cluster @ Mon Jun 29 03:31:23 2009 Member Status: Quorate Member Name ID Status ------ ---- ---- ------ xen0.genx.local

Hi all, I'm having issue with my Centos 5.1 /Xen installation. I'm having 2 dom0 running 2.6.18-53.1.4.el5xen (x86_64). These two dom0 are connected to a SAN. These two dom0 hosts multiple domU like Centos 4.5 (2.6.9-55.0.9.ELxenU) and Centos 5.1 (2.6.18-53.1.4.el5xen). These two dom0 run ntpd to synchronize dom0 time. When i start a virtual machine on the first dom0 all seems good, the

Situation: Running a simple UDP client/server program where the client on one domU on one computer sends echo packets to another domU on another computer, server sends echoes back. They do this on a specified port (will use any port between 5000-6000). This program works on non-Xen machines in various environments, Linux and Solaris. Program just hangs on the domUs. I believe I need help with

I have a new development box at home that I am working on. Currently it has CentOS 5.1 + Xen 3.2 running several domUs. I am using XDMCP on the domUs and an X Chooser on dom0 for connecting to them and it works well, but now I want to be able to get sound from my domUs and I have been struggling. I can get some from network transparent sound by using ESD, but I have no way of controlling the

I have a new development box at home that I am working on. Currently it has CentOS 5.1 + Xen 3.2 running several domUs. I am using XDMCP on the domUs and an X Chooser on dom0 for connecting to them and it works well, but now I want to be able to get sound from my domUs and I have been struggling. I can get some from network transparent sound by using ESD, but I have no way of controlling the

Hi. My domU date is about 75 seconds (and climbing?) behind domU. Tue Feb 21 23:11:31 UTC 2006 - dom0 Tue Feb 21 23:10:16 UTC 2006 - domu Tue Feb 21 18:10:17 EST 2006 - domu domUs'' /proc/sys/xen/independent_wallclock was 0 Set that to 1: echo 1 > /proc/sys/xen/independent_wallclock Still out by about 75 seconds: Tue Feb 21 23:14:32 UTC 2006 - dom0 Tue Feb 21 23:13:17 UTC 2006 -

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

We are pleased to announce the immediate availability of CentOS-5.6 for i386 and x86_64 Architectures. CentOS-5.6 is based on the upstream release EL 5.6 and includes packages from all variants including Server and Client. All upstream repositories have been combined into one, to make it easier for end users to work with. This is just an announcement email, not the release notes. The Release

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We are pleased to announce the immediate availability of CentOS-5.7 for i386 and x86_64 Architectures. CentOS-5.7 is based on the upstream release EL 5.7 and includes packages from all variants including Server and Client. All upstream repositories have been combined into one, to make it easier for end users to work with. This is just an

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We are pleased to announce the immediate availability of CentOS-5.7 for i386 and x86_64 Architectures. CentOS-5.7 is based on the upstream release EL 5.7 and includes packages from all variants including Server and Client. All upstream repositories have been combined into one, to make it easier for end users to work with. This is just an

We are pleased to announce the immediate availability of CentOS-5.5 for i386 and x86_64 Architectures. CentOS-5.5 is based on the upstream release EL 5.5 and includes packages from all variants including Server and Client. All upstream repositories have been combined into one, to make it easier for end users to work with. This is just an announcement email, not the release notes. The Release

We are pleased to announce the immediate availability of CentOS-5.5 for i386 and x86_64 Architectures. CentOS-5.5 is based on the upstream release EL 5.5 and includes packages from all variants including Server and Client. All upstream repositories have been combined into one, to make it easier for end users to work with. This is just an announcement email, not the release notes. The Release

Hello. Yesterday I tried installing Fedora 10 and Fedora 11 i386 Xen domUs/guests using virt-install and/or virt-manager on CentOS 5.3 Xen x86_64 dom0/host. It doesn't work. The guest kernel crashes early and the graphical VNC console newer shows up. Installing x86_64 domU on x86_64 dom0 work well. 32-on-32 works aswell. So it's a 32-on-64 bug. CentOS 5.3 32b guest on x86_64 host

Hi, I have some xen domU on Centos 5.2 server. For some weeks i had a problem with "xen domU" performances. Indeed my xen domU spend a lot of time in cpu waiting. Reading some informations on the net it seems to come ith I/O heavy load. Using collectd in my domU to monitor the "traffic" on virtual disk and virtuel network i don't see heavy I/O rates. Thinking my dom0

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

Hi folks, I''m new to Xen so apologies if this is a stupid question. Setup is as follows: Dom0 and DomU''s running Hardy Heron Kernel 2.6.24-16-xen Xen version 3.0 My problem is I want to run TShark on DomU to see packets sent to eth0 on Dom0. TShark on Dom0 can see packets sent to DomU on eth0 but DomU cannot see packets sent to Dom0 on eth0. I know the eth0 on DomU is a