[CentOS-virt] Can't get PCI card visible in guest
On Fri, 31 Oct 2008, Todd Deshane wrote: p.s., I felt like I spent a bunch of time scratching my head on this stuff because I couldn't find good, clear documentation. Is there such documentation to be found somewhere, or is it just lacking at this point? on one called Running Xen), but what really needs to happen is the Xen wiki needs to be cleaned up a lot and kept up to date. ... Isn't this basically the skew problem with any documentation which is not integrated with a release. A secondary source necessarily lags the primary released code; a wiki, or other webpage can linger 'forever', particularly if cross-linked or mirrored (I was unpleasantly surprised to find content that has 'rolled off' planet.centos.org, being mirrored by two seemingly separate unaffiliated third parties in a search earlier tonight -- static content that _will_ last forever, and be 'uncorrectable' - sadly it appeared in the google results before the primary source article I was seeking) I think wiki's (websites, secondary sources in general) seem to degenerate into 'write and abandon' because the 'payback' for keeping them up to date is less than the satisfaction of moving on to new development, once the old 'itch' is satisfied. -- Russ herrold ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Can't get PCI card visible in guest
Kenneth Tanzer wrote: p.p.s., In case it's useful for others, this is the mkinitrd command I used within the guest, and then copied the initrd to /boot on the host: mkinitrd --with=i2c_dev --with=ip6table_filter --with=ip6_tables --with=ip6t_REJECT --with=ip_conntrack --with=ip_conntrack_netbios_ns --with=iptable_filter --with=ip_tables --with=ipt_REJECT --with=nfnetlink --with=xenblk --with=xennet --with=x_tables --with=xt_state --with=xt_tcpudp /boot/initrd-2.6.18-92.1.13.el5xen.img.new 2.6.18-92.1.13.el5xen Do you really need more than xennet and xenblk in the initrd? You only need to get the machine running with it. The remaining modules whould be loaded from /lib/modules. -- Christopher G. Stach II ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Can't get PCI card visible in guest
Kenneth Tanzer <[EMAIL PROTECTED]> writes: > It really honestly seems to me that sometimes I was getting > inconsistent results, at least vis a vis the _current_ state of > configuration files. Also, I've had situations where I've been unable > to destory machines from the graphical virt-manager, but able to do so > with xm. Yesterday, I had a guest that didn't show up on an xm list, > but showed up in the virt-manager, constantly toggling between running > and stopped. xm and the virt-manager tools are different. I would suggest either always using one or always using the other. > My questions are: > > 1) whether either xm or virt-manager do any kind of caching of > settings, so that your current configuration might not actually be > what is executed? libvirt (virt-manager) does use a different config file, and can convert from the xm config format (I don't know if it does this automatically or if it uses the xm config file unchanged or what.) to the libvirt xml format. I would suggest you either use the libvirt/virt-manager tools, or the xm tools, but don't switch between them on the same installation, especially for guest startup. It's easy to get confused as to config file locations. if you want to use the libvirt tools on the command line, the tool you want is virsh. (personally, I use the xm tools, because I am more interested in Xen than RedHat, though I am currently running Xen on CentOS. I will, in fact, be abandoning the redhat xen kernels on my next servers so I get PVGRUB. ) > 2) does going through the xen / grub boot process do any kind of > changing or writing of settings? Again, I swear there were times > where I got different results on the second boot than the first one. Pygrub is read-only, as far as I know. It should not change your config file or guest disk. > 3) finally, what would account for the differences between > virt-manager and xm, and also is there any magic way to destroy an > un-destroyable machine without having to reboot your computer? 'xm destroy' has worked fine for me for some time. I think it's been more than a year since I've been unable to kill a zombie.Are you running a recent kernel? ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Can't get PCI card visible in guest
Thanks. I actually was running pygrub, and I _swear_ that the first time I ran it, it said that the initrd was not found. I then copied it to the host, and it ran. This actually brings me to another question/issue: It really honestly seems to me that sometimes I was getting inconsistent results, at least vis a vis the _current_ state of configuration files. Also, I've had situations where I've been unable to destory machines from the graphical virt-manager, but able to do so with xm. Yesterday, I had a guest that didn't show up on an xm list, but showed up in the virt-manager, constantly toggling between running and stopped. My questions are: 1) whether either xm or virt-manager do any kind of caching of settings, so that your current configuration might not actually be what is executed? 2) does going through the xen / grub boot process do any kind of changing or writing of settings? Again, I swear there were times where I got different results on the second boot than the first one. 3) finally, what would account for the differences between virt-manager and xm, and also is there any magic way to destroy an un-destroyable machine without having to reboot your computer? Thanks all--this seems like a very helpful mailing list! Ken Brett Worth wrote: Kenneth Tanzer wrote: Unfortunately, as it turns out, there are then a bunch of additional Asterisk modules that I would need to build for the xen kernel, and I didn't have any luck finding the source, so I think I might give up on this for a while. If you are using paravirtualisation then you can use pygrub instead of booting the kernel directly so that the kernel/initrd files etc are in the guest's storage. The virt-manager will configure pygrub by default when installing a client. You could install a temporary guest using virt-manager and see how it does the config of pygrub. This thread has some interesting info: http://lists.xensource.com/archives/html/xen-users/2006-12/msg00902.html Brett ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Can't get PCI card visible in guest
On Fri, Oct 31, 2008 at 7:17 PM, Kenneth Tanzer <[EMAIL PROTECTED]> wrote: > What I ended up doing was looking at my working CentOS PV guest, listing all > the modules, and finding the ones that were not loaded in my AsteriskNow > guest. That seemed to do the trick, and it booted. (Once I realized that > the initrd file had to be in /boot on the _host_, not the guest!) > > Unfortunately, as it turns out, there are then a bunch of additional > Asterisk modules that I would need to build for the xen kernel, and I didn't > have any luck finding the source, so I think I might give up on this for a > while. > > Thanks very much for your help! > > Ken > > p.s., I felt like I spent a bunch of time scratching my head on this stuff > because I couldn't find good, clear documentation. Is there such > documentation to be found somewhere, or is it just lacking at this point? > There really isn't good, clear, complete documentation on all of this. It is a bit scattered in READMEs, some on the xen wiki, some very good blog and sides site, there are a number of Xen books (I am a co-author on one called Running Xen), but what really needs to happen is the Xen wiki needs to be cleaned up a lot and kept up to date. Xen.org actually has documentation/the wiki in its plans to be worked on soon. I hope that that will help the documentation situation get a lot better. See our book's website (runningxen.com) for a lot of links and resources. Cheers, Todd > p.p.s., In case it's useful for others, this is the mkinitrd command I used > within the guest, and then copied the initrd to /boot on the host: > > mkinitrd --with=i2c_dev --with=ip6table_filter --with=ip6_tables > --with=ip6t_REJECT --with=ip_conntrack --with=ip_conntrack_netbios_ns > --with=iptable_filter --with=ip_tables --with=ipt_REJECT --with=nfnetlink > --with=xenblk --with=xennet --with=x_tables --with=xt_state --with=xt_tcpudp > /boot/initrd-2.6.18-92.1.13.el5xen.img.new 2.6.18-92.1.13.el5xen -- Todd Deshane http://todddeshane.net http://runningxen.com ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Can't get PCI card visible in guest
Kenneth Tanzer wrote: > Unfortunately, as it turns out, there are then a bunch of additional > Asterisk modules that I would need to build for the xen kernel, and I > didn't have any luck finding the source, so I think I might give up on > this for a while. If you are using paravirtualisation then you can use pygrub instead of booting the kernel directly so that the kernel/initrd files etc are in the guest's storage. The virt-manager will configure pygrub by default when installing a client. You could install a temporary guest using virt-manager and see how it does the config of pygrub. This thread has some interesting info: http://lists.xensource.com/archives/html/xen-users/2006-12/msg00902.html Brett ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
Re: [CentOS-virt] Can't get PCI card visible in guest
What I ended up doing was looking at my working CentOS PV guest, listing all the modules, and finding the ones that were not loaded in my AsteriskNow guest. That seemed to do the trick, and it booted. (Once I realized that the initrd file had to be in /boot on the _host_, not the guest!) Unfortunately, as it turns out, there are then a bunch of additional Asterisk modules that I would need to build for the xen kernel, and I didn't have any luck finding the source, so I think I might give up on this for a while. Thanks very much for your help! Ken p.s., I felt like I spent a bunch of time scratching my head on this stuff because I couldn't find good, clear documentation. Is there such documentation to be found somewhere, or is it just lacking at this point? p.p.s., In case it's useful for others, this is the mkinitrd command I used within the guest, and then copied the initrd to /boot on the host: mkinitrd --with=i2c_dev --with=ip6table_filter --with=ip6_tables --with=ip6t_REJECT --with=ip_conntrack --with=ip_conntrack_netbios_ns --with=iptable_filter --with=ip_tables --with=ipt_REJECT --with=nfnetlink --with=xenblk --with=xennet --with=x_tables --with=xt_state --with=xt_tcpudp /boot/initrd-2.6.18-92.1.13.el5xen.img.new 2.6.18-92.1.13.el5xen Todd Deshane wrote: On Thu, Oct 30, 2008 at 8:04 PM, Kenneth Tanzer <[EMAIL PROTECTED]> wrote: I am not seeing the errors in the red hat based boot that I am familiar with, As I understand it, this Asterisk disk I have is built on Centos 5.2, so I'm assuming Asterisk=CentOS=Redhat, at least for this purpose. Yeah, I meant Red Hat-based, CentOS, fedora etc. are quite similar it seems that you are running into one of the following (or similar: Your guest root file system is not where you expect it to be. If you haven't already, check the grub.conf in the guest. Here's my grub file: title CentOS (2.6.18-92.1.13.el5xen) root (hd0,0) kernel /xen.gz-2.6.18-92.1.13.el5 module /vmlinuz-2.6.18-92.1.13.el5xen ro root=/dev/VolGroup00/LogVol00 module /initrd-2.6.18-92.1.13.el5xen.img Here's the corresponding xen entries: kernel="/boot/vmlinuz-2.6.18-92.1.13.el5xen" ramdisk="/boot/initrd-2.6.18-92.1.13.el5xen.img" root="/dev/VolGroup00/LogVol00" extra="ro" They seem to match to me. Sanity check: the "root" in the xen config is specified as seen by the guest, right? Yes, with the guest disk image. OR You are missing modules in your ramdisk that are needed by your guest (in which case you would need to use mkinitrd to rebuild your xen initrd and make sure you include the necessary modules) I can boot the xen kernel as a fully-virtualized machine (with the grub.conf mentioned above). Is that a fair indicator that all the required modules exist? If not, any idea how to figure out what might be missing? Actually no, the fully virtual kernel modules in the guest are not used when booting with the kernel and ramdisk options in the xen config. Some of those more familiar with centos might be able to jump in to help with specific modules, but if I was you I would boot the full virtual guest, do an lsmod and compare the modules, especially the ones to do with disk drivers, lvm, device mappers etc. with the /lib/modules//modules Simply rebuilding the initrd with a mkinitrd and the right modules included might be all you need. This only the basic idea, I would suggest to take some time to search xen.markmail.org for either error messags or key words that may lead you to some exact instructions of the mkinitrd that will work for your setup. Hope that helps, Cheers, Todd ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Can't get USB printer visible in guest
I'm trying to get a USB printer which works on the host (CentOS 5.2 x86_64) to work on a guest (also CentOS 5.2 x86_64). I'm reading Running Xen at the moment, it is a great starting point that brings together all manner of information in one coherent place, but I'm finding the section on Device Virtualisation a bit unclear (or lacking detail). As I read it, to create a USB device for a HVM machine I need device_model = "/usr/lib64/xen/bin/qemu-dm" usb = 1 in the guest's config file. There is not much more specified in the text than this. I've done this but without success. When I go to add a device to the guest in the GUI tool, I still don't get an option for any kind of USB device. What have I missed? ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
[CentOS-virt] Very high cpu waiting on xen domU
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 was overloaded by my domUs i have stopped all my domUs except one but the problem persist. I don't know how to get more informations in order to solve my problem. For information our config is : - Hitachi SAN infrastructure - DELL 1950 servers with 2 qlogic hba adapters (we used qla2xx drivers and linux dm-multipath for multipathing ) - We have 1 LUN on the SAN for each domU - The dom0 manage theses LUNs using LVM - A domU xen disk configuration looks like this : disk = [ 'phy:/dev/VolGroupIdp/LogVolIdp-disk,xvda1,w'] - In the domU we doesn't use LVM. - At the network level we share a gigabit interface with all the domU using linux bridges. Each bridge refer to a different vlan. Anyone encoutered I/O performances problems with latests centos 5.2 xen releases ? (In fact i don't really understand if it's a xen problem or a "hardware" problem) Regards -- Frederic Soulier Administrateur Reseau Centre de Ressources Informatiques Université Toulouse 1 Sciences Sociales 2 RUE DU DOYEN GABRIEL MARTY 31042 TOULOUSE CEDEX 9 Tel : +33 5 61 63 39 98 / +33 5 61 63 39 98 Fax : +33 5 61 63 37 98 Bureau : AR38 bis http://cri.univ-tlse1.fr/ ___ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
