xen with kickstart
by tournesol
Hi all
Does anyone tried install xen GuestOS with kickstart (or PXE )?
Any advice please.
tournesol
18 years, 1 month
more advanced xenguest-install.py usage
by Ben
I'd like to install a Xen domU that uses a separate partition for its
swap space, and also only sees a specific NIC in my dom0. Is that
possible with xenguest-install? Looking at the questions it asks, I
don't see how, but I've been known to miss obvious things before....
18 years, 1 month
RE: [Fedora-xen] crash booting rawhide xen0
by You, Yongkang
>-----Original Message-----
>From: fedora-xen-bounces(a)redhat.com
>[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Andy Burns
>Sent: 2006年3月12日 18:52
>To: fedora-xen(a)redhat.com
>Subject: [Fedora-xen] crash booting rawhide xen0
>
>
>Having seen it fail twice, I attached a serial console and was preparing
>to capture that with console=ttyS0,115200, but on the next two boots the
>crash didn't happen, however my console output still went to the
>vgaconsole, does xen have a different way to use the serial console?
If want to get serial output in Xen, you can give the grub.conf like:
kernel /boot/xen.gz com1=115200,8n1 sync_console
module /boot/vmlinuz-hypervisor ro root=/dev/sda1 console=tty0 console=ttyS0
module /boot/initrd.img...
BTW, did the broken happen in booting XWin? I also catch a strange broken in 2032.
Best Regards,
Yongkang (Kangkang) 永康
18 years, 1 month
Fwd: Bugzilla Bug 185081 – soft lockup detected on CPU#0!
by Murali D
---------- Forwarded message ----------
From: Stephen C. Tweedie <sct(a)redhat.com>
Date: Mar 10, 2006 10:52 PM
Subject: Re: Bugzilla Bug 185081 – soft lockup detected on CPU#0!
To: Murali D <muralid.india(a)gmail.com>
Cc: Stephen Tweedie <sct(a)redhat.com>
Hi,
On Fri, 2006-03-10 at 19:40 +0530, Murali D wrote:
> I have filed a bug... Is this cpu intensive error.... the guest OS is
> getting hang..
> Any solutions...
Somebody else is working on this problem --- which is precisely why it's
better to be asking on the list, not just always directing the questions
to one person!
Thanks,
Stephen
18 years, 1 month
RE: [Fedora-xen] Latest Xen RPMS testing in FC5.
by You, Yongkang
>-----Original Message-----
>From: fedora-xen-bounces(a)redhat.com
>[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Stephen C. Tweedie
>Sent: 2006年3月10日 1:13
>To: You, Yongkang
>Cc: fedora-xen(a)redhat.com
>Subject: RE: [Fedora-xen] Latest Xen RPMS testing in FC5.
>
>Hi,
>
>On Thu, 2006-03-09 at 14:32 +0800, You, Yongkang wrote:
>
>
>> For the x86_64 problem of hang xen0 if destroying HVM(VMX), our
>> developer shared a information maybe usefully. From the failed info of
>> serial out, it seemed debug=y was opened when making Xen. And VMX will
>> meet some problem if debug option is opened. Could you have a double
>> check? And let the debug=n? :)
>
>What's the problem? I'd rather fix it than disable debug, and we're
>really close to the scheduled FC5 release date now so I don't want to be
>making significant changes at this point.
Emm~, our developers are trying to fix this issue and will send out the patch to Xen. After the patch come out, I will notify here to integrate it. Is it Okay?
>
>> For enabling serial console in Xen and Xen0, we still meet the bug
>> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=180126 . We have
>> to disable acpi to enable serial console operation and output, or Xen0
>> couldn't boot up. Do you have some updates?
>
>No -- it always works for me. But I did notice something from the
>bugzilla that might be important, and I just added:
>
> kernel /boot/xen.gz-2.6.15-1.29_FC5 com1=115200,8n1
> module /boot/vmlinuz-2.6.15-1.29_FC5hypervisor ro
>root=/dev/sda1
> console=tty0 console=ttyS0 sync_console
>
> This is wrong, the "sync_console" needs to be on the "kernel"
>hypervisor option
> list, not the xen0 "module" list. Can you reproduce with that change?
I have tried with your guide. It also worked for me.
I think it is a little strange, that we didn't use "sync_console" in Xen befero. :)
Maybe this specail config item should be added into something like readme in Fedora Xen, because Xen manual didn't mention it, user may meet the same trouble like me.
>
>Cheers,
> Stephen
>
Best Regards,
Yongkang (Kangkang) 永康
18 years, 1 month
RE: [Fedora-xen] Latest Xen RPMS testing in FC5.
by You, Yongkang
>-----Original Message-----
>From: fedora-xen-bounces(a)redhat.com
>[mailto:fedora-xen-bounces@redhat.com] On Behalf Of You, Yongkang
>Sent: 2006年3月10日 9:32
>To: Stephen C. Tweedie
>Cc: fedora-xen(a)redhat.com
>Subject: RE: [Fedora-xen] Latest Xen RPMS testing in FC5.
>
>>No -- it always works for me. But I did notice something from the
>>bugzilla that might be important, and I just added:
>>
>> kernel /boot/xen.gz-2.6.15-1.29_FC5 com1=115200,8n1
>> module /boot/vmlinuz-2.6.15-1.29_FC5hypervisor ro
>>root=/dev/sda1
>> console=tty0 console=ttyS0 sync_console
>>
>> This is wrong, the "sync_console" needs to be on the "kernel"
>>hypervisor option
>> list, not the xen0 "module" list. Can you reproduce with that change?
>
>I have tried with your guide. It also worked for me.
>
>I think it is a little strange, that we didn't use "sync_console" in Xen befero. :)
>Maybe this specail config item should be added into something like readme in
>Fedora Xen, because Xen manual didn't mention it, user may meet the same
>trouble like me.
>
With this config, I can get Xen0 start and serial output information. But I can not input any commands from serial console after Xen begin to boot. I have given the correct setting in Xen0 inittab. Can you input anything in serial console to control Xen? Is there any other configuration?
Best Regards,
Yongkang (Kangkang) 永康
18 years, 1 month
RE: [Fedora-xen] Latest Xen RPMS testing in FC5.
by You, Yongkang
Hi Stephen,
I couldn't reproduce the failed udev problem in either IA32 or x86_64 again. But I met it once on both IA32 and x86_64 platforms yesterday. If I catch it next time, I will record the detail and send to you.
For the x86_64 problem of hang xen0 if destroying HVM(VMX), our developer shared a information maybe usefully. From the failed info of serial out, it seemed debug=y was opened when making Xen. And VMX will meet some problem if debug option is opened. Could you have a double check? And let the debug=n? :)
For enabling serial console in Xen and Xen0, we still meet the bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=180126 . We have to disable acpi to enable serial console operation and output, or Xen0 couldn't boot up. Do you have some updates?
Best Regards,
Yongkang (Kangkang) 永康
>-----Original Message-----
>From: fedora-xen-bounces(a)redhat.com
>[mailto:fedora-xen-bounces@redhat.com] On Behalf Of Stephen C. Tweedie
>Sent: 2006年3月9日 11:08
>To: You, Yongkang
>Cc: fedora-xen(a)redhat.com
>Subject: Re: [Fedora-xen] Latest Xen RPMS testing in FC5.
>
>Hi,
>
>On Wed, 2006-03-08 at 18:49 +0800, You, Yongkang wrote:
>
>> We have done a fuller testing for latest Xen updates on FC5.
>
>Thanks!
>
>> Sometime when Xen0 boot, udev will be failed to start up. It will report time out
>and kernel bugs.
>
>Do you have any more details? What is the kernel bug output?
>
>Thanks,
> Stephen
>
>
>--
>Fedora-xen mailing list
>Fedora-xen(a)redhat.com
>https://www.redhat.com/mailman/listinfo/fedora-xen
18 years, 1 month
Latest Xen RPMS testing in FC5.
by You, Yongkang
Hi all,
We have done a fuller testing for latest Xen updates on FC5.
Brief results:
In IA32 platform VMX/XenU/Xen run well without any problem.
But in x86_64 platform destroy VMX domain will hang Xen0. The serial port output is put in attachment. (I will report a Bug to bugzilla)
The detailed testing results:
--------
IA32
--------
Xend start pass
Xm destroy pass
2.4 vmx domain creating with 128M memory pass
2.6 vmx domain creating with 256M memory pass
2.4 vmx domain creating with 512M memory pass
xenU domain creating pass
VMX and xenU coexit pass
2 VMXs and 2 XenUs coexist pass
4 VMXs coexist pass
VMX Xwindows testing pass
Boot up a Windows domain pass
-------
X86_64
--------
Xend start ok
Create VMX ok
Destroy VMX Fail. Hang Xen0.
Create and destroy XenU pass
================================
Environments:
The base FC5 environment is FC5-test3.
--------------------
The Xen RPMs are:
IA32:
kernel-xen0-2.6.15-1.2025_FC5.i686.rpm kernel-xenU-2.6.15-1.2025_FC5.i686.rpm
xen-3.0.1-2.i386.rpm
kernel-xen0-2.6.15-1.2032_FC5.i686.rpm kernel-xenU-2.6.15-1.2032_FC5.i686.rpm
xen-3.0.1-3.i386.rpm
x86_64:
kernel-xen0-2.6.15-1.2025_FC5.x86_64.rpm
kernel-xenU-2.6.15-1.2025_FC5.x86_64.rpm
xen-3.0.1-2.x86_64.rpm
kernel-xen0-2.6.15-1.2032_FC5.x86_64.rpm
kernel-xenU-2.6.15-1.2032_FC5.x86_64.rpm
xen-3.0.1-3.x86_64.rpm
=================================
Other issue:
Sometime when Xen0 boot, udev will be failed to start up. It will report time out and kernel bugs.
Best Regards,
Yongkang (Kangkang) 永康
18 years, 1 month
[Fwd: Re: [Fedora-xen] kernel naming]
by Jeremy Katz
-------- Forwarded Message --------
From: Jeremy Katz <katzj(a)redhat.com>
To: Justin Conover <justin.conover(a)gmail.com>
Subject: Re: [Fedora-xen] kernel naming
Date: Wed, 08 Mar 2006 13:38:14 -0500
On Wed, 2006-03-08 at 11:55 -0600, Justin Conover wrote:
> Apparently I missed this tidbit about kernel/name changes, back to the
> old style, any reason why yum didn't update them? Guess it doesn't
> really matter for final since the installs will use the
> "new/old-style" name changes.
We didn't add the obsoletes given that the names were only ever used in
test releases/rawhide and updates between that and final aren't
guaranteed.
And the reason you missed the tidbit is that I forgot to send mail. We
were having issues just getting rebased kernels working for a while and
then I forgot to send once the change actually went in. We've gone back
to kernel-xen0 and kernel-xenU as that is needed to make it possible to
build extra kernel modules against these packages as defined by the
Fedora Extras Kernel Module Package Policy
Jeremy
18 years, 1 month
