Hi, I am trying to launch a VM with xen 3.0.3 but it complains about "Device sda is already connected". I have already mounted my distribution image in the LVM partition /dev/vg1/domSLC4OldRoot and there is a swap partition for that as well. I have also included the xen configuration file! Any ideas? Many thanks Omer ===[root@lcg xen]# xm create SLC4OldScript Using config file "SLC4OldScript". Error: Device sda (2048, vbd) is already connected. [root@lcg xen]# lvscan ACTIVE ''/dev/vg1/domSLC4OldRoot'' [10.00 GB] inherit ACTIVE ''/dev/vg1/domSLC4OldSwap'' [1.00 GB] inherit [root@lcgctb9 xen]# more SLC4OldScript name = "SLC4Old" hostname="M-Ctb-Generic-5" kernel="/boot/vmlinuz-2.6.18-1.2835.slc4xen" memory = 512 #vcpus = 2 disk = [''phy:vg1/domSLC4OldRoot,sda,w'',''phy:vg1/domSLC4OldSwap,sda,w'' ] vif = [ '''' ] ip= "128.xxx.xxx.xxx" gateway="128.xxx.1.1" #bootloader="/usr/bin/pygrub" on_reboot = ''restart'' on_crash = ''restart'' on_poweroff = ''destroy'' --------------------------------------------------------------- CERN – European Organization for Nuclear Research Information Technology Department CH-1211 Geneva 23 Phone: +41 (0) 22 767 7996 Fax: +41 (0) 22 767 4900 E-mail : Omer.Khalid@cern.ch Homepage: http://cern.ch/Omer.Khalid _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Zhang, Thankyou very much for your prompt response. Infact by just updating "disk = [''phy:vg1/domSLC4OldRoot,sda1,w'',''phy:vg1/domSLC4OldSwap,sda2,w'' ]" worked. /etc/fstab with in the domU filesystem did already have /dev/sda1 as / and /dev/sda2 as swap. So "xm create SLC4OldScript -c" stopped complaining, and it starts booting the VM. But then it fails with the following error! ====== last few lines of the VM console output ===== XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2050 XENBUS: Device with no driver: device/vif/0 md: Autodetecting RAID arrays. md: autorun ... md: ... autorun DONE. 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) ====== Cheers Omer _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christopher G. Stach II
2006-Dec-14 14:47 UTC
Re: [Xen-users] Unable to deploy a VM on xen 3.0.3
Omer Khalid wrote:> 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)Did you bother to read the very obvious error messages? -- Christopher G. Stach II _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, 2006-12-14 at 11:45 +0100, Omer Khalid wrote:> > Hi, > > I am trying to launch a VM with xen 3.0.3 but it complains about > "Device sda is already connected". I have already mounted my > distribution image in the LVM partition /dev/vg1/domSLC4OldRoot and > there is a swap partition for that as well. > > I have also included the xen configuration file! > > Any ideas? Many thanksYou may want to re-examine this line of your configuration :> disk > [''phy:vg1/domSLC4OldRoot,sda,w'',''phy:vg1/domSLC4OldSwap,sda,w'' ]You can''t swap to the root file system, nor can one vbd magically become two. Make the root fs sda1, swap sdb1, or something similar.> CERN – European Organization for Nuclear ResearchNow *that* ***really*** frightens me :) Best, -Tim _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thankyou for point it out Tim but I made that change earlier, upon the advice of Zhang, but it still did''t work. Don''t be frightened with the word **Nuclear** in CERN''s name! Cheers OMER On 12/14/06, Tim Post <tim.post@netkinetics.net> wrote:> > On Thu, 2006-12-14 at 11:45 +0100, Omer Khalid wrote: > > > > Hi, > > > > I am trying to launch a VM with xen 3.0.3 but it complains about > > "Device sda is already connected". I have already mounted my > > distribution image in the LVM partition /dev/vg1/domSLC4OldRoot and > > there is a swap partition for that as well. > > > > I have also included the xen configuration file! > > > > Any ideas? Many thanks > > You may want to re-examine this line of your configuration : > > > disk > > [''phy:vg1/domSLC4OldRoot,sda,w'',''phy:vg1/domSLC4OldSwap,sda,w'' ] > > You can''t swap to the root file system, nor can one vbd magically become > two. > > Make the root fs sda1, swap sdb1, or something similar. > > > CERN – European Organization for Nuclear Research > > Now *that* ***really*** frightens me :) > > Best, > -Tim > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >-- --------------------------------------------------------------- CERN – European Organization for Nuclear Research Information Technology Department CH-1211 Geneva 23 Phone: +41 (0) 22 767 7996 Fax: +41 (0) 22 767 4900 E-mail : Omer.Khalid@cern.ch Homepage: http://cern.ch/Omer.Khalid _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
First of all thanks of all of you for your help and advices, especially to mention Zhang Binbin and Mats Peterssons. Status: Still not working! Whats tried so far: * selinux disabled for both dom0 and domU * added "root=''/dev/sda1 ro''" to xen config file. Also tried with xvd1 and hd1 in place of sd1. * created initrd for domU To recap, here is my === xen config file ==name = "slc4xern" hostname="M-Ctb-Generic-5" kernel="/boot/vmlinuz-2.6.18-1.2835.slc4xen" ramdisk="/boot/initrd-2.6.16-xen.img" memory = 512 #vcpus = 2 disk = [''phy:vg1/slc4xernroot,sda1,w'',''phy:vg1/slc4xernswap,sda2,w'' ] root= "/dev/sda1 ro" vif = [ '''' ] ip= "128.xxx.xxx.xxx" gateway="128.xxx.1.1" #bootloader="/usr/bin/pygrub" on_reboot = ''restart'' on_crash = ''restart'' on_poweroff = ''destroy'' === end of config file == When I try to start the domain by "xm create slc4xern -c", the output is the following: === domU console output ==Using config file "/etc/xen/slc4xern". Started domain SLC4Xern Linux version 2.6.18-1.2835.slc4xen (root@lxcert-i386) (gcc version 3.4.620060404 (Red Hat 3.4.6-3)) #1 SMP WedNov 29 21:05:58 CET 2006 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000020800000 (usable) 0MB HIGHMEM available. 520MB LOWMEM available. Using x86 segment limits to approximate NX protection ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 133120 Kernel command line: ip=128.142.200.218:1.2.3.4: 128.142.1.1::M-Ctb-Generic-5:eth0:off root=/dev/sda1 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07d4000 soft=c07b4000 PID hash table entries: 4096 (order: 12, 16384 bytes) Xen reported: 2790.700 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB disabled vmalloc area: e1000000-f4ffe000, maxmem 2d7fe000 Memory: 511232k/532480k available (2071k kernel code, 12640k reserved, 877k data, 184k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 6982.20 BogoMIPS (lpj=13964410) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K Checking ''hlt'' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 12k freed Brought up 1 CPUs checking if image is initramfs... it is Freeing initrd memory: 1507k freed Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled 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 NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 9, 2621440 bytes) TCP bind hash table entries: 65536 (order: 8, 1310720 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com> audit: initializing netlink socket (disabled) audit(1166113570.914:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key EE5FD53744D1DF1C - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Linux version 2.6.18-1.2835.slc4xen (root@lxcert-i386) (gcc version 3.4.620060404 (Red Hat 3.4.6-3)) #1 SMP WedNov 29 21:05:58 CET 2006 BIOS-provided physical RAM map: Xen: 0000000000000000 - 0000000020800000 (usable) 0MB HIGHMEM available. 520MB LOWMEM available. Using x86 segment limits to approximate NX protection ACPI in unprivileged domain disabled Built 1 zonelists. Total pages: 133120 Kernel command line: ip=128.xxx.xxx.xxx:1.2.3.4:128.xxx.1.1::M-Ctb-Generic-5:eth0:off root=/dev/sda1 ro Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Initializing CPU#0 CPU 0 irqstacks, hard=c07d4000 soft=c07b4000 PID hash table entries: 4096 (order: 12, 16384 bytes) Xen reported: 2790.700 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) Software IO TLB disabled vmalloc area: e1000000-f4ffe000, maxmem 2d7fe000 Memory: 511232k/532480k available (2071k kernel code, 12640k reserved, 877k data, 184k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay using timer specific routine.. 6982.20 BogoMIPS (lpj=13964410) Security Framework v1.0.0 initialized SELinux: Initializing. SELinux: Starting in permissive mode selinux_register_security: Registering secondary module capability Capability LSM initialized as secondary Mount-cache hash table entries: 512 CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 512K Checking ''hlt'' instruction... OK. SMP alternatives: switching to UP code Freeing SMP alternatives: 12k freed Brought up 1 CPUs checking if image is initramfs... it is Freeing initrd memory: 1507k freed Grant table initialized NET: Registered protocol family 16 Brought up 1 CPUs PCI: setting up Xen PCI frontend stub ACPI: Interpreter disabled. Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI: disabled 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 NetLabel: Initializing NetLabel: domain hash size = 128 NetLabel: protocols = UNLABELED CIPSOv4 NetLabel: unlabeled traffic allowed by default NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 9, 2621440 bytes) TCP bind hash table entries: 65536 (order: 8, 1310720 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com> audit: initializing netlink socket (disabled) audit(1166113570.914:1): initialized VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) SELinux: Registering netfilter hooks Initializing Cryptographic API ksign: Installing public key data Loading keyring - Added public key EE5FD53744D1DF1C - User ID: Red Hat, Inc. (Kernel Module GPG key) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci_hotplug: PCI Hot Plug PCI Core version: 0.5 rtc: IRQ 8 is not free. Non-volatile memory driver v1.2 Linux agpgart interface v0.101 (c) Dave Jones RAMDISK driver initialized: 16 RAM disks of 16384K size 4096 blocksize Xen virtual console successfully installed as xvc0 Event-channel device installed. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 50MHz system bus speed for PIO modes; override with idebus=xx ide-floppy driver 0.99.newide usbcore: registered new driver libusual usbcore: registered new driver hiddev usbcore: registered new driver usbhid drivers/usb/input/hid-core.c: v2.6:USB HID core driver PNP: No PS/2 controller found. Probing ports directly. i8042.c: No controller found. mice: PS/2 mouse device common for all mice md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27 md: bitmap version 4.39 TCP bic registered Initializing IPsec netlink socket NET: Registered protocol family 1 NET: Registered protocol family 17 Using IPI No-Shortcut mode XENBUS: Device with no driver: device/vbd/2049 XENBUS: Device with no driver: device/vbd/2050 XENBUS: Device with no driver: device/vif/0 Freeing unused kernel memory: 184k freed Write protecting the kernel read-only data: 348k Red Hat nash version starting Mounting proc filesystem Mounting sysfs filesystem Creating /dev Creating initial device nodes mknod: failed to create /dev/ram0: File exists mknod: failed to create /dev/ram1: File exists Setting up hotplug. Creating block device nodes. Loading jbd.ko module Loading ext3.ko module Loading dm-mod.ko module device-mapper: ioctl: 4.7.0-ioctl (2006-06-24) initialised: dm-devel@redhat.com Loading dm-mirror.ko module Loading dm-zero.ko module Loading dm-snapshot.ko module Creating root device. Mounting root filesystem. mount: could not find filesystem ''/dev/root'' Setting up other filesystems. Setting up new root fs setuproot: moving /dev failed: No such file or directory no fstab.sys, mounting internal defaults setuproot: error mounting /proc: No such file or directory setuproot: error mounting /sys: No such file or directory Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - not syncing: Attempted to kill init! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Omer Khalid wrote: Make sure when you try to start it that your LV are not already mounted as you seem to say in your notes. Xen by default cannot export mounted device as far as I know. ++> Thankyou for point it out Tim but I made that change earlier, upon the > advice of Zhang, but it still did''t work. > > Don''t be frightened with the word **Nuclear** in CERN''s name! > > Cheers > OMER > > On 12/14/06, *Tim Post* <tim.post@netkinetics.net > <mailto:tim.post@netkinetics.net>> wrote: > > On Thu, 2006-12-14 at 11:45 +0100, Omer Khalid wrote: > > > > Hi, > > > > I am trying to launch a VM with xen 3.0.3 but it complains about > > "Device sda is already connected". I have already mounted my > > distribution image in the LVM partition /dev/vg1/domSLC4OldRoot and > > there is a swap partition for that as well. > > > > I have also included the xen configuration file! > > > > Any ideas? Many thanks > > You may want to re-examine this line of your configuration : > > > disk > > [''phy:vg1/domSLC4OldRoot,sda,w'',''phy:vg1/domSLC4OldSwap,sda,w'' ] > > You can''t swap to the root file system, nor can one vbd magically > become > two. > > Make the root fs sda1, swap sdb1, or something similar. > > > CERN – European Organization for Nuclear Research > > Now *that* ***really*** frightens me :) > > Best, > -Tim > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com <mailto:Xen-users@lists.xensource.com> > http://lists.xensource.com/xen-users > > > > > -- > --------------------------------------------------------------- > > > CERN – European Organization for Nuclear Research > Information Technology Department > CH-1211 Geneva 23 > > Phone: +41 (0) 22 767 7996 > Fax: +41 (0) 22 767 4900 > E-mail : Omer.Khalid@cern.ch <mailto:Omer.Khalid@cern.ch> > Homepage: http://cern.ch/Omer.Khalid > ------------------------------------------------------------------------ > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users-- Virtual Space International Inc. Steven Dugway USA 206-734-HOST Canada 514-939-HOST (4678) ext 5 -------------------------------------------------------------- Internet Is Here To Stay, Make Sure Your Business Is! -------------------------------------------------------------- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Omer Khalid wrote:> Sure... my lvm partitions are not mounted when I create the vm!Ok. So you have a initrd problem like many many Xen users, the sad story is that there is no easy solution, a bunch of people are working and trying to get it to work, BUT it is intimatly related to linux complex boot process using ramdrives. My only successes so far were with compiling my own kernel, then you face the problem of wjich options to turn on/off and there again, it is a trial and error approach at best which requires tremendous time to do. I made one working under CentOs BUT I now have iptables not working and have NOT yet figure out how to enable it even mu kernels are compile with it. As for people who claim to simply install the REL4 RPMS, well I did it at first BUT they simply don''t boot at all, maybe these folks could post a detailed howto for the exact requirement of the ramdisk for it. Keep us all posted, I am doing around 4-5 compile everyday. Regards,> > Cheers > Omer > > On 12/14/06, *Xen Help* < steven@savetimehosting.net > <mailto:steven@savetimehosting.net>> wrote: > > Omer Khalid wrote: > > Make sure when you try to start it that your LV are not already > mounted > as you seem to say in your notes. > Xen by default cannot export mounted device as far as I know. > > ++ > > Thankyou for point it out Tim but I made that change earlier, > upon the > > advice of Zhang, but it still did''t work. > > > > Don''t be frightened with the word **Nuclear** in CERN''s name! > > > > Cheers > > OMER > > > > On 12/14/06, *Tim Post* <tim.post@netkinetics.net > <mailto:tim.post@netkinetics.net> > > <mailto:tim.post@netkinetics.net > <mailto:tim.post@netkinetics.net>>> wrote: > > > > On Thu, 2006-12-14 at 11:45 +0100, Omer Khalid wrote: > > > > > > Hi, > > > > > > I am trying to launch a VM with xen 3.0.3 but it complains > about > > > "Device sda is already connected". I have already mounted my > > > distribution image in the LVM partition > /dev/vg1/domSLC4OldRoot and > > > there is a swap partition for that as well. > > > > > > I have also included the xen configuration file! > > > > > > Any ideas? Many thanks > > > > You may want to re-examine this line of your configuration : > > > > > disk > > > > [''phy:vg1/domSLC4OldRoot,sda,w'',''phy:vg1/domSLC4OldSwap,sda,w'' ] > > > > You can''t swap to the root file system, nor can one vbd > magically > > become > > two. > > > > Make the root fs sda1, swap sdb1, or something similar. > > > > > CERN – European Organization for Nuclear Research > > > > Now *that* ***really*** frightens me :) > > > > Best, > > -Tim > > > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > <mailto:Xen-users@lists.xensource.com> > <mailto:Xen-users@lists.xensource.com > <mailto:Xen-users@lists.xensource.com>> > > http://lists.xensource.com/xen-users > > > > > > > > > > -- > > --------------------------------------------------------------- > > > > > > CERN – European Organization for Nuclear Research > > Information Technology Department > > CH-1211 Geneva 23 > > > > Phone: +41 (0) 22 767 7996 > > Fax: +41 (0) 22 767 4900 > > E-mail : Omer.Khalid@cern.ch <mailto:Omer.Khalid@cern.ch> > <mailto:Omer.Khalid@cern.ch <mailto:Omer.Khalid@cern.ch>> > > Homepage: http://cern.ch/Omer.Khalid > > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com <mailto:Xen-users@lists.xensource.com> > > http://lists.xensource.com/xen-users > > > -- > Virtual Space International Inc. > Steven Dugway USA 206-734-HOST Canada 514-939-HOST (4678) ext 5 > -------------------------------------------------------------- > Internet Is Here To Stay, Make Sure Your Business Is! > -------------------------------------------------------------- > > > > > -- > --------------------------------------------------------------- > > > CERN – European Organization for Nuclear Research > Information Technology Department > CH-1211 Geneva 23 > > Phone: +41 (0) 22 767 7996 > Fax: +41 (0) 22 767 4900 > E-mail : Omer.Khalid@cern.ch <mailto:Omer.Khalid@cern.ch> > Homepage: http://cern.ch/Omer.Khalid-- Virtual Space International Inc. Steven Dugway USA 206-734-HOST Canada 514-939-HOST (4678) ext 5 Skype:stevenvsi; savetimehosting.net 911hosting.net goodprivacy.net -------------------------------------------------------------- Internet Is Here To Stay, Make Sure Your Business Is! -------------------------------------------------------------- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christopher G. Stach II
2006-Dec-14 18:14 UTC
Re: [Xen-users] Unable to deploy a VM on xen 3.0.3
Omer Khalid wrote:> First of all thanks of all of you for your help and advices, especially > to mention Zhang Binbin and Mats Peterssons. > > Status: Still not working!1. Don''t use an initrd 2. Make sure SCSI is compiled in your kernel if you''re using sd, IDE if you''re using hd. Your output shows IDE being initialized, not SCSI. -- Christopher G. Stach II _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On Thu, 2006-12-14 at 17:36 +0100, Omer Khalid wrote:> mount: could not find filesystem ''/dev/root''Take out your initrd line, use sda1 for the root, sdb1 for swap, and full path to the VBD (i.e. include /dev/) in the disk config line when you specify the lvm backends. It looks like your initrd is broken. proc/real_root_fs is not being carried over by the "root" paramater. Make the initrd from within the dom-u, copy it over to dom-0, then try again. Or, mount and modify the initrd on dom-0 and fix breakage. I''m eliminating 4 or 5 things I see going on that have been problematic for me in the past. Below is each edit to make, as shown in your config : name = "slc4xern" hostname="M-Ctb-Generic-5" kernel="/boot/vmlinuz-2.6.18-1.2835.slc4xen" ramdisk="/boot/initrd-2.6.16-xen.img" <<<<<<<<<< nuke this memory = 512 #vcpus = 2 disk = [''phy:vg1/slc4xernroot,sda1,w'',''phy:vg1/slc4xernswap,sda2,w'' ] ^^^ sdb1 root= "/dev/sda1 ro" vif = [ '''' ] ip= "128.xxx.xxx.xxx" gateway="128.xxx.1.1" #bootloader="/usr/bin/pygrub" on_reboot = ''restart'' on_crash = ''restart'' on_poweroff = ''destroy'' Let me know if this works. Again, you can re-make the initrd from within the dom-u itself once you get it booting. Best, -Tim _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 14 Dec 2006 at 11:28, Xen Help wrote:> Omer Khalid wrote: > > Make sure when you try to start it that your LV are not already mounted > as you seem to say in your notes. > Xen by default cannot export mounted device as far as I know.I guess you''d just have to remove the check for mounted filesystems to enable shredding your filesystem. Regards, Ulrich _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Folks, Thankyou very much for your help. I finally managed to get my SLC4 domU working on xen 3.0.3. Most of you were pointing in the right direction. It have to do something with initrd image. Apparently, for kernel 2.6 one needs extra option for mkinitrd. I created my domU initrd image in the following way: 1) Mounted my domU file system to /mnt 2) chroot /mnt 3) cd /boot 4) mkinitrd --with=xenblk --with=xennet initrd-<version>-xen.img<version>-xen 5) exit 6) copied the new domU initrd to dom0 7) xm create /updated_config_file/ -c And then it worked fine. Many thanks for you help! Cheers Omer -- --------------------------------------------------------------- CERN – European Organization for Nuclear Research Information Technology Department CH-1211 Geneva 23 Phone: +41 (0) 22 767 7996 Fax: +41 (0) 22 767 4900 E-mail : Omer.Khalid@cern.ch Homepage: http://cern.ch/Omer.Khalid _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users