Ben Russo
2007-Jun-11 21:51 UTC
[Fedora-xen] XEN-3.0.3 on RHEL-5, fully virtualized guest of RH72 won''t start after install finishes.
I have many boxes running rh-7.2
(these are stripped down, minimal installs, for appliances on a private
network that isn''t routable) I want to run VIRTUAL images of the
same setup for testing purposes.
I read the Fedora 6 XEN getting started guide and skimmed through the
FAQ. I browsed through this mailing list to see if I could find my
problem here as well. No luck.
I have a Dell-2950 with Quad Core XEON processors, PAE, VMX, and it is
enabled in BIOS. 8GB RAM, 2GB assigned to Dom0
Booted into RHEL-5 Xen kernel, installed all the latest patches as of
6/11/2007, and rebooted.
Then Started Virtual Machine Manager GUI
Selected "New..." from File menu and followed the wizard.
then installed FULLY VIRTUALIZED
RH-72 from original Red Hat 7.2 CD''s
this went fine with the
Virtual Machine Manager GUI "New Machine" wizard.
The only non-usual thing I did for an RH72 install was
to give it the kernel boot option mem=500M
After the install completed, the DomU guest said it was now going to
reboot and I should remove any CD''s.
Then the DomU disappeared.
It took me forever to figure out that I couldn''t use the virt-manager
GUI to restore a DomU configuration file. There really should be
a more intuitive way for this to work. I am not a dummy, and it took
me forever to figure out how to start the DomU again.
Now that I figured out that I have to go to a command line prompt and
type "xm create -c /etc/xen/rh72-test",
I find out that the new guest gets a kernel panic on bootup
after the bootup menu
Unfortunately the messages scroll by really fast, and I can''t catch
them all, but at the end, the last page visible in the VNC console
says:
===================================================================Enabling
unmasked SIMD FPU exception support... done.
Checking ''hlt'' instruction... OK.
POSIX conformance testing by UNIFIX
Unable to handle kernel paging request at virtual address ffffffff
printing eip:
c0204a00
*pde = 00001063
*pte = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c0204a00>]
EFLAGS: 00010202
eax: fffffff ebx: 00000000 ecx: 00000004 edx: 00000004
esi: fffffff edi: c0229972 ebp: 0008e000 esp: c0257fb4
ds: 0018 es: 0018 ss: 0018
Process swapper (pid: 0, stackpage=c0257000)
Stack: c026d6e8 0000000 c024....
...
...
Call Trace: [<....
Code: f3 a6 ...
<0>Kernel panic: Attempted to kill the idle task!
In idle task - not syncing
===================================================================
The console where I ran the "xm create..." command shows nothing out
of the ordinary.
xm dmesg shows: ####### START xm dmesg #############
(XEN) (file=hvm.c, line=197) Allocated port 3 for hvm.
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83fc
(pseudophys a0): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83fb
(pseudophys a1): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83fa
(pseudophys a2): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f9
(pseudophys a3): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f8
(pseudophys a4): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f7
(pseudophys a5): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f6
(pseudophys a6): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f5
(pseudophys a7): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f4
(pseudophys a8): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f3
(pseudophys a9): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f2
(pseudophys aa): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f1
(pseudophys ab): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83f0
(pseudophys ac): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83ef
(pseudophys ad): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83ee
(pseudophys ae): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83ed
(pseudophys af): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83ec
(pseudophys b0): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83eb
(pseudophys b1): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83ea
(pseudophys b2): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e9
(pseudophys b3): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e8
(pseudophys b4): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e7
(pseudophys b5): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e6
(pseudophys b6): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e5
(pseudophys b7): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e4
(pseudophys b8): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e3
(pseudophys b9): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e2
(pseudophys ba): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e1
(pseudophys bb): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83e0
(pseudophys bc): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83df
(pseudophys bd): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83de
(pseudophys be): count=2 type=0
(XEN) (file=memory.c, line=188) Dom7 freeing in-use page a83dd
(pseudophys bf): count=2 type=0
(XEN) vmx_do_launch(): GUEST_CR3<=001adda0, HOST_CR3<=001adca0
(XEN) (GUEST: 7) HVM Loader
(XEN) (GUEST: 7) Detected Xen v3.0.3-rc5-8.1.4.el
(XEN) (GUEST: 7) Writing SMBIOS tables ...
(XEN) (GUEST: 7) Loading ROMBIOS ...
(XEN) (GUEST: 7) Creating MP tables ...
(XEN) (GUEST: 7) Loading Cirrus VGABIOS ...
(XEN) (GUEST: 7) Loading ACPI ...
(XEN) (GUEST: 7) Loading VMXAssist ...
(XEN) (GUEST: 7) VMX go ...
(XEN) (GUEST: 7) VMXAssist (Mar 8 2007)
(XEN) (GUEST: 7) Memory size 500 MB
(XEN) (GUEST: 7) E820 map:
(XEN) (GUEST: 7) 0000000000000000 - 000000000009F000 (RAM)
(XEN) (GUEST: 7) 000000000009F000 - 00000000000A0000 (Reserved)
(XEN) (GUEST: 7) 00000000000A0000 - 00000000000C0000 (Type 16)
(XEN) (GUEST: 7) 00000000000F0000 - 0000000000100000 (Reserved)
(XEN) (GUEST: 7) 0000000000100000 - 000000001F3F0000 (RAM)
(XEN) (GUEST: 7) 000000001F3F0000 - 000000001F3FA000 (ACPI Data)
(XEN) (GUEST: 7) 000000001F3FA000 - 000000001F3FD000 (ACPI NVS)
(XEN) (GUEST: 7) 000000001F3FD000 - 000000001F3FE000 (Type 19)
(XEN) (GUEST: 7) 000000001F3FE000 - 000000001F3FF000 (Type 18)
(XEN) (GUEST: 7) 000000001F3FF000 - 000000001F400000 (Type 17)
(XEN) (GUEST: 7) 00000000FEC00000 - 0000000100000000 (Type 16)
(XEN) (GUEST: 7)
(XEN) (GUEST: 7) Start BIOS ...
(XEN) (GUEST: 7) Starting emulated 16-bit real-mode: ip=F000:FFF0
(XEN) (GUEST: 7) rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
(XEN) (GUEST: 7) Remapping master: ICW2 0x8 -> 0x20
(XEN) (GUEST: 7) Remapping slave: ICW2 0x70 -> 0x28
(XEN) (GUEST: 7) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50
vruppert Exp $
(XEN) (GUEST: 7) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date:
2005/05/07 15: 55:26 $
(XEN) (GUEST: 7)
(XEN) (GUEST: 7) ata0-0: PCHS=12190/16/63 translation=none LCHS=1024/16/63
(XEN) (GUEST: 7) ata0 master: QEMU HARDDISK ATA-7 Hard-Disk (6000 MBytes)
(XEN) (GUEST: 7) ata0 slave: Unknown device
(XEN) (GUEST: 7)
(XEN) (GUEST: 7) Booting from Hard Disk...
(XEN) (GUEST: 7) int13_harddisk: function 41, unmapped device for ELDL=81
(XEN) (GUEST: 7) int13_harddisk: function 08, unmapped device for ELDL=81
(XEN) (GUEST: 7) *** int 15h function AX=00C0, BX=0000 not yet supported!
(XEN) (GUEST: 7) int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) (GUEST: 7) KBD: unsupported int 16h function 03
(XEN) (GUEST: 7) int13_harddisk: function 15, unmapped device for ELDL=81
################## end xm dmesg
There is nothing in /var/log/xen/xend-debug.log
This is what is in the /var/log/xen/xend.log
##### START xend.log
[2007-06-11 17:31:21 xend.XendDomainInfo 3251] DEBUG
(XendDomainInfo:190) XendDomainInfo.create([''vm'',
[''name'',
''rh72_test1''], [''memory'',
''500''], [''on_reboot'',
''restart''], [''on_crash'',
''restart''], [''vcpus'', 1],
[''uuid'',
''f7dff459-6b52-4d6f-d40f-087cdbf08b05''],
[''image'', [''hvm'',
[''kernel'',
''/usr/lib/xen/boot/hvmloader''],
[''device_model'',
''/usr/lib/xen/bin/qemu-dm''], [''pae'', 1],
[''vcpus'', 1], [''boot'',
''c''],
[''serial'', ''pty''], [''vnc'',
1], [''vncunused'', 1], [''display'',
'':0.0''],
[''xauthority'', ''/tmp/.gdm82ZSTT''],
[''acpi'', 1], [''apic'', 1],
[''vncpasswd'', None]]], [''device'',
[''vbd'', [''uname'',
''file:/opt/xen-machines/rh72-test/rh72_test1.disk1''],
[''dev'', ''hda''],
[''mode'', ''w'']]],
[''device'', [''vif'',
[''bridge'', ''xenbr0''],
[''mac'',
''00:16:3e:26:f0:37''], [''type'',
''ioemu'']]], [''device'',
[''vkbd'']],
[''device'', [''vfb'',
[''vncunused'', ''1''],
[''type'', ''vnc''],
[''xauthority'',
''/tmp/.gdm82ZSTT''], [''display'',
'':0.0'']]]])
[2007-06-11 17:31:21 xend.XendDomainInfo 3251] DEBUG
(XendDomainInfo:296) parseConfig: config is [''vm'',
[''name'',
''rh72_test1''], [''memory'',
''500''], [''on_reboot'',
''restart''], [''on_crash'',
''restart''], [''vcpus'', 1],
[''uuid'',
''f7dff459-6b52-4d6f-d40f-087cdbf08b05''],
[''image'', [''hvm'',
[''kernel'',
''/usr/lib/xen/boot/hvmloader''],
[''device_model'',
''/usr/lib/xen/bin/qemu-dm''], [''pae'', 1],
[''vcpus'', 1], [''boot'',
''c''],
[''serial'', ''pty''], [''vnc'',
1], [''vncunused'', 1], [''display'',
'':0.0''],
[''xauthority'', ''/tmp/.gdm82ZSTT''],
[''acpi'', 1], [''apic'', 1],
[''vncpasswd'', None]]], [''device'',
[''vbd'', [''uname'',
''file:/opt/xen-machines/rh72-test/rh72_test1.disk1''],
[''dev'', ''hda''],
[''mode'', ''w'']]],
[''device'', [''vif'',
[''bridge'', ''xenbr0''],
[''mac'',
''00:16:3e:26:f0:37''], [''type'',
''ioemu'']]], [''device'',
[''vkbd'']],
[''device'', [''vfb'',
[''vncunused'', ''1''],
[''type'', ''vnc''],
[''xauthority'',
''/tmp/.gdm82ZSTT''], [''display'',
'':0.0'']]]]
[2007-06-11 17:31:21 xend.XendDomainInfo 3251] DEBUG
(XendDomainInfo:397) parseConfig: result is {''shadow_memory'':
None,
''start_time'': None, ''uuid'':
''f7dff459-6b52-4d6f-d40f-087cdbf08b05'',
''on_crash'': ''restart'',
''on_reboot'': ''restart'',
''localtime'': None,
''image'': [''hvm'',
[''kernel'', ''/usr/lib/xen/boot/hvmloader''],
[''device_model'',
''/usr/lib/xen/bin/qemu-dm''], [''pae'', 1],
[''vcpus'', 1],
[''boot'', ''c''], [''serial'',
''pty''], [''vnc'', 1],
[''vncunused'', 1],
[''display'', '':0.0''],
[''xauthority'', ''/tmp/.gdm82ZSTT''],
[''acpi'', 1],
[''apic'', 1], [''vncpasswd'', None]],
''on_poweroff'': None,
''bootloader_args'': None, ''cpus'': None,
''name'': ''rh72_test1'',
''backend'':
[], ''vcpus'': 1, ''cpu_weight'': None,
''features'': None, ''vcpu_avail'':
None, ''memory'': 500, ''device'':
[(''vbd'', [''vbd'', [''uname'',
''file:/opt/xen-machines/rh72-test/rh72_test1.disk1''],
[''dev'', ''hda''],
[''mode'', ''w'']]), (''vif'',
[''vif'', [''bridge'',
''xenbr0''], [''mac'',
''00:16:3e:26:f0:37''], [''type'',
''ioemu'']]), (''vkbd'',
[''vkbd'']), (''vfb'',
[''vfb'', [''vncunused'',
''1''], [''type'', ''vnc''],
[''xauthority'',
''/tmp/.gdm82ZSTT''], [''display'',
'':0.0'']])], ''bootloader'': None,
''cpu'':
None, ''maxmem'': None}
[2007-06-11 17:31:21 xend.XendDomainInfo 3251] DEBUG
(XendDomainInfo:1264) XendDomainInfo.construct: None
[2007-06-11 17:31:22 xend.XendDomainInfo 3251] DEBUG
(XendDomainInfo:1296) XendDomainInfo.initDomain: 7 1.0
[2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: boot, val: c
[2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: fda, val: None
[2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: fdb, val: None
[2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: soundhw, val: None
[2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: localtime, val: None
[2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: serial, val: pty
[2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: std-vga, val: None
[2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: isa, val: None
[2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: vcpus, val: 1
[2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: acpi, val: 1
[2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: usb, val: None
[2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: usbdevice, val: None
[2007-06-11 17:31:22 xend 3251] DEBUG (image:329) args: k, val: None
[2007-06-11 17:31:22 xend 3251] DEBUG (balloon:127) Balloon: 6216092 KiB
free; need 528560; done.
[2007-06-11 17:31:22 xend 3251] INFO (image:136) buildDomain os=hvm
dom=7 vcpus=1
[2007-06-11 17:31:22 xend 3251] DEBUG (image:282) dom = 7
[2007-06-11 17:31:22 xend 3251] DEBUG (image:283) image =
/usr/lib/xen/boot/hvmloader
[2007-06-11 17:31:22 xend 3251] DEBUG (image:284) store_evtchn = 1
[2007-06-11 17:31:22 xend 3251] DEBUG (image:285) memsize = 500
[2007-06-11 17:31:22 xend 3251] DEBUG (image:286) vcpus = 1
[2007-06-11 17:31:22 xend 3251] DEBUG (image:287) pae = 1
[2007-06-11 17:31:22 xend 3251] DEBUG (image:288) acpi = 1
[2007-06-11 17:31:22 xend 3251] DEBUG (image:289) apic = 1
[2007-06-11 17:31:22 xend 3251] DEBUG (image:435) hvm shutdown watch
registered
[2007-06-11 17:31:22 xend 3251] DEBUG (DevController:110) DevController:
writing {''backend-id'': ''0'',
''virtual-device'': ''768'',
''device-type'':
''disk'', ''state'': ''1'',
''backend'':
''/local/domain/0/backend/vbd/7/768''} to
/local/domain/7/device/vbd/768.
[2007-06-11 17:31:22 xend 3251] DEBUG (DevController:112) DevController:
writing {''domain'': ''rh72_test1'',
''frontend'':
''/local/domain/7/device/vbd/768'', ''dev'':
''hda'', ''state'': ''1'',
''params'':
''/opt/xen-machines/rh72-test/rh72_test1.disk1'',
''mode'': ''w'', ''online'':
''1'', ''frontend-id'': ''7'',
''type'': ''file''} to
/local/domain/0/backend/vbd/7/768.
[2007-06-11 17:31:22 xend 3251] DEBUG (DevController:110) DevController:
writing {''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/vif/7/0''} to
/local/domain/7/device/vif/0.
[2007-06-11 17:31:22 xend 3251] DEBUG (DevController:112) DevController:
writing {''bridge'': ''xenbr0'',
''domain'': ''rh72_test1'',
''handle'': ''0'',
''script'': ''/etc/xen/scripts/vif-bridge'',
''state'': ''1'', ''frontend'':
''/local/domain/7/device/vif/0'', ''mac'':
''00:16:3e:26:f0:37'', ''online'':
''1'', ''frontend-id'': ''7'',
''type'': ''ioemu''} to
/local/domain/0/backend/vif/7/0.
[2007-06-11 17:31:22 xend 3251] DEBUG (DevController:110) DevController:
writing {''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/vkbd/7/0''} to
/local/domain/7/device/vkbd/0.
[2007-06-11 17:31:22 xend 3251] DEBUG (DevController:112) DevController:
writing {''frontend-id'': ''7'',
''domain'': ''rh72_test1'',
''frontend'':
''/local/domain/7/device/vkbd/0'', ''state'':
''1'', ''online'': ''1''} to
/local/domain/0/backend/vkbd/7/0.
[2007-06-11 17:31:22 xend 3251] DEBUG (DevController:110) DevController:
writing {''state'': ''1'',
''backend-id'': ''0'',
''backend'':
''/local/domain/0/backend/vfb/7/0''} to
/local/domain/7/device/vfb/0.
[2007-06-11 17:31:22 xend 3251] DEBUG (DevController:112) DevController:
writing {''vncunused'': ''1'',
''domain'': ''rh72_test1'',
''frontend'':
''/local/domain/7/device/vfb/0'',
''xauthority'': ''/tmp/.gdm82ZSTT'',
''state'': ''1'', ''online'':
''1'', ''frontend-id'': ''7'',
''type'': ''vnc'',
''display'': '':0.0''} to
/local/domain/0/backend/vfb/7/0.
[2007-06-11 17:31:22 xend 3251] DEBUG (vfbif:92) No VNC passwd
configured for vfb access
[2007-06-11 17:31:22 xend 3251] INFO (image:418) spawning device models:
/usr/lib/xen/bin/qemu-dm [''/usr/lib/xen/bin/qemu-dm'',
''-d'', ''7'', ''-m'',
''500'', ''-boot'', ''c'',
''-serial'', ''pty'',
''-vcpus'', ''1'', ''-acpi'',
''-domain-name'', ''rh72_test1'',
''-net'',
''nic,vlan=1,macaddr=00:16:3e:26:f0:37,model=rtl8139'',
''-net'',
''tap,vlan=1,bridge=xenbr0'', ''-vncunused'',
''-vnclisten'', ''127.0.0.1'']
[2007-06-11 17:31:22 xend 3251] INFO (image:420) device model pid: 6463
[2007-06-11 17:31:22 xend.XendDomainInfo 3251] DEBUG
(XendDomainInfo:715) Storing VM details: {''shadow_memory'':
''3'', ''uuid'':
''f7dff459-6b52-4d6f-d40f-087cdbf08b05'',
''on_reboot'': ''restart'',
''start_time'': ''1181597482.26'',
''on_poweroff'': ''destroy'',
''name'':
''rh72_test1'', ''xend/restart_count'':
''0'', ''vcpus'': ''1'',
''vcpu_avail'':
''1'', ''memory'': ''500'',
''on_crash'': ''restart'',
''image'': "(hvm (kernel
/usr/lib/xen/boot/hvmloader) (device_model /usr/lib/xen/bin/qemu-dm)
(pae 1) (vcpus 1) (boot c) (serial pty) (vnc 1) (vncunused 1) (display
:0.0) (xauthority /tmp/.gdm82ZSTT) (acpi 1) (apic 1) (vncpasswd
''None''))", ''maxmem'':
''500''}
[2007-06-11 17:31:22 xend.XendDomainInfo 3251] DEBUG
(XendDomainInfo:750) Storing domain details: {''console/port'':
''2'',
''name'': ''rh72_test1'',
''console/limit'': ''1048576'',
''vm'':
''/vm/f7dff459-6b52-4d6f-d40f-087cdbf08b05'',
''domid'': ''7'',
''cpu/0/availability'': ''online'',
''memory/target'': ''512000'',
''store/ring-ref'': ''757982'',
''store/port'': ''1''}
[2007-06-11 17:31:22 xend 3251] DEBUG (image:458) hvm_shutdown fired,
shutdown reason=None
[2007-06-11 17:31:22 xend.XendDomainInfo 3251] DEBUG
(XendDomainInfo:940) XendDomainInfo.handleShutdownWatch
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for
devices vif.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:149) Waiting for 0.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:471)
hotplugStatusCallback /local/domain/0/backend/vif/7/0/hotplug-status.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:485)
hotplugStatusCallback 1.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for
devices usb.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for
devices vbd.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:149) Waiting for 768.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:471)
hotplugStatusCallback /local/domain/0/backend/vbd/7/768/hotplug-status.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:471)
hotplugStatusCallback /local/domain/0/backend/vbd/7/768/hotplug-status.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:485)
hotplugStatusCallback 1.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for
devices irq.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for
devices vkbd.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:149) Waiting for 0.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:471)
hotplugStatusCallback /local/domain/0/backend/vkbd/7/0/hotplug-status.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:485)
hotplugStatusCallback 1.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for
devices vfb.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:149) Waiting for 0.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:471)
hotplugStatusCallback /local/domain/0/backend/vfb/7/0/hotplug-status.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:485)
hotplugStatusCallback 1.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for
devices pci.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for
devices ioports.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for
devices tap.
[2007-06-11 17:31:23 xend 3251] DEBUG (DevController:143) Waiting for
devices vtpm.
[2007-06-11 17:31:23 xend 3251] INFO (XendDomain:370) Domain rh72_test1
(7) unpaused.
[2007-06-11 17:41:01 xend 3251] DEBUG (image:458) hvm_shutdown fired,
shutdown reason=halt
[2007-06-11 17:41:01 xend.XendDomainInfo 3251] INFO (XendDomainInfo:899)
Domain has shutdown: name=rh72_test1 id=7 reason=halt.
[2007-06-11 17:41:01 xend.XendDomainInfo 3251] DEBUG
(XendDomainInfo:1463) XendDomainInfo.destroy: domid=7
[2007-06-11 17:41:01 xend.XendDomainInfo 3251] DEBUG
(XendDomainInfo:1471) XendDomainInfo.destroyDomain(7)
[2007-06-11 17:41:01 xend 3251] DEBUG (image:447) hvm shutdown watch
unregistered
########### end xend.log
My config file looks like this:
[root@testxen xen]# cat /etc/xen/rh72_test1
# Automatically generated xen config file
name = "rh72_test1"
builder = "hvm"
memory = "500"
disk = [
''file:/opt/xen-machines/rh72-test/rh72_test1.disk1,hda,w'', ]
vif = [ ''type=ioemu, mac=00:16:3e:26:f0:37, bridge=xenbr0'', ]
uuid = "f7dff459-6b52-4d6f-d40f-087cdbf08b05"
device_model = "/usr/lib/xen/bin/qemu-dm"
kernel = "/usr/lib/xen/boot/hvmloader"
#kernel = "/opt/xen-machines/rh72-test/vmlinuz-2.4.7-10"
#ramdisk = "/opt/xen-machines/rh72-test/initrd-2.4.7-10.img"
vnc=1
vncunused=1
apic=1
acpi=1
pae=1
vcpus=1
serial = "pty" # enable serial console
on_reboot = ''restart''
on_crash = ''restart''
#--- END CONFIG FILE
Any ideas?
I would have thought that a fully virtualized host would be pretty
foolproof?
Daniel P. Berrange
2007-Jun-12 14:15 UTC
Re: [Fedora-xen] XEN-3.0.3 on RHEL-5, fully virtualized guest of RH72 won''t start after install finishes.
On Mon, Jun 11, 2007 at 05:51:17PM -0400, Ben Russo wrote:> I have many boxes running rh-7.2 > (these are stripped down, minimal installs, for appliances on a private > network that isn''t routable) I want to run VIRTUAL images of the > same setup for testing purposes. > > I read the Fedora 6 XEN getting started guide and skimmed through the > FAQ. I browsed through this mailing list to see if I could find my > problem here as well. No luck. > > I have a Dell-2950 with Quad Core XEON processors, PAE, VMX, and it is > enabled in BIOS. 8GB RAM, 2GB assigned to Dom0 > > Booted into RHEL-5 Xen kernel, installed all the latest patches as of > 6/11/2007, and rebooted. > > Then Started Virtual Machine Manager GUI > Selected "New..." from File menu and followed the wizard. > then installed FULLY VIRTUALIZED > RH-72 from original Red Hat 7.2 CD''s > this went fine with the > Virtual Machine Manager GUI "New Machine" wizard. > The only non-usual thing I did for an RH72 install was > to give it the kernel boot option mem=500M > > After the install completed, the DomU guest said it was now going to > reboot and I should remove any CD''s. > > Then the DomU disappeared. > > It took me forever to figure out that I couldn''t use the virt-manager > GUI to restore a DomU configuration file. There really should be > a more intuitive way for this to work. I am not a dummy, and it took > me forever to figure out how to start the DomU again.The virt-manager release in Fedora 7 can now start existing inactive guests. We recently pushed an update to Fedora 6 updates-testing which can do the same.> Now that I figured out that I have to go to a command line prompt and > type "xm create -c /etc/xen/rh72-test",That is no longer neccessary. Virt-manager can do that. You can also do it with ''virsh'' which is the preferred tool for command line usage virsh start rh72-test> Unable to handle kernel paging request at virtual address ffffffff > printing eip: > c0204a00 > *pde = 00001063 > *pte = 00000000 > Oops: 0000 > CPU: 0 > EIP: 0010:[<c0204a00>] > EFLAGS: 00010202 > eax: fffffff ebx: 00000000 ecx: 00000004 edx: 00000004 > esi: fffffff edi: c0229972 ebp: 0008e000 esp: c0257fb4 > ds: 0018 es: 0018 ss: 0018 > Process swapper (pid: 0, stackpage=c0257000) > Stack: c026d6e8 0000000 c024.... > ... > ... > Call Trace: [<.... > > Code: f3 a6 ... > <0>Kernel panic: Attempted to kill the idle task!Please file BZ reports for any kernel panic issues - mailing lists are a very bad way to track kernel bugs. Dan. -- |=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=| |=- Perl modules: http://search.cpan.org/~danberr/ -=| |=- Projects: http://freshmeat.net/~danielpb/ -=| |=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
Ben Russo
2007-Jun-12 15:38 UTC
[Fedora-xen] Re: XEN-3.0.3 on RHEL-5, fully virtualized guest of RH72 won''t start after install finishes.
>> Now that I figured out that I have to go to a command line prompt and >> type "xm create -c /etc/xen/rh72-test", > > That is no longer neccessary. Virt-manager can do that. You can also > do it with ''virsh'' which is the preferred tool for command line usage > > virsh start rh72-testThanks Dan, that helps. I''m glad the Virt-Manager GUI is being updated.>> <0>Kernel panic: Attempted to kill the idle task! > > Please file BZ reports for any kernel panic issues - mailing lists > are a very bad way to track kernel bugs.The virtual machine kernel is the one panicking. Do you think anybody is going to care about a RH7.2 kernel panic? Nobody will care, right? They would close the BZ report just saying it is old, unsupported in this configuration (running that old 7.2 kernel in a Xen environment). Isn''t "fully-virtualized" Xen supposed to be able to run any i386 system that can utilize the virtual hardware presented? -Ben.
Ben Russo
2007-Jun-12 22:22 UTC
[Fedora-xen] Re: XEN-3.0.3 on RHEL-5, fully virtualized guest of RH72 won''t start after install finishes.
Ben Russo wrote:> Then Started Virtual Machine Manager GUI > Selected "New..." from File menu and followed the wizard. > then installed FULLY VIRTUALIZED > RH-72 from original Red Hat 7.2 CD''s > this went fine with the > Virtual Machine Manager GUI "New Machine" wizard. > The only non-usual thing I did for an RH72 install was > to give it the kernel boot option mem=500M > > After the install completed, the DomU guest said it was now going to > reboot and I should remove any CD''s. > > Then the DomU disappeared.> type "xm create -c /etc/xen/rh72-test", > I find out that the new guest gets a kernel panic on bootup > after the bootup menu >I found out that if I add the kernel option "nomxt" to the grub.conf kernel command for the DomU it gets much farther in the boot process. Now I get this on the console: ixmiestr2.9620000731 (Red Hat Linux 7.1 2.96-98)) #1 Thu Sep 6 17:27:27 EDT 2001 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f000 (usable) 0 - 00 000000003ff000 type 18 000000000a000 (e000000000 0000f000(sabe) BIOS-e820: 000000001f3ff000 - 000000001f400000 type 17 op... 18ghmem)000000fec00000 - 0000000100000000 tycngi Df Tiar D(20010327) Richard Goch (rgoochatnf.ciro.a) mrr: dtected mtrr type: Intel PC:CBSePCI: Probing PCI hardware CI: Using IRQ router PIIX [8086/7000] at 00:01.0 PCI: PIIX3: Enabling Passive Release on 00:01.0 Limiting direct PCI/PCI transfers. Activating ISA DMA hang workarounds. isapnp: Scanig orPn ad.un inx ET.0fo Lnu 24 BaedupnSwnsa nvesiy omutr ocet NT303 am:BIS erio .2Flg 003(rve vrson11) mx_san_bios: enter Starting kswapd v1.8 erwth MAY_PORTSMLTIPORTSHR_Q EA_I Sme lock Drive v.0dUnix98 ptysconfigured bk,102 lts per ueue RAMDISK driver n iserd tidebus=xx PIIX: IDE controller on PCI bus 00 dev 09 PIIX3: chipset revisn 0 PIIX3: nt 100% nativemode: iha:pio, hdb:pio ide1: BM-DM a0f d0 C/H/S=610/63fomha Then it hangs right there.
Ben Russo
2007-Jun-15 14:44 UTC
[Fedora-xen] Re: XEN-3.0.3 on RHEL-5, fully virtualized guest of RH72 won''t start after install finishes.
Ben Russo wrote:> Ben Russo wrote: >> installed FULLY VIRTUALIZED >> RH-72 from original Red Hat 7.2 CD''s >> this went fine>> type "xm create -c /etc/xen/rh72-test", >> I find out that the new guest gets a kernel panic on bootup >> after the bootup menu> I found out that if I add the kernel option "nomxt" to the > grub.conf kernel command for the DomU it gets much farther > in the boot process. > > Now I get this on the console: > > <snip> console hangs at scanning QEMU HARDDISK ide drive </snip> > > > Then it hangs right there.I give up. Looks like running fully virtualized old versions of Linux just isn''t going to work smoothly. I''m going to use VMware ESX server instead.