Hello, This is my first attempt at setting up Xen. I''ve got xend running without issue but can''t seem to create DomU''s. I''m sure I''m missing something obvious but I''ve exhausted my resources trying to find it. I installed from xen-3.0.2.2-86.1 RPMs. Do I need to do anything more to a LV before trying to use it with Xen? [root@phllu3 ~]# uname -a Linux phllu3 2.6.16-xen3_86.1_fc4 #1 SMP Thu Apr 13 08:26:52 PDT 2006 i686 i686 i386 GNU/Linux [root@phllu3 ~]# xm list Name ID Mem(MiB) VCPUs State Time(s) Domain-0 0 1894 4 r----- 75.8 [root@phllu3 ~]# fdisk -l Disk /dev/sda: 319.9 GB, 319954092032 bytes 255 heads, 63 sectors/track, 38898 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 1305 10482381 83 Linux /dev/sda2 1306 1827 4192965 82 Linux swap / Solaris /dev/sda3 1828 38898 297772807+ 8e Linux LVM [root@phllu3 ~]# lvdisplay --- Logical volume --- LV Name /dev/xen_vg/lvol0 VG Name xen_vg LV UUID c2Pefx-PKm0-sodt-5FG7-Id7s-9JCu-QDUF8Y LV Write Access read/write LV Status available # open 0 LV Size 20.00 GB Current LE 5120 Segments 1 Allocation inherit Read ahead sectors 0 Block device 254:0 [root@phllu3 ~]# cat /etc/xen/test.cfg kernel = "/boot/vmlinuz-2.6.16-xen3_86.1_fc4" memory = 64 name = "vm1" vif = [ '''' ] disk = [ ''phy:/dev/xen_vg/lvol0,sda1,w'' ] [root@phllu3 ~]# xm create -c test.cfg Using config file "/etc/xen/test.cfg". Started domain vm1 Linux version 2.6.16-xen3_86.1_fc4 (rread@fc4build.eng.hq.xensource.com) (gcc version 4.0.1 20050727 (Red Hat 4.0.1-5)) #1 SMP Thu Apr 13 08:26:52 PDT 2006 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000004000000 (usable) 0MB HIGHMEM available. 72MB LOWMEM available. ACPI in unprivileged domain disabled IRQ lockup detection disabled Built 1 zonelists Kernel command line: Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 PID hash table entries: 512 (order: 9, 8192 bytes) Xen reported: 2793.178 MHz processor. Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) Software IO TLB disabled vmalloc area: c5000000-fb7fe000, maxmem 33ffe000 Memory: 61016k/73728k available (2188k kernel code, 4452k reserved, 681k data, 168k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 5587.17 BogoMIPS (lpj=27935880) Security Framework v1.0.0 initialized Capability LSM initialized Mount-cache hash table entries: 512 CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 1024K Checking ''hlt'' instruction... OK. Brought up 1 CPUs migration_cost=0 Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: setting up Xen PCI frontend stub ACPI: Subsystem revision 20060127 ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay xen_mem: Initialising balloon driver. usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: System does not support PCI PCI: System does not support PCI IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com> VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) Initializing Cryptographic API io scheduler noop registered io scheduler anticipatory registered (default) io scheduler deadline registered io scheduler cfq registered PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize Xen virtual console successfully installed as tty1 Event-channel device installed. blkif_init: reqs=64, pages=704, mmap_vstart=0xc3800000 netfront: Initialising virtual ethernet driver. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx Registering block device major 8 ide-floppy driver 0.99.newide usbmon: debugfs is not available usbcore: registered new driver libusual mice: PS/2 mouse device common for all mice NET: Registered protocol family 2 IP route cache hash table entries: 1024 (order: 0, 4096 bytes) TCP established hash table entries: 4096 (order: 3, 32768 bytes) TCP bind hash table entries: 4096 (order: 3, 32768 bytes) TCP: Hash tables configured (established 4096 bind 4096) TCP reno registered Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 NET: Registered protocol family 8 NET: Registered protocol family 20 Using IPI No-Shortcut mode VFS: Cannot open root device "<NULL>" 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) _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andrew McConnell wrote:> This is my first attempt at setting up Xen. I''ve got xend running > without issue but can''t seem to create DomU''s. I''m sure I''m missing > something obvious but I''ve exhausted my resources trying to find it. > I installed from xen-3.0.2.2-86.1 RPMs. > > Do I need to do anything more to a LV before trying to use it with Xen?I assume you''ve created a filesystem on the LV and have drivers for said fs compiled into your domU kernel.> [root@phllu3 ~]# cat /etc/xen/test.cfg > kernel = "/boot/vmlinuz-2.6.16-xen3_86.1_fc4" > memory = 64 > name = "vm1" > vif = [ '''' ] > disk = [ ''phy:/dev/xen_vg/lvol0,sda1,w'' ]You''re missing the following line in /etc/xen/test.cfg : root = "/dev/sda1 ro";> [root@phllu3 ~]# xm create -c test.cfg> VFS: Cannot open root device "<NULL>" or unknown-block(0,0) > Please append a correct "root=" boot optionCheers Andrew _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 7/6/06, Andrew Ross <aross@westnet.com.au> wrote:> I assume you''ve created a filesystem on the LV and have drivers for said > fs compiled into your domU kernel.I created an ext3 filesystem on the LV. Whether ext3 drivers are compiled into the kernel is not something I can answer without some assistance but based on the output below, it looks like it''s trying to use ext2 instead. I''m using the kernel that shipped with the tarball from xensource.com. I''ve made no modifications, nor did I think I needed to.> You''re missing the following line in /etc/xen/test.cfg : > > root = "/dev/sda1 ro";I''ve added the line above and seem to get further now: [root@phllu3 ~]# xm create -c test.cfg Using config file "/etc/xen/test.cfg". Started domain vm1 Linux version 2.6.16-xen3_86.1_fc4 (rread@fc4build.eng.hq.xensource.com) (gcc version 4.0.1 20050727 (Red Hat 4.0.1-5)) #1 SMP Thu Apr 13 08:26:52 PDT 2006 (...) EXT2-fs warning (device sda1): ext2_fill_super: mounting ext3 filesystem as ext2 VFS: Mounted root (ext2 filesystem) readonly. Freeing unused kernel memory: 168k freed Warning: unable to open an initial console. Kernel panic - not syncing: No init found. Try passing init= option to kernel. I''m guessing this is probably normal since there is nothing on the filesystem so it can''t execute /sbin/init ??? Thanks for your help. Can you point me to some documentation that will clarify the next steps? I feel like I''m not catching on to something extremely important about this architecture...I was expecting to be able to go through a normal OS install upon successful creation of the new domain. -Andrew _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Andrew McConnell wrote:> On 7/6/06, Andrew Ross <aross@westnet.com.au> wrote: >> I assume you''ve created a filesystem on the LV and have drivers for said >> fs compiled into your domU kernel. > > I created an ext3 filesystem on the LV. Whether ext3 drivers are > compiled into the kernel is not something I can answer without some > assistance but based on the output below, it looks like it''s trying to > use ext2 instead.ext3 is simply ext2 with a journal, so ext3 volumes can be safely mounted as ext2 - you simply loose the benefit of the journal while the volume is mounted as ext2.> Warning: unable to open an initial console.This generally means you''re missing /dev/console , which makes sense, since you have an empty filesystem.> I''m guessing this is probably normal since there is nothing on the > filesystem so it can''t execute /sbin/init ???Yep.> Thanks for your help. Can you point me to some documentation that > will clarify the next steps? I feel like I''m not catching on to > something extremely important about this architecture...I was > expecting to be able to go through a normal OS install upon successful > creation of the new domain.I don''t really have any FC-specific experience, but my understanding is for paravirtualized guests you need to boostrap an initial system from dom0. For Gentoo domUs, the process is no different to a normal install, but for Debian you usually use debootstrap, and for rpm-based distros you can use rpmstrap. You might want to try domi (http://dl.bytesex.org/cvs-snapshots/), which is a shell script frontend for xen domU creation - it can easily create xen domUs for a range of Linux distros. Alternatively, I think the latest FC and SUSE setup programs support installing into locations other than /, which is probably the closest you''ll get to a regular-style install. Of course, with VMX (ie. unmodified) guests, I assume you simply boot the virtual machine from a CD image and run the installer as usual a la Qemu. If you haven''t already done so, check out the Xen Wiki (http://wiki.xensource.com/xenwiki/) - it contains howtos for a bunch of different domU distributions. Cheers -- Andrew Ross IT Officer Whitley College Ph: (03) 9340 8008 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users