Cannot run WinXP on the Xen fedora core 6
by Orathai Sukwong
Hi,
I've tried to bring the 32bit WinXP guest up on the Fedore Core 6-xen. My
xen release is 2.6.17-1.2647.fc6xen and version #1 SMP Wed Sep 13 13:26:53
EDT 2006. xen_caps are xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p. My
machine is running the Fedora Core 6 i686. The problem is that when I booted
the WinXP guest, it crashed. Here are some debugging info:
(XEN) (GUEST: 5) unsupported PCI BIOS function 0x0E
(XEN) (GUEST: 5) int13_harddisk: function 15, unmapped device for ELDL=81
(XEN) 0f 6f, This opcode isn't handled yet
(XEN) handle_mmio: failed to decode instruction
(XEN) mmio opcode: va 0xf81393c0, gpa 0xf00783c0, len 3: 0f 6f 06
(XEN) domain_crash_sync called from platform.c:869
(XEN) Domain 5 (vcpu#0) crashed on cpu#0:
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 0
(XEN) EIP: 0008:[<bf902854>]
(XEN) EFLAGS: 00010202 CONTEXT: hvm
(XEN) eax: f81393c0 ebx: e10875cc ecx: 0000002a edx: 00000008
(XEN) esi: f81393c0 edi: e10875d2 ebp: f86440d4 esp: f86440c8
(XEN) cr0: 80010031 cr3: 001f9ea0
(XEN) ds: 0023 es: 0023 fs: 0030 gs: 0000 ss: 0010 cs: 0008
(XEN) sh_update_paging_modes: postponing determination of shadow mode
(XEN) (file=hvm.c, line=195) Allocated port 3 for hvm.
(XEN) vmx_do_launch(): GUEST_CR3<=001f9ea0, HOST_CR3<=2bd03000
(XEN) (file=event_channel.c, line=176) EVTCHNOP failure: domain 0, error
-22, line 176
domid: 6
qemu: the number of cpus is 1
shared page at pfn:1ffff, mfn: 21d54
buffered io page at pfn:1fffd, mfn: 21d56
char device redirected to /dev/pts/2
bind interdomain ioctl error 22
Any ideas what went wrong? Please help me. Thank you.
17 years, 7 months
Dbus problem with virt-manager
by Chris Negus
I tried running virt-manager in FC6 T3 and got the following error
message:
dbus_bindings.DBusException Unable to determine the address of the
message bus (try 'man dbus-launch' and 'man dbus-daemon' for help)
Could not connection to session bus, disabling DBus service
My kernel is 2.6.17-1.2647.fc6xen. All packages are up to date. Any
suggestions?
-- Chris Negus
17 years, 7 months
fedora core 5 stock xen kernels nvidia drivers....
by Tom Bishop
Doea anyine know when the stock fedora xen kernels will be compatiable with
the nvidia binary kernels? I have read some posts on nvnet and ther are
some ways listed that allows you to do it, but it would be nice if the
stocked ones provided that. Also, the current stock Xen kernels do not
allow you to "hide" pci cards from dom0, saw a post that mentioned it was
turned on during th compile. Thanks.
17 years, 7 months
RE: [Fedora-xen] Testing for Xen of FC6 Test3 -- 2
by Zhao, Yunfeng
Two more issues were found on FC6 Test3.
1. Guest crashed when boot FC6 Test3 VMX guest with its PAE kernel host
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207769
Following is error message from serial console:
(XEN) (file=traps.c, line=1371) Domain attempted WRMSR 00000199 from 00000000:00000f00 to 00000000:00000c20.
(XEN) sh error: sh_remove_shadows(): can't find all shadows of mfn 36ec0 (shadow_flags=00000100)
(XEN) domain_crash called from common.c:2251
(XEN) Domain 5 (vcpu#0) crashed on cpu#1:
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 1
(XEN) EIP: 0060:[<c046f67f>]
(XEN) EFLAGS: 00010082 CONTEXT: hvm
(XEN) eax: 0000006b ebx: d469f380 ecx: 0000001d edx: 00000020
(XEN) esi: d469f380 edi: d469f383 ebp: d42afdd8 esp: d42afdcc
(XEN) cr0: 8005003b cr3: 001f8da0
(XEN) ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0068 cs: 0060
(XEN) sh_update_paging_modes: postponing determination of shadow mode
(XEN) sh_update_paging_modes: postponing determination of shadow mode
(XEN) (file=traps.c, line=1371) Domain attempted WRMSR 00000199 from 00000000:00000f00 to 00000000:00000f22.
(XEN) (file=hvm.c, line=195) Allocated port 3 for hvm.
(XEN) (file=hvm.c, line=195) Allocated port 4 for hvm.
(XEN) vmx_do_launch(): GUEST_CR3<=001f8da0, HOST_CR3<=1b073000
2. On FC6 Test3 I have to execute "xend stop; xend start" before can create the VMX guest
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207771
thanks
Yunfeng
>-----Original Message-----
>From: fedora-xen-bounces(a)redhat.com [mailto:fedora-xen-bounces@redhat.com]
>On Behalf Of Zhao, Yunfeng
>Sent: 2006年9月21日 11:20
>To: fedora-xen(a)redhat.com
>Subject: [Fedora-xen] Testing for Xen of FC6 Test3 -- 2
>
>Hi
>We have finished some manual device model tests, installation tests and
>manual function tests.
>And following are some issues we found in the testing:
>1. Blue screen happens when install Windows 2k with ACPI enabled.
>This issue should also exist in latest xen unstable tree.
>https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207565
>
> 2. Fails to boot fc6 test3 IA32 guest with 2048MB mem size
>The qemu window disappeared when booting. The qemu.log has been pasted
>in the bug below.
>https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207574
>
>3. Using "vi" on SDL console of VMX guest may cause the guest to hang
>https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207577
>This issue also exists in the latest xen unstable tree.
>
>4. Cannot use special number keys (when open Num Lock) on SDL console of
>VMX guest.
>https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207578
>This isse also exists in the latest xen unstable tree.
>
>Detail info:
>Function Part:
>IA32 host:
>Installation of IA32 UP XP SP2/win2k3 Windows Guest w/ ACPI Pass
>Installation of IA32 UP XP SP2/win2k3 Windows Guest w/o ACPI PASS
>Installation of IA32 UP Windows 2k Guest w/ ACPI PASS
>Installation of IA32 UP Windows 2k Guest w/o ACPI FAIL
>Boot up IA32 UP XP SP2/win2k3/win2k Guest PASS
>Installation of IA32 FC6-test3 with Graphic/text mode PASS
>Boot up IA32 FC6-test3 UP GUest PASS
>Boot up IA32 FC6-test3 SMP Guest FAIL
>Boot up IA32 RHEL4 UP/SMP Guest PASS
>Network in VMX Guest PASS
>
>IA32e host:
>Installation of IA32 UP XP SP2/win2k3 Windows Guest w/ ACPI Pass
>Installation of IA32 UP XP SP2/win2k3 Windows Guest w/o ACPI PASS
>Installation of IA32 UP Windows 2k Guest w/ ACPI PASS
>Installation of IA32 UP Windows 2k Guest w/o ACPI FAIL
>Boot up IA32 UP XP SP2/win2k3/win2k Guest PASS
>Installation of IA32/IA32e FC6-test3 with Graphic/text mode PASS
>Boot up IA32 FC6-test3 UP GUest PASS
>Boot up IA32 FC6-test3 SMP Guest FAIL
>Boot up IA32e FC6-test3 UP Guest PASS
>Boot up IA32e FC6-test3 SMP Guest FAIL
>Boot up IA32 RHEL4 UP/SMP Guest PASS
>Boot up IA32e RHEL4 UP/SMP Guest PASS
>Network in VMX Guest PASS
>
>Device Model Part:
>1. vi in VMX FAIL
>2. 4 NIC devices (4 rtl8139 and 4 ne2k) PASS
>3. Xwindows and Windows display in VMX PASS
>4. Switch between Xwindows and Text mode in VMX PASS
>5. keyboard in VMX FAIL
>6. Qemu command in Qemu console Window PASS
>7. USB mouse in Windows Guest PASS
>8. SDL and VNC mode in VMX PASS
>
>Thanks
>Yunfeng
>
>--
>Fedora-xen mailing list
>Fedora-xen(a)redhat.com
>https://www.redhat.com/mailman/listinfo/fedora-xen
17 years, 7 months
RE: Install
by Bill Lamb
How do you install fedora on a windows machine
Bob
17 years, 7 months
Xen0 booting problem with Fedora Core 5
by Francesco Laricchiuta
Hi,
i want to install xen 3.0.2 on Fedora Core 5 (
http://www.fedoraproject.org/wiki/FedoraXenQuickstartFC5), but i have a
problem with boot xen0.
i listed all xend-debug.log and xend.log.....
- xend-debug.log
Exception in thread Thread-3:
Traceback (most recent call last):
File "/usr/lib/python2.4/threading.py", line 442, in __bootstrap
self.run()
File "/usr/lib/python2.4/threading.py", line 422, in run
self.__target(*self.__args, **self.__kwargs)
File "/usr/lib/python2.4/site-packages/xen/xend/server/XMLRPCServer.py",
line 94, in run
self.server = UnixXMLRPCServer(XML_RPC_SOCKET, False)
File "/usr/lib/python2.4/site-packages/xen/util/xmlrpclib2.py", line 152,
in __init__
os.makedirs(parent, stat.S_IRWXU)
File "/usr/lib/python2.4/os.py", line 159, in makedirs
mkdir(name, mode)
OSError: [Errno 13] Permission denied: '/var/run/xend'
- xend.log
[2006-09-22 19:23:29 xend] INFO (SrvDaemon:283) Xend Daemon started
[2006-09-22 19:23:29 xend] INFO (SrvDaemon:287) Xend changeset: unavailable
.
[2006-09-22 19:23:29 xend.XendDomainInfo] DEBUG (XendDomainInfo:207)
XendDomainInfo.recreate({'paused': 0, 'cpu_time': 20918759483L, 'ssidref':
0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0],
'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 442720, 'maxmem_kb':
-4, 'max_vcpu_id': 0, 'crashed': 0, 'running': 1, 'shutdown': 0,
'online_vcpus': 1, 'blocked': 0})
[2006-09-22 19:23:29 xend.XendDomainInfo] INFO (XendDomainInfo:219)
Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000.
[2006-09-22 19:23:29 xend.XendDomainInfo] WARNING (XendDomainInfo:241) No vm
path in store for existing domain 0
[2006-09-22 19:23:29 xend.XendDomainInfo] DEBUG (XendDomainInfo:701) Storing
VM details: {'name': 'Domain-0', 'on_reboot': 'restart', 'on_poweroff':
'destroy', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_crash':
'restart', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '433', 'maxmem':
'433'}
[2006-09-22 19:23:29 xend.XendDomainInfo] DEBUG (XendDomainInfo:736) Storing
domain details: {'cpu/0/availability': 'online', 'memory/target': '443392',
'name': 'Domain-0', 'console/limit': '1048576', 'vm':
'/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'}
[2006-09-22 19:23:29 xend] DEBUG (XendDomain:153) number of vcpus to use is
0
[2006-09-22 19:23:29 xend.XendDomainInfo] DEBUG (XendDomainInfo:919)
XendDomainInfo.handleShutdownWatch
[2006-09-22 19:27:31 xend] INFO (SrvDaemon:283) Xend Daemon started
[2006-09-22 19:27:31 xend] INFO (SrvDaemon:287) Xend changeset: unavailable
.
[2006-09-22 19:27:31 xend.XendDomainInfo] DEBUG (XendDomainInfo:207)
XendDomainInfo.recreate({'paused': 0, 'cpu_time': 20638534618L, 'ssidref':
0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0],
'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 442720, 'maxmem_kb':
-4, 'max_vcpu_id': 0, 'crashed': 0, 'running': 1, 'shutdown': 0,
'online_vcpus': 1, 'blocked': 0})
[2006-09-22 19:27:31 xend.XendDomainInfo] INFO (XendDomainInfo:219)
Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000.
[2006-09-22 19:27:31 xend.XendDomainInfo] WARNING (XendDomainInfo:241) No vm
path in store for existing domain 0
[2006-09-22 19:27:31 xend.XendDomainInfo] DEBUG (XendDomainInfo:701) Storing
VM details: {'name': 'Domain-0', 'on_reboot': 'restart', 'on_poweroff':
'destroy', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_crash':
'restart', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '433', 'maxmem':
'433'}
[2006-09-22 19:27:31 xend.XendDomainInfo] DEBUG (XendDomainInfo:736) Storing
domain details: {'cpu/0/availability': 'online', 'memory/target': '443392',
'name': 'Domain-0', 'console/limit': '1048576', 'vm':
'/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'}
[2006-09-22 19:27:31 xend] DEBUG (XendDomain:153) number of vcpus to use is
0
[2006-09-22 19:27:31 xend.XendDomainInfo] DEBUG (XendDomainInfo:919)
XendDomainInfo.handleShutdownWatch
[2006-09-22 19:35:03 xend] INFO (SrvDaemon:283) Xend Daemon started
[2006-09-22 19:35:03 xend] INFO (SrvDaemon:287) Xend changeset: unavailable
.
[2006-09-22 19:35:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:207)
XendDomainInfo.recreate({'paused': 0, 'cpu_time': 20321279301L, 'ssidref':
0, 'handle': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0],
'shutdown_reason': 0, 'dying': 0, 'dom': 0, 'mem_kb': 442720, 'maxmem_kb':
-4, 'max_vcpu_id': 0, 'crashed': 0, 'running': 1, 'shutdown': 0,
'online_vcpus': 1, 'blocked': 0})
[2006-09-22 19:35:03 xend.XendDomainInfo] INFO (XendDomainInfo:219)
Recreating domain 0, UUID 00000000-0000-0000-0000-000000000000.
[2006-09-22 19:35:03 xend.XendDomainInfo] WARNING (XendDomainInfo:241) No vm
path in store for existing domain 0
[2006-09-22 19:35:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:701) Storing
VM details: {'name': 'Domain-0', 'on_reboot': 'restart', 'on_poweroff':
'destroy', 'uuid': '00000000-0000-0000-0000-000000000000', 'on_crash':
'restart', 'vcpus': '1', 'vcpu_avail': '1', 'memory': '433', 'maxmem':
'433'}
[2006-09-22 19:35:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:736) Storing
domain details: {'cpu/0/availability': 'online', 'memory/target': '443392',
'name': 'Domain-0', 'console/limit': '1048576', 'vm':
'/vm/00000000-0000-0000-0000-000000000000', 'domid': '0'}
[2006-09-22 19:35:03 xend] DEBUG (XendDomain:153) number of vcpus to use is
0
[2006-09-22 19:35:03 xend.XendDomainInfo] DEBUG (XendDomainInfo:919)
XendDomainInfo.handleShutdownWatch
Thanks for help
--
Francesco Laricchiuta
email: francesco.laricchiuta(a)gmail.com
17 years, 7 months
BUG: soft lockup detected on CPU#0!
by Philipp Jäggi
Dear Readers
Got a strange Problem when I try to start an application.
My System:
Distro: Fedora Core 5
Kernel: 2.6.17-1.2187_FC5xen0
CPU: Inter Xeon 3.20 GHz
RAM: 2.5GB
Guest and Dom0 are Fedora Core 5 with 2.6.17-1.2187 Kernels.
My Error MSG:
BUG: soft lockup detected on CPU#0!
<c043a582> softlockup_tick+0x9f/0xb4 <c0408760>
timer_interrupt+0x4fc/0x544
<c0404d79> hypervisor_callback+0x3d/0x48 <c043a63d>
handle_IRQ_event+0x42/0x85
<c043a70d> __do_IRQ+0x8d/0xdc <c040665a> do_IRQ+0x1a/0x25
<c051a159> evtchn_do_upcall+0x66/0x9f <c0404d79>
hypervisor_callback+0x3d/0x48
<c05ae0f8> general_protection+0x0/0xc <c0404dfe>
failsafe_callback+0xe/0x40
<c0410e27> write_ldt_entry+0xd4/0xdb <c0408d43> write_ldt+0x18d/0x1af
<c0404ba7> syscall_call+0x7/0xb
After this message, you can see in XenTop that my guest is using 100% of
the cpu. After a while, the dom0 is rebooting from itself. But between the
crash of the guest and the restart of the dom0, I can work in the dom0. I
really can't understand this. Thanks a lot for any help or link...
bye Philipp
===============================================
Philipp Jäggi
SNCT Sandweiler
bp 23
L-5230 Sandweiler
+352 35'72'14'342
mailto: philipp.jaeggi(a)snct.lu
17 years, 7 months
RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result
by You, Yongkang
Hi Akio,
Sorry for response late. It is very detailed instructions. :)
I found my initrd doesn't preload xenblk.ko. Then it failed to create root device.
Now I can create xenU too with your guide. Thank you so much.
But did you notice xenU booting is a little slow?
Best Regards,
Yongkang (Kangkang) 永康
>-----Original Message-----
>From: Akio Takebe [mailto:takebe_akio@jp.fujitsu.com]
>Sent: 2006年9月22日 13:06
>To: You, Yongkang; Yang, Fred; y-oguchi(a)jp.fujitsu.com;
>fedora-xen(a)redhat.com
>Cc: xen-ia64-devel(a)lists.xensource.com; Akio Takebe
>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result
>
>Hi, Yongkang and all
>
>I can boot up domU by using my special initrd without vif.
>I think mkinitrd of fc6 make initrd by using dom0 infomation.
>(for example dom0's /etc/fstab, dom0's pci infomaition. )
>So when xm boot domU, domU kernel don't use bootparmeter of domU.
>
>The below is a recipe of making my special inird
>
>1. copy initrd
># mkdir tmp
># cp /boot/efi/efi/redhat/initrd-2.6.18-1.2679.fc6xenU.img tmp/
>
>2. expand inird
># cd tmp
># gzip -cd ../initrd-2.6.18-1.2679.fc6xenU.img |cpio -id
>
>3. modify init in initrd
># vi init
> insmod /lib/ohci-hcd.ko
> echo "Loading ehci-hcd.ko module"
> insmod /lib/ehci-hcd.ko
> mount -t usbfs /proc/bus/usb /proc/bus/usb
> echo "Loading jbd.ko module"
> insmod /lib/jbd.ko
> echo "Loading ext3.ko module"
> insmod /lib/ext3.ko
> #echo "Loading scsi_mod.ko module" <<<<<< comment out
> #insmod /lib/scsi_mod.ko <<<<<< comment out
> #echo "Loading sd_mod.ko module" <<<<<< comment out
> #insmod /lib/sd_mod.ko <<<<<< comment out
> #echo "Loading scsi_transport_spi.ko module" <<<<<< comment out
> #insmod /lib/scsi_transport_spi.ko <<<<<< comment out
> #echo "Loading mptbase.ko module" <<<<<< comment out
> #insmod /lib/mptbase.ko <<<<<< comment out
> #echo "Loading mptscsih.ko module" <<<<<< comment out
> #insmod /lib/mptscsih.ko <<<<<< comment out
> #echo "Loading mptspi.ko module" <<<<<< comment out
> #insmod /lib/mptspi.ko <<<<<< comment out
> echo "Loading xenblk.ko module"
> insmod /lib/xenblk.ko
> mkblkdevs
> #resume LABEL=SWAP-sda3 <<<<<< comment
>out
> echo Creating root device.
> mkrootdev -t ext3 -o defaults,ro sda1 <<<<change device to sda1
> echo Mounting root filesystem.
> mount /sysroot
> echo Setting up other filesystems.
> setuproot
> echo Switching to new root and running init.
> switchroot
>4. make new initrd
># find . -print | cpio --quiet -c -o | gzip -9 >../initrd-new.img
>
>5. my domU configuration
>kernel = "/boot/efi/efi/redhat/vmlinuz-2.6.18-1.2679.fc6xen"
>ramdisk = "/xen/initrd-new.img"
>memory = 1024
>name = "fc6.DomU"
>#vif = [ '' ]
>disk = [ 'file:/xen/image/fc6.root.img,sda1,w' ]
>root = "/dev/sda1 ro"
>extra = "4 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe selinux=0
>rhgb"
>
>6. etc
> 6.1. copy modlues into domU image file
> # mount -o loop domU.img /mnt
> # cp -a /lib/modules/2.6.18-1.2679.fc6xen/ /mnt/lib/modules/
> 6.2. disable selinux
> # vi /etc/sysconfig/selinux
> SELINUX=disabled <<<< change enforcing to disabled
> 6.3. modify /etc/fstab in domU.img
> /dev/sda1 / ext3 defaults 1 1
> devpts /dev/pts devpts gid=5,mode=620 0 0
> tmpfs /dev/shm tmpfs defaults 0 0
> proc /proc proc defaults 0 0
> sysfs /sys sysfs defaults 0 0
>
>
>But I cannot use network on domU.
>I'll check the src.rpm of kernel-xen.
>
>Best Regards,
>
>Akio Takebe
>
>
>>Hi Akio,
>>
>>Sorry for response late. I just tried with the config you provide (I
>>changed xenU modprobe.conf and fstab). But unfortunately it still couldn't
>>work. XenU booting still report can not find filesystem /dev/root/ and
>>kernel panic.
>>
>>Well, after add "ide0=noprobe" etc. xenU won't complain to check hda, hdb
>>etc. again. Thanks for this information.
>>
>>Best Regards,
>>Yongkang (Kangkang) モタソオ
>>>-----Original Message-----
>>>From: Akio Takebe [mailto:takebe_akio@jp.fujitsu.com]
>>>Sent: 2006ト・ヤツ21ネユ 10:18
>>>To: Akio Takebe; You, Yongkang; Yang, Fred; y-oguchi(a)jp.fujitsu.com;
>>>fedora-xen(a)redhat.com
>>>Cc: xen-ia64-devel(a)lists.xensource.com
>>>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result
>>>
>>>Hi, Yongkang
>>>
>>>I have a small mistake.
>>>
>>>Please try the following configuration.
>>> kernel = "vmlinuz-2.6.17-1.2630.fc6xen"
>>> ramdisk = "initrd-2.6.17-1.2630.fc6xenU.img"
>>> memory = 512
>>> name = "domU"
>>> vif = [ '' ]
>>> disk = [ 'file:/xen/image/fc6.root.img,sda1,w' ] <----this
>>> root = "/dev/sda1 ro" <--------this
>>> extra = "3 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe"
><---
>>>-this
>>>
>>>Best Regards,
>>>
>>>Akio Takebe
>>>
>>>>Hi, Yongkang
>>>>
>>>>I think this issue is configuration mistakes.
>>>>Can you try the following configuration?
>>>>I cannot try it because I meet another issue...
>>>>
>>>>1. /etc/modprobe.conf for initrd of domU
>>>>The following configuration would solve the issue of booting domU.
>>>> [root@tiger156 xen]# cat /etc/modprobe.conf
>>>> #alias eth0 e1000
>>>> #alias scsi_hostadapter mptbase
>>>> #alias scsi_hostadapter1 mptspi
>>>> alias eth0 xennet <----this
>>>> alias scsi_hostadapter xenblk <----and this
>>>>
>>>>
>>>>2. domU.conf
>>>>The following configuration would solve the issue of probing ide disk.
>>>> kernel = "vmlinuz-2.6.17-1.2630.fc6xen"
>>>> ramdisk = "initrd-2.6.17-1.2630.fc6xenU.img"
>>>> memory = 512
>>>> name = "domU"
>>>> vif = [ '' ]
>>>> disk = [ 'file:/xen/image/fc6.root.img,hda1,w' ]
>>>> root = "/dev/hda1 ro"
>>>> extra = "3 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe"
>>><----this
>>>>
>>>>
>>>>Best Regards,
>>>>
>>>>Akio Takebe
>>>>
>>>>>Hi,
>>>>>
>>>>>I have reported 2 bugs to redhat bugzilla:
>>>>>[Bug 207227] New: Xen0 reboot command can not reboot Tiger4
>machine.
>>>>>[Bug 207241] New: XenU domain can not be created successfully.
>>>>>New xenU created failure serial log has been pasted to the bug.
>>>>>
>>>>>I also notice FC6-test3 Xen0 operation is a little slower, compared with
>>>>>RHEL4u3. I assign 2 vcpus to Xen0. When I destroy domains or do some
>>>heavy
>>>>>IO operations, Xen0 operations will be blocked for a while. I didn't track
>>>>>this to bugzilla.
>>>>>
>>>>>There are also a lot of unaligned accessing from some applications. They
>>>>>should be common FC6-test3 issues.
>>>>>
>>>>>Sometime Xen0 monitor will print "Bug: soft lockup detected on
>CPU#0(or
>>>#1)"
>>>>>
>>>>>Best Regards,
>>>>>Yongkang (Kangkang) ・筵ソ・ス・ェ
>>>>>
>>>>>>-----Original Message-----
>>>>>>From: xen-ia64-devel-bounces(a)lists.xensource.com
>>>>>>[mailto:xen-ia64-devel-bounces@lists.xensource.com] On Behalf Of
>You,
>>>>>>Yongkang
>>>>>>Sent: 2006・ネs・茹ト20・ヘ・・10:07
>>>>>>To: Yang, Fred; y-oguchi(a)jp.fujitsu.com; fedora-xen(a)redhat.com
>>>>>>Cc: xen-ia64-devel(a)lists.xensource.com
>>>>>>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test
>>>>>>result
>>>>>>
>>>>>>Hi Fred & Yoshi,
>>>>>>
>>>>>>The former XenU creating failure issue seemed to be the config issue.
>>>Now I
>>>>>>can create XenU. But XenU booting process met an old bug. It will cost
>a
>>>>>>long
>>>>>>time to check hard disk IRQ response from hda to hdh.
>>>>>>
>>>>>>After that, xenU met the problem of mounting root partition to start
>>>>>>services,
>>>>>>and then XenU booting failed (Kill init). I am not sure if it is because
>>>>>>initrd issue.
>>>>>>I will continue to check it.
>>>>>>
>>>>>>Best Regards,
>>>>>>Yongkang (Kangkang) ・筵ソ・ス・ェ
>>>>>>
>>>>>>>-----Original Message-----
>>>>>>>From: xen-ia64-devel-bounces(a)lists.xensource.com
>>>>>>>[mailto:xen-ia64-devel-bounces@lists.xensource.com] On Behalf Of
>>>Yang,
>>>>>>>Fred
>>>>>>>Sent: 2006・ネs・茹ト20・ヘ・・8:26
>>>>>>>To: y-oguchi(a)jp.fujitsu.com; fedora-xen(a)redhat.com
>>>>>>>Cc: xen-ia64-devel(a)lists.xensource.com
>>>>>>>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test
>>>result
>>>>>>>
>>>>>>>Here it comes!
>>>>>>>-Fred
>>>>>>>
>>>>>>>>-----Original Message-----
>>>>>>>>From: y-oguchi(a)jp.fujitsu.com [mailto:y-oguchi@jp.fujitsu.com]
>>>>>>>>Sent: Tuesday, September 19, 2006 4:23 PM
>>>>>>>>To: Yang, Fred; fedora-xen(a)redhat.com
>>>>>>>>Cc: xen-ia64-devel(a)lists.xensource.com
>>>>>>>>Subject: Re: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test
>>>>>>>>result
>>>>>>>>
>>>>>>>>Fred, Yongkang,
>>>>>>>>
>>>>>>>>> Other issues:
>>>>>>>>> 1) Xen0 operation is a little slower than RHEL4u3.
>>>>>>>>> 2) XenU creating failure, please see attachment for the serial
>>>>>>>>> output.
>>>>>>>>
>>>>>>>>I can't find the attachment.
>>>>>>>>Could you repost the serial log?
>>>>>>>>
>>>>>>>>Thanks,
>>>>>>>>Yoshi Oguchi
>>>>>>>>
>>>>>>>>"Yang, Fred" <fred.yang(a)intel.com> wrote。ケ・ウ
>>>>>>>>> Following is the quick Xen test result with FC6 Test3. We will file
>>>>>>>>BZ for the issues tonight; the early data is to get community to fix
>>>>>>>>Xen
>>>>>>>>issues ASAP
>>>>>>>>> Thanks,
>>>>>>>>> -Fred
>>>>>>>>>
>>>>>>>>> ====
>>>>>>>>> I have followed Redhat instructions (FC6-test3 can not be installed
>>>>>>>>from CDs) to install FC6-Test3 and do some testing. Both Xen0 and
>>>VTI
>>>>>>>>can all boot up, but XenU couldn't be created successfully.
>>>>>>>>>
>>>>>>>>> Detailed Items:
>>>>>>>>> 1. Using yum to upgrade FC6 Test2 to FC6 Test3 [almost
>Pass]
>>>>>>need
>>>>>>>>manually reinstall kernel-xen rpm package.
>>>>>>>>> 2. Boot Native Linux of FC6 Test3 [Pass]
>>>>>>>>> 3. Boot Xen of FC6 Test3 [Pass]
>>>>>>>>> 4. xend and xm commands are working. [Pass]
>>>>>>>>> 5. XenU Domain creating failed. [__FAIL__]
>>>>>>>>> 6. Missing VTI guest firmware
>(/usr/lib/xen/boot/guest_firmware.bin)
>>>>>>>> [__FAIL__ (expected)]
>>>>>>>>> 7. After manually copy VTI guest firmware, creating VTI domain
>>>>>>>>[Pass]
>>>>>>>>> 8. VTI domain with network supported [Pass]
>>>>>>>>> 9. 2 VTI domains coexisting testing [Pass]
>>>>>>>>> 10. Linux Kernel build in VTI domain [Pass]
>>>>>>>>> 11. LTP testing in VTI domain [Pass]
>>>>>>>>> 12. SMP VTI domain [Pass]
>>>>>>>>> 13. SMP Xen0 [Pass]
>>>>>>>>> 14. 1 VTI Windows 2k3 [Pass] a little slower.
>>>>>>>>> 15. 1 VTI Linux + 1 VTI Windows [__FAIL__ VTI Windows
>blue
>>>>>>>screen]
>>>>>>>>> 16. Reboot machine failed with Xen FC6-test3. [__FAIL__]
>>>>>>>>>
>>>>>>>>> Other issues:
>>>>>>>>> 1) Xen0 operation is a little slower than RHEL4u3.
>>>>>>>>> 2) XenU creating failure, please see attachment for the serial
>>>>>>>>> output.
>>>>>>>>>
>>>>>>>>> Best Regards,
>>>>>>>>> Yongkang (Kangkang) ・筵ソ・ス・ェ
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Xen-ia64-devel mailing list
>>>>>>>>> Xen-ia64-devel(a)lists.xensource.com
>>>>>>>>> http://lists.xensource.com/xen-ia64-devel
>>>>>>
>>>>>>_______________________________________________
>>>>>>Xen-ia64-devel mailing list
>>>>>>Xen-ia64-devel(a)lists.xensource.com
>>>>>>http://lists.xensource.com/xen-ia64-devel
>>>>>
>>>>>_______________________________________________
>>>>>Xen-ia64-devel mailing list
>>>>>Xen-ia64-devel(a)lists.xensource.com
>>>>>http://lists.xensource.com/xen-ia64-devel
>>>>
>>>>
>>>>_______________________________________________
>>>>Xen-ia64-devel mailing list
>>>>Xen-ia64-devel(a)lists.xensource.com
>>>>http://lists.xensource.com/xen-ia64-devel
17 years, 7 months
Re: blkbk/netbk modules fail to load on fedora xen/ia64
by Akio Takebe
Hi, Aron and all
>> We may have to change dom0_mem of FC6 default to 1GB.
>> But I think the best fix is (1) statically link the modules.
>> (Because all kernel-xen need blkbk/netbk and xenblk/net.
>> ide module is also static link. And because xen community member
>> test the statically linked modules, I think the statically linked
>> modules is stabler than the dynamic linked modlues.)
>
>I don't mind asking RH to statically link the modules if there is good
>reason. However I don't understand why it is needed. 512M is a lot
>of memory! How can it be filled to the extent that the blkbk/netbk
>modules won't load? What are their requirements?
>
Please see the following error message.
FATAL: Error inserting blkbk
(/lib/modules/2.6.17-1.2566.fc6xen/kernel/drivers/xen/
blkback/blkbk.ko): Cannot allocate memory
modprobe: page allocation failure. order:8, mode:0xd0
blkbk.ko request order8 pages in blkif_init().
order8 pages is very big.
page_alloc() probably fail when it is requested order8 pages,
because page_alloc() must return contiguos pages.
Especially after boot and terminate some processes,
page_alloc() is hard to allocate order8 pages.
So when dom0_mem=1G, page_allo() is easier to allocate them
than dom0_mem=512M.
And when statically linked modules, page_alloc() is the easest
to allocate them.
I think implementation of blk/netbk.ko is not good.
But I think statically linked modules is the best solution in your
solutions.
And I think this issue is happened in the case of not only ia64,
but also x86.
(In the case of x86, default size of dom0_mem is physcal memory size.
So this issue is hard to be happened.)
Please commets.
FYI
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=202971
Best Regards,
Akio Takebe
17 years, 7 months
RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result
by You, Yongkang
Hi Akio,
Sorry for response late. I just tried with the config you provide (I changed xenU modprobe.conf and fstab). But unfortunately it still couldn't work. XenU booting still report can not find filesystem /dev/root/ and kernel panic.
Well, after add "ide0=noprobe" etc. xenU won't complain to check hda, hdb etc. again. Thanks for this information.
Best Regards,
Yongkang (Kangkang) 永康
>-----Original Message-----
>From: Akio Takebe [mailto:takebe_akio@jp.fujitsu.com]
>Sent: 2006年9月21日 10:18
>To: Akio Takebe; You, Yongkang; Yang, Fred; y-oguchi(a)jp.fujitsu.com;
>fedora-xen(a)redhat.com
>Cc: xen-ia64-devel(a)lists.xensource.com
>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result
>
>Hi, Yongkang
>
>I have a small mistake.
>
>Please try the following configuration.
> kernel = "vmlinuz-2.6.17-1.2630.fc6xen"
> ramdisk = "initrd-2.6.17-1.2630.fc6xenU.img"
> memory = 512
> name = "domU"
> vif = [ '' ]
> disk = [ 'file:/xen/image/fc6.root.img,sda1,w' ] <----this
> root = "/dev/sda1 ro" <--------this
> extra = "3 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe" <---
>-this
>
>Best Regards,
>
>Akio Takebe
>
>>Hi, Yongkang
>>
>>I think this issue is configuration mistakes.
>>Can you try the following configuration?
>>I cannot try it because I meet another issue...
>>
>>1. /etc/modprobe.conf for initrd of domU
>>The following configuration would solve the issue of booting domU.
>> [root@tiger156 xen]# cat /etc/modprobe.conf
>> #alias eth0 e1000
>> #alias scsi_hostadapter mptbase
>> #alias scsi_hostadapter1 mptspi
>> alias eth0 xennet <----this
>> alias scsi_hostadapter xenblk <----and this
>>
>>
>>2. domU.conf
>>The following configuration would solve the issue of probing ide disk.
>> kernel = "vmlinuz-2.6.17-1.2630.fc6xen"
>> ramdisk = "initrd-2.6.17-1.2630.fc6xenU.img"
>> memory = 512
>> name = "domU"
>> vif = [ '' ]
>> disk = [ 'file:/xen/image/fc6.root.img,hda1,w' ]
>> root = "/dev/hda1 ro"
>> extra = "3 ide0=noprobe ide1=noprobe ide2=noprobe ide3=noprobe"
><----this
>>
>>
>>Best Regards,
>>
>>Akio Takebe
>>
>>>Hi,
>>>
>>>I have reported 2 bugs to redhat bugzilla:
>>>[Bug 207227] New: Xen0 reboot command can not reboot Tiger4 machine.
>>>[Bug 207241] New: XenU domain can not be created successfully.
>>>New xenU created failure serial log has been pasted to the bug.
>>>
>>>I also notice FC6-test3 Xen0 operation is a little slower, compared with
>>>RHEL4u3. I assign 2 vcpus to Xen0. When I destroy domains or do some
>heavy
>>>IO operations, Xen0 operations will be blocked for a while. I didn't track
>>>this to bugzilla.
>>>
>>>There are also a lot of unaligned accessing from some applications. They
>>>should be common FC6-test3 issues.
>>>
>>>Sometime Xen0 monitor will print "Bug: soft lockup detected on CPU#0(or
>#1)"
>>>
>>>Best Regards,
>>>Yongkang (Kangkang) モタソオ
>>>
>>>>-----Original Message-----
>>>>From: xen-ia64-devel-bounces(a)lists.xensource.com
>>>>[mailto:xen-ia64-devel-bounces@lists.xensource.com] On Behalf Of You,
>>>>Yongkang
>>>>Sent: 2006トsヤツ20ネユ 10:07
>>>>To: Yang, Fred; y-oguchi(a)jp.fujitsu.com; fedora-xen(a)redhat.com
>>>>Cc: xen-ia64-devel(a)lists.xensource.com
>>>>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result
>>>>
>>>>Hi Fred & Yoshi,
>>>>
>>>>The former XenU creating failure issue seemed to be the config issue.
>Now I
>>>>can create XenU. But XenU booting process met an old bug. It will cost a
>>>>long
>>>>time to check hard disk IRQ response from hda to hdh.
>>>>
>>>>After that, xenU met the problem of mounting root partition to start
>>>>services,
>>>>and then XenU booting failed (Kill init). I am not sure if it is because
>>>>initrd issue.
>>>>I will continue to check it.
>>>>
>>>>Best Regards,
>>>>Yongkang (Kangkang) モタソオ
>>>>
>>>>>-----Original Message-----
>>>>>From: xen-ia64-devel-bounces(a)lists.xensource.com
>>>>>[mailto:xen-ia64-devel-bounces@lists.xensource.com] On Behalf Of
>Yang,
>>>>>Fred
>>>>>Sent: 2006トsヤツ20ネユ 8:26
>>>>>To: y-oguchi(a)jp.fujitsu.com; fedora-xen(a)redhat.com
>>>>>Cc: xen-ia64-devel(a)lists.xensource.com
>>>>>Subject: RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test
>result
>>>>>
>>>>>Here it comes!
>>>>>-Fred
>>>>>
>>>>>>-----Original Message-----
>>>>>>From: y-oguchi(a)jp.fujitsu.com [mailto:y-oguchi@jp.fujitsu.com]
>>>>>>Sent: Tuesday, September 19, 2006 4:23 PM
>>>>>>To: Yang, Fred; fedora-xen(a)redhat.com
>>>>>>Cc: xen-ia64-devel(a)lists.xensource.com
>>>>>>Subject: Re: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test
>>>>>>result
>>>>>>
>>>>>>Fred, Yongkang,
>>>>>>
>>>>>>> Other issues:
>>>>>>> 1) Xen0 operation is a little slower than RHEL4u3.
>>>>>>> 2) XenU creating failure, please see attachment for the serial output.
>>>>>>
>>>>>>I can't find the attachment.
>>>>>>Could you repost the serial log?
>>>>>>
>>>>>>Thanks,
>>>>>>Yoshi Oguchi
>>>>>>
>>>>>>"Yang, Fred" <fred.yang(a)intel.com> wrote」コ
>>>>>>> Following is the quick Xen test result with FC6 Test3. We will file
>>>>>>BZ for the issues tonight; the early data is to get community to fix Xen
>>>>>>issues ASAP
>>>>>>> Thanks,
>>>>>>> -Fred
>>>>>>>
>>>>>>> ====
>>>>>>> I have followed Redhat instructions (FC6-test3 can not be installed
>>>>>>from CDs) to install FC6-Test3 and do some testing. Both Xen0 and
>VTI
>>>>>>can all boot up, but XenU couldn't be created successfully.
>>>>>>>
>>>>>>> Detailed Items:
>>>>>>> 1. Using yum to upgrade FC6 Test2 to FC6 Test3 [almost Pass]
>>>>need
>>>>>>manually reinstall kernel-xen rpm package.
>>>>>>> 2. Boot Native Linux of FC6 Test3 [Pass]
>>>>>>> 3. Boot Xen of FC6 Test3 [Pass]
>>>>>>> 4. xend and xm commands are working. [Pass]
>>>>>>> 5. XenU Domain creating failed. [__FAIL__]
>>>>>>> 6. Missing VTI guest firmware (/usr/lib/xen/boot/guest_firmware.bin)
>>>>>> [__FAIL__ (expected)]
>>>>>>> 7. After manually copy VTI guest firmware, creating VTI domain
>>>>>>[Pass]
>>>>>>> 8. VTI domain with network supported [Pass]
>>>>>>> 9. 2 VTI domains coexisting testing [Pass]
>>>>>>> 10. Linux Kernel build in VTI domain [Pass]
>>>>>>> 11. LTP testing in VTI domain [Pass]
>>>>>>> 12. SMP VTI domain [Pass]
>>>>>>> 13. SMP Xen0 [Pass]
>>>>>>> 14. 1 VTI Windows 2k3 [Pass] a little slower.
>>>>>>> 15. 1 VTI Linux + 1 VTI Windows [__FAIL__ VTI Windows blue
>>>>>screen]
>>>>>>> 16. Reboot machine failed with Xen FC6-test3. [__FAIL__]
>>>>>>>
>>>>>>> Other issues:
>>>>>>> 1) Xen0 operation is a little slower than RHEL4u3.
>>>>>>> 2) XenU creating failure, please see attachment for the serial output.
>>>>>>>
>>>>>>> Best Regards,
>>>>>>> Yongkang (Kangkang) モタソオ
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Xen-ia64-devel mailing list
>>>>>>> Xen-ia64-devel(a)lists.xensource.com
>>>>>>> http://lists.xensource.com/xen-ia64-devel
>>>>
>>>>_______________________________________________
>>>>Xen-ia64-devel mailing list
>>>>Xen-ia64-devel(a)lists.xensource.com
>>>>http://lists.xensource.com/xen-ia64-devel
>>>
>>>_______________________________________________
>>>Xen-ia64-devel mailing list
>>>Xen-ia64-devel(a)lists.xensource.com
>>>http://lists.xensource.com/xen-ia64-devel
>>
>>
>>_______________________________________________
>>Xen-ia64-devel mailing list
>>Xen-ia64-devel(a)lists.xensource.com
>>http://lists.xensource.com/xen-ia64-devel
17 years, 7 months
