I am confused. Can someone either point me to some documentation a normal human can use or point out my error? The only domU''s I have been able to create in CentOS 5.1 + Xen is another CentOS 5.1 and a Fedora 8 instance. Neither of those seem to be appropriate for MythTV because the IVTV driver comes bundled with the 2.6.22 kernel, and CentOS isn''t about video hardware, and the FC8 driver at atrpms is apparently tied to another non-Xen kernel from who knows where (it''s not Fedora stock). So... I''d like to try Fedora Core 9 (currently beta) or Ubuntu. I cannot get either of them to boot into an installer. FC9 doesn''t recognize the xen network (xennet, I think?) and I cannot for the life of me figure out what kernel/initrd images to use for Ubuntu. If I manually choose the FC9 xennet driver, it just spews across the consoles and dies! Ubuntu never even gets off the ground. I looked at Debian, but it''s the same thing -- I don''t know how to even get it started. :-( So... I thought it was great that jailtime.org has a Ubuntu 7.04 image. But, I cannot even get *that* to boot. Here''s my error message when watching the console:> VFS: Cannot open root device "sda1" or unknown-block(0,0) > Please append a correct "root=" boot option > Kernel panic - not syncing: VFS: Unable to mount root fs on > unknown-block(0,0) >And my config:> kernel = "/boot/vmlinuz-2.6.18-53.1.14.el5xen" > memory = "256" > name = "ubuntu" > vif = [''''] > dhcp = "dhcp" > disk = [''file:/var/lib/xen/images/ubuntu.img,sda1,w'', > ''file:/var/lib/xen/images/ubuntu.swap,sda2,w''] > root = "/dev/sda1 ro" >I didn''t know which kernel to grab, so I just used the CentOS. However, if that''s not right, I don''t know what to use! Here''s the sample config file that ships with the Ubuntu 7.04 image:> kernel = "/boot/vmlinuz-2.6.18-xen" > memory = "256" > name = "ubuntu" > vif = [''''] > dhcp = "dhcp" > disk = [''file:/xen/ubuntu/ubuntu.7-04.img,sda1,w'', > ''file:/xen/ubuntu/ubuntu.swap,sda2,w''] > root = "/dev/sda1 ro" >Sorry about the whining, but I am really missing something basic here and do not see it where I''m looking. TIA. -Rob _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, Rob. I''m a confused newbie too but I think I can help with this one...> Here''s my error message when watching the console: > > > VFS: Cannot open root device "sda1" or unknown-block(0,0) > > Please append a correct "root=" boot option > > Kernel panic - not syncing: VFS: Unable to mount root fs on > > unknown-block(0,0)Okay, kernel don''t know no sda1, probably because it doesn''t have a Xen block device driver loaded...> And my config: > > > kernel = "/boot/vmlinuz-2.6.18-53.1.14.el5xen" > > memory = "256" > > name = "ubuntu" > > vif = [''''] > > dhcp = "dhcp" > > disk = [''file:/var/lib/xen/images/ubuntu.img,sda1,w'', > > ''file:/var/lib/xen/images/ubuntu.swap,sda2,w''] > > root = "/dev/sda1 ro"This all looks fine to me, but there''s no ''ramdisk'' line, and I bet the el5 kernel stores its block drivers in its ramdisk (or not; see below). Alongside wherever you got your kernel, there should be a file named something like "initrd-[same exact version string].img". Copy it into the same area where you''re storing your Xen kernel, and add ramdisk = "/boot/initrd-2.6.18-53.1.14.el5xen.img" ...(tweaking the details as appropriate) to your xm config file. That might not get you out of the woods though. I found that the RHEL kernels tended to be missing bits that I needed, like the ability to recognize PCI cards passed through from the dom0; they''re also notorious for leaving the xenblk driver out of the ramdisk, meaning you have to generate your own using mkinitrd. If you still have trouble after copying over the initrd file for your kernel, here''s a page that talks about that, including an example of a fix: http://wiki.xensource.com/xenwiki/Fedora5Xen0DomU I''ve also found that mixing distro X with a kernel from distro Y is asking for mysterious hangups at the moment when init should be taking over from the kernel boot process; your mileage may vary, try it and see.> I didn''t know which kernel to grab, so I just used the CentOS. However, if > that''s not right, I don''t know what to use!I have yet to get anybody''s install CD to work properly. The closest I got was OpenSolaris, which booted and happily installed the OS, but the system then kernel panics on boot. I could get the RHEL4 install CD to boot, but even with a monolithic kernel it wouldn''t recognize any block devices, including the CD it had just booted from (so I know the problem wasn''t within Xen), so I couldn''t use it to actually set up the system. The only reliable method I''ve found so far is to build the domU inside a chroot on the dom0. HTH, -j _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, Apr 24, 2008 at 08:59:22PM -0500, Rob Greene wrote:> I am confused. Can someone either point me to some documentation a normal > human can use or point out my error? > > The only domU''s I have been able to create in CentOS 5.1 + Xen is another > CentOS 5.1 and a Fedora 8 instance. Neither of those seem to be appropriate > for MythTV because the IVTV driver comes bundled with the 2.6.22 kernel, and > CentOS isn''t about video hardware, and the FC8 driver at atrpms is > apparently tied to another non-Xen kernel from who knows where (it''s not > Fedora stock).Let me correct a couple of statements: o CentOS/RHEL is a great platform for video hardware, more and more myth users go that route, especially ivtv users. o All Fedora stock kernels are supported by ATrpms, and more. You may just have seen the "more" part of it, if you looks closer you''ll find the kmdl you need (although not for xen on Fedora). o There is very good ivtv support for CentOS kernels.> So... I''d like to try Fedora Core 9 (currently beta) or Ubuntu. [...]-- Axel.Thimm at ATrpms.net _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Crap! I did it again. :-( Meant to send it to the group. -Rob On Fri, Apr 25, 2008 at 2:53 PM, Rob Greene <robgreene@gmail.com> wrote:> On Fri, Apr 25, 2008 at 1:52 AM, Axel Thimm <Axel.Thimm@atrpms.net> wrote: > >> o CentOS/RHEL is a great platform for video hardware, more and more >> myth users go that route, especially ivtv users. >> > > I swear I had looked and came up empty, but you''re right (of course). I > think I''ll try that route, because... > > >> o All Fedora stock kernels are supported by ATrpms, and more. You may >> just have seen the "more" part of it, if you looks closer you''ll >> find the kmdl you need (although not for xen on Fedora). > > > Exactly. My assumptions were wrong. Nothing for the Xen folks on F8. > (Reference here: http://atrpms.net/dist/f8/ivtv/). > > >> o There is very good ivtv support for CentOS kernels. > > > Ok, I''ll give that a whirl. At least I''ll be making forward progress > again!! > -Rob >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Quick status update and need more direction... Per the discussion, I am trying to stick with CentOS as the domU since it apparently does have ivtv drivers. So, I did hook them in without too much of an issue but the kernel crashes. I''ve got both 32 and 64 bit configurations right now, and both appear to have the same problem. The pertinent part of the dump (to me) is: Fatal DMA error! Please use ''swiotlb=force''> ------------[ cut here ]------------ > kernel BUG at arch/i386/kernel/pci-dma-xen.c:364! > invalid opcode: 0000 [#1] > SMP > last sysfs file: /class/video4linux/video0/dev > Modules linked in: msp3400 saa7115 tuner ivtv(U) i2c_algo_bit cx2341x > tveeprom i2c_core videodev v4l1_compat v4l2_common pcspkr dm_snapshot > dm_zero dm_mirror dm_mod xenblk ext3 jbd ehci_hcd ohci_hcd uhci_hcd > CPU: 0 >So, after googling, I did add the swiotlb=force line to both my extras line in the Xen config file as well as to the grub.conf file within the domU itself (I left the dom0 alone). Unfortunately, this message tells me nothing: ------------[ cut here ]------------> kernel BUG at lib/../arch/i386/kernel/swiotlb.c:160! > invalid opcode: 0000 [#1] > SMP > last sysfs file: > Modules linked in: > CPU: 0 > EIP: e019:[<c04e1370>] Not tainted VLI > EFLAGS: 00010282 (2.6.18-53.1.14.el5xen #1) > EIP is at swiotlb_init_with_default_size+0x88/0x14e > eax: fffffff4 ebx: 00000180 ecx: 00000000 edx: f5416000 > esi: c0702b64 edi: 08000000 ebp: c06d4fc0 esp: c06d4fb4 > ds: e021 es: e021 ss: e021 > Process swapper (pid: 0, ti=c06d4000 task=c065e2c0 task.ti=c06d4000) > Stack: c1825000 c0702b64 c0271b07 00000020 c06e3bae 0000000e 00000002 > c1825000 > c0702b64 c181fa64 00000020 c06d9873 00008000 c0748800 03040800 > c0ef7000 > 00000000 00000000 c040006f > Call Trace: > [<c06e3bae>] mem_init+0x58/0x390 > [<c06d9873>] start_kernel+0x1fb/0x388 > ======================> Code: c2 b6 f3 ff 83 c8 ff 40 83 f8 06 75 fa 89 d8 b9 1e 00 00 00 c1 e0 0b > ba 06 00 00 00 03 05 14 c7 78 c0 e8 00 41 f3 ff 85 c0 74 08 <0f> 0b a0 00 c1 > 4e 62 c0 83 eb 80 a1 18 c7 78 c0 39 c3 72 c5 b9 > EIP: [<c04e1370>] swiotlb_init_with_default_size+0x88/0x14e SS:ESP > e021:c06d4fb4 > <0>Kernel panic - not syncing: Fatal exception >I did try a number of "swiotlb=(64|128|256),force" lines and then upped the VM image to 1GB ram also since one post suggested it could simply be not enough memory (I have 8GB physical). I remember something about a Xen permissive mode for PCI cards... do I need that? Some of the messages I''ve been seeing looked to actually have that test in the logs somewhere and I don''t see it, so I''m guessing no. I''m not sure where to proceed from here. I guess worst case, I put these cards back into the original machine and dedicate it to Myth or Sage (which it ran ok for a couple of years). I''d really like to consolidate all of this, and the virtual world would really rock. :-/ Any suggestions? -Rob _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users