run this commands
1- umount /dev/mapper/vg-lvm1
2- xm create -c vm01.cfg
3- and remove the parameter in fstab for lvm
> Thanks, I tried your suggestion, the results are the same. The system
> seems
> to be unable to find the IDE devices, I am using LVM devices
> IDE device = hde, 60Gb hd
> primary partition = hde1 , volume group = vg, logical volume =
> /dev/vg/lvm1
> which is a pointer to /dev/mapper/vg-lvm1
> When the /dev/vg/lvm1 device is mounted the Xencommand " xm create -c
> vm01.cfg" produces the following error:
>
> # 'local': the device may not be used because it is mounted in the
> current
> # (i.e. the privileged domain) in a way incompatible with the
> # requested mode;
>
> This error is produced by /etc/xen/scripts/block.
> When unmounted the following is shown on the screen:
>
> [root@rhfc401 /]# xm create -c vm01.cfg
> Using config file "/etc/xen/vm01.cfg".
> Started domain vm01
> Linux version 2.6.12.6-xen3_7.1_fc4 ( <mailto:rread@shandlx>
> rread@shandlx)
> (gcc version 4.0.1 20050727 (Red Hat 4.0.1-5)) #1 SMP Tue Dec 13 16:33:43
> PST 2005
> BIOS-provided physical RAM map:
> Xen: 0000000000000000 - 000000001c000000 (usable)
> 0MB HIGHMEM available.
> 456MB LOWMEM available.
> ACPI in unprivileged domain disabled
> IRQ lockup detection disabled
> Built 1 zonelists
> Kernel command line: ip=:1.2.3.4::::eth0:dhcp root=/dev/sda1 ro selinux=0
> 3
> Initializing CPU#0
> PID hash table entries: 2048 (order: 11, 32768 bytes)
> Xen reported: 2171.584 MHz processor.
> Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
> Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
> Software IO TLB disabled
> vmalloc area: dd000000-fb7fe000, maxmem 34000000
> Memory: 449664k/466944k available (2214k kernel code, 8876k reserved, 885k
> data, 188k init, 0k highmem)
> Checking if this processor honours the WP bit even in supervisor mode...
> Ok.
> Security Framework v1.0.0 initialized
> SELinux: Disabled at boot.
> Capability LSM initialized
> Mount-cache hash table entries: 512
> CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
> CPU: L2 Cache: 256K (64 bytes/line)
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... disabled
> Brought up 1 CPUs
> NET: Registered protocol family 16
> Brought up 1 CPUs
> ACPI: Subsystem revision 20050309
> 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: Using ACPI for IRQ routing
> PCI: If a device doesn't work, try "pci=routeirq". If it helps, post a
> report
> PCI: System does not support PCI
> PCI: System does not support PCI
> Grant table initialized
> IA-32 Microcode Update Driver: v1.14-xen < <mailto:tigran@xxxxxxxxxxx>
> tigran@xxxxxxxxxxx>
> VFS: Disk quotas dquot_6.5.1
> Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
> Initializing Cryptographic API
> isapnp: Scanning for PnP cards...
> isapnp: No Plug & Play device found
> PNP: No PS/2 controller found. Probing ports directly.
> i8042.c: No controller found.
> io scheduler noop registered
> io scheduler anticipatory registered
> io scheduler deadline registered
> io scheduler cfq registered
> RAMDISK driver initialized: 16 RAM disks of 16384K size 1024 blocksize
> Xen virtual console successfully installed as tty1
> Event-channel device installed.
> 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 0
> xen_blk: can't get major 0 with name xvd
> Unable to handle kernel NULL pointer dereference at virtual address
> 00000104
> printing eip:
> c023f2f9
> *pde = ma 00000000 pa 55555000
> Oops: 0002 [#1]
> SMP
> Modules linked in:
> CPU: 0
> EIP: 0061:[<c023f2f9>] Not tainted VLI
> EFLAGS: 00010086 (2.6.12.6-xen3_7.1_fc4)
> EIP is at blk_start_queue+0x9/0x50
> eax: 00000000 ebx: 00000000 ecx: fbf7d000 edx: 00000000
> esi: c04f5da0 edi: c04b4000 ebp: c04b5f9c esp: c04b5f30
> ds: 007b es: 007b ss: 0069
> Process xenwatch (pid: 7, threadinfo=c04b4000 task=c1442a80)
> Stack: 00000004 c05ca000 c0258000 00000000 c05ca000 c0257f19 c05ca000
> 00000000
> 00000004 00000000 00000200 c05ca000 c034e6dd c04b5f78 c03566b4
> c034bc96
> c04b5f7c 00000000 00000000 00000200 01b00000 c0252280 c02514f7
> c05ca000
> Call Trace:
> [<c0258000>] kick_pending_request_queues+0x20/0x40
> [<c0257f19>] connect+0xe9/0x130
> [<c0252280>] otherend_changed+0x0/0xa0
> [<c02514f7>] xenwatch_thread+0x87/0x140
> [<c013ba10>] autoremove_wake_function+0x0/0x60
> [<c0251470>] xenwatch_thread+0x0/0x140
> [<c013b4f8>] kthread+0xc8/0xd0
> [<c013b430>] kthread+0x0/0xd0
> [<c0107c3d>] kernel_thread_helper+0x5/0x18
> Code: 00 00 8b 44 24 04 8b 48 60 ff e1 8d b4 26 00 00 00 00 81 44 24 04 a0
> 00 00 00 e9 e3 27 00 00 8d 76 00 53 83 ec 04 8b 5c 24 0c 90 <0f> ba b3 04
> 01
> 00 00 02 90 0f ba ab 04 01 00 00 06 19 c0 85 c0
> <7>Probing IDE interface ide0...
> Probing IDE interface ide1...
> Probing IDE interface ide2...
> Probing IDE interface ide3...
> Probing IDE interface ide4...
> Probing IDE interface ide5...
> ide-floppy driver 0.99.newide
> mice: PS/2 mouse device common for all mice
> NET: Registered protocol family 2
> IP: routing cache hash table of 4096 buckets, 32Kbytes
> TCP established hash table entries: 16384 (order: 5, 131072 bytes)
> TCP bind hash table entries: 16384 (order: 5, 131072 bytes)
> TCP: Hash tables configured (established 16384 bind 16384)
> NET: Registered protocol family 8
> NET: Registered protocol family 20
> 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)
>
>
> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Colin Coe
> Sent: Thursday, December 29, 2005 9:49 PM
> To: seven@xxxxxxxx; xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [Xen-users] Xen 3.0 domain creation issues on fc4
>
>
>
> I'm only a newbie myself but try changing
>
> disk = [ 'phy:/dev/vg/lvm1,sda1,w' ]
>
> to
>
> disk = [ 'phy:vg/lvm1,sda1,w' ]
>
>
>
> CC
>
>
>
>
> _____
>
>
> From: James [mailto:seven@xxxxxxxx]
> Sent: Friday, 30 December 2005 11:29 AM
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] Xen 3.0 domain creation issues on fc4
>
>
>
> I could use some help.
>
>
>
> I made some modifications after reading the list messages in my e-mail
> box.
> I am now getting the following error:
>
> [2005-12-29 20:05:12 xend] DEBUG (blkif:24) exception looking up device
> number for sda1: [Errno 2] No such file or directory: '/dev/sda1'
>
> I also get an error on the screen that /dev/sda1 or /mnt/sda1does not
> exist
> and I need to properly specify the boot parameter.
>
> I get this error when I attempt to use /dev/sda1 or /mnt/sda1; the LVM
> partition will mount successfully with a mount command. I moved it to
> /mnt/sda1 because the os deletes /dev/sda1 on reboot and I have to
> recreate
> it with a mkdir command. When I mount the /mnt/sda1 device and run "xm
> create -c vm01.cfg" I get an error that the domain cannot mount because
> the
> device is in use.
>
>
>
>
>
> FSTAB on the vm01 file system
>
> /mnt/sda1 / 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
>
>
>
> vm01.cfg used to start the domain
>
> kernel = "/boot/vmlinuz-2.6.12.6-xen3_7.1_fc4"
>
> memory = 448
>
> name = "vm01"
>
> nics = 1
>
> disk = [ 'phy:/dev/vg/lvm1,sda1,w' ]
>
> dhcp = "dhcp"
>
> root = "/mnt/sda1"
>
> extra = "ro selinux=0 3
>
>
>
>
>
>
>
>
> ************************************************************************
> Bunnings Legal Disclaimer:
>
> 1) This email is confidential and may contain legally privileged
> information. If you are not the intended recipient, you must not
> disclose or use the information contained in it. If you have received
> this email in error, please notify us immediately by return email and
> delete the document.
>
> 2) All emails sent to and sent from Bunnings Group Limited.
> are scanned for content. Any material deemed to contain inappropriate
> subject matter will be reported to the email administrator of all
> parties concerned.
> ************************************************************************
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home