<div>
<div>You need to tell it your root device in the cfg. </div><div><br></div><div>root = '/dev/xvda ro'</div><div><div><br></div><div>-- </div><div>Joe Fialkowski</div></div>
</div>
<div><div><br></div><div>-- </div><div>Joe Fialkowski</div><div><br></div></div>
<p style="color: #A0A0A8;">On Tuesday, December 4, 2012 at 5:10 PM, Steven Spencer wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div><div>On 12/04/2012 11:01 AM, Steven Spencer wrote:</div><blockquote type="cite"><div><div>On 12/04/2012 09:12 AM, Joe Fialkowski wrote:</div><blockquote type="cite"><div><div>Here is a sample config of mine. Sets the proper IP and bridge info. I</div><div>am also using lvm's for the VM disks rather than image files.</div><div><br></div><div>## Cfg type: XEN-PV-LOCAL-STORAGE</div><div><br></div><div>bootloader = '/usr/bin/pygrub'</div><div>extra = ''</div><div>memory = 1536</div><div>hostname = '<a href="http://hostname.domain.com">hostname.domain.com</a>'</div><div>cpu_weight = 256</div><div>name = 'vm1039'</div><div>vif = ['ip=123.123.123.132, vifname=vifvm1039.0,</div><div>mac=00:16:3e:1f:bf:1a, bridge=br0, model=e1000']</div><div>vnc = 0</div><div>vcpus = 4</div><div>vncviewer = 0</div><div>serial = 'pty'</div><div>disk = ['phy:/dev/vg_xm3/vm1039_img,xvda1,w',</div><div>'phy:/dev/vg_xm3/vm1039_swap,xvda2,w']</div><div><br></div><div><br></div><div><br></div><div>_______________________________________________</div><div>kernel-xen mailing list</div><div><a href="mailto:kernel-xen@lists.wireless.org.au">kernel-xen@lists.wireless.org.au</a></div><div><a href="https://lists.wireless.org.au/mailman/listinfo/kernel-xen">https://lists.wireless.org.au/mailman/listinfo/kernel-xen</a></div></div></blockquote><div>Joe,</div><div><br></div><div>Thanks for that. For some reason I'm not getting past the initial start</div><div>stage of the vm. When I do a xm create /etc/xen/config.file.cfg it</div><div>starts without error, but I can go no further to do the OS install, etc.</div><div>I attempted using a kickstart config file as well, which had no affect.</div><div>Here's what the console shows for the VM when it is started:</div><div><br></div><div>Xen Minimal OS!</div><div> start_info: 0xb9f000(VA)</div><div> nr_pages: 0x40000</div><div> shared_inf: 0xdfd93000(MA)</div><div> pt_base: 0xba2000(VA)</div><div>nr_pt_frames: 0xb</div><div> mfn_list: 0x99f000(VA)</div><div> mod_start: 0x0(VA)</div><div> mod_len: 0</div><div> flags: 0x0</div><div> cmd_line: (hd0)/boot/grub/grub.conf</div><div> stack: 0x95e900-0x97e900</div><div>MM: Init</div><div> _text: 0x0(VA)</div><div> _etext: 0x70b24(VA)</div><div> _erodata: 0x8b000(VA)</div><div> _edata: 0x90e40(VA)</div><div>stack start: 0x95e900(VA)</div><div> _end: 0x99ef00(VA)</div><div> start_pfn: bb0</div><div> max_pfn: 40000</div><div>Mapping memory range 0x1000000 - 0x40000000</div><div>setting 0x0-0x8b000 readonly</div><div>skipped 0x1000</div><div>MM: Initialise page allocator for da8000(da8000)-40000000(40000000)</div><div>MM: done</div><div>Demand map pfns at 40001000-2040001000.</div><div>Heap resides at 2040002000-4040002000.</div><div>Initialising timer interface</div><div>Initialising console ... done.</div><div>gnttab_table mapped at 0x40001000.</div><div>Initialising scheduler</div><div>Thread "Idle": pointer: 0x2040002050, stack: 0xfc0000</div><div>Thread "xenstore": pointer: 0x2040002800, stack: 0xfd0000</div><div>xenbus initialised on irq 1 mfn 0x19e644</div><div>Dummy main: start_info=0x97ea00</div><div>Thread "main": pointer: 0x2040002fb0, stack: 0xfe0000</div><div>"main" "(hd0)/boot/grub/grub.conf"</div><div>vbd 51712 is hd0</div><div>******************* BLKFRONT for device/vbd/51712 **********</div><div><br></div><div><br></div><div>backend at /local/domain/0/backend/tap/7/51712</div><div><br></div><div>Thanks,</div></div></blockquote><div><br></div><div>So, I've sort of made headway, but now have new problems.</div><div><br></div><div>First, I'm using the vmlinuz and initramfs from the /boot directory on </div><div>Dom0. I'm not sure if that is correct or not. If not, what are good </div><div>CentOS6 vmlinuz and initramfs that can be used?</div><div><br></div><div>Here's the DomU config with the IP obfuscated:</div><div><br></div><div>kernel="/boot/vmlinuz-2.6.32-279.14.1.el6.x86_64"</div><div>ramdisk="/boot/initramfs-3.6.7-1.el6xen.x86_64.img"</div><div>name = "vm_test"</div><div>memory = 1024</div><div>vcpus = 1</div><div>disk = [ 'tap:aio:/virtual/vm_test.img,xvda,w' ]</div><div>extra="text ks=<a href="http://10.10.10.104/sample.ks.cfg">http://10.10.10.104/sample.ks.cfg</a>"</div><div>on_poweroff = 'destroy'</div><div>on_reboot = 'restart'</div><div>on_crash = 'restart'</div><div>vif = [ </div><div>"ip=10.10.10.132,mac=00:16:36:35:35:97,bridge=br0,script=vif-bridge" ]</div><div># extra="(hd0)/boot/grub/grub.conf"</div><div><br></div><div>When I run with this config, the console takes off like it's going to </div><div>fly through, then bombs with this error:</div><div><br></div><div>dracut: FATAL: No or empty root= argument</div><div>dracut: Refusing to continue</div><div><br></div><div><br></div><div>dracut Warning: Signal caught!</div><div>dracut Warning: dracut: FATAL: No or empty root= argument</div><div>dracut Warning: dracut: Refusing to continue</div><div>Kernel panic - not syncing: Attempted to kill init!</div><div>Pid: 1, comm: init Not tainted 2.6.32-279.14.1.el6.x86_64 #1</div><div>Call Trace:</div><div> [<ffffffff814fd98a>] ? panic+0xa0/0x168</div><div> [<ffffffff81070c42>] ? do_exit+0x862/0x870</div><div> [<ffffffff8117d0a5>] ? fput+0x25/0x30</div><div> [<ffffffff81070ca8>] ? do_group_exit+0x58/0xd0</div><div> [<ffffffff81070d37>] ? sys_exit_group+0x17/0x20</div><div> [<ffffffff8100b0f2>] ? system_call_fastpath+0x16/0x1b</div><div><br></div><div>What am I missing? Once I have this, I'll have it for good, but I'm </div><div>struggling to get a working config.</div><div><br></div><div>Thanks in advance.</div><div>-- </div><div>-- </div><div>Steven G. Spencer, Network Administrator</div><div>KSC Corporate - The Kelly Supply Family of Companies</div><div>Office 308-382-8764 Ext. 231</div><div>Mobile 308-380-7957</div><div>_______________________________________________</div><div>kernel-xen mailing list</div><div><a href="mailto:kernel-xen@lists.wireless.org.au">kernel-xen@lists.wireless.org.au</a></div><div><a href="https://lists.wireless.org.au/mailman/listinfo/kernel-xen">https://lists.wireless.org.au/mailman/listinfo/kernel-xen</a></div></div></div></span>
</blockquote>
<div>
<br>
</div>