|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11609
Hi, Yongkang,
I came across the same message, too. The changeset were 11609 and
11456. The number of vcpus in a guest seems to have some relevance
since I see this bug almost always with vcpus=4 in XenU configuration,
while I have no problem with vcpus=1, 2 and 3. In addition, I could
biring up XenU with vcpus=3 just after the failure occurred with vcpus=4.
The command line and the message:
# xm create /etc/xen/rhel4PAR-xx.xx.xx.xx-vcpu4 -c
Using config file "/etc/xen/rhel4PAR-xx.xx.xx.xx-vcpu4".
Error: Device 768 (vbd) could not be connected. Backend device not found.
A detailed configurations:
[XenU config]
# grep -v '^#' /etc/xen/rhel4PAR-xx.xx.xx.xx-vcpu4 |grep -v '^$'
kernel = "/boot/efi/efi/xen/vmlinuz-2.6.16.29-xen-cs11609-inakoshi"
ramdisk = "/boot/efi/efi/xen/initrd-2.6.16.29-xen.img-cs11609-inakoshi"
memory = 512
name = "rhel4PAR-179.69"
vcpus = 4
vif = [ '' ]
disk = [ 'file:/xen/image/rhel4u2-xx.xx.xx.xx-5GB-inakoshi.img,hda,w' ]
root = "/dev/hda2 ro"
extra = "nomca console=tty0 root=/dev/hda2 3"
[elilo.conf]
prompt
timeout=20
default=xen-cs11609-inakoshi
relocatable
image=vmlinuz-2.6.9-42.EL
label=linux
initrd=initrd-2.6.9-42.EL.img
read-only
append="rhgb quiet root=LABEL=/"
image=vmlinuz-2.6.16.29-xen-cs11609-inakoshi
label=xen-cs11609-inakoshi
vmm=xen.gz-cs11609-inakoshi
initrd=initrd-2.6.16.29-xen.img-cs11609-inakoshi
read-only
append="com2=115200,8n1 console=com2 sched=credit tbuf_size=128
maxcpus=4 dom0_max_vcpus=4 -- nomca dom0_vcpus=4 console=tty0
console=ttyS1,115200,8n1 rhgb root=LABEL=/"
## Note: The append line below also caused the bug.
# append="com2=115200,8n1 console=com2 sched=credit tbuf_size=128
dom0_vcpus_pin -- nomca console=tty0 console=ttyS1,115200,8n1 rhgb
root=LABEL=/"
[xm info]
host : xx.xx.xx.xx
release : 2.6.16.29-xen
version : #1 SMP Thu Sep 28 14:26:53 JST 2006
machine : ia64
nr_cpus : 4
nr_nodes : 1
sockets_per_node : 2
cores_per_socket : 2
threads_per_core : 1
cpu_mhz : 1396
hw_caps :
00000000:00000000:00000000:00000000:00000000:00000000:00000000:00000000:
total_memory : 4070
free_memory : 3503
xen_major : 3
xen_minor : 0
xen_extra : -unstable
xen_caps : xen-3.0-ia64 hvm-3.0-ia64
xen_pagesize : 16384
platform_params : virt_start=0xe800000000000000
xen_changeset : Sun Sep 24 14:55:57 2006 -0600 11609:7b250cf49e50
cc_compiler : gcc version 3.4.5
cc_compile_by : inakoshi
cc_compile_domain : xx.xx.xx.xx
cc_compile_date : Thu Sep 28 15:13:08 JST 2006
xend_config_format : 2
Regards,
Hiroya
You, Yongkang wrote:
> The 2 XenU coexisting testing is easy to fail.
>
> I try 3 times to create 2 XenU domains at the same time "(xm create config1
> &) ; xm create config2 &" . The first 2 times are pass. But the 3rd time.
> XenU creating failed.
> After that, "xm list" can not list domains and will report "Error: Device 768
> not connected"
>
> Use "xend stop and xend start" could recover "xm list".
> But if try to create 2 XenU domains again, there will be 4 Zombie-Domains in
> "xm list".
>
> It is same with the bug
> http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=747
>
> Best Regards,
> Yongkang (Kangkang) 永康
>
>> -----Original Message-----
>> From: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
>> [mailto:xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of You,
>> Yongkang
>> Sent: 2006年9月27日 15:05
>> To: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>> Subject: [Xen-ia64-devel] Xen/IA64 Healthiness Report -Cset#11609
>>
>> Xen/IA64 Healthiness Report
>>
>> 2 XenU coexisting case failed.
>> If try to create 2 XenU at the same time, Xend will be broken, e.g. "xm
>> list" just
>> show "xm help" information. Have to reboot machine to recover. We will report
>> a
>> new bug for this.
>>
>> Testing Environment:
>> ----------------------------
>> Platform: Tiger4
>> Processor: Itanium 2 Processor
>> Logic Processors number: 8 (2 processors with Due Core)
>> PAL version: 8.15
>> Service OS: RHEL4u3 IA64 SMP with 2 VCPUs
>> VTI Guest OS: RHEL4u2 & RHEL4u3
>> XenU Guest OS: RHEL4u2
>> Xen IA64 Unstable tree: 11635:f34e37d0742d
>> Xen Schedule: credit
>> VTI Guest Firmware MD5: ea1815932b91e5a6481bb64468e50254
>>
>> Summary Test Report:
>> -----------------------------
>> Total cases: 16
>> Passed: 15
>> Failed: 1
>>
>> Detailed test cases info:
>> -----------------------------
>> 1. One_VTI_without_vif pass
>> 2. One_VTI pass
>> 3. One_XenU pass
>> 4. Two_VTI_Coexist pass
>> 5. One_VTI_and_One_XenU pass
>> 6. Two_XenU_Coexist __FAIL__
>> 7. One_VTI_4096M pass
>> 8. VTI_Network pass
>> 9. XenU_Network pass
>> 10. One_SMP_XenU pass
>> 11. One_SMP_VTI pass
>> 12. UP_VTI_LTP pass
>> 13. VTI_Kernel_Build pass
>> 14. Four_VTI_Coexist pass
>> 15. VTI_Windows pass
>> 16. VTI_Win_Linux_XenU_Coexist pass
>>
>> Notes:
>> -----------------------------
>>
>> The last stable changeset:
>> -----------------------------
>> 11609:7b250cf49e50
>>
>> Best Regards,
>> Yongkang (Kangkang) 永康
>>
>> _______________________________________________
>> Xen-ia64-devel mailing list
>> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-ia64-devel
>
> _______________________________________________
> Xen-ia64-devel mailing list
> Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-ia64-devel
>
>
_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |