virt December 2007

virt@lists.centos.org

23 participants
12 discussions

open-vm-tools for latest CentOS-4 and CentOS-5 kernel-vms
by Johnny Hughes 02 Jan '08

02 Jan '08

All, There are some (very much) testing open-vm-tools RPMS for both the CentOS-4 and CentOS-5 i386 and x86_64 kernel-vm's and standard UP kernels. The kernel-vm's are available here: http://people.centos.org/~tru/kernel-vm/ (The kernel-vm kernels are designed to run inside the VMs at a clock rate of 100HZ instead of 1000Hz.) The open-vm-tools are available here: http://people.centos.org/~hughesjr/open-vm-tools/ The purpose of these RPMS (open-vm-tools) is to replace the VMware-Tools RPMS that come with VMWare. Please remove VMWare-Tools inside the VM if you are going to install these open-vm-tools for testing. There is an xorg.conf file that should be used to replace the one in /etc/X11/ inside the VM Client only (not on your host). The open-vm-tools SHOULD ONLY be installed inside a VM Client and not on the VM Host. These open-vm-tools RPMS are only designed to work with CentOS VM Clients/Guests (should not matter what the host is), though they should also work if RHEL4 or RHEL5 are the VM Clients/Guests. Documentation for the vm tools can be found here: http://open-vm-tools.wiki.sourceforge.net/Packaging and chapter3 here: http://www.vmware.com/pdf/server_vm_manual.pdf (In that PDF file, the installation parts can be ignored, but the configuration parts and usage parts should work) Thanks, Johnny Hughes

5 8

xen dom0/domU network speed
by David Kostal 31 Dec '07

31 Dec '07

Hi all, I have problem reaching 1Gbps network speed with dom0 / domU (paravirtualized) on my centos5 installations. The fastest speed I measured in domU was about 800/600 receive/transmit Mbps, dom0 being a bit slower. I'm using bridging (eeither with default xen/centos network-bridge script or with my own scripts assigning vlans to bridges). Is anyone experiencing same network slowdown? Or could it be just some configuration issue on my side? Thanks, david.kostal(a)gmail.com ----+

3 4

xen dependencies
by Joseph L. Casale 30 Dec '07

30 Dec '07

Hi all, I posted this question originally in the users list as I was unaware of this one and have reposted here by that lists suggestion. It appears that if I perform an install of CentOS 5.1 without changing *anything* in the options, then do a #yum groupinstall 'Virtualization' I can now get Xen to function in bridged mode (it has network connectivity). If I perform a minimal install, then #yum install xen xen-kernel, once I reboot I do not have network access to or from the box unless I switch to routed mode. In lieu of this, can anyone shed some light on what dependency Xen has that is not installed when you do a completely bare install and execute a #yum install xen? I am hoping to finally end up with a minimum install of CentOS with Xen functioning without a gui or any additional services that won't be needed. Thanks! jlc

2 10

LVM + kickstart -> dom0 && domUs
by Karl Erisman 19 Dec '07

19 Dec '07

centos-virt, I'm trying to create/install domU guests all in "one" step, following Daniel's wiki page (I've found these pages really helpful, BTW): http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU I have a few questions about this process: (1) How would it be modified (w/respect to defining the disk in the domain configuration file) to use a disk layout where dom0 has N logical volumes, one for each of N domU guests? (2) Using this method (where dom0 has an LV for each domU disk), I would avoid the entire "Creating an image" step, correct? (3) I'm setting up a dom0 kickstart. If I proceed as described, doing this (where domU_i is the ith guest): ####### in dom0 kickstart... ####### # logical volume for guest domU_i logvol /var/lib/xen/images/domU_i_disk --fstype ext3 --name=LV_domU_i_disk --vgname=vg00 --size=5120 # ...[other guest disk LVs]... ####### ...I'd need to unmount those logical volumes before trying to kickstart the guest domUs, right? (4) Additionally, how would domU "see" its disk during the install process? Assume I specify a backend LV_domU_i_disk logical volume (an LV in dom0 that I just described) as the disk and map it to a frontend device called 'xvda'. Again using kickstart, I expect it would look like this: ####### in domU kickstart... ####### clearpart --all --initlabel --drives=xvda #... part pv.01 --size=100 --grow --asprimary --ondisk=xvda volgroup volgroup00 --pesize=4096 pv.01 logvol /home --fstype ext3 --name=LV_home --vgname=volgroup00 --size=3072 #... ####### (5) Any comments, criticisms, or suggestions for improvement on these ideas? Thanks!

1 1

5.1: problem opening console from vm manager
by Kai Schaetzl 19 Dec '07

19 Dec '07

With the upgrade to 5.1 I get new behavior when I "open" the console from vm manager. Before 5.1 it showed the console login message like on a physical machine. However, with 5.1 I get a window that wants a password and has a checkbox "save the password in your keyring". What password? No matter, what I enter there the window just hangs and when I try to close it I get a "not responding" dialog and finally the whole VM manager gets killed. I can switch to serial console on that machine window fine. I was able to get to the console of the VM when I opened it *during* the boot up. Then it scrolls out the normal bootup information and finally stops at the login message and I can login, just like before 5.1. But if I open the console once it's already booted up I get this dreaded "Password:" prompt. I can also switch and login with "xm console", but using the vm manager way doesn't work. (BTW: how can I switch back from a DomU console to the Dom0 console in a terminal tab? When I "exit" it just logs me out and presents the login message of the DomU. It doesn't go back to the host console.) Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

2 2

Problem with foreign-language keyboard
by James Wilde 18 Dec '07

18 Dec '07

I am testing Xen on a Centos5 machine. On this machine, the locale is en_US.UTF-8 and the keyboard is Sweden. Everything works fine. I have created a guest operating system (I'm using vmware terminology, as I am still confused about DomU and Dom0). The guest is also Centos5. According to the configuration files, the locale on the guest is also en_US.UTF-8 and the keyboard Sweden. However, in the guest, only the alphanumeric keys (a-z, 0-9) work as intended. The numeric keyboard does not appear to work at all. And the non-alphanumeric keys on the alpha keyboard do not produce the symbols they should provided with the Swedish keyboard. There is no key, for example, which produces the hyphen, which means that it is impossible to enter a parameter to a command, such as ls -la. I wonder if anyone else has had a similar difficulty and found a solution. It doesn't have to be a solution for the Swedish keyboard. Just a pointer or hint would be appreciated. I'm not too familiar with Centos, which I installed on this test machine because of other dependencies, as we are a Solaris shop and my personal workstation is Ubuntu. Thanks in advance for any help. //James

5 5

Problems booting DomU on CentOS 5.1
by Maurício Luís Wecker - SouthTech Super Datacenter 14 Dec '07

14 Dec '07

1 0

Re: VMware tools in standard CentOS [ was Re: www.centos.org - Contact the CentOS Development Team Form ]
by Andrew Sharpe 12 Dec '07

12 Dec '07

[ Sorry for the very belated response ] Thanks, Tru. What is the process for Sean's work to make it into the standard CentOS5 and 5.1 repositories? How will the tools package get updated as you patch the kernel? Perhaps we should cc Sean on the email? His home page on the Duke server has no contact information. Thanks, Andrew [ Resent to the centos-virt email list, as recommended by Karanbir Singh ] On 11/16/2007 12:30 PM, Tru Huynh wrote: > On Fri, Nov 16, 2007 at 11:05:05AM -0800, Andrew Sharpe wrote: >> Hi Johnny, >> >> Eventually, we'd like to see a "virtual appliance" install profile in >> CentOS. This install profile would install a small subset of the >> CentOS server packages, and ideally install a reduced-footprint kernel >> that only had drivers installed for the hardware platform presented by >> the VMware Infrastructure, include paravirt support for CPU and I/O, >> and include the VMware tools drivers, commands and daemons. >> > That could probably be provided by a special repository without too much hassle. > > Someone has already been working on it: > http://www.duke.edu/~sean/rpms/open-vm-tools/ > from http://open-vm-tools.wiki.sourceforge.net/Distro+Package+Status > > mostof the work seems to be in the install process (at least from the few threads > I have been reading) > http://sourceforge.net/mailarchive/forum.php?thread_name=f89c49a90710300702… > >> Has someone else from VMware previously contacted you about this type >> of cooperation and support? If so, I'll be glad to touch base with >> them, and if not, I'll be happy to get you connected to the right >> folks around here to make this happen. > > keep us posted, > > Cheers, > > Tru

2 1

i386 VM on x86_64 host in Xen
by Karanbir Singh 11 Dec '07

11 Dec '07

hi, Just wondering if people had started using i386 Xen DomU's on a x86_64 dom0 machine with 5.1 as yet ? And just wondering what their experiences have been. -- Karanbir Singh : http://www.karan.org/ : 2522219@icq

5 11

Network Problem after update 3.0 -> 3.1: blkback
by kfx 11 Dec '07

11 Dec '07

Hello, I have a big problem: Dom0 is centos5.1, domU are centos5.1. My setup is really simple, the only thing is that I give 3 nics to the domU so I use a modified network script (which has worked since january... since fedora 6): " #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" vifnum=0 "$dir/network-bridge" "$@" vifnum=1 "$dir/network-bridge" "$@" vifnum=2 " So I have updated my xen dom0 from 3.0.3-rc5-8.1.15.el5 to 3.1.0-53.1.4.el5 (and kernel-xen 2.6.18-8.1.15.el5xen to 2.6.18-53.1.4.el5xen) and now my domU cant access the network. The interfaces are good in the domU, all seems to be ok but there are no connectivity at all (no arp entries). This message shows up on the dom0 each time I launch a domU: blkback: ring-ref 9, event-channel 7, protocol 1 (x86_64-abi) Do someone know what is happening ? this is very embarrassing after a simple upgrade... Hopefully I have another identical server (Centos 5.0 with 5.1 domUs) which is still in 3.0 but I cant stay not updated. Thanks for any help. xm info: host : host.foo.com release : 2.6.18-53.1.4.el5xen version : #1 SMP Fri Nov 30 01:21:23 EST 2007 machine : x86_64 nr_cpus : 4 nr_nodes : 1 sockets_per_node : 2 cores_per_socket : 1 threads_per_core : 2 cpu_mhz : 2992 hw_caps : bfebfbff:20100800:00000000:00000180:0000641d total_memory : 4095 free_memory : 3246 xen_major : 3 xen_minor : 1 xen_extra : .0-53.1.4.el5 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable cc_compiler : gcc version 4.1.2 20070626 (Red Hat 4.1.2-14) cc_compile_by : mockbuild cc_compile_domain : cc_compile_date : Fri Nov 30 00:37:12 EST 2007 xend_config_format : 2

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt December 2007