Zhang Binbin
2006-Dec-10 16:22 UTC
[Xen-users] Why creating DomU failed (seems it is due to LVM)
Hi,
i installed CentOS4_x86_64+Xen-3.0.3 from xen source code and didn''t
encounter any exceptions, but DomU can''t boot up.
i use LVM to management Dom vbd. this is the partition:
---------------------------------------------------
LVM Volume Groups
VolGroup00
LogVol00 Swap
LogVol01 / ext3 Dom0 filesystem
VG_Guests
Dom1 ext3 Dom1 filesystem
Hard Drivers
/dev/sda
/dev/sda1 /boot ext3
/dev/sda2 VolGroup00 LVM PV
/dev/sda3 GuestVG LVM PV
---------------------------------------------------
And i made Dom1 filesystem like this:
---------------------------------------------------
1. mount /dev/GuestVG/Dom1 /mnt
2. cp -ax /{root,etc,dev,sbin,bin,lib,var,usr} /mnt
3. mkdir /mnt/{proc,sys,tmp,home}
4. modify /mnt/etc/fstab and modify eth0 config
5. umount /mnt
---------------------------------------------------
When i create Dom1, it get the following output:
---------------------------------------------------
Using config file "dom1_config".
Started domain Dom1
Bootdata ok (command line is root=/dev/sda1,ro)
Linux version 2.6.16.29-xen (shand@endor) (gcc version 3.4.4 20050314
(prerelease) (Debian 3.4.3-13)) #3 SMP Sun Oct 15 13:15:34 BST 2006
BIOS-provided physical RAM map:
Xen: 0000000000000000 - 0000000010800000 (usable)
No mptable found.
Built 1 zonelists
Kernel command line: root=/dev/sda1,ro
Initializing CPU#0
PID hash table entries: 2048 (order: 11, 65536 bytes)
Xen reported: 1862.323 MHz processor.
Dentry cache hash table entries: 65536 (order: 7, 524288 bytes)
Inode-cache hash table entries: 32768 (order: 6, 262144 bytes)
Software IO TLB disabled
Memory: 248468k/270336k available (1918k kernel code, 13348k reserved, 809k
data, 168k init)
Calibrating delay using timer specific routine.. 3725.91 BogoMIPS (lpj=18629558)
Security Framework v1.0.0 initialized
Capability LSM initialized
Mount-cache hash table entries: 256
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 2048K
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
Brought up 1 CPUs
migration_cost=0
checking if image is initramfs... it is
Freeing initrd memory: 3792k freed
DMI not present or invalid.
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
pnp: PnP ACPI: disabled
xen_mem: Initialising balloon driver.
PCI: System does not support PCI
PCI: System does not support PCI
IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com >
IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
audit: initializing netlink socket (disabled)
audit(1165766218.701:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Initializing Cryptographic API
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
rtc: IRQ 8 is not free.
Non-volatile memory driver v1.2
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
loop: loaded (max 8 devices)
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 8
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
NET: Registered protocol family 2
netfront: device eth0 has flipping receive path.
IP route cache hash table entries: 4096 (order: 3, 32768 bytes)
TCP established hash table entries: 16384 (order: 6, 262144 bytes)
TCP bind hash table entries: 16384 (order: 6, 262144 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
NET: Registered protocol family 1
NET: Registered protocol family 17
Red Hat nash version 4.2.1.8 starting
Mounted /proc filesystem
Mounting sysfs
Creating /dev
Starting udev
Loading scsi_mod.ko module
SCSI subsystem initialized
Loading sd_mod.ko module
register_blkdev: cannot get major 8 for sd
Loading libata.ko module
Loading ahci.ko module
Loading ata_piix.ko module
Loading ide-disk.ko module
Loading dm-mod.ko module
device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com
Loading jbd.ko module
Loading ext3.ko module
Loading dm-mirror.ko module
Loading dm-zero.ko module
Loading dm-snapshot.ko module
Making device-mapper control node
Scanning logical volumes
Reading all physical volumes. This may take a while...
No volume groups found
Activating logical volumes
Volume group "VolGroup00" not found
ERROR: /bin/lvm exited abnormally! (pid 353)
Creating root device
Mounting root filesystem
mount: error 6 mounting ext3
mount: error 2 mounting none
Switching to new root
switchroot: mount failed: 22
umount /initrd/dev failed: 2
Kernel panic - not syncing: Attempted to kill init!
-------------------------------------------------
The Dom1 config file:
-------------------------------------------------
kernel=''/boot/vmlinuz-2.6-xen''
ramdisk=''/boot/initrd-2.6.16.29-xen.img''
memory=256
name=''Dom1''
vif=[''mac=00:AA:00:00:11:12,bridge=xenbr0'']
disk=[''phy:GuestVG/DOM1,/dev/sda1,w'']
root=''/dev/sda1,ro''
-------------------------------------------------
and /var/log/xen/xend.log:
[2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:190)
XendDomainInfo.create([''vm'', [''name'',
''Dom1''], [''memory'', 256],
[''vcpus'', 1], [''image'',
[''linux'', [''kernel'',
''/boot/vmlinuz-2.6-xen''], [''ramdisk'',
''/boot/initrd-2.6.16.29-xen.img''], [''root'',
''/dev/sda1,ro'']]], [''device'',
[''vbd'', [''uname'',
''phy:GuestVG/DOM1''], [''dev'',
''/dev/sda1''], [''mode'',
''w'']]], [''device'', [''vif'',
[''bridge'',
''xenbr0''], [''mac'',
''00:AA:00:00:11:12'']]]])
[2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:296)
parseConfig: config is [''vm'', [''name'',
''Dom1''], [''memory'', 256],
[''vcpus'', 1], [''image'',
[''linux'', [''kernel'',
''/boot/vmlinuz-2.6-xen''], [''ramdisk'',
''/boot/initrd-2.6.16.29-xen.img''], [''root'',
''/dev/sda1,ro'']]], [''device'',
[''vbd'', [''uname'',
''phy:GuestVG/DOM1''], [''dev'',
''/dev/sda1''], [''mode'',
''w'']]], [''device'', [''vif'',
[''bridge'',
''xenbr0''], [''mac'',
''00:AA:00:00:11:12'']]]]
[2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:395)
parseConfig: result is {''shadow_memory'': None,
''uuid'': None,
''on_crash'': None, ''on_reboot'': None,
''localtime'': None, ''image'':
[''linux'', [''kernel'',
''/boot/vmlinuz-2.6-xen''], [''ramdisk'',
''/boot/initrd-2.6.16.29-xen.img''], [''root'',
''/dev/sda1,ro'']], ''on_poweroff'': None,
''bootloader_args'': None, ''cpus'': None,
''name'': ''Dom1'',
''backend'': [], ''vcpus'': 1,
''cpu_weight'': None, ''features'': None,
''vcpu_avail'': None, ''memory'': 256,
''device'': [(''vbd'', [''vbd'',
[''uname'',
''phy:GuestVG/DOM1''], [''dev'',
''/dev/sda1''], [''mode'',
''w'']]), (''vif'', [''vif'',
[''bridge'', ''xenbr0''],
[''mac'', ''00:AA:00:00:11:12'']])],
''bootloader'': None, ''cpu'': None,
''maxmem'': None}
[2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:1253)
XendDomainInfo.construct: None
[2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:1285)
XendDomainInfo.initDomain: 7 1.0
[2006-12-10 23:56:58 xend 4801] DEBUG (balloon:127) Balloon: 262556 KiB free;
need 262144; done.
[2006-12-10 23:56:58 xend 4801] INFO (image:136) buildDomain os=linux dom=7
vcpus=1
[2006-12-10 23:56:58 xend 4801] DEBUG (image:191) dom = 7
[2006-12-10 23:56:58 xend 4801] DEBUG (image:192) image =
/boot/vmlinuz-2.6-xen
[2006-12-10 23:56:58 xend 4801] DEBUG (image:193) store_evtchn = 1
[2006-12-10 23:56:58 xend 4801] DEBUG (image:194) console_evtchn = 2
[2006-12-10 23:56:58 xend 4801] DEBUG (image:195) cmdline =
root=/dev/sda1,ro
[2006-12-10 23:56:58 xend 4801] DEBUG (image:196) ramdisk =
/boot/initrd-2.6.16.29-xen.img
[2006-12-10 23:56:58 xend 4801] DEBUG (image:197) vcpus = 1
[2006-12-10 23:56:58 xend 4801] DEBUG (image:198) features =
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:110) DevController: writing
{''backend-id'': ''0'',
''virtual-device'': ''2049'',
''device-type'': ''disk'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/7/2049''} to
/local/domain/7/device/vbd/2049.
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:112) DevController: writing
{''domain'': ''Dom1'',
''frontend'':
''/local/domain/7/device/vbd/2049'', ''dev'':
''/dev/sda1'', ''state'': ''1'',
''params'': ''GuestVG/DOM1'',
''mode'': ''w'', ''online'':
''1'', ''frontend-id'':
''7'', ''type'': ''phy''} to
/local/domain/0/backend/vbd/7/2049.
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:110) DevController: writing
{''backend-id'': ''0'', ''mac'':
''00:AA:00:00:11:12'', ''handle'':
''0'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vif/7/0''} to
/local/domain/7/device/vif/0.
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:112) DevController: writing
{''bridge'': ''xenbr0'',
''domain'': ''Dom1'',
''handle'': ''0'',
''script'': ''/etc/xen/scripts/vif-bridge'',
''state'': ''1'', ''frontend'':
''/local/domain/7/device/vif/0'', ''mac'':
''00:AA:00:00:11:12'', ''online'':
''1'', ''frontend-id'': ''7''}
to /local/domain/0/backend/vif/7/0.
[2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:712)
Storing VM details: {''shadow_memory'': ''0'',
''uuid'':
''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'',
''on_reboot'': ''restart'',
''start_time'': ''1165766218.22'',
''on_poweroff'': ''destroy'',
''name'': ''Dom1'',
''xend/restart_count'': ''0'',
''vcpus'': ''1'',
''vcpu_avail'': ''1'',
''memory'': ''256'',
''on_crash'': ''restart'',
''image'': "(linux (kernel
/boot/vmlinuz-2.6-xen) (ramdisk /boot/initrd-2.6.16.29-xen.img) (root
''/dev/sda1,ro''))", ''maxmem'':
''256''}
[2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:747)
Storing domain details: {''console/ring-ref'':
''154261'',
''console/port'': ''2'',
''name'': ''Dom1'',
''console/limit'': ''1048576'',
''vm'':
''/vm/e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'',
''domid'': ''7'',
''cpu/0/availability'': ''online'',
''memory/target'': ''262144'',
''store/ring-ref'': ''102647'',
''store/port'': ''1''}
[2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:933)
XendDomainInfo.handleShutdownWatch
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for devices
vif.
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:149) Waiting for 0.
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) hotplugStatusCallback
/local/domain/0/backend/vif/7/0/hotplug-status.
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) hotplugStatusCallback
/local/domain/0/backend/vif/7/0/hotplug-status.
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:478) hotplugStatusCallback
1.
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for devices
usb.
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for devices
vbd.
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:149) Waiting for 2049.
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) hotplugStatusCallback
/local/domain/0/backend/vbd/7/2049/hotplug-status.
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) hotplugStatusCallback
/local/domain/0/backend/vbd/7/2049/hotplug-status.
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:478) hotplugStatusCallback
1.
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for devices
irq.
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for devices
pci.
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for devices
ioports.
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for devices
tap.
[2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for devices
vtpm.
[2006-12-10 23:56:58 xend 4801] INFO (XendDomain:370) Domain Dom1 (7) unpaused.
[2006-12-10 23:56:59 xend.XendDomainInfo 4801] WARNING (XendDomainInfo:875)
Domain has crashed: name=Dom1 id=7.
[2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:1457)
XendDomainInfo.destroyDomain(7)
[2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:190)
XendDomainInfo.create([''domain'', [''domid'',
7], [''uuid'',
''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3''],
[''vcpus'', 1], [''vcpu_avail'', 1],
[''cpu_weight'', 1.0], [''memory'', 256],
[''shadow_memory'', 0],
[''maxmem'', 256], [''features'',
''''], [''name'', ''Dom1''],
[''on_poweroff'', ''destroy''],
[''on_reboot'', ''restart''],
[''on_crash'', ''restart''],
[''image'', [''linux'',
[''kernel'', ''/boot/vmlinuz-2.6-xen''],
[''ramdisk'',
''/boot/initrd-2.6.16.29-xen.img''], [''root'',
''/dev/sda1,ro'']]],
[''device'', [''vif'',
[''backend'', 0], [''script'',
''vif-bridge''], [''bridge'',
''xenbr0''], [''mac'',
''00:AA:00:00:11:12'']]], [''device'',
[''vbd'',
[''backend'', 0], [''dev'',
''/dev/sda1:disk''], [''uname'',
''phy:GuestVG/DOM1''], [''mode'',
''w'']]], [''state'',
''----c-''], [''shutdown_reason'',
''crash''], [''cpu_time'', 0.48078367100000002],
[''online_vcpus'', 1], [''up_time'',
''0.922783136368''], [''start_time'',
''1165766218.22''],
[''store_mfn'', 102647], [''console_mfn'',
154261]])
[2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:296)
parseConfig: config is [''domain'', [''domid'',
7], [''uuid'',
''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3''],
[''vcpus'', 1], [''vcpu_avail'', 1],
[''cpu_weight'', 1.0], [''memory'', 256],
[''shadow_memory'', 0],
[''maxmem'', 256], [''features'',
''''], [''name'', ''Dom1''],
[''on_poweroff'', ''destroy''],
[''on_reboot'', ''restart''],
[''on_crash'', ''restart''],
[''image'', [''linux'',
[''kernel'', ''/boot/vmlinuz-2.6-xen''],
[''ramdisk'',
''/boot/initrd-2.6.16.29-xen.img''], [''root'',
''/dev/sda1,ro'']]],
[''device'', [''vif'',
[''backend'', 0], [''script'',
''vif-bridge''], [''bridge'',
''xenbr0''], [''mac'',
''00:AA:00:00:11:12'']]], [''device'',
[''vbd'',
[''backend'', 0], [''dev'',
''/dev/sda1:disk''], [''uname'',
''phy:GuestVG/DOM1''], [''mode'',
''w'']]], [''state'',
''----c-''], [''shutdown_reason'',
''crash''], [''cpu_time'', 0.48078367100000002],
[''online_vcpus'', 1], [''up_time'',
''0.922783136368''], [''start_time'',
''1165766218.22''],
[''store_mfn'', 102647], [''console_mfn'',
154261]]
[2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:395)
parseConfig: result is {''shadow_memory'': 0,
''uuid'':
''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'',
''on_crash'': ''restart'',
''on_reboot'': ''restart'',
''localtime'': None, ''image'':
[''linux'', [''kernel'',
''/boot/vmlinuz-2.6-xen''], [''ramdisk'',
''/boot/initrd-2.6.16.29-xen.img''], [''root'',
''/dev/sda1,ro'']], ''on_poweroff'':
''destroy'',
''bootloader_args'': None, ''cpus'': None,
''name'': ''Dom1'', ''backend'':
[], ''vcpus'': 1, ''cpu_weight'': 1.0,
''features'': '''',
''vcpu_avail'': 1,
''memory'': 256, ''device'':
[(''vif'', [''vif'',
[''backend'', 0], [''script'',
''vif-bridge''], [''bridge'',
''xenbr0''], [''mac'',
''00:AA:00:00:11:12'']]),
(''vbd'', [''vbd'',
[''backend'', 0], [''dev'',
''/dev/sda1:disk''], [''uname'',
''phy:GuestVG/DOM1''], [''mode'',
''w'']])], ''bootloader'': None,
''cpu'':
None, ''maxmem'': 256}
[2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:1253)
XendDomainInfo.construct: None
[2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:1285)
XendDomainInfo.initDomain: 8 1.0
[2006-12-10 23:56:59 xend 4801] DEBUG (balloon:133) Balloon: 51792 KiB free;
210752 to scrub; need 262144; retries: 20.
[2006-12-10 23:56:59 xend 4801] DEBUG (balloon:141) Balloon: waiting on
scrubbing
[2006-12-10 23:56:59 xend 4801] DEBUG (balloon:127) Balloon: 262556 KiB free;
need 262144; done.
[2006-12-10 23:56:59 xend 4801] INFO (image:136) buildDomain os=linux dom=8
vcpus=1
[2006-12-10 23:56:59 xend 4801] DEBUG (image:191) dom = 8
[2006-12-10 23:56:59 xend 4801] DEBUG (image:192) image =
/boot/vmlinuz-2.6-xen
[2006-12-10 23:56:59 xend 4801] DEBUG (image:193) store_evtchn = 1
[2006-12-10 23:56:59 xend 4801] DEBUG (image:194) console_evtchn = 2
[2006-12-10 23:56:59 xend 4801] DEBUG (image:195) cmdline =
root=/dev/sda1,ro
[2006-12-10 23:56:59 xend 4801] DEBUG (image:196) ramdisk =
/boot/initrd-2.6.16.29-xen.img
[2006-12-10 23:56:59 xend 4801] DEBUG (image:197) vcpus = 1
[2006-12-10 23:56:59 xend 4801] DEBUG (image:198) features =
[2006-12-10 23:56:59 xend 4801] DEBUG (DevController:110) DevController: writing
{''backend-id'': ''0'', ''mac'':
''00:AA:00:00:11:12'', ''handle'':
''0'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vif/8/0''} to
/local/domain/8/device/vif/0.
[2006-12-10 23:56:59 xend 4801] DEBUG (DevController:112) DevController: writing
{''bridge'': ''xenbr0'',
''domain'': ''Dom1'',
''handle'': ''0'',
''script'': ''/etc/xen/scripts/vif-bridge'',
''state'': ''1'', ''frontend'':
''/local/domain/8/device/vif/0'', ''mac'':
''00:AA:00:00:11:12'', ''online'':
''1'', ''frontend-id'': ''8''}
to /local/domain/0/backend/vif/8/0.
[2006-12-10 23:56:59 xend 4801] DEBUG (DevController:110) DevController: writing
{''backend-id'': ''0'',
''virtual-device'': ''2049'',
''device-type'': ''disk'',
''state'': ''1'', ''backend'':
''/local/domain/0/backend/vbd/8/2049''} to
/local/domain/8/device/vbd/2049.
[2006-12-10 23:56:59 xend 4801] DEBUG (DevController:112) DevController: writing
{''domain'': ''Dom1'',
''frontend'':
''/local/domain/8/device/vbd/2049'', ''dev'':
''/dev/sda1'', ''state'': ''1'',
''params'': ''GuestVG/DOM1'',
''mode'': ''w'', ''online'':
''1'', ''frontend-id'':
''8'', ''type'': ''phy''} to
/local/domain/0/backend/vbd/8/2049.
[2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:712)
Storing VM details: {''shadow_memory'': ''0'',
''uuid'':
''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'',
''on_reboot'': ''restart'',
''start_time'': ''1165766219.69'',
''on_poweroff'': ''destroy'',
''name'': ''Dom1'',
''vcpus'': ''1'',
''vcpu_avail'': ''1'',
''memory'': ''256'',
''on_crash'': ''restart'',
''image'': "(linux (kernel /boot/vmlinuz-2.6-xen) (ramdisk
/boot/initrd-2.6.16.29-xen.img) (root ''/dev/sda1,ro''))",
''maxmem'': ''256''}
[2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:747)
Storing domain details: {''console/ring-ref'':
''174838'',
''console/port'': ''2'',
''name'': ''Dom1'',
''console/limit'': ''1048576'',
''vm'':
''/vm/e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'',
''domid'': ''8'',
''cpu/0/availability'': ''online'',
''memory/target'': ''262144'',
''store/ring-ref'': ''174688'',
''store/port'': ''1''}
[2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:933)
XendDomainInfo.handleShutdownWatch
[2006-12-10 23:57:00 xend.XendDomainInfo 4801] WARNING (XendDomainInfo:875)
Domain has crashed: name=Dom1 id=8.
[2006-12-10 23:57:00 xend.XendDomainInfo 4801] ERROR (XendDomainInfo:1661) VM
Dom1 restarting too fast (1.212585 seconds since the last
restart). Refusing to restart to avoid loops.
[2006-12-10 23:57:00 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:1449)
XendDomainInfo.destroy: domid=8
[2006-12-10 23:57:00 xend.XendDomainInfo 4801] DEBUG (XendDomainInfo:1457)
XendDomainInfo.destroyDomain(8)
it seems that it has tried to create dom1 for two times.
THANKS,
sml
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Steven Dugway
2006-Dec-10 17:44 UTC
Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
Zhang Binbin wrote: Hi, I had the exact same problem for months and asked many times over but never got a response, sorry I cannot help you. I know many people who are switching to Vmware as a result. No real doc and no support. ++> Hi, > i installed CentOS4_x86_64+Xen-3.0.3 from xen source code and didn''t > encounter any exceptions, but DomU can''t boot up. > i use LVM to management Dom vbd. this is the partition: > --------------------------------------------------- > LVM Volume Groups > VolGroup00 > LogVol00 Swap > LogVol01 / ext3 Dom0 filesystem > VG_Guests > Dom1 ext3 Dom1 filesystem > Hard Drivers > /dev/sda > /dev/sda1 /boot ext3 > /dev/sda2 VolGroup00 LVM PV > /dev/sda3 GuestVG LVM PV > --------------------------------------------------- > And i made Dom1 filesystem like this: > --------------------------------------------------- > 1. mount /dev/GuestVG/Dom1 /mnt > 2. cp -ax /{root,etc,dev,sbin,bin,lib,var,usr} /mnt > 3. mkdir /mnt/{proc,sys,tmp,home} > 4. modify /mnt/etc/fstab and modify eth0 config > 5. umount /mnt > --------------------------------------------------- > When i create Dom1, it get the following output: > --------------------------------------------------- > Using config file "dom1_config". > Started domain Dom1 > Bootdata ok (command line is root=/dev/sda1,ro) > Linux version 2.6.16.29-xen (shand@endor) (gcc version 3.4.4 20050314 > (prerelease) (Debian 3.4.3-13)) #3 SMP Sun Oct 15 13:15:34 BST 2006 > BIOS-provided physical RAM map: > Xen: 0000000000000000 - 0000000010800000 (usable) > No mptable found. > Built 1 zonelists > Kernel command line: root=/dev/sda1,ro > Initializing CPU#0 > PID hash table entries: 2048 (order: 11, 65536 bytes) > Xen reported: 1862.323 MHz processor. > Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) > Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) > Software IO TLB disabled > Memory: 248468k/270336k available (1918k kernel code, 13348k reserved, > 809k data, 168k init) > Calibrating delay using timer specific routine.. 3725.91 BogoMIPS > (lpj=18629558) > Security Framework v1.0.0 initialized > Capability LSM initialized > Mount-cache hash table entries: 256 > CPU: L1 I cache: 32K, L1 D cache: 32K > CPU: L2 cache: 2048K > CPU: Physical Processor ID: 0 > CPU: Processor Core ID: 0 > Brought up 1 CPUs > migration_cost=0 > checking if image is initramfs... it is > Freeing initrd memory: 3792k freed > DMI not present or invalid. > 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 > pnp: PnP ACPI: disabled > xen_mem: Initialising balloon driver. > PCI: System does not support PCI > PCI: System does not support PCI > IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com > > IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $ > audit: initializing netlink socket (disabled) > audit(1165766218.701:1): initialized > VFS: Disk quotas dquot_6.5.1 > Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > Initializing Cryptographic API > io scheduler noop registered > io scheduler anticipatory registered > io scheduler deadline registered > io scheduler cfq registered (default) > rtc: IRQ 8 is not free. > Non-volatile memory driver v1.2 > 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 > loop: loaded (max 8 devices) > 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 8 > 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 > NET: Registered protocol family 2 > netfront: device eth0 has flipping receive path. > IP route cache hash table entries: 4096 (order: 3, 32768 bytes) > TCP established hash table entries: 16384 (order: 6, 262144 bytes) > TCP bind hash table entries: 16384 (order: 6, 262144 bytes) > TCP: Hash tables configured (established 16384 bind 16384) > TCP reno registered > NET: Registered protocol family 1 > NET: Registered protocol family 17 > Red Hat nash version 4.2.1.8 starting > Mounted /proc filesystem > Mounting sysfs > Creating /dev > Starting udev > Loading scsi_mod.ko module > SCSI subsystem initialized > Loading sd_mod.ko module > register_blkdev: cannot get major 8 for sd > Loading libata.ko module > Loading ahci.ko module > Loading ata_piix.ko module > Loading ide-disk.ko module > Loading dm-mod.ko module > device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com > Loading jbd.ko module > Loading ext3.ko module > Loading dm-mirror.ko module > Loading dm-zero.ko module > Loading dm-snapshot.ko module > Making device-mapper control node > Scanning logical volumes > Reading all physical volumes. This may take a while... > No volume groups found > Activating logical volumes > Volume group "VolGroup00" not found > ERROR: /bin/lvm exited abnormally! (pid 353) > Creating root device > Mounting root filesystem > mount: error 6 mounting ext3 > mount: error 2 mounting none > Switching to new root > switchroot: mount failed: 22 > umount /initrd/dev failed: 2 > Kernel panic - not syncing: Attempted to kill init! > ------------------------------------------------- > The Dom1 config file: > ------------------------------------------------- > kernel=''/boot/vmlinuz-2.6-xen'' > ramdisk=''/boot/initrd-2.6.16.29-xen.img'' > memory=256 > name=''Dom1'' > vif=[''mac=00:AA:00:00:11:12,bridge=xenbr0''] > disk=[''phy:GuestVG/DOM1,/dev/sda1,w''] > root=''/dev/sda1,ro'' > ------------------------------------------------- > and /var/log/xen/xend.log: > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:190) XendDomainInfo.create([''vm'', [''name'', ''Dom1''], > [''memory'', 256], > [''vcpus'', 1], [''image'', [''linux'', [''kernel'', ''/boot/vmlinuz-2.6-xen''], > [''ramdisk'', ''/boot/initrd-2.6.16.29-xen.img''], [''root'', > ''/dev/sda1,ro'']]], [''device'', [''vbd'', [''uname'', ''phy:GuestVG/DOM1''], > [''dev'', ''/dev/sda1''], [''mode'', ''w'']]], [''device'', [''vif'', [''bridge'', > ''xenbr0''], [''mac'', ''00:AA:00:00:11:12'']]]]) > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:296) parseConfig: config is [''vm'', [''name'', ''Dom1''], > [''memory'', 256], > [''vcpus'', 1], [''image'', [''linux'', [''kernel'', ''/boot/vmlinuz-2.6-xen''], > [''ramdisk'', ''/boot/initrd-2.6.16.29-xen.img''], [''root'', > ''/dev/sda1,ro'']]], [''device'', [''vbd'', [''uname'', ''phy:GuestVG/DOM1''], > [''dev'', ''/dev/sda1''], [''mode'', ''w'']]], [''device'', [''vif'', [''bridge'', > ''xenbr0''], [''mac'', ''00:AA:00:00:11:12'']]]] > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:395) parseConfig: result is {''shadow_memory'': None, > ''uuid'': None, > ''on_crash'': None, ''on_reboot'': None, ''localtime'': None, ''image'': > [''linux'', [''kernel'', ''/boot/vmlinuz-2.6-xen''], [''ramdisk'', > ''/boot/initrd-2.6.16.29-xen.img''], [''root'', ''/dev/sda1,ro'']], > ''on_poweroff'': None, ''bootloader_args'': None, ''cpus'': None, ''name'': > ''Dom1'', > ''backend'': [], ''vcpus'': 1, ''cpu_weight'': None, ''features'': None, > ''vcpu_avail'': None, ''memory'': 256, ''device'': [(''vbd'', [''vbd'', [''uname'', > ''phy:GuestVG/DOM1''], [''dev'', ''/dev/sda1''], [''mode'', ''w'']]), (''vif'', > [''vif'', [''bridge'', ''xenbr0''], [''mac'', ''00:AA:00:00:11:12'']])], > ''bootloader'': None, ''cpu'': None, ''maxmem'': None} > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:1253) XendDomainInfo.construct: None > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:1285) XendDomainInfo.initDomain: 7 1.0 > [2006-12-10 23:56:58 xend 4801] DEBUG (balloon:127) Balloon: 262556 > KiB free; need 262144; done. > [2006-12-10 23:56:58 xend 4801] INFO (image:136) buildDomain os=linux > dom=7 vcpus=1 > [2006-12-10 23:56:58 xend 4801] DEBUG (image:191) dom = 7 > [2006-12-10 23:56:58 xend 4801] DEBUG (image:192) image = > /boot/vmlinuz-2.6-xen > [2006-12-10 23:56:58 xend 4801] DEBUG (image:193) store_evtchn = 1 > [2006-12-10 23:56:58 xend 4801] DEBUG (image:194) console_evtchn = 2 > [2006-12-10 23:56:58 xend 4801] DEBUG (image:195) cmdline = > root=/dev/sda1,ro > [2006-12-10 23:56:58 xend 4801] DEBUG (image:196) ramdisk = > /boot/initrd-2.6.16.29-xen.img > [2006-12-10 23:56:58 xend 4801] DEBUG (image:197) vcpus = 1 > [2006-12-10 23:56:58 xend 4801] DEBUG (image:198) features > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:110) > DevController: writing {''backend-id'': ''0'', ''virtual-device'': ''2049'', > ''device-type'': ''disk'', ''state'': ''1'', ''backend'': > ''/local/domain/0/backend/vbd/7/2049''} to /local/domain/7/device/vbd/2049. > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:112) > DevController: writing {''domain'': ''Dom1'', ''frontend'': > ''/local/domain/7/device/vbd/2049'', ''dev'': ''/dev/sda1'', ''state'': ''1'', > ''params'': ''GuestVG/DOM1'', ''mode'': ''w'', ''online'': ''1'', ''frontend-id'': > ''7'', ''type'': ''phy''} to /local/domain/0/backend/vbd/7/2049. > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:110) > DevController: writing {''backend-id'': ''0'', ''mac'': ''00:AA:00:00:11:12'', > ''handle'': > ''0'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vif/7/0''} to > /local/domain/7/device/vif/0. > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:112) > DevController: writing {''bridge'': ''xenbr0'', ''domain'': ''Dom1'', > ''handle'': ''0'', > ''script'': ''/etc/xen/scripts/vif-bridge'', ''state'': ''1'', ''frontend'': > ''/local/domain/7/device/vif/0'', ''mac'': ''00:AA:00:00:11:12'', ''online'': > ''1'', ''frontend-id'': ''7''} to /local/domain/0/backend/vif/7/0. > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:712) Storing VM details: {''shadow_memory'': ''0'', ''uuid'': > ''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'', ''on_reboot'': ''restart'', > ''start_time'': ''1165766218.22'', ''on_poweroff'': ''destroy'', ''name'': ''Dom1'', > ''xend/restart_count'': ''0'', ''vcpus'': ''1'', ''vcpu_avail'': ''1'', ''memory'': > ''256'', ''on_crash'': ''restart'', ''image'': "(linux (kernel > /boot/vmlinuz-2.6-xen) (ramdisk /boot/initrd-2.6.16.29-xen.img) (root > ''/dev/sda1,ro''))", ''maxmem'': ''256''} > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:747) Storing domain details: {''console/ring-ref'': > ''154261'', > ''console/port'': ''2'', ''name'': ''Dom1'', ''console/limit'': ''1048576'', ''vm'': > ''/vm/e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'', ''domid'': ''7'', > ''cpu/0/availability'': ''online'', ''memory/target'': ''262144'', > ''store/ring-ref'': ''102647'', ''store/port'': ''1''} > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:933) XendDomainInfo.handleShutdownWatch > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for > devices vif. > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:149) Waiting for 0. > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) > hotplugStatusCallback /local/domain/0/backend/vif/7/0/hotplug-status. > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) > hotplugStatusCallback /local/domain/0/backend/vif/7/0/hotplug-status. > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:478) > hotplugStatusCallback 1. > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for > devices usb. > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for > devices vbd. > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:149) Waiting for > 2049. > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) > hotplugStatusCallback /local/domain/0/backend/vbd/7/2049/hotplug-status. > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) > hotplugStatusCallback /local/domain/0/backend/vbd/7/2049/hotplug-status. > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:478) > hotplugStatusCallback 1. > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for > devices irq. > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for > devices pci. > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for > devices ioports. > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for > devices tap. > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for > devices vtpm. > [2006-12-10 23:56:58 xend 4801] INFO (XendDomain:370) Domain Dom1 (7) > unpaused. > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] WARNING > (XendDomainInfo:875) Domain has crashed: name=Dom1 id=7. > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:1457) XendDomainInfo.destroyDomain(7) > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:190) XendDomainInfo.create([''domain'', [''domid'', 7], > [''uuid'', > ''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3''], [''vcpus'', 1], [''vcpu_avail'', > 1], [''cpu_weight'', 1.0], [''memory'', 256], [''shadow_memory'', 0], > [''maxmem'', 256], [''features'', ''''], [''name'', ''Dom1''], [''on_poweroff'', > ''destroy''], [''on_reboot'', ''restart''], [''on_crash'', ''restart''], > [''image'', [''linux'', [''kernel'', ''/boot/vmlinuz-2.6-xen''], [''ramdisk'', > ''/boot/initrd-2.6.16.29-xen.img''], [''root'', ''/dev/sda1,ro'']]], > [''device'', [''vif'', [''backend'', 0], [''script'', ''vif-bridge''], > [''bridge'', ''xenbr0''], [''mac'', ''00:AA:00:00:11:12'']]], [''device'', [''vbd'', > [''backend'', 0], [''dev'', ''/dev/sda1:disk''], [''uname'', > ''phy:GuestVG/DOM1''], [''mode'', ''w'']]], [''state'', ''----c-''], > [''shutdown_reason'', > ''crash''], [''cpu_time'', 0.48078367100000002], [''online_vcpus'', 1], > [''up_time'', ''0.922783136368''], [''start_time'', ''1165766218.22''], > [''store_mfn'', 102647], [''console_mfn'', 154261]]) > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:296) parseConfig: config is [''domain'', [''domid'', 7], > [''uuid'', > ''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3''], [''vcpus'', 1], [''vcpu_avail'', > 1], [''cpu_weight'', 1.0], [''memory'', 256], [''shadow_memory'', 0], > [''maxmem'', 256], [''features'', ''''], [''name'', ''Dom1''], [''on_poweroff'', > ''destroy''], [''on_reboot'', ''restart''], [''on_crash'', ''restart''], > [''image'', [''linux'', [''kernel'', ''/boot/vmlinuz-2.6-xen''], [''ramdisk'', > ''/boot/initrd-2.6.16.29-xen.img''], [''root'', ''/dev/sda1,ro'']]], > [''device'', [''vif'', [''backend'', 0], [''script'', ''vif-bridge''], > [''bridge'', ''xenbr0''], [''mac'', ''00:AA:00:00:11:12'']]], [''device'', [''vbd'', > [''backend'', 0], [''dev'', ''/dev/sda1:disk''], [''uname'', > ''phy:GuestVG/DOM1''], [''mode'', ''w'']]], [''state'', ''----c-''], > [''shutdown_reason'', > ''crash''], [''cpu_time'', 0.48078367100000002], [''online_vcpus'', 1], > [''up_time'', ''0.922783136368''], [''start_time'', ''1165766218.22''], > [''store_mfn'', 102647], [''console_mfn'', 154261]] > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:395) parseConfig: result is {''shadow_memory'': 0, ''uuid'': > ''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'', ''on_crash'': ''restart'', > ''on_reboot'': ''restart'', ''localtime'': None, ''image'': [''linux'', [''kernel'', > ''/boot/vmlinuz-2.6-xen''], [''ramdisk'', > ''/boot/initrd-2.6.16.29-xen.img''], [''root'', ''/dev/sda1,ro'']], > ''on_poweroff'': ''destroy'', > ''bootloader_args'': None, ''cpus'': None, ''name'': ''Dom1'', ''backend'': [], > ''vcpus'': 1, ''cpu_weight'': 1.0, ''features'': '''', ''vcpu_avail'': 1, > ''memory'': 256, ''device'': [(''vif'', [''vif'', [''backend'', 0], [''script'', > ''vif-bridge''], [''bridge'', ''xenbr0''], [''mac'', ''00:AA:00:00:11:12'']]), > (''vbd'', [''vbd'', [''backend'', 0], [''dev'', ''/dev/sda1:disk''], [''uname'', > ''phy:GuestVG/DOM1''], [''mode'', ''w'']])], ''bootloader'': None, ''cpu'': > None, ''maxmem'': 256} > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:1253) XendDomainInfo.construct: None > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:1285) XendDomainInfo.initDomain: 8 1.0 > [2006-12-10 23:56:59 xend 4801] DEBUG (balloon:133) Balloon: 51792 KiB > free; 210752 to scrub; need 262144; retries: 20. > [2006-12-10 23:56:59 xend 4801] DEBUG (balloon:141) Balloon: waiting > on scrubbing > [2006-12-10 23:56:59 xend 4801] DEBUG (balloon:127) Balloon: 262556 > KiB free; need 262144; done. > [2006-12-10 23:56:59 xend 4801] INFO (image:136) buildDomain os=linux > dom=8 vcpus=1 > [2006-12-10 23:56:59 xend 4801] DEBUG (image:191) dom = 8 > [2006-12-10 23:56:59 xend 4801] DEBUG (image:192) image = > /boot/vmlinuz-2.6-xen > [2006-12-10 23:56:59 xend 4801] DEBUG (image:193) store_evtchn = 1 > [2006-12-10 23:56:59 xend 4801] DEBUG (image:194) console_evtchn = 2 > [2006-12-10 23:56:59 xend 4801] DEBUG (image:195) cmdline = > root=/dev/sda1,ro > [2006-12-10 23:56:59 xend 4801] DEBUG (image:196) ramdisk = > /boot/initrd-2.6.16.29-xen.img > [2006-12-10 23:56:59 xend 4801] DEBUG (image:197) vcpus = 1 > [2006-12-10 23:56:59 xend 4801] DEBUG (image:198) features > [2006-12-10 23:56:59 xend 4801] DEBUG (DevController:110) > DevController: writing {''backend-id'': ''0'', ''mac'': ''00:AA:00:00:11:12'', > ''handle'': > ''0'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vif/8/0''} to > /local/domain/8/device/vif/0. > [2006-12-10 23:56:59 xend 4801] DEBUG (DevController:112) > DevController: writing {''bridge'': ''xenbr0'', ''domain'': ''Dom1'', > ''handle'': ''0'', > ''script'': ''/etc/xen/scripts/vif-bridge'', ''state'': ''1'', ''frontend'': > ''/local/domain/8/device/vif/0'', ''mac'': ''00:AA:00:00:11:12'', ''online'': > ''1'', ''frontend-id'': ''8''} to /local/domain/0/backend/vif/8/0. > [2006-12-10 23:56:59 xend 4801] DEBUG (DevController:110) > DevController: writing {''backend-id'': ''0'', ''virtual-device'': ''2049'', > ''device-type'': ''disk'', ''state'': ''1'', ''backend'': > ''/local/domain/0/backend/vbd/8/2049''} to /local/domain/8/device/vbd/2049. > [2006-12-10 23:56:59 xend 4801] DEBUG (DevController:112) > DevController: writing {''domain'': ''Dom1'', ''frontend'': > ''/local/domain/8/device/vbd/2049'', ''dev'': ''/dev/sda1'', ''state'': ''1'', > ''params'': ''GuestVG/DOM1'', ''mode'': ''w'', ''online'': ''1'', ''frontend-id'': > ''8'', ''type'': ''phy''} to /local/domain/0/backend/vbd/8/2049. > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:712) Storing VM details: {''shadow_memory'': ''0'', ''uuid'': > ''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'', ''on_reboot'': ''restart'', > ''start_time'': ''1165766219.69'', ''on_poweroff'': ''destroy'', ''name'': ''Dom1'', > ''vcpus'': ''1'', ''vcpu_avail'': ''1'', ''memory'': ''256'', ''on_crash'': > ''restart'', ''image'': "(linux (kernel /boot/vmlinuz-2.6-xen) (ramdisk > /boot/initrd-2.6.16.29-xen.img) (root ''/dev/sda1,ro''))", ''maxmem'': ''256''} > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:747) Storing domain details: {''console/ring-ref'': > ''174838'', > ''console/port'': ''2'', ''name'': ''Dom1'', ''console/limit'': ''1048576'', ''vm'': > ''/vm/e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'', ''domid'': ''8'', > ''cpu/0/availability'': ''online'', ''memory/target'': ''262144'', > ''store/ring-ref'': ''174688'', ''store/port'': ''1''} > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:933) XendDomainInfo.handleShutdownWatch > [2006-12-10 23:57:00 xend.XendDomainInfo 4801] WARNING > (XendDomainInfo:875) Domain has crashed: name=Dom1 id=8. > [2006-12-10 23:57:00 xend.XendDomainInfo 4801] ERROR > (XendDomainInfo:1661) VM Dom1 restarting too fast (1.212585 seconds > since the last > restart). Refusing to restart to avoid loops. > [2006-12-10 23:57:00 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:1449) XendDomainInfo.destroy: domid=8 > [2006-12-10 23:57:00 xend.XendDomainInfo 4801] DEBUG > (XendDomainInfo:1457) XendDomainInfo.destroyDomain(8) > it seems that it has tried to create dom1 for two times. > THANKS, > sml > ------------------------------------------------------------------------ > > _______________________________________________ > 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 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
TMC
2006-Dec-10 20:01 UTC
Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
can you please post your config here? I suspect that your trying to start LVM configuration from Dom0 in DomU... There are two ways to do things. a) put all disk in Dom0 under LVM and manage disk for all DomU instances that way.. or b) put several disks into DomU and runb LVM in DomU Which is the one youre trying to do? Regards Tomasz On 11/12/06, Steven Dugway <steven@savetimehosting.net> wrote:> Zhang Binbin wrote: > > Hi, > > I had the exact same problem for months and asked many times over but > never got a response, sorry I cannot help you. I know many people who > are switching to Vmware as a result. No real doc and no support. > > ++ > > Hi, > > i installed CentOS4_x86_64+Xen-3.0.3 from xen source code and didn''t > > encounter any exceptions, but DomU can''t boot up. > > i use LVM to management Dom vbd. this is the partition: > > --------------------------------------------------- > > LVM Volume Groups > > VolGroup00 > > LogVol00 Swap > > LogVol01 / ext3 Dom0 filesystem > > VG_Guests > > Dom1 ext3 Dom1 filesystem > > Hard Drivers > > /dev/sda > > /dev/sda1 /boot ext3 > > /dev/sda2 VolGroup00 LVM PV > > /dev/sda3 GuestVG LVM PV > > --------------------------------------------------- > > And i made Dom1 filesystem like this: > > --------------------------------------------------- > > 1. mount /dev/GuestVG/Dom1 /mnt > > 2. cp -ax /{root,etc,dev,sbin,bin,lib,var,usr} /mnt > > 3. mkdir /mnt/{proc,sys,tmp,home} > > 4. modify /mnt/etc/fstab and modify eth0 config > > 5. umount /mnt > > --------------------------------------------------- > > When i create Dom1, it get the following output: > > --------------------------------------------------- > > Using config file "dom1_config". > > Started domain Dom1 > > Bootdata ok (command line is root=/dev/sda1,ro) > > Linux version 2.6.16.29-xen (shand@endor) (gcc version 3.4.4 20050314 > > (prerelease) (Debian 3.4.3-13)) #3 SMP Sun Oct 15 13:15:34 BST 2006 > > BIOS-provided physical RAM map: > > Xen: 0000000000000000 - 0000000010800000 (usable) > > No mptable found. > > Built 1 zonelists > > Kernel command line: root=/dev/sda1,ro > > Initializing CPU#0 > > PID hash table entries: 2048 (order: 11, 65536 bytes) > > Xen reported: 1862.323 MHz processor. > > Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) > > Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) > > Software IO TLB disabled > > Memory: 248468k/270336k available (1918k kernel code, 13348k reserved, > > 809k data, 168k init) > > Calibrating delay using timer specific routine.. 3725.91 BogoMIPS > > (lpj=18629558) > > Security Framework v1.0.0 initialized > > Capability LSM initialized > > Mount-cache hash table entries: 256 > > CPU: L1 I cache: 32K, L1 D cache: 32K > > CPU: L2 cache: 2048K > > CPU: Physical Processor ID: 0 > > CPU: Processor Core ID: 0 > > Brought up 1 CPUs > > migration_cost=0 > > checking if image is initramfs... it is > > Freeing initrd memory: 3792k freed > > DMI not present or invalid. > > 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 > > pnp: PnP ACPI: disabled > > xen_mem: Initialising balloon driver. > > PCI: System does not support PCI > > PCI: System does not support PCI > > IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com > > > IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $ > > audit: initializing netlink socket (disabled) > > audit(1165766218.701:1): initialized > > VFS: Disk quotas dquot_6.5.1 > > Dquot-cache hash table entries: 512 (order 0, 4096 bytes) > > Initializing Cryptographic API > > io scheduler noop registered > > io scheduler anticipatory registered > > io scheduler deadline registered > > io scheduler cfq registered (default) > > rtc: IRQ 8 is not free. > > Non-volatile memory driver v1.2 > > 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 > > loop: loaded (max 8 devices) > > 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 8 > > 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 > > NET: Registered protocol family 2 > > netfront: device eth0 has flipping receive path. > > IP route cache hash table entries: 4096 (order: 3, 32768 bytes) > > TCP established hash table entries: 16384 (order: 6, 262144 bytes) > > TCP bind hash table entries: 16384 (order: 6, 262144 bytes) > > TCP: Hash tables configured (established 16384 bind 16384) > > TCP reno registered > > NET: Registered protocol family 1 > > NET: Registered protocol family 17 > > Red Hat nash version 4.2.1.8 starting > > Mounted /proc filesystem > > Mounting sysfs > > Creating /dev > > Starting udev > > Loading scsi_mod.ko module > > SCSI subsystem initialized > > Loading sd_mod.ko module > > register_blkdev: cannot get major 8 for sd > > Loading libata.ko module > > Loading ahci.ko module > > Loading ata_piix.ko module > > Loading ide-disk.ko module > > Loading dm-mod.ko module > > device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com > > Loading jbd.ko module > > Loading ext3.ko module > > Loading dm-mirror.ko module > > Loading dm-zero.ko module > > Loading dm-snapshot.ko module > > Making device-mapper control node > > Scanning logical volumes > > Reading all physical volumes. This may take a while... > > No volume groups found > > Activating logical volumes > > Volume group "VolGroup00" not found > > ERROR: /bin/lvm exited abnormally! (pid 353) > > Creating root device > > Mounting root filesystem > > mount: error 6 mounting ext3 > > mount: error 2 mounting none > > Switching to new root > > switchroot: mount failed: 22 > > umount /initrd/dev failed: 2 > > Kernel panic - not syncing: Attempted to kill init! > > ------------------------------------------------- > > The Dom1 config file: > > ------------------------------------------------- > > kernel=''/boot/vmlinuz-2.6-xen'' > > ramdisk=''/boot/initrd-2.6.16.29-xen.img'' > > memory=256 > > name=''Dom1'' > > vif=[''mac=00:AA:00:00:11:12,bridge=xenbr0''] > > disk=[''phy:GuestVG/DOM1,/dev/sda1,w''] > > root=''/dev/sda1,ro'' > > ------------------------------------------------- > > and /var/log/xen/xend.log: > > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:190) XendDomainInfo.create([''vm'', [''name'', ''Dom1''], > > [''memory'', 256], > > [''vcpus'', 1], [''image'', [''linux'', [''kernel'', ''/boot/vmlinuz-2.6-xen''], > > [''ramdisk'', ''/boot/initrd-2.6.16.29-xen.img''], [''root'', > > ''/dev/sda1,ro'']]], [''device'', [''vbd'', [''uname'', ''phy:GuestVG/DOM1''], > > [''dev'', ''/dev/sda1''], [''mode'', ''w'']]], [''device'', [''vif'', [''bridge'', > > ''xenbr0''], [''mac'', ''00:AA:00:00:11:12'']]]]) > > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:296) parseConfig: config is [''vm'', [''name'', ''Dom1''], > > [''memory'', 256], > > [''vcpus'', 1], [''image'', [''linux'', [''kernel'', ''/boot/vmlinuz-2.6-xen''], > > [''ramdisk'', ''/boot/initrd-2.6.16.29-xen.img''], [''root'', > > ''/dev/sda1,ro'']]], [''device'', [''vbd'', [''uname'', ''phy:GuestVG/DOM1''], > > [''dev'', ''/dev/sda1''], [''mode'', ''w'']]], [''device'', [''vif'', [''bridge'', > > ''xenbr0''], [''mac'', ''00:AA:00:00:11:12'']]]] > > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:395) parseConfig: result is {''shadow_memory'': None, > > ''uuid'': None, > > ''on_crash'': None, ''on_reboot'': None, ''localtime'': None, ''image'': > > [''linux'', [''kernel'', ''/boot/vmlinuz-2.6-xen''], [''ramdisk'', > > ''/boot/initrd-2.6.16.29-xen.img''], [''root'', ''/dev/sda1,ro'']], > > ''on_poweroff'': None, ''bootloader_args'': None, ''cpus'': None, ''name'': > > ''Dom1'', > > ''backend'': [], ''vcpus'': 1, ''cpu_weight'': None, ''features'': None, > > ''vcpu_avail'': None, ''memory'': 256, ''device'': [(''vbd'', [''vbd'', [''uname'', > > ''phy:GuestVG/DOM1''], [''dev'', ''/dev/sda1''], [''mode'', ''w'']]), (''vif'', > > [''vif'', [''bridge'', ''xenbr0''], [''mac'', ''00:AA:00:00:11:12'']])], > > ''bootloader'': None, ''cpu'': None, ''maxmem'': None} > > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:1253) XendDomainInfo.construct: None > > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:1285) XendDomainInfo.initDomain: 7 1.0 > > [2006-12-10 23:56:58 xend 4801] DEBUG (balloon:127) Balloon: 262556 > > KiB free; need 262144; done. > > [2006-12-10 23:56:58 xend 4801] INFO (image:136) buildDomain os=linux > > dom=7 vcpus=1 > > [2006-12-10 23:56:58 xend 4801] DEBUG (image:191) dom = 7 > > [2006-12-10 23:56:58 xend 4801] DEBUG (image:192) image > > /boot/vmlinuz-2.6-xen > > [2006-12-10 23:56:58 xend 4801] DEBUG (image:193) store_evtchn = 1 > > [2006-12-10 23:56:58 xend 4801] DEBUG (image:194) console_evtchn = 2 > > [2006-12-10 23:56:58 xend 4801] DEBUG (image:195) cmdline > > root=/dev/sda1,ro > > [2006-12-10 23:56:58 xend 4801] DEBUG (image:196) ramdisk > > /boot/initrd-2.6.16.29-xen.img > > [2006-12-10 23:56:58 xend 4801] DEBUG (image:197) vcpus = 1 > > [2006-12-10 23:56:58 xend 4801] DEBUG (image:198) features > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:110) > > DevController: writing {''backend-id'': ''0'', ''virtual-device'': ''2049'', > > ''device-type'': ''disk'', ''state'': ''1'', ''backend'': > > ''/local/domain/0/backend/vbd/7/2049''} to /local/domain/7/device/vbd/2049. > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:112) > > DevController: writing {''domain'': ''Dom1'', ''frontend'': > > ''/local/domain/7/device/vbd/2049'', ''dev'': ''/dev/sda1'', ''state'': ''1'', > > ''params'': ''GuestVG/DOM1'', ''mode'': ''w'', ''online'': ''1'', ''frontend-id'': > > ''7'', ''type'': ''phy''} to /local/domain/0/backend/vbd/7/2049. > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:110) > > DevController: writing {''backend-id'': ''0'', ''mac'': ''00:AA:00:00:11:12'', > > ''handle'': > > ''0'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vif/7/0''} to > > /local/domain/7/device/vif/0. > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:112) > > DevController: writing {''bridge'': ''xenbr0'', ''domain'': ''Dom1'', > > ''handle'': ''0'', > > ''script'': ''/etc/xen/scripts/vif-bridge'', ''state'': ''1'', ''frontend'': > > ''/local/domain/7/device/vif/0'', ''mac'': ''00:AA:00:00:11:12'', ''online'': > > ''1'', ''frontend-id'': ''7''} to /local/domain/0/backend/vif/7/0. > > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:712) Storing VM details: {''shadow_memory'': ''0'', ''uuid'': > > ''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'', ''on_reboot'': ''restart'', > > ''start_time'': ''1165766218.22'', ''on_poweroff'': ''destroy'', ''name'': ''Dom1'', > > ''xend/restart_count'': ''0'', ''vcpus'': ''1'', ''vcpu_avail'': ''1'', ''memory'': > > ''256'', ''on_crash'': ''restart'', ''image'': "(linux (kernel > > /boot/vmlinuz-2.6-xen) (ramdisk /boot/initrd-2.6.16.29-xen.img) (root > > ''/dev/sda1,ro''))", ''maxmem'': ''256''} > > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:747) Storing domain details: {''console/ring-ref'': > > ''154261'', > > ''console/port'': ''2'', ''name'': ''Dom1'', ''console/limit'': ''1048576'', ''vm'': > > ''/vm/e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'', ''domid'': ''7'', > > ''cpu/0/availability'': ''online'', ''memory/target'': ''262144'', > > ''store/ring-ref'': ''102647'', ''store/port'': ''1''} > > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:933) XendDomainInfo.handleShutdownWatch > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for > > devices vif. > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:149) Waiting for 0. > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) > > hotplugStatusCallback /local/domain/0/backend/vif/7/0/hotplug-status. > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) > > hotplugStatusCallback /local/domain/0/backend/vif/7/0/hotplug-status. > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:478) > > hotplugStatusCallback 1. > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for > > devices usb. > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for > > devices vbd. > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:149) Waiting for > > 2049. > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) > > hotplugStatusCallback /local/domain/0/backend/vbd/7/2049/hotplug-status. > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) > > hotplugStatusCallback /local/domain/0/backend/vbd/7/2049/hotplug-status. > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:478) > > hotplugStatusCallback 1. > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for > > devices irq. > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for > > devices pci. > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for > > devices ioports. > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for > > devices tap. > > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for > > devices vtpm. > > [2006-12-10 23:56:58 xend 4801] INFO (XendDomain:370) Domain Dom1 (7) > > unpaused. > > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] WARNING > > (XendDomainInfo:875) Domain has crashed: name=Dom1 id=7. > > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:1457) XendDomainInfo.destroyDomain(7) > > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:190) XendDomainInfo.create([''domain'', [''domid'', 7], > > [''uuid'', > > ''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3''], [''vcpus'', 1], [''vcpu_avail'', > > 1], [''cpu_weight'', 1.0], [''memory'', 256], [''shadow_memory'', 0], > > [''maxmem'', 256], [''features'', ''''], [''name'', ''Dom1''], [''on_poweroff'', > > ''destroy''], [''on_reboot'', ''restart''], [''on_crash'', ''restart''], > > [''image'', [''linux'', [''kernel'', ''/boot/vmlinuz-2.6-xen''], [''ramdisk'', > > ''/boot/initrd-2.6.16.29-xen.img''], [''root'', ''/dev/sda1,ro'']]], > > [''device'', [''vif'', [''backend'', 0], [''script'', ''vif-bridge''], > > [''bridge'', ''xenbr0''], [''mac'', ''00:AA:00:00:11:12'']]], [''device'', [''vbd'', > > [''backend'', 0], [''dev'', ''/dev/sda1:disk''], [''uname'', > > ''phy:GuestVG/DOM1''], [''mode'', ''w'']]], [''state'', ''----c-''], > > [''shutdown_reason'', > > ''crash''], [''cpu_time'', 0.48078367100000002], [''online_vcpus'', 1], > > [''up_time'', ''0.922783136368''], [''start_time'', ''1165766218.22''], > > [''store_mfn'', 102647], [''console_mfn'', 154261]]) > > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:296) parseConfig: config is [''domain'', [''domid'', 7], > > [''uuid'', > > ''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3''], [''vcpus'', 1], [''vcpu_avail'', > > 1], [''cpu_weight'', 1.0], [''memory'', 256], [''shadow_memory'', 0], > > [''maxmem'', 256], [''features'', ''''], [''name'', ''Dom1''], [''on_poweroff'', > > ''destroy''], [''on_reboot'', ''restart''], [''on_crash'', ''restart''], > > [''image'', [''linux'', [''kernel'', ''/boot/vmlinuz-2.6-xen''], [''ramdisk'', > > ''/boot/initrd-2.6.16.29-xen.img''], [''root'', ''/dev/sda1,ro'']]], > > [''device'', [''vif'', [''backend'', 0], [''script'', ''vif-bridge''], > > [''bridge'', ''xenbr0''], [''mac'', ''00:AA:00:00:11:12'']]], [''device'', [''vbd'', > > [''backend'', 0], [''dev'', ''/dev/sda1:disk''], [''uname'', > > ''phy:GuestVG/DOM1''], [''mode'', ''w'']]], [''state'', ''----c-''], > > [''shutdown_reason'', > > ''crash''], [''cpu_time'', 0.48078367100000002], [''online_vcpus'', 1], > > [''up_time'', ''0.922783136368''], [''start_time'', ''1165766218.22''], > > [''store_mfn'', 102647], [''console_mfn'', 154261]] > > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:395) parseConfig: result is {''shadow_memory'': 0, ''uuid'': > > ''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'', ''on_crash'': ''restart'', > > ''on_reboot'': ''restart'', ''localtime'': None, ''image'': [''linux'', [''kernel'', > > ''/boot/vmlinuz-2.6-xen''], [''ramdisk'', > > ''/boot/initrd-2.6.16.29-xen.img''], [''root'', ''/dev/sda1,ro'']], > > ''on_poweroff'': ''destroy'', > > ''bootloader_args'': None, ''cpus'': None, ''name'': ''Dom1'', ''backend'': [], > > ''vcpus'': 1, ''cpu_weight'': 1.0, ''features'': '''', ''vcpu_avail'': 1, > > ''memory'': 256, ''device'': [(''vif'', [''vif'', [''backend'', 0], [''script'', > > ''vif-bridge''], [''bridge'', ''xenbr0''], [''mac'', ''00:AA:00:00:11:12'']]), > > (''vbd'', [''vbd'', [''backend'', 0], [''dev'', ''/dev/sda1:disk''], [''uname'', > > ''phy:GuestVG/DOM1''], [''mode'', ''w'']])], ''bootloader'': None, ''cpu'': > > None, ''maxmem'': 256} > > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:1253) XendDomainInfo.construct: None > > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:1285) XendDomainInfo.initDomain: 8 1.0 > > [2006-12-10 23:56:59 xend 4801] DEBUG (balloon:133) Balloon: 51792 KiB > > free; 210752 to scrub; need 262144; retries: 20. > > [2006-12-10 23:56:59 xend 4801] DEBUG (balloon:141) Balloon: waiting > > on scrubbing > > [2006-12-10 23:56:59 xend 4801] DEBUG (balloon:127) Balloon: 262556 > > KiB free; need 262144; done. > > [2006-12-10 23:56:59 xend 4801] INFO (image:136) buildDomain os=linux > > dom=8 vcpus=1 > > [2006-12-10 23:56:59 xend 4801] DEBUG (image:191) dom = 8 > > [2006-12-10 23:56:59 xend 4801] DEBUG (image:192) image > > /boot/vmlinuz-2.6-xen > > [2006-12-10 23:56:59 xend 4801] DEBUG (image:193) store_evtchn = 1 > > [2006-12-10 23:56:59 xend 4801] DEBUG (image:194) console_evtchn = 2 > > [2006-12-10 23:56:59 xend 4801] DEBUG (image:195) cmdline > > root=/dev/sda1,ro > > [2006-12-10 23:56:59 xend 4801] DEBUG (image:196) ramdisk > > /boot/initrd-2.6.16.29-xen.img > > [2006-12-10 23:56:59 xend 4801] DEBUG (image:197) vcpus = 1 > > [2006-12-10 23:56:59 xend 4801] DEBUG (image:198) features > > [2006-12-10 23:56:59 xend 4801] DEBUG (DevController:110) > > DevController: writing {''backend-id'': ''0'', ''mac'': ''00:AA:00:00:11:12'', > > ''handle'': > > ''0'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vif/8/0''} to > > /local/domain/8/device/vif/0. > > [2006-12-10 23:56:59 xend 4801] DEBUG (DevController:112) > > DevController: writing {''bridge'': ''xenbr0'', ''domain'': ''Dom1'', > > ''handle'': ''0'', > > ''script'': ''/etc/xen/scripts/vif-bridge'', ''state'': ''1'', ''frontend'': > > ''/local/domain/8/device/vif/0'', ''mac'': ''00:AA:00:00:11:12'', ''online'': > > ''1'', ''frontend-id'': ''8''} to /local/domain/0/backend/vif/8/0. > > [2006-12-10 23:56:59 xend 4801] DEBUG (DevController:110) > > DevController: writing {''backend-id'': ''0'', ''virtual-device'': ''2049'', > > ''device-type'': ''disk'', ''state'': ''1'', ''backend'': > > ''/local/domain/0/backend/vbd/8/2049''} to /local/domain/8/device/vbd/2049. > > [2006-12-10 23:56:59 xend 4801] DEBUG (DevController:112) > > DevController: writing {''domain'': ''Dom1'', ''frontend'': > > ''/local/domain/8/device/vbd/2049'', ''dev'': ''/dev/sda1'', ''state'': ''1'', > > ''params'': ''GuestVG/DOM1'', ''mode'': ''w'', ''online'': ''1'', ''frontend-id'': > > ''8'', ''type'': ''phy''} to /local/domain/0/backend/vbd/8/2049. > > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:712) Storing VM details: {''shadow_memory'': ''0'', ''uuid'': > > ''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'', ''on_reboot'': ''restart'', > > ''start_time'': ''1165766219.69'', ''on_poweroff'': ''destroy'', ''name'': ''Dom1'', > > ''vcpus'': ''1'', ''vcpu_avail'': ''1'', ''memory'': ''256'', ''on_crash'': > > ''restart'', ''image'': "(linux (kernel /boot/vmlinuz-2.6-xen) (ramdisk > > /boot/initrd-2.6.16.29-xen.img) (root ''/dev/sda1,ro''))", ''maxmem'': ''256''} > > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:747) Storing domain details: {''console/ring-ref'': > > ''174838'', > > ''console/port'': ''2'', ''name'': ''Dom1'', ''console/limit'': ''1048576'', ''vm'': > > ''/vm/e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'', ''domid'': ''8'', > > ''cpu/0/availability'': ''online'', ''memory/target'': ''262144'', > > ''store/ring-ref'': ''174688'', ''store/port'': ''1''} > > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:933) XendDomainInfo.handleShutdownWatch > > [2006-12-10 23:57:00 xend.XendDomainInfo 4801] WARNING > > (XendDomainInfo:875) Domain has crashed: name=Dom1 id=8. > > [2006-12-10 23:57:00 xend.XendDomainInfo 4801] ERROR > > (XendDomainInfo:1661) VM Dom1 restarting too fast (1.212585 seconds > > since the last > > restart). Refusing to restart to avoid loops. > > [2006-12-10 23:57:00 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:1449) XendDomainInfo.destroy: domid=8 > > [2006-12-10 23:57:00 xend.XendDomainInfo 4801] DEBUG > > (XendDomainInfo:1457) XendDomainInfo.destroyDomain(8) > > it seems that it has tried to create dom1 for two times. > > THANKS, > > sml > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > 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 > 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 >-- GPG key fingerprint: 3883 B308 8256 2246 D3ED A1FF 3A1D 0EAD 41C4 C2F0 GPG public key availabe on pgp.mit .edu keyserver _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Steven Dugway
2006-Dec-10 21:32 UTC
Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
TMC wrote:> can you please post your config here? > > I suspect that your trying to start LVM configuration from Dom0 in > DomU... > > There are two ways to do things. > > a) put all disk in Dom0 under LVM and manage disk for all DomU > instances that way..That is how I do it and then export the partitions for each domU, works fine with old FC5 packages. Here is an config file: kernel = "/boot/vmlinuz-2.6.18-1.2849.fc6xen" #kernel = "/boot/2.6.16-1.2122_FC5xenU" memory = 250 name = "spooner" ramdisk = "/boot/initrd-2.6.18-1.2849.fc6xen.img" vif = [ '''' ] disk=[''phy:/dev/VolGroup00/spooner,sda1,w'',''phy:/dev/VolGroup00/spoonerHS,sda4,w'',''phy:/dev/VolGroup00/swap1,sda2,w'',''file:/img/tmpfiles,sda3,w''] root = "/dev/sda1 ro" ++> > or > > b) put several disks into DomU and runb LVM in DomU > > Which is the one youre trying to do? > > Regards > Tomasz > > On 11/12/06, Steven Dugway <steven@savetimehosting.net> wrote: >> Zhang Binbin wrote: >> >> Hi, >> >> I had the exact same problem for months and asked many times over but >> never got a response, sorry I cannot help you. I know many people who >> are switching to Vmware as a result. No real doc and no support. >> >> ++ >> > Hi, >> > i installed CentOS4_x86_64+Xen-3.0.3 from xen source code and didn''t >> > encounter any exceptions, but DomU can''t boot up. >> > i use LVM to management Dom vbd. this is the partition: >> > --------------------------------------------------- >> > LVM Volume Groups >> > VolGroup00 >> > LogVol00 Swap >> > LogVol01 / ext3 Dom0 filesystem >> > VG_Guests >> > Dom1 ext3 Dom1 filesystem >> > Hard Drivers >> > /dev/sda >> > /dev/sda1 /boot ext3 >> > /dev/sda2 VolGroup00 LVM PV >> > /dev/sda3 GuestVG LVM PV >> > --------------------------------------------------- >> > And i made Dom1 filesystem like this: >> > --------------------------------------------------- >> > 1. mount /dev/GuestVG/Dom1 /mnt >> > 2. cp -ax /{root,etc,dev,sbin,bin,lib,var,usr} /mnt >> > 3. mkdir /mnt/{proc,sys,tmp,home} >> > 4. modify /mnt/etc/fstab and modify eth0 config >> > 5. umount /mnt >> > --------------------------------------------------- >> > When i create Dom1, it get the following output: >> > --------------------------------------------------- >> > Using config file "dom1_config". >> > Started domain Dom1 >> > Bootdata ok (command line is root=/dev/sda1,ro) >> > Linux version 2.6.16.29-xen (shand@endor) (gcc version 3.4.4 20050314 >> > (prerelease) (Debian 3.4.3-13)) #3 SMP Sun Oct 15 13:15:34 BST 2006 >> > BIOS-provided physical RAM map: >> > Xen: 0000000000000000 - 0000000010800000 (usable) >> > No mptable found. >> > Built 1 zonelists >> > Kernel command line: root=/dev/sda1,ro >> > Initializing CPU#0 >> > PID hash table entries: 2048 (order: 11, 65536 bytes) >> > Xen reported: 1862.323 MHz processor. >> > Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) >> > Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) >> > Software IO TLB disabled >> > Memory: 248468k/270336k available (1918k kernel code, 13348k reserved, >> > 809k data, 168k init) >> > Calibrating delay using timer specific routine.. 3725.91 BogoMIPS >> > (lpj=18629558) >> > Security Framework v1.0.0 initialized >> > Capability LSM initialized >> > Mount-cache hash table entries: 256 >> > CPU: L1 I cache: 32K, L1 D cache: 32K >> > CPU: L2 cache: 2048K >> > CPU: Physical Processor ID: 0 >> > CPU: Processor Core ID: 0 >> > Brought up 1 CPUs >> > migration_cost=0 >> > checking if image is initramfs... it is >> > Freeing initrd memory: 3792k freed >> > DMI not present or invalid. >> > 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 >> > pnp: PnP ACPI: disabled >> > xen_mem: Initialising balloon driver. >> > PCI: System does not support PCI >> > PCI: System does not support PCI >> > IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com > >> > IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $ >> > audit: initializing netlink socket (disabled) >> > audit(1165766218.701:1): initialized >> > VFS: Disk quotas dquot_6.5.1 >> > Dquot-cache hash table entries: 512 (order 0, 4096 bytes) >> > Initializing Cryptographic API >> > io scheduler noop registered >> > io scheduler anticipatory registered >> > io scheduler deadline registered >> > io scheduler cfq registered (default) >> > rtc: IRQ 8 is not free. >> > Non-volatile memory driver v1.2 >> > 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 >> > loop: loaded (max 8 devices) >> > 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 8 >> > 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 >> > NET: Registered protocol family 2 >> > netfront: device eth0 has flipping receive path. >> > IP route cache hash table entries: 4096 (order: 3, 32768 bytes) >> > TCP established hash table entries: 16384 (order: 6, 262144 bytes) >> > TCP bind hash table entries: 16384 (order: 6, 262144 bytes) >> > TCP: Hash tables configured (established 16384 bind 16384) >> > TCP reno registered >> > NET: Registered protocol family 1 >> > NET: Registered protocol family 17 >> > Red Hat nash version 4.2.1.8 starting >> > Mounted /proc filesystem >> > Mounting sysfs >> > Creating /dev >> > Starting udev >> > Loading scsi_mod.ko module >> > SCSI subsystem initialized >> > Loading sd_mod.ko module >> > register_blkdev: cannot get major 8 for sd >> > Loading libata.ko module >> > Loading ahci.ko module >> > Loading ata_piix.ko module >> > Loading ide-disk.ko module >> > Loading dm-mod.ko module >> > device-mapper: 4.5.0-ioctl (2005-10-04) initialised: >> dm-devel@redhat.com >> > Loading jbd.ko module >> > Loading ext3.ko module >> > Loading dm-mirror.ko module >> > Loading dm-zero.ko module >> > Loading dm-snapshot.ko module >> > Making device-mapper control node >> > Scanning logical volumes >> > Reading all physical volumes. This may take a while... >> > No volume groups found >> > Activating logical volumes >> > Volume group "VolGroup00" not found >> > ERROR: /bin/lvm exited abnormally! (pid 353) >> > Creating root device >> > Mounting root filesystem >> > mount: error 6 mounting ext3 >> > mount: error 2 mounting none >> > Switching to new root >> > switchroot: mount failed: 22 >> > umount /initrd/dev failed: 2 >> > Kernel panic - not syncing: Attempted to kill init! >> > ------------------------------------------------- >> > The Dom1 config file: >> > ------------------------------------------------- >> > kernel=''/boot/vmlinuz-2.6-xen'' >> > ramdisk=''/boot/initrd-2.6.16.29-xen.img'' >> > memory=256 >> > name=''Dom1'' >> > vif=[''mac=00:AA:00:00:11:12,bridge=xenbr0''] >> > disk=[''phy:GuestVG/DOM1,/dev/sda1,w''] >> > root=''/dev/sda1,ro'' >> > ------------------------------------------------- >> > and /var/log/xen/xend.log: >> > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:190) XendDomainInfo.create([''vm'', [''name'', ''Dom1''], >> > [''memory'', 256], >> > [''vcpus'', 1], [''image'', [''linux'', [''kernel'', ''/boot/vmlinuz-2.6-xen''], >> > [''ramdisk'', ''/boot/initrd-2.6.16.29-xen.img''], [''root'', >> > ''/dev/sda1,ro'']]], [''device'', [''vbd'', [''uname'', ''phy:GuestVG/DOM1''], >> > [''dev'', ''/dev/sda1''], [''mode'', ''w'']]], [''device'', [''vif'', [''bridge'', >> > ''xenbr0''], [''mac'', ''00:AA:00:00:11:12'']]]]) >> > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:296) parseConfig: config is [''vm'', [''name'', ''Dom1''], >> > [''memory'', 256], >> > [''vcpus'', 1], [''image'', [''linux'', [''kernel'', ''/boot/vmlinuz-2.6-xen''], >> > [''ramdisk'', ''/boot/initrd-2.6.16.29-xen.img''], [''root'', >> > ''/dev/sda1,ro'']]], [''device'', [''vbd'', [''uname'', ''phy:GuestVG/DOM1''], >> > [''dev'', ''/dev/sda1''], [''mode'', ''w'']]], [''device'', [''vif'', [''bridge'', >> > ''xenbr0''], [''mac'', ''00:AA:00:00:11:12'']]]] >> > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:395) parseConfig: result is {''shadow_memory'': None, >> > ''uuid'': None, >> > ''on_crash'': None, ''on_reboot'': None, ''localtime'': None, ''image'': >> > [''linux'', [''kernel'', ''/boot/vmlinuz-2.6-xen''], [''ramdisk'', >> > ''/boot/initrd-2.6.16.29-xen.img''], [''root'', ''/dev/sda1,ro'']], >> > ''on_poweroff'': None, ''bootloader_args'': None, ''cpus'': None, ''name'': >> > ''Dom1'', >> > ''backend'': [], ''vcpus'': 1, ''cpu_weight'': None, ''features'': None, >> > ''vcpu_avail'': None, ''memory'': 256, ''device'': [(''vbd'', [''vbd'', >> [''uname'', >> > ''phy:GuestVG/DOM1''], [''dev'', ''/dev/sda1''], [''mode'', ''w'']]), (''vif'', >> > [''vif'', [''bridge'', ''xenbr0''], [''mac'', ''00:AA:00:00:11:12'']])], >> > ''bootloader'': None, ''cpu'': None, ''maxmem'': None} >> > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:1253) XendDomainInfo.construct: None >> > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:1285) XendDomainInfo.initDomain: 7 1.0 >> > [2006-12-10 23:56:58 xend 4801] DEBUG (balloon:127) Balloon: 262556 >> > KiB free; need 262144; done. >> > [2006-12-10 23:56:58 xend 4801] INFO (image:136) buildDomain os=linux >> > dom=7 vcpus=1 >> > [2006-12-10 23:56:58 xend 4801] DEBUG (image:191) dom = 7 >> > [2006-12-10 23:56:58 xend 4801] DEBUG (image:192) image >> > /boot/vmlinuz-2.6-xen >> > [2006-12-10 23:56:58 xend 4801] DEBUG (image:193) store_evtchn = 1 >> > [2006-12-10 23:56:58 xend 4801] DEBUG (image:194) console_evtchn = 2 >> > [2006-12-10 23:56:58 xend 4801] DEBUG (image:195) cmdline >> > root=/dev/sda1,ro >> > [2006-12-10 23:56:58 xend 4801] DEBUG (image:196) ramdisk >> > /boot/initrd-2.6.16.29-xen.img >> > [2006-12-10 23:56:58 xend 4801] DEBUG (image:197) vcpus = 1 >> > [2006-12-10 23:56:58 xend 4801] DEBUG (image:198) features >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:110) >> > DevController: writing {''backend-id'': ''0'', ''virtual-device'': ''2049'', >> > ''device-type'': ''disk'', ''state'': ''1'', ''backend'': >> > ''/local/domain/0/backend/vbd/7/2049''} to >> /local/domain/7/device/vbd/2049. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:112) >> > DevController: writing {''domain'': ''Dom1'', ''frontend'': >> > ''/local/domain/7/device/vbd/2049'', ''dev'': ''/dev/sda1'', ''state'': ''1'', >> > ''params'': ''GuestVG/DOM1'', ''mode'': ''w'', ''online'': ''1'', ''frontend-id'': >> > ''7'', ''type'': ''phy''} to /local/domain/0/backend/vbd/7/2049. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:110) >> > DevController: writing {''backend-id'': ''0'', ''mac'': ''00:AA:00:00:11:12'', >> > ''handle'': >> > ''0'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vif/7/0''} to >> > /local/domain/7/device/vif/0. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:112) >> > DevController: writing {''bridge'': ''xenbr0'', ''domain'': ''Dom1'', >> > ''handle'': ''0'', >> > ''script'': ''/etc/xen/scripts/vif-bridge'', ''state'': ''1'', ''frontend'': >> > ''/local/domain/7/device/vif/0'', ''mac'': ''00:AA:00:00:11:12'', ''online'': >> > ''1'', ''frontend-id'': ''7''} to /local/domain/0/backend/vif/7/0. >> > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:712) Storing VM details: {''shadow_memory'': ''0'', >> ''uuid'': >> > ''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'', ''on_reboot'': ''restart'', >> > ''start_time'': ''1165766218.22'', ''on_poweroff'': ''destroy'', ''name'': >> ''Dom1'', >> > ''xend/restart_count'': ''0'', ''vcpus'': ''1'', ''vcpu_avail'': ''1'', ''memory'': >> > ''256'', ''on_crash'': ''restart'', ''image'': "(linux (kernel >> > /boot/vmlinuz-2.6-xen) (ramdisk /boot/initrd-2.6.16.29-xen.img) (root >> > ''/dev/sda1,ro''))", ''maxmem'': ''256''} >> > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:747) Storing domain details: {''console/ring-ref'': >> > ''154261'', >> > ''console/port'': ''2'', ''name'': ''Dom1'', ''console/limit'': ''1048576'', ''vm'': >> > ''/vm/e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'', ''domid'': ''7'', >> > ''cpu/0/availability'': ''online'', ''memory/target'': ''262144'', >> > ''store/ring-ref'': ''102647'', ''store/port'': ''1''} >> > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:933) XendDomainInfo.handleShutdownWatch >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for >> > devices vif. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:149) Waiting >> for 0. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) >> > hotplugStatusCallback /local/domain/0/backend/vif/7/0/hotplug-status. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) >> > hotplugStatusCallback /local/domain/0/backend/vif/7/0/hotplug-status. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:478) >> > hotplugStatusCallback 1. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for >> > devices usb. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for >> > devices vbd. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:149) Waiting for >> > 2049. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) >> > hotplugStatusCallback >> /local/domain/0/backend/vbd/7/2049/hotplug-status. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) >> > hotplugStatusCallback >> /local/domain/0/backend/vbd/7/2049/hotplug-status. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:478) >> > hotplugStatusCallback 1. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for >> > devices irq. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for >> > devices pci. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for >> > devices ioports. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for >> > devices tap. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for >> > devices vtpm. >> > [2006-12-10 23:56:58 xend 4801] INFO (XendDomain:370) Domain Dom1 (7) >> > unpaused. >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] WARNING >> > (XendDomainInfo:875) Domain has crashed: name=Dom1 id=7. >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:1457) XendDomainInfo.destroyDomain(7) >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:190) XendDomainInfo.create([''domain'', [''domid'', 7], >> > [''uuid'', >> > ''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3''], [''vcpus'', 1], [''vcpu_avail'', >> > 1], [''cpu_weight'', 1.0], [''memory'', 256], [''shadow_memory'', 0], >> > [''maxmem'', 256], [''features'', ''''], [''name'', ''Dom1''], [''on_poweroff'', >> > ''destroy''], [''on_reboot'', ''restart''], [''on_crash'', ''restart''], >> > [''image'', [''linux'', [''kernel'', ''/boot/vmlinuz-2.6-xen''], [''ramdisk'', >> > ''/boot/initrd-2.6.16.29-xen.img''], [''root'', ''/dev/sda1,ro'']]], >> > [''device'', [''vif'', [''backend'', 0], [''script'', ''vif-bridge''], >> > [''bridge'', ''xenbr0''], [''mac'', ''00:AA:00:00:11:12'']]], [''device'', >> [''vbd'', >> > [''backend'', 0], [''dev'', ''/dev/sda1:disk''], [''uname'', >> > ''phy:GuestVG/DOM1''], [''mode'', ''w'']]], [''state'', ''----c-''], >> > [''shutdown_reason'', >> > ''crash''], [''cpu_time'', 0.48078367100000002], [''online_vcpus'', 1], >> > [''up_time'', ''0.922783136368''], [''start_time'', ''1165766218.22''], >> > [''store_mfn'', 102647], [''console_mfn'', 154261]]) >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:296) parseConfig: config is [''domain'', [''domid'', 7], >> > [''uuid'', >> > ''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3''], [''vcpus'', 1], [''vcpu_avail'', >> > 1], [''cpu_weight'', 1.0], [''memory'', 256], [''shadow_memory'', 0], >> > [''maxmem'', 256], [''features'', ''''], [''name'', ''Dom1''], [''on_poweroff'', >> > ''destroy''], [''on_reboot'', ''restart''], [''on_crash'', ''restart''], >> > [''image'', [''linux'', [''kernel'', ''/boot/vmlinuz-2.6-xen''], [''ramdisk'', >> > ''/boot/initrd-2.6.16.29-xen.img''], [''root'', ''/dev/sda1,ro'']]], >> > [''device'', [''vif'', [''backend'', 0], [''script'', ''vif-bridge''], >> > [''bridge'', ''xenbr0''], [''mac'', ''00:AA:00:00:11:12'']]], [''device'', >> [''vbd'', >> > [''backend'', 0], [''dev'', ''/dev/sda1:disk''], [''uname'', >> > ''phy:GuestVG/DOM1''], [''mode'', ''w'']]], [''state'', ''----c-''], >> > [''shutdown_reason'', >> > ''crash''], [''cpu_time'', 0.48078367100000002], [''online_vcpus'', 1], >> > [''up_time'', ''0.922783136368''], [''start_time'', ''1165766218.22''], >> > [''store_mfn'', 102647], [''console_mfn'', 154261]] >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:395) parseConfig: result is {''shadow_memory'': 0, >> ''uuid'': >> > ''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'', ''on_crash'': ''restart'', >> > ''on_reboot'': ''restart'', ''localtime'': None, ''image'': [''linux'', >> [''kernel'', >> > ''/boot/vmlinuz-2.6-xen''], [''ramdisk'', >> > ''/boot/initrd-2.6.16.29-xen.img''], [''root'', ''/dev/sda1,ro'']], >> > ''on_poweroff'': ''destroy'', >> > ''bootloader_args'': None, ''cpus'': None, ''name'': ''Dom1'', ''backend'': [], >> > ''vcpus'': 1, ''cpu_weight'': 1.0, ''features'': '''', ''vcpu_avail'': 1, >> > ''memory'': 256, ''device'': [(''vif'', [''vif'', [''backend'', 0], [''script'', >> > ''vif-bridge''], [''bridge'', ''xenbr0''], [''mac'', ''00:AA:00:00:11:12'']]), >> > (''vbd'', [''vbd'', [''backend'', 0], [''dev'', ''/dev/sda1:disk''], [''uname'', >> > ''phy:GuestVG/DOM1''], [''mode'', ''w'']])], ''bootloader'': None, ''cpu'': >> > None, ''maxmem'': 256} >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:1253) XendDomainInfo.construct: None >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:1285) XendDomainInfo.initDomain: 8 1.0 >> > [2006-12-10 23:56:59 xend 4801] DEBUG (balloon:133) Balloon: 51792 KiB >> > free; 210752 to scrub; need 262144; retries: 20. >> > [2006-12-10 23:56:59 xend 4801] DEBUG (balloon:141) Balloon: waiting >> > on scrubbing >> > [2006-12-10 23:56:59 xend 4801] DEBUG (balloon:127) Balloon: 262556 >> > KiB free; need 262144; done. >> > [2006-12-10 23:56:59 xend 4801] INFO (image:136) buildDomain os=linux >> > dom=8 vcpus=1 >> > [2006-12-10 23:56:59 xend 4801] DEBUG (image:191) dom = 8 >> > [2006-12-10 23:56:59 xend 4801] DEBUG (image:192) image >> > /boot/vmlinuz-2.6-xen >> > [2006-12-10 23:56:59 xend 4801] DEBUG (image:193) store_evtchn = 1 >> > [2006-12-10 23:56:59 xend 4801] DEBUG (image:194) console_evtchn = 2 >> > [2006-12-10 23:56:59 xend 4801] DEBUG (image:195) cmdline >> > root=/dev/sda1,ro >> > [2006-12-10 23:56:59 xend 4801] DEBUG (image:196) ramdisk >> > /boot/initrd-2.6.16.29-xen.img >> > [2006-12-10 23:56:59 xend 4801] DEBUG (image:197) vcpus = 1 >> > [2006-12-10 23:56:59 xend 4801] DEBUG (image:198) features >> > [2006-12-10 23:56:59 xend 4801] DEBUG (DevController:110) >> > DevController: writing {''backend-id'': ''0'', ''mac'': ''00:AA:00:00:11:12'', >> > ''handle'': >> > ''0'', ''state'': ''1'', ''backend'': ''/local/domain/0/backend/vif/8/0''} to >> > /local/domain/8/device/vif/0. >> > [2006-12-10 23:56:59 xend 4801] DEBUG (DevController:112) >> > DevController: writing {''bridge'': ''xenbr0'', ''domain'': ''Dom1'', >> > ''handle'': ''0'', >> > ''script'': ''/etc/xen/scripts/vif-bridge'', ''state'': ''1'', ''frontend'': >> > ''/local/domain/8/device/vif/0'', ''mac'': ''00:AA:00:00:11:12'', ''online'': >> > ''1'', ''frontend-id'': ''8''} to /local/domain/0/backend/vif/8/0. >> > [2006-12-10 23:56:59 xend 4801] DEBUG (DevController:110) >> > DevController: writing {''backend-id'': ''0'', ''virtual-device'': ''2049'', >> > ''device-type'': ''disk'', ''state'': ''1'', ''backend'': >> > ''/local/domain/0/backend/vbd/8/2049''} to >> /local/domain/8/device/vbd/2049. >> > [2006-12-10 23:56:59 xend 4801] DEBUG (DevController:112) >> > DevController: writing {''domain'': ''Dom1'', ''frontend'': >> > ''/local/domain/8/device/vbd/2049'', ''dev'': ''/dev/sda1'', ''state'': ''1'', >> > ''params'': ''GuestVG/DOM1'', ''mode'': ''w'', ''online'': ''1'', ''frontend-id'': >> > ''8'', ''type'': ''phy''} to /local/domain/0/backend/vbd/8/2049. >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:712) Storing VM details: {''shadow_memory'': ''0'', >> ''uuid'': >> > ''e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'', ''on_reboot'': ''restart'', >> > ''start_time'': ''1165766219.69'', ''on_poweroff'': ''destroy'', ''name'': >> ''Dom1'', >> > ''vcpus'': ''1'', ''vcpu_avail'': ''1'', ''memory'': ''256'', ''on_crash'': >> > ''restart'', ''image'': "(linux (kernel /boot/vmlinuz-2.6-xen) (ramdisk >> > /boot/initrd-2.6.16.29-xen.img) (root ''/dev/sda1,ro''))", ''maxmem'': >> ''256''} >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:747) Storing domain details: {''console/ring-ref'': >> > ''174838'', >> > ''console/port'': ''2'', ''name'': ''Dom1'', ''console/limit'': ''1048576'', ''vm'': >> > ''/vm/e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'', ''domid'': ''8'', >> > ''cpu/0/availability'': ''online'', ''memory/target'': ''262144'', >> > ''store/ring-ref'': ''174688'', ''store/port'': ''1''} >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:933) XendDomainInfo.handleShutdownWatch >> > [2006-12-10 23:57:00 xend.XendDomainInfo 4801] WARNING >> > (XendDomainInfo:875) Domain has crashed: name=Dom1 id=8. >> > [2006-12-10 23:57:00 xend.XendDomainInfo 4801] ERROR >> > (XendDomainInfo:1661) VM Dom1 restarting too fast (1.212585 seconds >> > since the last >> > restart). Refusing to restart to avoid loops. >> > [2006-12-10 23:57:00 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:1449) XendDomainInfo.destroy: domid=8 >> > [2006-12-10 23:57:00 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:1457) XendDomainInfo.destroyDomain(8) >> > it seems that it has tried to create dom1 for two times. >> > THANKS, >> > sml >> > >> ------------------------------------------------------------------------ >> > >> > _______________________________________________ >> > 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 >> 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 >> > >-- 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
TMC
2006-Dec-10 23:59 UTC
Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
On 11/12/06, Steven Dugway <steven@savetimehosting.net> wrote:> TMC wrote: > > can you please post your config here? > > > > I suspect that your trying to start LVM configuration from Dom0 in > > DomU... > > > > There are two ways to do things. > > > > a) put all disk in Dom0 under LVM and manage disk for all DomU > > instances that way.. > That is how I do it and then export the partitions for each domU, works > fine with old FC5 packages. > Here is an config file: > > kernel = "/boot/vmlinuz-2.6.18-1.2849.fc6xen" > #kernel = "/boot/2.6.16-1.2122_FC5xenU" > memory = 250 > name = "spooner" > ramdisk = "/boot/initrd-2.6.18-1.2849.fc6xen.img" > vif = [ '''' ] > disk=[''phy:/dev/VolGroup00/spooner,sda1,w'',''phy:/dev/VolGroup00/spoonerHS,sda4,w'',''phy:/dev/VolGroup00/swap1,sda2,w'',''file:/img/tmpfiles,sda3,w''] > root = "/dev/sda1 ro" >Ok. What I suspect is happening is that you have copied a whole parent server instance (with a running /etc and such like) instead of doing a clean install to your patritions with kickstart, jump-start or debootstrap. This means that your LVM subsystem is looking in /etc, finds configs and goesa looking for disks to manage and fails, bacuse it must. you are accessing abstracted devices not raw devices in your DomU. I think you need to blow away (or at least rename) all LVM configs in /etc/ of your DomU. They are not needed. Also you need to change: your networking (unless you DHCP) hostname edit the fstab to refer to /dev/sda1, /dev/sda2, /dev/sda3 and /dev/sda4 as required instead of lables or /dev/VolGroup** stuff. Also Please boot the XenU specific kernel, if your packages provide it. Its safer. Hope this helps Tomasz _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Zhang Binbin
2006-Dec-11 05:54 UTC
Re: Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
Thanks for your reply. I want to put all disk in Dom0 under LVM and manage disk for all DomU instances. Each DomU use a LV (in Dom0) as its disk. vbd config: disk=['phy:GuestVG/DOM1,/dev/sda1,w'] ======= 2006-12-11 04:01:19 您在来信中写道：======>can you please post your config here? > >I suspect that your trying to start LVM configuration from Dom0 in DomU... > >There are two ways to do things. > >a) put all disk in Dom0 under LVM and manage disk for all DomU >instances that way.. > >or > >b) put several disks into DomU and runb LVM in DomU > >Which is the one youre trying to do? > >Regards >Tomasz > >On 11/12/06, Steven Dugway <steven@savetimehosting.net> wrote: >> Zhang Binbin wrote: >> >> Hi, >> >> I had the exact same problem for months and asked many times over but >> never got a response, sorry I cannot help you. I know many people who >> are switching to Vmware as a result. No real doc and no support. >> >> ++ >> > Hi, >> > i installed CentOS4_x86_64+Xen-3.0.3 from xen source code and didn't >> > encounter any exceptions, but DomU can't boot up. >> > i use LVM to management Dom vbd. this is the partition: >> > --------------------------------------------------- >> > LVM Volume Groups >> > VolGroup00 >> > LogVol00 Swap >> > LogVol01 / ext3 Dom0 filesystem >> > VG_Guests >> > Dom1 ext3 Dom1 filesystem >> > Hard Drivers >> > /dev/sda >> > /dev/sda1 /boot ext3 >> > /dev/sda2 VolGroup00 LVM PV >> > /dev/sda3 GuestVG LVM PV >> > --------------------------------------------------- >> > And i made Dom1 filesystem like this: >> > --------------------------------------------------- >> > 1. mount /dev/GuestVG/Dom1 /mnt >> > 2. cp -ax /{root,etc,dev,sbin,bin,lib,var,usr} /mnt >> > 3. mkdir /mnt/{proc,sys,tmp,home} >> > 4. modify /mnt/etc/fstab and modify eth0 config >> > 5. umount /mnt >> > --------------------------------------------------- >> > When i create Dom1, it get the following output: >> > --------------------------------------------------- >> > Using config file "dom1_config". >> > Started domain Dom1 >> > Bootdata ok (command line is root=/dev/sda1,ro) >> > Linux version 2.6.16.29-xen (shand@endor) (gcc version 3.4.4 20050314 >> > (prerelease) (Debian 3.4.3-13)) #3 SMP Sun Oct 15 13:15:34 BST 2006 >> > BIOS-provided physical RAM map: >> > Xen: 0000000000000000 - 0000000010800000 (usable) >> > No mptable found. >> > Built 1 zonelists >> > Kernel command line: root=/dev/sda1,ro >> > Initializing CPU#0 >> > PID hash table entries: 2048 (order: 11, 65536 bytes) >> > Xen reported: 1862.323 MHz processor. >> > Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) >> > Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) >> > Software IO TLB disabled >> > Memory: 248468k/270336k available (1918k kernel code, 13348k reserved, >> > 809k data, 168k init) >> > Calibrating delay using timer specific routine.. 3725.91 BogoMIPS >> > (lpj=18629558) >> > Security Framework v1.0.0 initialized >> > Capability LSM initialized >> > Mount-cache hash table entries: 256 >> > CPU: L1 I cache: 32K, L1 D cache: 32K >> > CPU: L2 cache: 2048K >> > CPU: Physical Processor ID: 0 >> > CPU: Processor Core ID: 0 >> > Brought up 1 CPUs >> > migration_cost=0 >> > checking if image is initramfs... it is >> > Freeing initrd memory: 3792k freed >> > DMI not present or invalid. >> > 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 >> > pnp: PnP ACPI: disabled >> > xen_mem: Initialising balloon driver. >> > PCI: System does not support PCI >> > PCI: System does not support PCI >> > IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com > >> > IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $ >> > audit: initializing netlink socket (disabled) >> > audit(1165766218.701:1): initialized >> > VFS: Disk quotas dquot_6.5.1 >> > Dquot-cache hash table entries: 512 (order 0, 4096 bytes) >> > Initializing Cryptographic API >> > io scheduler noop registered >> > io scheduler anticipatory registered >> > io scheduler deadline registered >> > io scheduler cfq registered (default) >> > rtc: IRQ 8 is not free. >> > Non-volatile memory driver v1.2 >> > 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 >> > loop: loaded (max 8 devices) >> > 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 8 >> > 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 >> > NET: Registered protocol family 2 >> > netfront: device eth0 has flipping receive path. >> > IP route cache hash table entries: 4096 (order: 3, 32768 bytes) >> > TCP established hash table entries: 16384 (order: 6, 262144 bytes) >> > TCP bind hash table entries: 16384 (order: 6, 262144 bytes) >> > TCP: Hash tables configured (established 16384 bind 16384) >> > TCP reno registered >> > NET: Registered protocol family 1 >> > NET: Registered protocol family 17 >> > Red Hat nash version 4.2.1.8 starting >> > Mounted /proc filesystem >> > Mounting sysfs >> > Creating /dev >> > Starting udev >> > Loading scsi_mod.ko module >> > SCSI subsystem initialized >> > Loading sd_mod.ko module >> > register_blkdev: cannot get major 8 for sd >> > Loading libata.ko module >> > Loading ahci.ko module >> > Loading ata_piix.ko module >> > Loading ide-disk.ko module >> > Loading dm-mod.ko module >> > device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com >> > Loading jbd.ko module >> > Loading ext3.ko module >> > Loading dm-mirror.ko module >> > Loading dm-zero.ko module >> > Loading dm-snapshot.ko module >> > Making device-mapper control node >> > Scanning logical volumes >> > Reading all physical volumes. This may take a while... >> > No volume groups found >> > Activating logical volumes >> > Volume group "VolGroup00" not found >> > ERROR: /bin/lvm exited abnormally! (pid 353) >> > Creating root device >> > Mounting root filesystem >> > mount: error 6 mounting ext3 >> > mount: error 2 mounting none >> > Switching to new root >> > switchroot: mount failed: 22 >> > umount /initrd/dev failed: 2 >> > Kernel panic - not syncing: Attempted to kill init! >> > ------------------------------------------------- >> > The Dom1 config file: >> > ------------------------------------------------- >> > kernel='/boot/vmlinuz-2.6-xen' >> > ramdisk='/boot/initrd-2.6.16.29-xen.img' >> > memory=256 >> > name='Dom1' >> > vif=['mac=00:AA:00:00:11:12,bridge=xenbr0'] >> > disk=['phy:GuestVG/DOM1,/dev/sda1,w'] >> > root='/dev/sda1,ro' >> > ------------------------------------------------- >> > and /var/log/xen/xend.log: >> > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:190) XendDomainInfo.create(['vm', ['name', 'Dom1'], >> > ['memory', 256], >> > ['vcpus', 1], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6-xen'], >> > ['ramdisk', '/boot/initrd-2.6.16.29-xen.img'], ['root', >> > '/dev/sda1,ro']]], ['device', ['vbd', ['uname', 'phy:GuestVG/DOM1'], >> > ['dev', '/dev/sda1'], ['mode', 'w']]], ['device', ['vif', ['bridge', >> > 'xenbr0'], ['mac', '00:AA:00:00:11:12']]]]) >> > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:296) parseConfig: config is ['vm', ['name', 'Dom1'], >> > ['memory', 256], >> > ['vcpus', 1], ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6-xen'], >> > ['ramdisk', '/boot/initrd-2.6.16.29-xen.img'], ['root', >> > '/dev/sda1,ro']]], ['device', ['vbd', ['uname', 'phy:GuestVG/DOM1'], >> > ['dev', '/dev/sda1'], ['mode', 'w']]], ['device', ['vif', ['bridge', >> > 'xenbr0'], ['mac', '00:AA:00:00:11:12']]]] >> > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:395) parseConfig: result is {'shadow_memory': None, >> > 'uuid': None, >> > 'on_crash': None, 'on_reboot': None, 'localtime': None, 'image': >> > ['linux', ['kernel', '/boot/vmlinuz-2.6-xen'], ['ramdisk', >> > '/boot/initrd-2.6.16.29-xen.img'], ['root', '/dev/sda1,ro']], >> > 'on_poweroff': None, 'bootloader_args': None, 'cpus': None, 'name': >> > 'Dom1', >> > 'backend': [], 'vcpus': 1, 'cpu_weight': None, 'features': None, >> > 'vcpu_avail': None, 'memory': 256, 'device': [('vbd', ['vbd', ['uname', >> > 'phy:GuestVG/DOM1'], ['dev', '/dev/sda1'], ['mode', 'w']]), ('vif', >> > ['vif', ['bridge', 'xenbr0'], ['mac', '00:AA:00:00:11:12']])], >> > 'bootloader': None, 'cpu': None, 'maxmem': None} >> > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:1253) XendDomainInfo.construct: None >> > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:1285) XendDomainInfo.initDomain: 7 1.0 >> > [2006-12-10 23:56:58 xend 4801] DEBUG (balloon:127) Balloon: 262556 >> > KiB free; need 262144; done. >> > [2006-12-10 23:56:58 xend 4801] INFO (image:136) buildDomain os=linux >> > dom=7 vcpus=1 >> > [2006-12-10 23:56:58 xend 4801] DEBUG (image:191) dom = 7 >> > [2006-12-10 23:56:58 xend 4801] DEBUG (image:192) image >> > /boot/vmlinuz-2.6-xen >> > [2006-12-10 23:56:58 xend 4801] DEBUG (image:193) store_evtchn = 1 >> > [2006-12-10 23:56:58 xend 4801] DEBUG (image:194) console_evtchn = 2 >> > [2006-12-10 23:56:58 xend 4801] DEBUG (image:195) cmdline >> > root=/dev/sda1,ro >> > [2006-12-10 23:56:58 xend 4801] DEBUG (image:196) ramdisk >> > /boot/initrd-2.6.16.29-xen.img >> > [2006-12-10 23:56:58 xend 4801] DEBUG (image:197) vcpus = 1 >> > [2006-12-10 23:56:58 xend 4801] DEBUG (image:198) features >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:110) >> > DevController: writing {'backend-id': '0', 'virtual-device': '2049', >> > 'device-type': 'disk', 'state': '1', 'backend': >> > '/local/domain/0/backend/vbd/7/2049'} to /local/domain/7/device/vbd/2049. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:112) >> > DevController: writing {'domain': 'Dom1', 'frontend': >> > '/local/domain/7/device/vbd/2049', 'dev': '/dev/sda1', 'state': '1', >> > 'params': 'GuestVG/DOM1', 'mode': 'w', 'online': '1', 'frontend-id': >> > '7', 'type': 'phy'} to /local/domain/0/backend/vbd/7/2049. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:110) >> > DevController: writing {'backend-id': '0', 'mac': '00:AA:00:00:11:12', >> > 'handle': >> > '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/7/0'} to >> > /local/domain/7/device/vif/0. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:112) >> > DevController: writing {'bridge': 'xenbr0', 'domain': 'Dom1', >> > 'handle': '0', >> > 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': >> > '/local/domain/7/device/vif/0', 'mac': '00:AA:00:00:11:12', 'online': >> > '1', 'frontend-id': '7'} to /local/domain/0/backend/vif/7/0. >> > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:712) Storing VM details: {'shadow_memory': '0', 'uuid': >> > 'e44ebfc5-f6a6-17ff-1df7-887d3308bcb3', 'on_reboot': 'restart', >> > 'start_time': '1165766218.22', 'on_poweroff': 'destroy', 'name': 'Dom1', >> > 'xend/restart_count': '0', 'vcpus': '1', 'vcpu_avail': '1', 'memory': >> > '256', 'on_crash': 'restart', 'image': "(linux (kernel >> > /boot/vmlinuz-2.6-xen) (ramdisk /boot/initrd-2.6.16.29-xen.img) (root >> > '/dev/sda1,ro'))", 'maxmem': '256'} >> > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:747) Storing domain details: {'console/ring-ref': >> > '154261', >> > 'console/port': '2', 'name': 'Dom1', 'console/limit': '1048576', 'vm': >> > '/vm/e44ebfc5-f6a6-17ff-1df7-887d3308bcb3', 'domid': '7', >> > 'cpu/0/availability': 'online', 'memory/target': '262144', >> > 'store/ring-ref': '102647', 'store/port': '1'} >> > [2006-12-10 23:56:58 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:933) XendDomainInfo.handleShutdownWatch >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for >> > devices vif. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:149) Waiting for 0. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) >> > hotplugStatusCallback /local/domain/0/backend/vif/7/0/hotplug-status. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) >> > hotplugStatusCallback /local/domain/0/backend/vif/7/0/hotplug-status. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:478) >> > hotplugStatusCallback 1. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for >> > devices usb. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for >> > devices vbd. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:149) Waiting for >> > 2049. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) >> > hotplugStatusCallback /local/domain/0/backend/vbd/7/2049/hotplug-status. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:464) >> > hotplugStatusCallback /local/domain/0/backend/vbd/7/2049/hotplug-status. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:478) >> > hotplugStatusCallback 1. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for >> > devices irq. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for >> > devices pci. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for >> > devices ioports. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for >> > devices tap. >> > [2006-12-10 23:56:58 xend 4801] DEBUG (DevController:143) Waiting for >> > devices vtpm. >> > [2006-12-10 23:56:58 xend 4801] INFO (XendDomain:370) Domain Dom1 (7) >> > unpaused. >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] WARNING >> > (XendDomainInfo:875) Domain has crashed: name=Dom1 id=7. >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:1457) XendDomainInfo.destroyDomain(7) >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:190) XendDomainInfo.create(['domain', ['domid', 7], >> > ['uuid', >> > 'e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'], ['vcpus', 1], ['vcpu_avail', >> > 1], ['cpu_weight', 1.0], ['memory', 256], ['shadow_memory', 0], >> > ['maxmem', 256], ['features', ''], ['name', 'Dom1'], ['on_poweroff', >> > 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'], >> > ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6-xen'], ['ramdisk', >> > '/boot/initrd-2.6.16.29-xen.img'], ['root', '/dev/sda1,ro']]], >> > ['device', ['vif', ['backend', 0], ['script', 'vif-bridge'], >> > ['bridge', 'xenbr0'], ['mac', '00:AA:00:00:11:12']]], ['device', ['vbd', >> > ['backend', 0], ['dev', '/dev/sda1:disk'], ['uname', >> > 'phy:GuestVG/DOM1'], ['mode', 'w']]], ['state', '----c-'], >> > ['shutdown_reason', >> > 'crash'], ['cpu_time', 0.48078367100000002], ['online_vcpus', 1], >> > ['up_time', '0.922783136368'], ['start_time', '1165766218.22'], >> > ['store_mfn', 102647], ['console_mfn', 154261]]) >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:296) parseConfig: config is ['domain', ['domid', 7], >> > ['uuid', >> > 'e44ebfc5-f6a6-17ff-1df7-887d3308bcb3'], ['vcpus', 1], ['vcpu_avail', >> > 1], ['cpu_weight', 1.0], ['memory', 256], ['shadow_memory', 0], >> > ['maxmem', 256], ['features', ''], ['name', 'Dom1'], ['on_poweroff', >> > 'destroy'], ['on_reboot', 'restart'], ['on_crash', 'restart'], >> > ['image', ['linux', ['kernel', '/boot/vmlinuz-2.6-xen'], ['ramdisk', >> > '/boot/initrd-2.6.16.29-xen.img'], ['root', '/dev/sda1,ro']]], >> > ['device', ['vif', ['backend', 0], ['script', 'vif-bridge'], >> > ['bridge', 'xenbr0'], ['mac', '00:AA:00:00:11:12']]], ['device', ['vbd', >> > ['backend', 0], ['dev', '/dev/sda1:disk'], ['uname', >> > 'phy:GuestVG/DOM1'], ['mode', 'w']]], ['state', '----c-'], >> > ['shutdown_reason', >> > 'crash'], ['cpu_time', 0.48078367100000002], ['online_vcpus', 1], >> > ['up_time', '0.922783136368'], ['start_time', '1165766218.22'], >> > ['store_mfn', 102647], ['console_mfn', 154261]] >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:395) parseConfig: result is {'shadow_memory': 0, 'uuid': >> > 'e44ebfc5-f6a6-17ff-1df7-887d3308bcb3', 'on_crash': 'restart', >> > 'on_reboot': 'restart', 'localtime': None, 'image': ['linux', ['kernel', >> > '/boot/vmlinuz-2.6-xen'], ['ramdisk', >> > '/boot/initrd-2.6.16.29-xen.img'], ['root', '/dev/sda1,ro']], >> > 'on_poweroff': 'destroy', >> > 'bootloader_args': None, 'cpus': None, 'name': 'Dom1', 'backend': [], >> > 'vcpus': 1, 'cpu_weight': 1.0, 'features': '', 'vcpu_avail': 1, >> > 'memory': 256, 'device': [('vif', ['vif', ['backend', 0], ['script', >> > 'vif-bridge'], ['bridge', 'xenbr0'], ['mac', '00:AA:00:00:11:12']]), >> > ('vbd', ['vbd', ['backend', 0], ['dev', '/dev/sda1:disk'], ['uname', >> > 'phy:GuestVG/DOM1'], ['mode', 'w']])], 'bootloader': None, 'cpu': >> > None, 'maxmem': 256} >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:1253) XendDomainInfo.construct: None >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:1285) XendDomainInfo.initDomain: 8 1.0 >> > [2006-12-10 23:56:59 xend 4801] DEBUG (balloon:133) Balloon: 51792 KiB >> > free; 210752 to scrub; need 262144; retries: 20. >> > [2006-12-10 23:56:59 xend 4801] DEBUG (balloon:141) Balloon: waiting >> > on scrubbing >> > [2006-12-10 23:56:59 xend 4801] DEBUG (balloon:127) Balloon: 262556 >> > KiB free; need 262144; done. >> > [2006-12-10 23:56:59 xend 4801] INFO (image:136) buildDomain os=linux >> > dom=8 vcpus=1 >> > [2006-12-10 23:56:59 xend 4801] DEBUG (image:191) dom = 8 >> > [2006-12-10 23:56:59 xend 4801] DEBUG (image:192) image >> > /boot/vmlinuz-2.6-xen >> > [2006-12-10 23:56:59 xend 4801] DEBUG (image:193) store_evtchn = 1 >> > [2006-12-10 23:56:59 xend 4801] DEBUG (image:194) console_evtchn = 2 >> > [2006-12-10 23:56:59 xend 4801] DEBUG (image:195) cmdline >> > root=/dev/sda1,ro >> > [2006-12-10 23:56:59 xend 4801] DEBUG (image:196) ramdisk >> > /boot/initrd-2.6.16.29-xen.img >> > [2006-12-10 23:56:59 xend 4801] DEBUG (image:197) vcpus = 1 >> > [2006-12-10 23:56:59 xend 4801] DEBUG (image:198) features >> > [2006-12-10 23:56:59 xend 4801] DEBUG (DevController:110) >> > DevController: writing {'backend-id': '0', 'mac': '00:AA:00:00:11:12', >> > 'handle': >> > '0', 'state': '1', 'backend': '/local/domain/0/backend/vif/8/0'} to >> > /local/domain/8/device/vif/0. >> > [2006-12-10 23:56:59 xend 4801] DEBUG (DevController:112) >> > DevController: writing {'bridge': 'xenbr0', 'domain': 'Dom1', >> > 'handle': '0', >> > 'script': '/etc/xen/scripts/vif-bridge', 'state': '1', 'frontend': >> > '/local/domain/8/device/vif/0', 'mac': '00:AA:00:00:11:12', 'online': >> > '1', 'frontend-id': '8'} to /local/domain/0/backend/vif/8/0. >> > [2006-12-10 23:56:59 xend 4801] DEBUG (DevController:110) >> > DevController: writing {'backend-id': '0', 'virtual-device': '2049', >> > 'device-type': 'disk', 'state': '1', 'backend': >> > '/local/domain/0/backend/vbd/8/2049'} to /local/domain/8/device/vbd/2049. >> > [2006-12-10 23:56:59 xend 4801] DEBUG (DevController:112) >> > DevController: writing {'domain': 'Dom1', 'frontend': >> > '/local/domain/8/device/vbd/2049', 'dev': '/dev/sda1', 'state': '1', >> > 'params': 'GuestVG/DOM1', 'mode': 'w', 'online': '1', 'frontend-id': >> > '8', 'type': 'phy'} to /local/domain/0/backend/vbd/8/2049. >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:712) Storing VM details: {'shadow_memory': '0', 'uuid': >> > 'e44ebfc5-f6a6-17ff-1df7-887d3308bcb3', 'on_reboot': 'restart', >> > 'start_time': '1165766219.69', 'on_poweroff': 'destroy', 'name': 'Dom1', >> > 'vcpus': '1', 'vcpu_avail': '1', 'memory': '256', 'on_crash': >> > 'restart', 'image': "(linux (kernel /boot/vmlinuz-2.6-xen) (ramdisk >> > /boot/initrd-2.6.16.29-xen.img) (root '/dev/sda1,ro'))", 'maxmem': '256'} >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:747) Storing domain details: {'console/ring-ref': >> > '174838', >> > 'console/port': '2', 'name': 'Dom1', 'console/limit': '1048576', 'vm': >> > '/vm/e44ebfc5-f6a6-17ff-1df7-887d3308bcb3', 'domid': '8', >> > 'cpu/0/availability': 'online', 'memory/target': '262144', >> > 'store/ring-ref': '174688', 'store/port': '1'} >> > [2006-12-10 23:56:59 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:933) XendDomainInfo.handleShutdownWatch >> > [2006-12-10 23:57:00 xend.XendDomainInfo 4801] WARNING >> > (XendDomainInfo:875) Domain has crashed: name=Dom1 id=8. >> > [2006-12-10 23:57:00 xend.XendDomainInfo 4801] ERROR >> > (XendDomainInfo:1661) VM Dom1 restarting too fast (1.212585 seconds >> > since the last >> > restart). Refusing to restart to avoid loops. >> > [2006-12-10 23:57:00 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:1449) XendDomainInfo.destroy: domid=8 >> > [2006-12-10 23:57:00 xend.XendDomainInfo 4801] DEBUG >> > (XendDomainInfo:1457) XendDomainInfo.destroyDomain(8) >> > it seems that it has tried to create dom1 for two times. >> > THANKS, >> > sml >> > ------------------------------------------------------------------------ >> > >> > _______________________________________________ >> > 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 >> 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 >> > > >-- >GPG key fingerprint: 3883 B308 8256 2246 D3ED A1FF 3A1D 0EAD 41C4 C2F0 >GPG public key availabe on pgp.mit .edu keyserver= = = = = = = = = = = = = = = = = = = 致 礼！ Zhang Binbin binbinzh@126.com 2006-12-11 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Zhangbinbin
2006-Dec-11 06:25 UTC
Re: Fwd: [Xen-users] Why creating DomU failed (seems it is due to LVM)
Thanks a lot!
I did simply cp /{root,etc,dev,bin,sbin,var,usr,lib} from Dom0 to DomU with some
config modification, and mkdir /{home,proc,sys,tmp} in DomU instead of clean
install.
I'll try to blow away all LVM configs...
Best Regards,
Binbin
======= 2006-12-11 14:18:01 您在来信中写道：======>---------- Forwarded message ----------
>From: TMC <tmciolek@gmail.com>
>Date: 11-Dec-2006 10:59
>Subject: Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
>To: steven@savetimehosting.net
>Cc: Zhang Binbin <binbinzh@126.com>, xen-users
<xen-users@lists.xensource.com>
>
>
>On 11/12/06, Steven Dugway <steven@savetimehosting.net> wrote:
>> TMC wrote:
>> > can you please post your config here?
>> >
>> > I suspect that your trying to start LVM configuration from Dom0 in
>> > DomU...
>> >
>> > There are two ways to do things.
>> >
>> > a) put all disk in Dom0 under LVM and manage disk for all DomU
>> > instances that way..
>> That is how I do it and then export the partitions for each domU, works
>> fine with old FC5 packages.
>> Here is an config file:
>>
>> kernel = "/boot/vmlinuz-2.6.18-1.2849.fc6xen"
>> #kernel = "/boot/2.6.16-1.2122_FC5xenU"
>> memory = 250
>> name = "spooner"
>> ramdisk = "/boot/initrd-2.6.18-1.2849.fc6xen.img"
>> vif = [ '' ]
>>
disk=['phy:/dev/VolGroup00/spooner,sda1,w','phy:/dev/VolGroup00/spoonerHS,sda4,w','phy:/dev/VolGroup00/swap1,sda2,w','file:/img/tmpfiles,sda3,w']
>> root = "/dev/sda1 ro"
>>
>
>Ok.
>
>What I suspect is happening is that you have copied a whole parent
>server instance (with a running /etc and such like) instead of doing a
>clean install to your patritions with kickstart, jump-start or
>debootstrap.
>
>This means that your LVM subsystem is looking in /etc, finds configs
>and goesa looking for disks to manage and fails, bacuse it must. you
>are accessing abstracted devices not raw devices in your DomU.
>
>I think you need to blow away (or at least rename) all LVM configs in
>/etc/ of your DomU. They are not needed.
>
>Also you need to change:
>your networking (unless you DHCP)
>hostname
>edit the fstab to refer to /dev/sda1, /dev/sda2, /dev/sda3 and
>/dev/sda4 as required instead of lables or /dev/VolGroup** stuff.
>
>Also Please boot the XenU specific kernel, if your packages provide
>it. Its safer.
>
>
>Hope this helps
>
>Tomasz
>
>
>--
>GPG key fingerprint: 3883 B308 8256 2246 D3ED A1FF 3A1D 0EAD 41C4 C2F0
>GPG public key availabe on pgp.mit .edu keyserver
>
= = = = = = = = = = = = = = = = = = =
致
礼！
Zhangbinbin
binbin.zhang@tom.com
2006-12-11
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Zhang Binbin
2006-Dec-11 06:27 UTC
Re: Fwd: [Xen-users] Why creating DomU failed (seems it is due to LVM)
Thanks a lot!
I did simply cp /{root,etc,dev,bin,sbin,var,usr,lib} from Dom0 to DomU with some
config modification, and mkdir /{home,proc,sys,tmp} in DomU instead of clean
install.
I'll try to blow away all LVM configs...
Best Regards,
Binbin
======= 2006-12-11 14:18:01 您在来信中写道：======>---------- Forwarded message ----------
>From: TMC <tmciolek@gmail.com>
>Date: 11-Dec-2006 10:59
>Subject: Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
>To: steven@savetimehosting.net
>Cc: Zhang Binbin <binbinzh@126.com>, xen-users
<xen-users@lists.xensource.com>
>
>
>On 11/12/06, Steven Dugway <steven@savetimehosting.net> wrote:
>> TMC wrote:
>> > can you please post your config here?
>> >
>> > I suspect that your trying to start LVM configuration from Dom0 in
>> > DomU...
>> >
>> > There are two ways to do things.
>> >
>> > a) put all disk in Dom0 under LVM and manage disk for all DomU
>> > instances that way..
>> That is how I do it and then export the partitions for each domU, works
>> fine with old FC5 packages.
>> Here is an config file:
>>
>> kernel = "/boot/vmlinuz-2.6.18-1.2849.fc6xen"
>> #kernel = "/boot/2.6.16-1.2122_FC5xenU"
>> memory = 250
>> name = "spooner"
>> ramdisk = "/boot/initrd-2.6.18-1.2849.fc6xen.img"
>> vif = [ '' ]
>>
disk=['phy:/dev/VolGroup00/spooner,sda1,w','phy:/dev/VolGroup00/spoonerHS,sda4,w','phy:/dev/VolGroup00/swap1,sda2,w','file:/img/tmpfiles,sda3,w']
>> root = "/dev/sda1 ro"
>>
>
>Ok.
>
>What I suspect is happening is that you have copied a whole parent
>server instance (with a running /etc and such like) instead of doing a
>clean install to your patritions with kickstart, jump-start or
>debootstrap.
>
>This means that your LVM subsystem is looking in /etc, finds configs
>and goesa looking for disks to manage and fails, bacuse it must. you
>are accessing abstracted devices not raw devices in your DomU.
>
>I think you need to blow away (or at least rename) all LVM configs in
>/etc/ of your DomU. They are not needed.
>
>Also you need to change:
>your networking (unless you DHCP)
>hostname
>edit the fstab to refer to /dev/sda1, /dev/sda2, /dev/sda3 and
>/dev/sda4 as required instead of lables or /dev/VolGroup** stuff.
>
>Also Please boot the XenU specific kernel, if your packages provide
>it. Its safer.
>
>
>Hope this helps
>
>Tomasz
>
>
>--
>GPG key fingerprint: 3883 B308 8256 2246 D3ED A1FF 3A1D 0EAD 41C4 C2F0
>GPG public key availabe on pgp.mit .edu keyserver
>
= = = = = = = = = = = = = = = = = = =
致
礼！
Zhang Binbin
binbinzh@126.com
2006-12-11
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Zhang Binbin
2006-Dec-11 07:49 UTC
Re: Fwd: [Xen-users] Why creating DomU failed (seems it is due to LVM)
I''ve searched all "VolGroup00" in DomU /etc, and delete them, but it didn''t help. It still scaned logical volumes and failed: Scanning logical volumes Reading all physical volumes. This may take a while... No volume groups found Activating logical volumes olume group "VolGroup00" not found ERROR: /bin/lvm exited abnormally! (pid 353) Maybe a clean install is a must... Best, Binbin ======= 2006-12-11 14:18:01 you wrote:======>---------- Forwarded message ---------- >From: TMC <tmciolek@gmail.com> >Date: 11-Dec-2006 10:59 >Subject: Re: [Xen-users] Why creating DomU failed (seems it is due to LVM) >To: steven@savetimehosting.net >Cc: Zhang Binbin <binbinzh@126.com>, xen-users <xen-users@lists.xensource.com> > > >On 11/12/06, Steven Dugway <steven@savetimehosting.net> wrote: >> TMC wrote: >> > can you please post your config here? >> > >> > I suspect that your trying to start LVM configuration from Dom0 in >> > DomU... >> > >> > There are two ways to do things. >> > >> > a) put all disk in Dom0 under LVM and manage disk for all DomU >> > instances that way.. >> That is how I do it and then export the partitions for each domU, works >> fine with old FC5 packages. >> Here is an config file: >> >> kernel = "/boot/vmlinuz-2.6.18-1.2849.fc6xen" >> #kernel = "/boot/2.6.16-1.2122_FC5xenU" >> memory = 250 >> name = "spooner" >> ramdisk = "/boot/initrd-2.6.18-1.2849.fc6xen.img" >> vif = [ '''' ] >> disk=[''phy:/dev/VolGroup00/spooner,sda1,w'',''phy:/dev/VolGroup00/spoonerHS,sda4,w'',''phy:/dev/VolGroup00/swap1,sda2,w'',''file:/img/tmpfiles,sda3,w''] >> root = "/dev/sda1 ro" >> > >Ok. > >What I suspect is happening is that you have copied a whole parent >server instance (with a running /etc and such like) instead of doing a >clean install to your patritions with kickstart, jump-start or >debootstrap. > >This means that your LVM subsystem is looking in /etc, finds configs >and goesa looking for disks to manage and fails, bacuse it must. you >are accessing abstracted devices not raw devices in your DomU. > >I think you need to blow away (or at least rename) all LVM configs in >/etc/ of your DomU. They are not needed. > >Also you need to change: >your networking (unless you DHCP) >hostname >edit the fstab to refer to /dev/sda1, /dev/sda2, /dev/sda3 and >/dev/sda4 as required instead of lables or /dev/VolGroup** stuff. > >Also Please boot the XenU specific kernel, if your packages provide >it. Its safer. > > >Hope this helps > >Tomasz > > >-- >GPG key fingerprint: 3883 B308 8256 2246 D3ED A1FF 3A1D 0EAD 41C4 C2F0 >GPG public key availabe on pgp.mit .edu keyserver >= = = = = = = = = = = = = = = = = = = _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
TMC
2006-Dec-11 08:01 UTC
Re: Fwd: [Xen-users] Why creating DomU failed (seems it is due to LVM)
scan DomU /etc/ for ''lvm'' Tomasz On 11/12/06, Zhang Binbin <binbinzh@126.com> wrote:> I''ve searched all "VolGroup00" in DomU /etc, and delete them, but it didn''t help. > It still scaned logical volumes and failed: > > Scanning logical volumes > Reading all physical volumes. This may take a while... > No volume groups found > Activating logical volumes > olume group "VolGroup00" not found > ERROR: /bin/lvm exited abnormally! (pid 353) > > Maybe a clean install is a must... > > Best, > Binbin > > ======= 2006-12-11 14:18:01 you wrote:======> > >---------- Forwarded message ---------- > >From: TMC <tmciolek@gmail.com> > >Date: 11-Dec-2006 10:59 > >Subject: Re: [Xen-users] Why creating DomU failed (seems it is due to LVM) > >To: steven@savetimehosting.net > >Cc: Zhang Binbin <binbinzh@126.com>, xen-users <xen-users@lists.xensource.com> > > > > > >On 11/12/06, Steven Dugway <steven@savetimehosting.net> wrote: > >> TMC wrote: > >> > can you please post your config here? > >> > > >> > I suspect that your trying to start LVM configuration from Dom0 in > >> > DomU... > >> > > >> > There are two ways to do things. > >> > > >> > a) put all disk in Dom0 under LVM and manage disk for all DomU > >> > instances that way.. > >> That is how I do it and then export the partitions for each domU, works > >> fine with old FC5 packages. > >> Here is an config file: > >> > >> kernel = "/boot/vmlinuz-2.6.18-1.2849.fc6xen" > >> #kernel = "/boot/2.6.16-1.2122_FC5xenU" > >> memory = 250 > >> name = "spooner" > >> ramdisk = "/boot/initrd-2.6.18-1.2849.fc6xen.img" > >> vif = [ '''' ] > >> disk=[''phy:/dev/VolGroup00/spooner,sda1,w'',''phy:/dev/VolGroup00/spoonerHS,sda4,w'',''phy:/dev/VolGroup00/swap1,sda2,w'',''file:/img/tmpfiles,sda3,w''] > >> root = "/dev/sda1 ro" > >> > > > >Ok. > > > >What I suspect is happening is that you have copied a whole parent > >server instance (with a running /etc and such like) instead of doing a > >clean install to your patritions with kickstart, jump-start or > >debootstrap. > > > >This means that your LVM subsystem is looking in /etc, finds configs > >and goesa looking for disks to manage and fails, bacuse it must. you > >are accessing abstracted devices not raw devices in your DomU. > > > >I think you need to blow away (or at least rename) all LVM configs in > >/etc/ of your DomU. They are not needed. > > > >Also you need to change: > >your networking (unless you DHCP) > >hostname > >edit the fstab to refer to /dev/sda1, /dev/sda2, /dev/sda3 and > >/dev/sda4 as required instead of lables or /dev/VolGroup** stuff. > > > >Also Please boot the XenU specific kernel, if your packages provide > >it. Its safer. > > > > > >Hope this helps > > > >Tomasz > > > > > >-- > >GPG key fingerprint: 3883 B308 8256 2246 D3ED A1FF 3A1D 0EAD 41C4 C2F0 > >GPG public key availabe on pgp.mit .edu keyserver > > > > = = = = = = = = = = = = = = = = = = = > > > > > >-- GPG key fingerprint: 3883 B308 8256 2246 D3ED A1FF 3A1D 0EAD 41C4 C2F0 GPG public key availabe on pgp.mit .edu keyserver _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Steven Dugway
2006-Dec-11 16:04 UTC
Re: Fwd: [Xen-users] Why creating DomU failed (seems it is due to LVM)
TMC wrote:> scan DomU /etc/ for ''lvm'' > > Tomasz > > On 11/12/06, Zhang Binbin <binbinzh@126.com> wrote: >> I''ve searched all "VolGroup00" in DomU /etc, and delete them, but it >> didn''t help. >> It still scaned logical volumes and failed: >> >> Scanning logical volumes >> Reading all physical volumes. This may take a while... >> No volume groups found >> Activating logical volumes >> olume group "VolGroup00" not found >> ERROR: /bin/lvm exited abnormally! (pid 353)Same thing for me, even with a freshly compiled kernel, it is definytly related to LVM. We are in the dark here, any help from a speciallist on LVM and how it boots who be greatly appreciated. ++>> >> Maybe a clean install is a must... >> >> Best, >> Binbin >> >> ======= 2006-12-11 14:18:01 you wrote:======>> >> >---------- Forwarded message ---------- >> >From: TMC <tmciolek@gmail.com> >> >Date: 11-Dec-2006 10:59 >> >Subject: Re: [Xen-users] Why creating DomU failed (seems it is due >> to LVM) >> >To: steven@savetimehosting.net >> >Cc: Zhang Binbin <binbinzh@126.com>, xen-users >> <xen-users@lists.xensource.com> >> > >> > >> >On 11/12/06, Steven Dugway <steven@savetimehosting.net> wrote: >> >> TMC wrote: >> >> > can you please post your config here? >> >> > >> >> > I suspect that your trying to start LVM configuration from Dom0 in >> >> > DomU... >> >> > >> >> > There are two ways to do things. >> >> > >> >> > a) put all disk in Dom0 under LVM and manage disk for all DomU >> >> > instances that way.. >> >> That is how I do it and then export the partitions for each domU, >> works >> >> fine with old FC5 packages. >> >> Here is an config file: >> >> >> >> kernel = "/boot/vmlinuz-2.6.18-1.2849.fc6xen" >> >> #kernel = "/boot/2.6.16-1.2122_FC5xenU" >> >> memory = 250 >> >> name = "spooner" >> >> ramdisk = "/boot/initrd-2.6.18-1.2849.fc6xen.img" >> >> vif = [ '''' ] >> >> >> disk=[''phy:/dev/VolGroup00/spooner,sda1,w'',''phy:/dev/VolGroup00/spoonerHS,sda4,w'',''phy:/dev/VolGroup00/swap1,sda2,w'',''file:/img/tmpfiles,sda3,w''] >> >> >> root = "/dev/sda1 ro" >> >> >> > >> >Ok. >> > >> >What I suspect is happening is that you have copied a whole parent >> >server instance (with a running /etc and such like) instead of doing a >> >clean install to your patritions with kickstart, jump-start or >> >debootstrap. >> > >> >This means that your LVM subsystem is looking in /etc, finds configs >> >and goesa looking for disks to manage and fails, bacuse it must. you >> >are accessing abstracted devices not raw devices in your DomU. >> > >> >I think you need to blow away (or at least rename) all LVM configs in >> >/etc/ of your DomU. They are not needed. >> > >> >Also you need to change: >> >your networking (unless you DHCP) >> >hostname >> >edit the fstab to refer to /dev/sda1, /dev/sda2, /dev/sda3 and >> >/dev/sda4 as required instead of lables or /dev/VolGroup** stuff. >> > >> >Also Please boot the XenU specific kernel, if your packages provide >> >it. Its safer. >> > >> > >> >Hope this helps >> > >> >Tomasz >> > >> > >> >-- >> >GPG key fingerprint: 3883 B308 8256 2246 D3ED A1FF 3A1D 0EAD 41C4 C2F0 >> >GPG public key availabe on pgp.mit .edu keyserver >> > >> >> = = = = = = = = = = = = = = = = = = = >> >> >> >> >> >> > >-- 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
Steven Dugway
2006-Dec-11 22:18 UTC
Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
TMC wrote:> On 11/12/06, Steven Dugway <steven@savetimehosting.net> wrote: >> TMC wrote: >> > can you please post your config here? >> > >> > I suspect that your trying to start LVM configuration from Dom0 in >> > DomU... >> > >> > There are two ways to do things. >> > >> > a) put all disk in Dom0 under LVM and manage disk for all DomU >> > instances that way.. >> That is how I do it and then export the partitions for each domU, works >> fine with old FC5 packages. >> Here is an config file: >> >> kernel = "/boot/vmlinuz-2.6.18-1.2849.fc6xen" >> #kernel = "/boot/2.6.16-1.2122_FC5xenU" >> memory = 250 >> name = "spooner" >> ramdisk = "/boot/initrd-2.6.18-1.2849.fc6xen.img" >> vif = [ '''' ] >> disk=[''phy:/dev/VolGroup00/spooner,sda1,w'',''phy:/dev/VolGroup00/spoonerHS,sda4,w'',''phy:/dev/VolGroup00/swap1,sda2,w'',''file:/img/tmpfiles,sda3,w''] >> >> root = "/dev/sda1 ro" >> > > Ok. > > What I suspect is happening is that you have copied a whole parent > server instance (with a running /etc and such like) instead of doing a > clean install to your patritions with kickstart, jump-start or > debootstrap. >This is not working. There is some mystery about the initrd setup. I did everything I could test on my own and from suggestions on this list, in vain. It is hard to make timely decisions with the current state of affairs with Xen. I spent 4 months since the first broken package in FC5 in september to try to get my Centos domU running and nothing works, which means I am stuck with old version of Xen. I had hope the FC6 version would fix it but no. The centos no better. Does anybody know a GNU linux distro that is serious about supporting Xen? I did figure out the howtos of mkinird and the ramdisk concepts, the problem is I do not know what to put/modify inside to make it work. This is very frustrating. Thanks anyway.> This means that your LVM subsystem is looking in /etc, finds configs > and goesa looking for disks to manage and fails, bacuse it must. you > are accessing abstracted devices not raw devices in your DomU. > > I think you need to blow away (or at least rename) all LVM configs in > /etc/ of your DomU. They are not needed. > > Also you need to change: > your networking (unless you DHCP) > hostname > edit the fstab to refer to /dev/sda1, /dev/sda2, /dev/sda3 and > /dev/sda4 as required instead of lables or /dev/VolGroup** stuff. > > Also Please boot the XenU specific kernel, if your packages provide > it. Its safer. > > > Hope this helps > > Tomasz >-- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Mark Nijmeijer
2006-Dec-12 01:53 UTC
Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
> > > I did figure out the howtos of mkinird and the ramdisk concepts, the > problem is I do not know what to put/modify inside to make it work. > This is very frustrating. >Try adding insmod xenbk to the init script in the initrd. You will have to copy that module into the /lib directory of the initrd as well. I believe the fc6 xen kernel has the back end block driver compiled as a module, and because dom0 doesn''t need this module, it''s not in the dom0 initrd. Greetz, Mark _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christopher G. Stach II
2006-Dec-12 03:38 UTC
Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
Steven Dugway wrote:> This is not working. > > There is some mystery about the initrd setup. > I did everything I could test on my own and from suggestions on this > list, in vain. > > It is hard to make timely decisions with the current state of affairs > with Xen. I spent 4 months since the first broken package in FC5 in > september to try to get my Centos domU running and nothing works, which > means I am stuck with old version of Xen. I had hope the FC6 version > would fix it but no. The centos no better. Does anybody know a GNU linux > distro that is serious about supporting Xen? > > I did figure out the howtos of mkinird and the ramdisk concepts, the > problem is I do not know what to put/modify inside to make it work. > This is very frustrating. > > Thanks anyway.Plenty of people are using it with plenty of success. It works on multiple distributions. It works for people who compile it on their own. Where do you think the problem lies? -- Christopher G. Stach II _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ulrich Windl
2006-Dec-12 08:01 UTC
Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
On 11 Dec 2006 at 16:18, Steven Dugway wrote:> I did figure out the howtos of mkinird and the ramdisk concepts, the > problem is I do not know what to put/modify inside to make it work. > This is very frustrating. >Have you tried to simply run it (=mkinitrd) from within chroot-ing into the mounted system? For SUSE you might also adjust /etc/sysconfig/kernel ... Ulrich _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Zhang Binbin
2006-Dec-12 08:01 UTC
Re: Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
I moved a little :-) Something does be wrong with initrd. I make a new initrd according to DomU''s fstab: # mount /dev/GuestVG/DOM1 /mnt # mkinitrd --fstab=/mnt/etc/fstab /boot/initrd.2.6.16.29-xenU.img 2.6.16.29-xen # umount /mnt then create Dom1 there is no more LVM info. but it still failed to mount /root. I''m working to find out why... ======= 2006-12-12 05:20:33 you wrote:======>TMC wrote: >> On 11/12/06, Steven Dugway <steven@savetimehosting.net> wrote: >>> TMC wrote: >>> > can you please post your config here? >>> > >>> > I suspect that your trying to start LVM configuration from Dom0 in >>> > DomU... >>> > >>> > There are two ways to do things. >>> > >>> > a) put all disk in Dom0 under LVM and manage disk for all DomU >>> > instances that way.. >>> That is how I do it and then export the partitions for each domU, works >>> fine with old FC5 packages. >>> Here is an config file: >>> >>> kernel = "/boot/vmlinuz-2.6.18-1.2849.fc6xen" >>> #kernel = "/boot/2.6.16-1.2122_FC5xenU" >>> memory = 250 >>> name = "spooner" >>> ramdisk = "/boot/initrd-2.6.18-1.2849.fc6xen.img" >>> vif = [ '''' ] >>> disk=[''phy:/dev/VolGroup00/spooner,sda1,w'',''phy:/dev/VolGroup00/spoonerHS,sda4,w'',''phy:/dev/VolGroup00/swap1,sda2,w'',''file:/img/tmpfiles,sda3,w''] >>> >>> root = "/dev/sda1 ro" >>> >> >> Ok. >> >> What I suspect is happening is that you have copied a whole parent >> server instance (with a running /etc and such like) instead of doing a >> clean install to your patritions with kickstart, jump-start or >> debootstrap. >> >This is not working. > >There is some mystery about the initrd setup. >I did everything I could test on my own and from suggestions on this >list, in vain. > >It is hard to make timely decisions with the current state of affairs >with Xen. I spent 4 months since the first broken package in FC5 in >september to try to get my Centos domU running and nothing works, which >means I am stuck with old version of Xen. I had hope the FC6 version >would fix it but no. The centos no better. Does anybody know a GNU linux >distro that is serious about supporting Xen? > >I did figure out the howtos of mkinird and the ramdisk concepts, the >problem is I do not know what to put/modify inside to make it work. >This is very frustrating. > >Thanks anyway. > >> This means that your LVM subsystem is looking in /etc, finds configs >> and goesa looking for disks to manage and fails, bacuse it must. you >> are accessing abstracted devices not raw devices in your DomU. >> >> I think you need to blow away (or at least rename) all LVM configs in >> /etc/ of your DomU. They are not needed. >> >> Also you need to change: >> your networking (unless you DHCP) >> hostname >> edit the fstab to refer to /dev/sda1, /dev/sda2, /dev/sda3 and >> /dev/sda4 as required instead of lables or /dev/VolGroup** stuff. >> >> Also Please boot the XenU specific kernel, if your packages provide >> it. Its safer. >> >> >> Hope this helps >> >> Tomasz >> > >-- > >_______________________________________________ >Xen-users mailing list >Xen-users@lists.xensource.com >http://lists.xensource.com/xen-users= = = = = = = = = = = = = = = = = = = _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
lists@higgers.me.uk
2006-Dec-12 08:20 UTC
[Xen-users] Is it Possible to use ISO Image to Boot HVM DomU?
Hi All, Is it possible to use an ISO image of an OS installation disc to start an HVM DomU install? I''d like to be able to install a domU remotely but at the moment I have to climb over loads of old tins of paint in my cellar to get to my server to put the windows 2003 server install CD in the CD drive. :-) Thanks in advance, Steve. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Zhang Binbin
2006-Dec-12 08:25 UTC
Re: [Xen-users] Is it Possible to use ISO Image to Boot HVM DomU?
disk = [ ''phy:/dev/GuestVG/HVM1,ioemu:hda,w'',''file:/tmp/WIN2KSP2_3IN1_CN.ISO,hdc:cdrom,r'' ] it succeeds, but it is a local ISO image. ======= 2006-12-12 16:21:10 you wrote:======>Hi All, > >Is it possible to use an ISO image of an OS installation disc to start an HVM >DomU install? I''d like to be able to install a domU remotely but at >the moment >I have to climb over loads of old tins of paint in my cellar to get to >my server >to put the windows 2003 server install CD in the CD drive. :-) > >Thanks in advance, > >Steve. > > > >_______________________________________________ >Xen-users mailing list >Xen-users@lists.xensource.com >http://lists.xensource.com/xen-users >= = = = = = = = = = = = = = = = = = = _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
lists@higgers.me.uk
2006-Dec-12 08:26 UTC
Re: [Xen-users] Is it Possible to use ISO Image to Boot HVM DomU?
I think I''ve answered my own question. Put the path to the ISO file in the cdrom= line of the xen config file! Quoting lists@higgers.me.uk:> Hi All, > > Is it possible to use an ISO image of an OS installation disc to start an HVM > DomU install? I''d like to be able to install a domU remotely but at > the moment > I have to climb over loads of old tins of paint in my cellar to get > to my server > to put the windows 2003 server install CD in the CD drive. :-) > > Thanks in advance, > > Steve. > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ulrich Windl
2006-Dec-12 12:58 UTC
Re: [Xen-users] Is it Possible to use ISO Image to Boot HVM DomU?
On 12 Dec 2006 at 16:25, Zhang Binbin wrote:> disk = [ ''phy:/dev/GuestVG/HVM1,ioemu:hda,w'',''file:/tmp/WIN2KSP2_3IN1_CN.ISO,hdc:cdrom,r'' ]Stupid question: Where is the definitive reference (besides the python source, maybe, for this syntax. I found a "cdrom=" in some example file, and I''m wondering why "ioemu:hda,w", but "hdc:cdrom,r"... Regards, Ulrich _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Henning Sprang
2006-Dec-12 14:04 UTC
Re: [Xen-users] Is it Possible to use ISO Image to Boot HVM DomU?
On 12/12/06, Ulrich Windl <ulrich.windl@rz.uni-regensburg.de> wrote:> [...] > Stupid question: > Where is the definitive reference (besides the python source, > maybe, for this syntax. I found a "cdrom=" in some example file, and I''m wondering > why "ioemu:hda,w", but "hdc:cdrom,r"...I guess there''s nothing better than the source in this case (but I am not sure if even this gives you a fast and easy answer here). There is the user manual, and "man xmdomain.cfg", and the example files that come with the xen packages. But they seem all be incomplete, and not to answer your question. Maybe there''s a release announcement that tells more about the changes, or the developers can answer this. The cdrom= syntax has changed in 3.0.3 example files to the above (see also hvmexample cofig file), but I haven''t played that much with 3.0.3 and hvm to know if cdrom= is completely obsolete now. Henning _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Steven Dugway
2006-Dec-12 15:55 UTC
Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
Christopher G. Stach II wrote:> Steven Dugway wrote: > >> This is not working. >> >> There is some mystery about the initrd setup. >> I did everything I could test on my own and from suggestions on this >> list, in vain. >> >> It is hard to make timely decisions with the current state of affairs >> with Xen. I spent 4 months since the first broken package in FC5 in >> september to try to get my Centos domU running and nothing works, which >> means I am stuck with old version of Xen. I had hope the FC6 version >> would fix it but no. The centos no better. Does anybody know a GNU linux >> distro that is serious about supporting Xen? >> >> I did figure out the howtos of mkinird and the ramdisk concepts, the >> problem is I do not know what to put/modify inside to make it work. >> This is very frustrating. >> >> Thanks anyway. >> > > Plenty of people are using it with plenty of success. It works on > multiple distributions. It works for people who compile it on their > own. Where do you think the problem lies? > >Well, maybe it is because I am not a kernel hacker? Looks like many people have had the same problem for months. It is not limited to FC5-6 or CentOS, looks like people with SUSE and Debian have many similar problems. I remember when moving from FC4 to FC5 I had a similar problem, had to rebuild all my domU, now this is no longer an option for me, the alternative (droping Xen for now) seems more appropriate, the question then would be for what? Vmware, OpenVZ etc. all have pros and cons so I would rather fix the Xen problem with booting, after all if you cannot boot you cannot Xen. ++ -- sTEVEN _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christopher G. Stach II
2006-Dec-12 16:46 UTC
Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
Steven Dugway wrote:> Well, maybe it is because I am not a kernel hacker? > > Looks like many people have had the same problem for months. It is not > limited to FC5-6 or CentOS, looks like people with SUSE and Debian have > many similar problems.You don''t have to know much about a kernel to get it to work. Start fresh with a very plain dom0. Don''t use an initrd for _anything_. initrds are only good for dynamic kernel configuration on unknown hardware setups (great for distros) and certain network booting configurations. -- Christopher G. Stach II _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tim Post
2006-Dec-12 16:58 UTC
Re: [Xen-users] Is it Possible to use ISO Image to Boot HVM DomU?
On Tue, 2006-12-12 at 15:04 +0100, Henning Sprang wrote:> On 12/12/06, Ulrich Windl <ulrich.windl@rz.uni-regensburg.de> wrote:> The cdrom= syntax has changed in 3.0.3 example files to the above (see > also hvmexample cofig file), but I haven''t played that much with 3.0.3 > and hvm to know if cdrom= is completely obsolete now. > > Henning >afaik, both work, but cdrom= is about to be depreciated. You should specify cdrom just like any other vbd or face breakage on the next (or next to next) release upgrade. I''ve only tried it specifying the cdrom just like any other vbd, which works fine in 3.0.3 Best, -Tim> _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats
2006-Dec-12 17:08 UTC
RE: [Xen-users] Is it Possible to use ISO Image to Boot HVM DomU?
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Tim Post > Sent: 12 December 2006 16:58 > To: Henning Sprang > Cc: Ulrich Windl; xen-users > Subject: Re: [Xen-users] Is it Possible to use ISO Image to > Boot HVM DomU? > > On Tue, 2006-12-12 at 15:04 +0100, Henning Sprang wrote: > > On 12/12/06, Ulrich Windl <ulrich.windl@rz.uni-regensburg.de> wrote: > > > > The cdrom= syntax has changed in 3.0.3 example files to the > above (see > > also hvmexample cofig file), but I haven''t played that much > with 3.0.3 > > and hvm to know if cdrom= is completely obsolete now. > > > > Henning > > > > afaik, both work, but cdrom= is about to be depreciated. You should > specify cdrom just like any other vbd or face breakage on the next (or > next to next) release upgrade. > > I''ve only tried it specifying the cdrom just like any other vbd, which > works fine in 3.0.3I actually believe it''s NOT working in 3.0.3 but I could be wrong. Anyway, the "new" syntax should be used in 3.0.3 and future configurations, that''s for sure. -- Mats> > Best, > -Tim > > > _______________________________________________ > > Xen-users mailing list > > Xen-users@lists.xensource.com > > http://lists.xensource.com/xen-users > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Steven Dugway
2006-Dec-12 17:14 UTC
Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
Christopher G. Stach II wrote:> Steven Dugway wrote: > >> Well, maybe it is because I am not a kernel hacker? >> >> Looks like many people have had the same problem for months. It is not >> limited to FC5-6 or CentOS, looks like people with SUSE and Debian have >> many similar problems. >> > > You don''t have to know much about a kernel to get it to work. Start > fresh with a very plain dom0. Don''t use an initrd for _anything_. > initrds are only good for dynamic kernel configuration on unknown > hardware setups (great for distros) and certain network booting > configurations. > >Hi, Sound simple BUT it is not. I did with RPM and by compiling from source. I never succeeded in starting any dom0 OR domU without an initrd as stated by many. With an initrd it worked fine with old versions of Xen (3.0.2 etc.). Thanks anyway. -- Steven _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christopher G. Stach II
2006-Dec-12 17:23 UTC
Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
Steven Dugway wrote:> > Hi, > > Sound simple BUT it is not. I did with RPM and by compiling from source. > > I never succeeded in starting any dom0 OR domU without an initrd as > stated by many. > With an initrd it worked fine with old versions of Xen (3.0.2 etc.). > > Thanks anyway. >Yeah, that sounds pretty hopeless. Good luck with Windows. :) -- Christopher G. Stach II _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Petersson, Mats
2006-Dec-12 17:25 UTC
RE: [Xen-users] Why creating DomU failed (seems it is due to LVM)
> -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of > Steven Dugway > Sent: 12 December 2006 17:14 > To: Christopher G. Stach II > Cc: xen-users > Subject: Re: [Xen-users] Why creating DomU failed (seems it > is due to LVM) > > Christopher G. Stach II wrote: > > Steven Dugway wrote: > > > >> Well, maybe it is because I am not a kernel hacker? > >> > >> Looks like many people have had the same problem for > months. It is not > >> limited to FC5-6 or CentOS, looks like people with SUSE > and Debian have > >> many similar problems. > >> > > > > You don''t have to know much about a kernel to get it to work. Start > > fresh with a very plain dom0. Don''t use an initrd for _anything_. > > initrds are only good for dynamic kernel configuration on unknown > > hardware setups (great for distros) and certain network booting > > configurations. > > > > > > Hi, > > Sound simple BUT it is not. I did with RPM and by compiling > from source. > > I never succeeded in starting any dom0 OR domU without an initrd as > stated by many. > With an initrd it worked fine with old versions of Xen (3.0.2 etc.). > > Thanks anyway.Creating an initrd file isn''t rocket surgery in itself Making a system boot when you haven''t got the right drivers can be a pain in the posterior... If you know what drivers you need to make the system boot and you''re changing your config file to make that work, you may just as well skip the part of making something a module - it doesn''t ACTUALLY help anything to have a module instead of a built-in driver. On the other hand, if you don''t have a clue what driver you actually need, and you''re adding drivers "wholesale", you probably don''t want to bloat the kernel by adding all of your drivers as "builtin", even if it saves you a bit of hassle by not creating an initrd. It''s often a good idea to start by using a simple setup - LVM, RAID, SCSI all add extra complications and more drivers are needed. Some of which may not work in a particular permutation of Xen + Dom0! If you can''t make the machine boot in a complex setup, you may want to try a simpler setup before you try reconfiguring the kernel. Obviously, if you use LVM, you''ll need the relevant "lvm modules" either builtin (my recommendation) or as a module when you build the initrd. Carefull inspection of "dmesg" and any other "boot output" will also be useful. "lspci" is a good hint. Note also that if you build Xen on one machine, and install on another, you''ll need to do "depmod" as well as "mkinitrd" - and if you''re copying individual files, make sure you copy the modules to the right place under /lib/modules/ - it happens automagically if you copy the whole .../dist directory, but I sometimes try to cheat by copying individual files, and it''s been known to "fail". -- Mats> > -- > Steven > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Christopher G. Stach II
2006-Dec-12 17:33 UTC
Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
Steven Dugway wrote:> Hi, > > Sound simple BUT it is not. I did with RPM and by compiling from source. > > I never succeeded in starting any dom0 OR domU without an initrd as > stated by many. > With an initrd it worked fine with old versions of Xen (3.0.2 etc.). > > Thanks anyway. >Maybe if you gave the list your processor type, motherboard model, amount of memory, and lspci output, some kind soul would make a dom0 .config for you to use, or even a kernel image. It might not be ideal, and it might be overconfigured, but it would probably boot just fine. -- Christopher G. Stach II _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Jaroslaw Zdrzalek
2006-Dec-12 19:40 UTC
Re: [Xen-users] Is it Possible to use ISO Image to Boot HVM DomU?
Am Dienstag 12 Dezember 2006 15:04 schrieb Henning Sprang:> On 12/12/06, Ulrich Windl <ulrich.windl@rz.uni-regensburg.de> wrote: > > [...] > > Stupid question: > > Where is the definitive reference (besides the python source, > > maybe, for this syntax. I found a "cdrom=" in some example file, and I''m wondering > > why "ioemu:hda,w", but "hdc:cdrom,r"...according to this post: http://lists.xensource.com/archives/html/xen-devel/2006-08/msg00369.html the syntax for the hvm config file has changed since 3.0.3. ioemu becomes obsolete, it is ignored by the parser...> > I guess there''s nothing better than the source in this case (but I am > not sure if even this gives you a fast and easy answer here). There is > the user manual, and "man xmdomain.cfg", and the example files that > come with the xen packages. But they seem all be incomplete, and not > to answer your question. > Maybe there''s a release announcement that tells more about the > changes, or the developers can answer this. > > The cdrom= syntax has changed in 3.0.3 example files to the above (see > also hvmexample cofig file), but I haven''t played that much with 3.0.3 > and hvm to know if cdrom= is completely obsolete now. > > Henning > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >cheers Jaroslaw _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Etienne Duguay
2006-Dec-13 01:17 UTC
Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
Zhang Binbin wrote:> I moved a little :-) > Something does be wrong with initrd. > I make a new initrd according to DomU''s fstab: > # mount /dev/GuestVG/DOM1 /mnt > # mkinitrd --fstab=/mnt/etc/fstab /boot/initrd.2.6.16.29-xenU.img 2.6.16.29-xen > # umount /mnt > then create Dom1 > there is no more LVM info. > but it still failed to mount /root. I''m working to find out why... >Hi, I am making progress, I will publish the results soon, takes roughly an hour for each compile, already made a few today. The tricky part is figuring out the ramdisk. I found this document helpful for initrd understanding and creation: http://www-128.ibm.com/developerworks/linux/library/l-initrd.html ++> ======= 2006-12-12 05:20:33 you wrote:======> > >> TMC wrote: >> >>> On 11/12/06, Steven Dugway <steven@savetimehosting.net> wrote: >>> >>>> TMC wrote: >>>> >>>>> can you please post your config here? >>>>> >>>>> I suspect that your trying to start LVM configuration from Dom0 in >>>>> DomU... >>>>> >>>>> There are two ways to do things. >>>>> >>>>> a) put all disk in Dom0 under LVM and manage disk for all DomU >>>>> instances that way.. >>>>> >>>> That is how I do it and then export the partitions for each domU, works >>>> fine with old FC5 packages. >>>> Here is an config file: >>>> >>>> kernel = "/boot/vmlinuz-2.6.18-1.2849.fc6xen" >>>> #kernel = "/boot/2.6.16-1.2122_FC5xenU" >>>> memory = 250 >>>> name = "spooner" >>>> ramdisk = "/boot/initrd-2.6.18-1.2849.fc6xen.img" >>>> vif = [ '''' ] >>>> disk=[''phy:/dev/VolGroup00/spooner,sda1,w'',''phy:/dev/VolGroup00/spoonerHS,sda4,w'',''phy:/dev/VolGroup00/swap1,sda2,w'',''file:/img/tmpfiles,sda3,w''] >>>> >>>> root = "/dev/sda1 ro" >>>> >>>> >>> Ok. >>> >>> What I suspect is happening is that you have copied a whole parent >>> server instance (with a running /etc and such like) instead of doing a >>> clean install to your patritions with kickstart, jump-start or >>> debootstrap. >>> >>> >> This is not working. >> >> There is some mystery about the initrd setup. >> I did everything I could test on my own and from suggestions on this >> list, in vain. >> >> It is hard to make timely decisions with the current state of affairs >> with Xen. I spent 4 months since the first broken package in FC5 in >> september to try to get my Centos domU running and nothing works, which >> means I am stuck with old version of Xen. I had hope the FC6 version >> would fix it but no. The centos no better. Does anybody know a GNU linux >> distro that is serious about supporting Xen? >> >> I did figure out the howtos of mkinird and the ramdisk concepts, the >> problem is I do not know what to put/modify inside to make it work. >> This is very frustrating. >> >> Thanks anyway. >> >> >>> This means that your LVM subsystem is looking in /etc, finds configs >>> and goesa looking for disks to manage and fails, bacuse it must. you >>> are accessing abstracted devices not raw devices in your DomU. >>> >>> I think you need to blow away (or at least rename) all LVM configs in >>> /etc/ of your DomU. They are not needed. >>> >>> Also you need to change: >>> your networking (unless you DHCP) >>> hostname >>> edit the fstab to refer to /dev/sda1, /dev/sda2, /dev/sda3 and >>> /dev/sda4 as required instead of lables or /dev/VolGroup** stuff. >>> >>> Also Please boot the XenU specific kernel, if your packages provide >>> it. Its safer. >>> >>> >>> Hope this helps >>> >>> Tomasz >>> >>> >> -- >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> > > = = = = = = = = = = = = = = = = = = = > > > > > > >-- Etienne R. Duguay 514-939-HOST (4678) ext 5 Author of/ Auteur de "Se lancer en affaires dans Internet" ISBN 2-89521-001-2; ISBN 2-89472-062-9 Virtual Space International INC., -------------------------------------------------------------- Internet Is Here To Stay, Make Sure Your Business Is! http://www.savetimehosting.net / 25-50% commission for life on referrals -------------------------------------------------------------- "The best way to predict the future is to invent it" Alan Kay "One who trades freedom for security deserves neither." -Benjamin Franklin "most propaganda is not designed to fool the critical thinker but only to give moral cowards an excuse not to think at all." - Michael Rivero "Anyone who believes exponential growth can go on forever in a finite world is either a madman or an economist." - Kenneth Boulding "The State''s coercive interference in either money or banking, including its licensing of a monopolistic central bank, reduces all men''s freedom and most men''s wealth" -Ludwig von Mises "The Law, when the law, which is force and can be legitimately used only in defense of just rights to life and property, is perverted into an instrument of aggression, slavery, theft, and plunder, it has destroyed its own object" -Frédéric Bastiat "A fine is a tax you pay for doing wrong, and a tax is a fine you pay for doing all right" -Unknown _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Zhang Binbin
2006-Dec-13 02:53 UTC
Re: Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
In default config, blkfront is built in the kernel. So there is no xenblk.ko in modules. Do I have to make it as a module? Thanks. BTW: This is copied from menuconfig of XenU kernel: [ ] Privileged Guest (domain 0) < > Backend driver support <*> Block-device frontend driver <*> Network-device frontend driver [*] Scrub memory before freeing it to Xen [*] Disable serial port drivers <*> Export Xen attributes in sysfs Xen version compatibility (3.0.2 and later) ---> ======= 2006-12-13 02:39:04 you wrote:======>you can find the module in >/lib/modules/<kernelversion>/kernel/drivers/xen/blkfront >for me it''s here : >/lib/modules/2.6.18-1.2798.fc6xen/kernel/drivers/xen/blkfront/xenblk.ko > >copy that file to /initrd/lib >then add insmod /lib/xenblk.ko to the init file > >re-create the initrd file from your /initrd directory, and change the VM >config to use this initrd, instead of the one in /boot. > > > > >Zhang Binbin wrote: > >>Thanks for your suggestion! >>I changed initrd for DomU, and lvm problem has been resolved. >>but kernel still panic when creating DomU: >> >>===============================================================================================>># xm create domUconfig >>Using config file "dom1_config". >>Started domain Dom1 >>Bootdata ok (command line is root=/dev/hda1,ro) >>Linux version 2.6.16.29-xen (root@localhost.localdomain) (gcc version 3.4.6 20060404 (Red Hat 3.4.6 >> >>-3)) #3 SMP Tue Dec 12 15:59:19 CST 2006 >>BIOS-provided physical RAM map: >> Xen: 0000000000000000 - 0000000010800000 (usable) >>No mptable found. >>Built 1 zonelists >>Kernel command line: root=/dev/hda1,ro >>Initializing CPU#0 >>PID hash table entries: 2048 (order: 11, 65536 bytes) >>Xen reported: 1862.322 MHz processor. >>Dentry cache hash table entries: 65536 (order: 7, 524288 bytes) >>Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) >>Software IO TLB disabled >>Memory: 249944k/270336k available (2000k kernel code, 11868k reserved, 883k data, 172k init) >>Calibrating delay using timer specific routine.. 3726.62 BogoMIPS (lpj=18633142) >>Security Framework v1.0.0 initialized >>Capability LSM initialized >>Mount-cache hash table entries: 256 >>CPU: L1 I cache: 32K, L1 D cache: 32K >>CPU: L2 cache: 2048K >>CPU: Physical Processor ID: 0 >>CPU: Processor Core ID: 0 >>Brought up 1 CPUs >>migration_cost=0 >>checking if image is initramfs... it is >>Freeing initrd memory: 2141k freed >>DMI not present or invalid. >>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 >>pnp: PnP ACPI: disabled >>xen_mem: Initialising balloon driver. >>SCSI subsystem initialized >>PCI: System does not support PCI >>PCI: System does not support PCI >>IA-32 Microcode Update Driver: v1.14-xen <tigran@veritas.com> >>IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $ >>audit: initializing netlink socket (disabled) >>audit(1165911995.790:1): initialized >>VFS: Disk quotas dquot_6.5.1 >>Dquot-cache hash table entries: 512 (order 0, 4096 bytes) >>Initializing Cryptographic API >>io scheduler noop registered >>io scheduler anticipatory registered >>io scheduler deadline registered >>io scheduler cfq registered (default) >>rtc: IRQ 8 is not free. >>Non-volatile memory driver v1.2 >>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 >>loop: loaded (max 8 devices) >>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 3 >>netfront: device eth0 has flipping receive path. >>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 >>NET: Registered protocol family 2 >>IP route cache hash table entries: 4096 (order: 3, 32768 bytes) >>TCP established hash table entries: 16384 (order: 6, 262144 bytes) >>TCP bind hash table entries: 16384 (order: 6, 262144 bytes) >>TCP: Hash tables configured (established 16384 bind 16384) >>TCP reno registered >>NET: Registered protocol family 1 >>NET: Registered protocol family 17 >>Red Hat nash version 4.2.1.8 starting >>Mounted /proc filesystem >>Mounting sysfs >>Creating /dev >>Starting udev >>Loading sd_mod.ko module >>Loading libata.ko module >>Loading ahci.ko module >>Loading ata_piix.ko module >>Loading ide-disk.ko module >>Loading dm-mod.ko module >>device-mapper: 4.5.0-ioctl (2005-10-04) initialised: dm-devel@redhat.com >>Loading jbd.ko module >>Loading ext3.ko module >>Creating root device >>Mounting root filesystem >>mount: error 6 mounting ext3 >>mount: error 2 mounting none >>Switching to new root >>switchroot: mount failed: 22 >>umount /initrd/dev failed: 2 >>Kernel panic - not syncing: Attempted to kill init! >>===============================================================================================>> >>I decompressed the initrd-xenU, this is init script: >>===============================================================================================>>#!/bin/nash >>mount -t proc /proc /proc >>setquiet >>echo Mounted /proc filesystem >>echo Mounting sysfs >>mount -t sysfs none /sys >>echo Creating /dev >>mount -o mode=0755 -t tmpfs none /dev >>mknod /dev/console c 5 1 >>mknod /dev/null c 1 3 >>mknod /dev/zero c 1 5 >>mkdir /dev/pts >>mkdir /dev/shm >>echo Starting udev >>/sbin/udevstart >>echo -n "/sbin/hotplug" > /proc/sys/kernel/hotplug >>echo "Loading libata.ko module" >>insmod /lib/libata.ko >>echo "Loading ahci.ko module" >>insmod /lib/ahci.ko >>echo "Loading ata_piix.ko module" >>insmod /lib/ata_piix.ko >>echo "Loading dm-mod.ko module" >>insmod /lib/dm-mod.ko >>/sbin/udevstart >>echo Creating root device >>mkrootdev /dev/root >>umount /sys >>echo Mounting root filesystem >>mount -o defaults --ro -t ext3 /dev/root /sysroot >>mount -t tmpfs --bind /dev /sysroot/dev >>echo Switching to new root >>switchroot /sysroot >>umount /initrd/dev >>===============================================================================================>>And there is no xenbk module in /initrd/lib/. >>where can I find it please? >> >>Thanks. >> >>======= 2006-12-12 17:51:41 you wrote:======>> >> >> >>>>I did figure out the howtos of mkinird and the ramdisk concepts, the >>>>problem is I do not know what to put/modify inside to make it work. >>>>This is very frustrating. >>>> >>>> >>>> >>>Try adding insmod xenbk to the init script in the initrd. You will have >>>to copy that module into the /lib directory of the initrd as well. >>>I believe the fc6 xen kernel has the back end block driver compiled as a >>>module, and because dom0 doesn''t need this module, it''s not in the dom0 >>>initrd. >>> >>>Greetz, >>> >>>Mark >>> >>> >>>_______________________________________________ >>>Xen-users mailing list >>>Xen-users@lists.xensource.com >>>http://lists.xensource.com/xen-users >>> >>> >>> >> >>= = = = = = = = = = = = = = = = = = = >> >> >> >> >> >> >> >= = = = = = = = = = = = = = = = = = = _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Zhang Binbin
2006-Dec-13 03:36 UTC
Re: Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
Thanks for your suggestion! I checked init in initrd for DomU, and modified mount -o defaults --ro -t ext3 /dev/root /sysroot to mount -o defaults --ro -t ext3 /dev/sda1 /sysroot /dev/sda1 is DomU root device. Then DomU can boot successfully! Waiting for your details :-) Thanks again! ======= 2006-12-13 08:17:37 you wrote:======>Zhang Binbin wrote: >> I moved a little :-) >> Something does be wrong with initrd. >> I make a new initrd according to DomU's fstab: >> # mount /dev/GuestVG/DOM1 /mnt >> # mkinitrd --fstab=/mnt/etc/fstab /boot/initrd.2.6.16.29-xenU.img 2.6.16.29-xen >> # umount /mnt >> then create Dom1 >> there is no more LVM info. >> but it still failed to mount /root. I'm working to find out why... >> >Hi, > >I am making progress, I will publish the results soon, takes roughly an >hour for each compile, already made a few today. >The tricky part is figuring out the ramdisk. > >I found this document helpful for initrd understanding and creation: > >http://www-128.ibm.com/developerworks/linux/library/l-initrd.html > >++ >> ======= 2006-12-12 05:20:33 you wrote:======>> >> >>> TMC wrote: >>> >>>> On 11/12/06, Steven Dugway <steven@savetimehosting.net> wrote: >>>> >>>>> TMC wrote: >>>>> >>>>>> can you please post your config here? >>>>>> >>>>>> I suspect that your trying to start LVM configuration from Dom0 in >>>>>> DomU... >>>>>> >>>>>> There are two ways to do things. >>>>>> >>>>>> a) put all disk in Dom0 under LVM and manage disk for all DomU >>>>>> instances that way.. >>>>>> >>>>> That is how I do it and then export the partitions for each domU, works >>>>> fine with old FC5 packages. >>>>> Here is an config file: >>>>> >>>>> kernel = "/boot/vmlinuz-2.6.18-1.2849.fc6xen" >>>>> #kernel = "/boot/2.6.16-1.2122_FC5xenU" >>>>> memory = 250 >>>>> name = "spooner" >>>>> ramdisk = "/boot/initrd-2.6.18-1.2849.fc6xen.img" >>>>> vif = [ '' ] >>>>> disk=['phy:/dev/VolGroup00/spooner,sda1,w','phy:/dev/VolGroup00/spoonerHS,sda4,w','phy:/dev/VolGroup00/swap1,sda2,w','file:/img/tmpfiles,sda3,w'] >>>>> >>>>> root = "/dev/sda1 ro" >>>>> >>>>> >>>> Ok. >>>> >>>> What I suspect is happening is that you have copied a whole parent >>>> server instance (with a running /etc and such like) instead of doing a >>>> clean install to your patritions with kickstart, jump-start or >>>> debootstrap. >>>> >>>> >>> This is not working. >>> >>> There is some mystery about the initrd setup. >>> I did everything I could test on my own and from suggestions on this >>> list, in vain. >>> >>> It is hard to make timely decisions with the current state of affairs >>> with Xen. I spent 4 months since the first broken package in FC5 in >>> september to try to get my Centos domU running and nothing works, which >>> means I am stuck with old version of Xen. I had hope the FC6 version >>> would fix it but no. The centos no better. Does anybody know a GNU linux >>> distro that is serious about supporting Xen? >>> >>> I did figure out the howtos of mkinird and the ramdisk concepts, the >>> problem is I do not know what to put/modify inside to make it work. >>> This is very frustrating. >>> >>> Thanks anyway. >>> >>> >>>> This means that your LVM subsystem is looking in /etc, finds configs >>>> and goesa looking for disks to manage and fails, bacuse it must. you >>>> are accessing abstracted devices not raw devices in your DomU. >>>> >>>> I think you need to blow away (or at least rename) all LVM configs in >>>> /etc/ of your DomU. They are not needed. >>>> >>>> Also you need to change: >>>> your networking (unless you DHCP) >>>> hostname >>>> edit the fstab to refer to /dev/sda1, /dev/sda2, /dev/sda3 and >>>> /dev/sda4 as required instead of lables or /dev/VolGroup** stuff. >>>> >>>> Also Please boot the XenU specific kernel, if your packages provide >>>> it. Its safer. >>>> >>>> >>>> Hope this helps >>>> >>>> Tomasz >>>> >>>> >>> -- >>> >>> _______________________________________________ >>> Xen-users mailing list >>> Xen-users@lists.xensource.com >>> http://lists.xensource.com/xen-users >>> >> >> = = = = = = = = = = = = = = = = = = = >> >> >> >> >> >> >> > > >-- >Etienne R. Duguay 514-939-HOST (4678) ext 5 >Author of/ Auteur de "Se lancer en affaires dans Internet" >ISBN 2-89521-001-2; ISBN 2-89472-062-9 >Virtual Space International INC., >-------------------------------------------------------------- >Internet Is Here To Stay, Make Sure Your Business Is! >http://www.savetimehosting.net / 25-50% commission for life on referrals >-------------------------------------------------------------- >"The best way to predict the future is to invent it" Alan Kay >"One who trades freedom for security deserves neither." > -Benjamin Franklin >"most propaganda is not designed to fool the critical thinker > but only to give moral cowards an excuse not to think at all." > - Michael Rivero >"Anyone who believes exponential growth can go on forever in a >finite world is either a madman or an economist." > - Kenneth Boulding >"The State's coercive interference in either money or banking, >including its licensing of a monopolistic central bank, >reduces all men's freedom and most men's wealth" > -Ludwig von Mises >"The Law, when the law, which is force and can be legitimately >used only in defense of just rights to life and property, is >perverted into an instrument of aggression, slavery, theft, and >plunder, it has destroyed its own object" > -Frédéric Bastiat >"A fine is a tax you pay for doing wrong, and a tax is a fine >you pay for doing all right" > -Unknown > >= = = = = = = = = = = = = = = = = = = _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Ulrich Windl
2006-Dec-13 07:12 UTC
Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
On 12 Dec 2006 at 9:55, Steven Dugway wrote:> Looks like many people have had the same problem for months. It is notMaybe the problem is the partially poor documentation. Reminds me of...: Rumours said that about 14 years ago SAP Germany had a pattern where every developer had to run the hotline for a week or so. That was very good for getting user input back to the ebony tower ;-) Those people really knew what the error messages meant (or were meant to mean). Of course these days no mortal gets any developer on a hotline, those guys are such precious resources ;-) Regards, Ulrich _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Nico Kadel-Garcia
2006-Dec-14 00:07 UTC
Re: [Xen-users] Why creating DomU failed (seems it is due to LVM)
Ulrich Windl wrote:> Maybe the problem is the partially poor documentation. Reminds me of...: > > Rumours said that about 14 years ago SAP Germany had a pattern where every > developer had to run the hotline for a week or so. That was very good for getting > user input back to the ebony tower ;-) Those people really knew what the error > messages meant (or were meant to mean). Of course these days no mortal gets any > developer on a hotline, those guys are such precious resources ;-) >Heh. When I worked at one place, we put the Q/A people on the hot seat. Everybody took a one-day shift, it went in turns. It made them very, very picky about product testing. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users