The silly mistake that always gets me is I forget to put the .img extension on the initrd file, be careful when running mkinitrd that the exact command is:
# mkinitrd -f --preload=pciback /boot/initrd-$(uname -r).img $(uname -r)
You can remove the pciback stuff from grub.conf, but make sure the modprobe.conf options are there prior to running mkinitrd.
-Ross
----- Original Message ----- From: centos-virt-bounces@centos.org centos-virt-bounces@centos.org To: Discussion about the virtualization on CentOS centos-virt@centos.org Sent: Thu Apr 17 17:03:07 2008 Subject: RE: [CentOS-virt] Xen List
Here's an example using my sound card.
/etc/modprobe.conf: options pciback hide=(00:10.1) # If you aren't preloading pciback in the initrd uncomment the next line #install snd-hda-intel /usr/sbin/modprobe pciback; /sbin/modprobe --first-time --ignore-install snd-hda-intel
To preload pciback in initrd:
# mkinitrd -f --preload=pciback /etc/initrd-$(uname -r).img $(uname -r)
That should do it.
Ok, this is where I got messed up (No grub line :)). I originally had the rpmforge sk98ln rpm installed to make this realtek nic work before I tried this, then using this procedure which I followed to a "t" didn't mask the device from Dom0? It loaded the driver and setup the nic? I know I had the pci slot number right. I thought the initrd was wrong, so I looked through grub and looked at what it loaded, then checked the timestamp of the one I made with that command and it was consistent? I assume something still wasn't right with my mkinitrd, it completed with zero verbosity, mayeb I should try to use -v and see what happens.
Any ideas?
Thanks! jlc _______________________________________________ CentOS-virt mailing list CentOS-virt@centos.org http://lists.centos.org/mailman/listinfo/centos-virt
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.
The silly mistake that always gets me is I forget to put the .img extension on the initrd file, be careful when running mkinitrd that the exact command is:
# mkinitrd -f --preload=pciback /boot/initrd-$(uname -r).img $(uname -r)
You can remove the pciback stuff from grub.conf, but make sure the modprobe.conf options are there prior to running mkinitrd.
-Ross
Ross, You rock! I think the issue before was one of iether two sceanrios, I may not have had the modprobe.conf line in before I ran mkinitrd, or it wasn't at the top (would that matter?).
Anyway, I saw dmesg indicate the module siezed the device!
Thanks so much! jlc
Ps. Do you run any hvm's in production?
Joseph L. Casale wrote:
The silly mistake that always gets me is I forget to put the .img extension on the initrd file, be careful when running mkinitrd that the exact command is:
# mkinitrd -f --preload=pciback /boot/initrd-$(uname -r).img $(uname -r)
You can remove the pciback stuff from grub.conf, but make sure the modprobe.conf options are there prior to running mkinitrd.
-Ross
Ross, You rock! I think the issue before was one of iether two sceanrios, I may not have had the modprobe.conf line in before I ran mkinitrd, or it wasn't at the top (would that matter?).
Doesn't matter where in modprobe.conf it is because it gets grepped out when the module loads.
Anyway, I saw dmesg indicate the module siezed the device!
Thanks so much! jlc
Ps. Do you run any hvm's in production?
Not so much HVMs but we have a number of PVMs in production. We are still using VMware/MSVS for our HVMs. It just makes sense to consolidate Linux onto Xen and Windows onto VMware/MSVS right now.
There's a whole cost/benefit and cost/performance analysis I could go into on this, but I think you can get the picture.
-Ross
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.
We are still using VMware/MSVS for our HVMs.
Yea, I am eagerly awaiting opensource pv drivers for xen hvms:)
I am trying to find the url for the other guy developing them but can't, you remember who that was that was working on them besides James?
Thanks, jlc
Joseph L. Casale wrote:
We are still using VMware/MSVS for our HVMs.
Yea, I am eagerly awaiting opensource pv drivers for xen hvms:)
I am trying to find the url for the other guy developing them but can't, you remember who that was that was working on them besides James?
I only know of James who I believe compiles and distributes the drivers, but the drivers are very early alpha and definitely not to be used in production, so I am just waiting until they have a 1.0 release of them.
-Ross
______________________________________________________________________ This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution or copying of this e-mail, and any attachments thereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify the sender and permanently delete the original and any copy or printout thereof.
I only know of James who I believe compiles and distributes the drivers, but the drivers are very early alpha and definitely not to be used in production, so I am just waiting until they have a 1.0 release of them.
-Ross
Ok, appreciate that. I was looking last night on installing CentOS as a pv guest. It seems there are several ways. If I wanted to avoid virsh and use the original "xm" command its associated text files, can I still install from an iso and create a vnc connection that I can immediately connect to? It appears that Xen wants to boot the install with a kernel and initrd that exists inside Dom0's /boot?
How do I populate this with the correct images for a pv CentOS guest?
What do you do for pv installs on your xen servers?
Thanks a lot! jlc
-
Joseph L. Casale -
Ross S. W. Walker