Testing for Xen of FC6 Test3 -- 2
by Zhao, Yunfeng
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
17 years, 7 months
Re: [Xen-devel] Re: [Fedora-xen] IP addresses used by domU
by Daniel P. Berrange
On Thu, Sep 21, 2006 at 10:50:11AM -0700, Sanjam Garg wrote:
> thanks a lot.
>
> Your assumption on bridging was correct...but the fact is that i
> cant use sniffing to make a guess as my system has constraints laid
> down by the intentions of the user who may use some packet source
> IP spoofing to mislead dom0.if thats all that can be done then i
> would need to do something more rigrous...
When using bridging the network security concerns are pretty much exactly
the same for those of a bare metal machine - the whole point of bridging
is that the guest is connecting directly to the LAN as any physical machine
would.
Thus if you don't trust the admin of the DomU then don't let them connect straight
to the network. For example, you can switch Xen to an alternative networking
config where DomU's have to be forwarded & NAT'd using IPTables to get LAN
access. If you really want to use bridging I guess you could try filtering
out any traffic from the DomU's particular vif which has an unexpected
source IP address, but really best bet is to go for NAT & remove their
direct access
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 -=|
17 years, 7 months
IP addresses used by domU
by Sanjam Garg
Hi
I am having FC5 guest run on top FC5 host.I have configured the virtual network card for FC5 in the guest operating system.This network card is expected to have been allotted many IP addresses.Is there a secure way in Xen to get information as to what are those IP's?
Thanks
Sanjam
---------------------------------
Get your own web address for just $1.99/1st yr. We'll help. Yahoo! Small Business.
17 years, 7 months
Re: [Fedora-xen] IP addresses used by domU
by Sanjam Garg
Hi
Thanks for replying.I want to get a list of IPs being used by a virtual machine(domU).I do not want to rule out the future possibility of a user wanting to run his own virtual machines on top of domU.So I need to figure out all the IPs that are being used by the virtual interface dedicated to a virtual machine.I have been constrained from using sniffing to detect IPs because a mean user could use some packet spoofing tool and trick dom0 to expect more IPs that actually present.
Thanks once again
Sanjam Garg
"Patricio A. Bruna" <pbruna(a)it-linux.cl> wrote: Can you explain what you meant by: "Is there a secure way in Xen to get information as to what are those IP's"?
----- Original Message -----
From: Sanjam Garg <sanjamg(a)yahoo.com>
To: xen-devel(a)lists.xensource.com
Cc: fedora-xen(a)redhat.com
Sent: jueves 21 de septiembre de 2006 08H21 GMT-0400
Subject: [Fedora-xen] IP addresses used by domU
Hi
I am having FC5 guest run on top FC5 host.I have configured the virtual network card for FC5 in the guest operating system.This network card is expected to have been allotted many IP addresses.Is there a secure way in Xen to get information as to what are those IP's?
Thanks
Sanjam
---------------------------------
Get your own web address for just $1.99/1st yr. We'll help. Yahoo! Small Business.
---------------------------------
Get your email and more, right on the new Yahoo.com
17 years, 7 months
FC5 -- with new "development" Xen kernels/xend
by Russell McOrmond
Just for kicks I tried the kernel-xen, xen and dependencies from the
'development' yum repository. When trying to create the XenU's it gave
me a "Error: (22, 'Invalid argument')".
With FC5 there was a xen0 kernel for the Xen0 and a xenU kernel that
was put in each XenU. I believe that for the development branch (and
FC6) that something different is being done, with the Xen0 using a
'kernel-xen' package: kernel-xen-2.6.17-1.2647.fc6 . I'm gathering
that the XenU kernels are also different now (like what happened with
the FC4 to FC5 switch), meaning I can't continue to use the xenU kernels
I currently have installed.
When I mentioned this issue on Bugzilla (In a different context of
waiting for a new FC5 kernel with a specific patch
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=199944 ), Herbert
Xu mentioned I need to have XenU kernels with the PAE patch.
Does anyone know which Fedora kernels to be putting in the XenU's if
I'm wanting to use the new "development" xen and kernel-xen?
--
Russell McOrmond, Internet Consultant: <http://www.flora.ca/>
Please help us tell the Canadian Parliament to protect our property
rights as owners of Information Technology. Sign the petition!
http://www.digital-copyright.ca/petition/ict/
"The government, lobbied by legacy copyright holders and hardware
manufacturers, can pry my camcorder, computer, home theatre, or
portable media player from my cold dead hands!"
17 years, 7 months
RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result
by You, Yongkang
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年9月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年9月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
17 years, 7 months
[FYI] SELinux issue for create domU on xen
by Akio Takebe
Hi,
I have the following error.
[root@tiger156 xen]# ls /boot/efi/efi/redhat/vmlinuz-2.6.17-1.2630.
fc6xen
/boot/efi/efi/redhat/vmlinuz-2.6.17-1.2630.fc6xen
[root@tiger156 xen]# xm create -c fc6.para.conf
Using config file "fc6.para.conf".
Error: Kernel image does not exist: /boot/efi/efi/redhat/vmlinuz-2.6.17-
1.2630.fc6xen
I don't mistake kernel path of domU config, but this error is shown.
I could solve this issue by disabling SELinux.
Best Regards,
Akio Takebe
17 years, 7 months
Testing for Xen of FC6 Test3 -- 1
by Zhao, Yunfeng
Hi.
We are now doing a full testing for Xen of FC6 Test3.
As a part of the full testing, we have already completed a basic
functional testing.
The testing includes boot vmx guests, installing fc6 test3 ia32/ia32e
into vmx, and installing win 2000/xp/2003 into vmx.
The test box is an Intel SDV with a presler processor.
Following are the test results, and more test results will be available
soon.
Here are some issues I found in the basic functional testing:
1. Cannot boot fc6 test3 ia32 smp guest, xen0 reboot
fc6 test3 ia32 guest can be booted up with 1 vcpu, but if boot it as a
smp guest with enabling 2 vcpus and apic=1 in config file, xen0 will
reboot.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207418
2. Cannot reboot/poweroff vmx guests.
After reboot vmx guest,a white window will be popped up.
After poweroff, vmx guest will not be destroyed.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207402
3. VGA issues of win2k and fc6 test3 IA32e guests
I cannot install FC6 test3 IA32e guest with graphic mode.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207407
VGA of win2k vmx guest is unusable.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207405
4. Installer of Fc6 test3 ia32e doesn't make initrd
After installed fc6 ia32e native and vmx, I could not find initrd. So to
boot FC6 Test3 native or vmx, I have to create initrd by myself.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=207407
Here is detailed result about the testing:
1. Install windows xp sp2/2000/2003 on ia32-pae/ia32e hv PASS
2. Install FC6-test3 ia32 with graphical mode PASS
3. Install FC6-test3 ia32e with graphical mode FAIL
4. Install FC6-test3 ia32e with text mode PASS
5. Boot FC5 UP IA32/IA32e VMX guests PASS
6. Boot FC6 Test3 IA32 UP VMX guest PASS
7. Boot FC6 Test3 IA32 SMP VMX guest FAIL
(Xen0 reboot)
8. Boot FC6 Test3e IA32 UP VMX guest FAIL (No
initrd)
9. Boot FC6 Test3e IA32 SMP VMX guest FAIL (No
initrd)
Thanks
Yunfeng
17 years, 7 months
DomainU crashing - Zombie
by Kwan Lowe
Hello all:
After doing some recent updates I've noticed that one previously stable domain is
now crashing regularly. The dom0 is running 2.6.17-1.2187_FC5xen0 and the
corresponding domU kernel on the virtuals. Dom0 hardware is an Athlon XP 2200
with 1G RAM. This occurs under moderately heavy network. The crashed domain is a
fileserver image with a physical disk and was serving up a Solaris installation
iso when it died.
The DomU will not shutdown with "xm shutdown" or "xm destroy" and I need to kill -9
the "xend start" processes to force it down. This also prevents the Dom0 from
rebooting.
Ahh... And just noticed that I can't "xm shutdown" two running VMs either. They both
go to Zombie state.
(domain
(domid 4)
(uuid 314e3d58-a8b9-a7d6-4d86-472aa42cbcc5)
(vcpus 1)
(cpu_weight 1.0)
(memory 256)
(maxmem 256)
(bootloader /usr/bin/pygrub)
(features )
(name Zombie-xm-fc5-001)
(on_poweroff destroy)
(on_reboot restart)
(on_crash restart)
(image
(linux
(ramdisk /var/lib/xen/initrd.huJonl)
(kernel /var/lib/xen/vmlinuz.cTMDsO)
(args 'ro root=/dev/rootvg/root_lv')
)
)
(state ----cd)
(shutdown_reason crash)
(cpu_time 59.409401921)
(online_vcpus 1)
(up_time 11961.170969)
(start_time 1158775219.69)
(store_mfn 235518)
(console_mfn 235517)
)
--
* The Digital Hermit http://www.digitalhermit.com
* Unix and Linux Solutions kwan(a)digitalhermit.com
17 years, 7 months
RE: [Xen-ia64-devel] [Fedora-ia64-list] FC6 Test3 Xen test result
by You, Yongkang
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年9月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
17 years, 7 months
