Hi I''ve got the following problem when running xen on fedora core 4 Test 1 using, xm create -c rawhide: VFS: Cannot open root device "mapper/VolGroup00-LogVol00" 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) Can anyone please help with this? I''ve tried mapping different device nodes, but I can''t narrow down the problem, my mount looks like this: /dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw) /dev/proc on /proc type proc (rw) /dev/sys on /sys type sysfs (rw) /dev/devpts on /dev/pts type devpts (rw,gid=5,mode=620) /dev/hda1 on /boot type ext3 (rw) /dev/shm on /dev/shm type tmpfs (rw) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) My xen domain file (/etc/xen/rawhide) looks like this kernel ="/boot/vmlinuz-2.6.11-1.1225_FC4xenU" memory = 100 name = "rawhide" nics = 1 disk = [''file:/root/fedora.img,mapper,w''] root = "/dev/mapper/VolGroup00-LogVol00 ro" Any help will be greatly appreciated. Many Thanks Shaz Chase de Vere Financial Solutions plc operates under the trading names of Chase de Vere Private Clients, Chase de Vere Employee Benefits and Moneyextra. Chase de Vere Financial Solutions plc is an independent financial adviser and is authorised and regulated by the Financial Services Authority. Registered Office: 1 King Street, Manchester M2 6AW. Registered in England No: 1723284 VAT No: 503 374571 A wholly owned subsidiary of AWD Group plc. AWD Group plc is a member of AWD Holding AG, Europe''s premier independent financial services group. *************************************************************************** This message is intended for the named recipient only and is confidential and no other person can place any reliance upon it. The recipient acknowledges that transmissions made via the Internet can be corrupted and therefore Chase de Vere Financial Solutions plc does not give any warranty as to the quality or accuracy of any information contained in this message or assumes any liability for it or for its transmission, reception or storage. This footnote also confirms that this e-mail message has been swept for the presence of computer viruses. Chase de Vere Financial Solutions plc is authorised and regulated by the Financial Services Authority and is an independent financial adviser *************************************************************************** _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, 7 Apr 2005, Shahzad Chohan wrote:> My xen domain file (/etc/xen/rawhide) looks like this > > kernel ="/boot/vmlinuz-2.6.11-1.1225_FC4xenU" > memory = 100 > name = "rawhide" > nics = 1 > disk = [''file:/root/fedora.img,mapper,w''] > root = "/dev/mapper/VolGroup00-LogVol00 ro"I don''t think making your disk available as /dev/mapper inside domU is going to work. /dev/mapper should be a directory. Do you have an LVM volume inside /root/fedora.img? If not, you should not be using /dev/mapper at all for domU. -- Robin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi, Thanks for the reply. my /etc/fstab in fedora.img is set to : /dev/mapper/VolGroup00-LogVol00 / ext3 defaults 1 1 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 Although I''m not to sure about its config. The way I decided to configure iot was that fedora.img is on the volume group: /dev/mapper/VolGroup00-LogVol00 Basically my main problem is understanding where things are fitting in. I''ve read around the topic but I''m still hazy with the details. Is this right or wrong? Many Thanks for your help Shaz Robin Green wrote:> On Thu, 7 Apr 2005, Shahzad Chohan wrote: > > My xen domain file (/etc/xen/rawhide) looks like this > > > > kernel ="/boot/vmlinuz-2.6.11-1.1225_FC4xenU" > > memory = 100 > > name = "rawhide" > > nics = 1 > > disk = [''file:/root/fedora.img,mapper,w''] > > root = "/dev/mapper/VolGroup00-LogVol00 ro" > > I don''t think making your disk available as /dev/mapper inside domU is > going to work. /dev/mapper should be a directory. > > Do you have an LVM volume inside /root/fedora.img? If not, you should not > be using /dev/mapper at all for domU. > > -- > Robin >Chase de Vere Financial Solutions plc operates under the trading names of Chase de Vere Private Clients, Chase de Vere Employee Benefits and Moneyextra. Chase de Vere Financial Solutions plc is an independent financial adviser and is authorised and regulated by the Financial Services Authority. Registered Office: 1 King Street, Manchester M2 6AW. Registered in England No: 1723284 VAT No: 503 374571 A wholly owned subsidiary of AWD Group plc. AWD Group plc is a member of AWD Holding AG, Europe''s premier independent financial services group. *************************************************************************** This message is intended for the named recipient only and is confidential and no other person can place any reliance upon it. The recipient acknowledges that transmissions made via the Internet can be corrupted and therefore Chase de Vere Financial Solutions plc does not give any warranty as to the quality or accuracy of any information contained in this message or assumes any liability for it or for its transmission, reception or storage. This footnote also confirms that this e-mail message has been swept for the presence of computer viruses. Chase de Vere Financial Solutions plc is authorised and regulated by the Financial Services Authority and is an independent financial adviser *************************************************************************** _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, 7 Apr 2005, Shahzad Chohan wrote:> Hi, > Thanks for the reply. my /etc/fstab in fedora.img is set to : > > /dev/mapper/VolGroup00-LogVol00 / ext3 defaults 1 1 > none /dev/pts devpts gid=5,mode=620 0 0 > none /dev/shm tmpfs defaults 0 0 > none /proc proc defaults 0 0 > none /sys sysfs defaults 0 0 > > Although I''m not to sure about its config. The way I decided to configure iot > was that fedora.img is on the volume group: /dev/mapper/VolGroup00-LogVol00Sure, but do you have another volume group INSIDE fedora.img? That''s what I''m asking. Please type file /root/fedora.img at the shell prompt and post the output. And how did you install rawhide onto fedora.img? -- Robin _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, 7 Apr 2005, Shahzad Chohan wrote:> Hi Robin, > > Thats a great idea, perhaps I''ll try that way. I''ll give a go and let you > know.OK> BTW: when using sda1 in the xen config, what would happen if I did have a > mount on a existing partition called /dev/sda1, and why is sda chosen to be > in the config? If you have time I''d love to know how these things work, and > is there a document you know of the explains the inner workings of xen.When you have for example file:/root/fedora.img,sda1,rw the file:/root/fedora.img refers to a real file (or device on dom0) the sda1 however, refers to a VIRTUAL device /dev/sda1 that exists only inside the domU virtual machine. It means make /root/fedora.img visible inside the domU virtual machine _as_ /dev/sda1. It has _nothing_ to do with the real partition /dev/sda1 on the real machine! They are two completely separate devices, one virtual and one real. Of course, you can still map the virtual /dev/sda1 onto the real /dev/sda1 so that they _refer_ to effectively the same device, which is what my example in my previous email does, but with /dev/hda5 instead of /dev/sda1:> Robin Green wrote: >> > hmmmm bit lost what to do now. I could try to reinstall , but I''m >> thinking >> > how you have gone about an install. >> >> What I did is installed another copy of fedora on a spare partition in >> the normal way, from a DVD, then booted that inside Xen *after* I''d >> installed it. You just use >> >> phy:hda5,hda5,w >> >> for the disk in the configuration file (assuming that hda5 is where you >> installed the new copy of fedora)._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users