virt

virt@lists.centos.org

1608 discussions

No console from VM Manager since 5.1
by Kai Schaetzl 10 Jan '08

10 Jan '08

Since I updated my CentOS 5.0 host machine to 5.1 I cannot open a console from the VM Manager to a guest. Before 5.1 it opened a VM window that looks close to the VMWare window and displays the console in it, so that I can login to the console. Now I get a "pre-window" that shows a "password" textbox, a Login button and a checkbox for "Save this password in your keyring". What is this? What password am I supposed to enter? Entering the root password (of host or guest) does not work. Once I press the Login button it just hangs and when I try to close it I get a warning that it hangs and when I kill it this way the VM console and the VM Manager are destroyed. I can login via "xm console". Kai -- Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com

1 0

Problem with CentOS 5.1/xen/RTL8110
by Chris Gow 08 Jan '08

08 Jan '08

Hello: I'm having issues with my CentOS 5.1/Xen installation. If I run the xen-bridge, I seem to get flaky ethernet. By flaky I mean everything seems fine from the host machine, but if I attempt to contact the host machine from another remote machine (eg. my laptop which is on the same subnet as the xen machine, separated by 10 ft of cable and a router) I either get extremely high ping times or Destination Host Unreachable. Ditto with ssh. I've disabled the firewall and it does not make a difference. If I stop the xen-bridge (/etc/xen/scripts/network-bridge stop) then I get what I would consider normal network access to the xen machine. Hardware: Gigabyte GA-G33M-S2H MB (Realtek R8110SC onboard nic) OS: CentOS 5.1 64bit Xen I installed CentOS last night with the Xen kernel, the stock kernel did not support my nic which I was aware of. So I downloaded the r1000 source rpm from the centos wiki, built and installed it. Once I did that the card was detected (an ifconfig would actually display eth0), but it would never get an IP address (the xen machine is configured for dhcp at the moment). Today, I installed the non-xen kernel, applied the non-xen r1000 kernel module and the onboard nic was found and working. I then grabbed the updates from centos, saw that there were some kernel updates, applied the r1000 kernel modules again, restarted and (the non-xen kernel) eth0 was still happy. Good. Restarted again, but booted into the xen kernel, eth0 was still happy. eth0 would get an IP address, and was able to see the outside world. However, the outside world (eg. my laptop) could not see the xen machine or it could inconsistently. That is, ping times would be extremely high (on the order of 2+ seconds) or I would get Destination Host Unreachable errors. Trying to connect via ssh would also be sporadic. Thinking it might be firewall related, I disabled the firewall. There was no change in behaviour. I then disabled the xen-bridge and was able to ping with reasonable numbers (<200ms) and connect via ssh. Just to note though, after I stopped the bridge I immediately tried to connect via ssh/ping and did not get through, so I ran service iptables stop (again) and then was able to get correct network access. I'm not sure if stopping iptables again did anything (I doubt) or I did not leave enough time from stopping the bridge to letting everything get reconfigured. I'm not sure what the problem is or how exactly to troubleshoot it. The NIC is slightly different than the one specified in the CentOS wiki (the wiki mentions RTL8110 and RTL8169SC and mine is a RTL8110SC) but I'm not familiar enough with the devices to know how much of a big deal that is, if any. Also, just to be clear, the problem is other physical machines have a difficult time accessing the xen host pc when the xen-bridge is running. I have not gotten as far as creating a VM yet. Any assistance would be great. thanks -- chris

1 0

VMware images
by Ted Miller 07 Jan '08

07 Jan '08

Can someone please clarify the status of minimal install images of Centos 5 for VMware? I see the work that 'tru' did, but it is still at 5 (not 5.1). Is that the best image available (just run yum update), or what about the minimal image listed on the VMware Virtual Appliance site? Ted Miller Indiana, USA

4 4

tick_divider kernel parameter for guest vm
by Fabian Arrotin 03 Jan '08

03 Jan '08

When upstream released 5.1, everybody wanted to test a new kernel parameter that could adjust the system clock rate at boot time to something else than the standard 1000Hz clock rate. A lot of testings has been done (thanks to Akemi Yagi for her great work) and you can see the results here : http://bugs.centos.org/view.php?id=2189 As you can read at the bottom of the comments, it seems it was a typo in the official RH Release Notes : you'd have to read divider= and *NOT* tick_divider= ! (see http://www.centos.org/docs/5/html/release-notes/as-x86/RELEASE-NOTES-U1-x86…) It seems so to work with the correct kernel parameter and so there is no need to build a kernel-vm for CentOS 5.1 guests .. (it's still needed for example for 4.x ..) Keep on reading the comments on bugs.centos.org for further informations ... I assume that upstream release notes will be corrected to reflect the real parameter -- Fabian Arrotin <fabian.arrotin(a)arrfab.net> Solution ? echo '16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlbxq' | dc

3 2

No CD/DVD option in virt-manager for para-virtualized VM?
by brad lodgen 02 Jan '08

02 Jan '08

Hey Everyone, I'm fairly new to linux(6 months or so experience) and very new to using Xen virtualization. First post on the mailing list here! Thanks in advance for any and all help attempts, whether it actually helps me or not! I've been reading the Red Hat virtualization guide and in the appendix labs, using virt-manager, it says to: "Specify either CD-ROM or DVD and enter the path to install media. Specify ISO Image location if you will install from an ISO image. Click Forward." Is this option only available in fully-virtualized VM installs? It asks for URL media only when picking para-virtualized VM. Brad

2 1

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

virt