automating the install of windows 2000 or XP

_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users

xm shutdown and reboot without console

Hi,

is there a specific reason, whe "xm create" has an option "-c" (for console), but 
"xm shutdown" or "xm reboot" do not (in XEN 3.0.2)? The console is useful in any 
case.

Regards,
Ulrich

kernel BUG at drivers/xen/core/evtchn.c:765

Howdy,

I'm running Debian Sarge/Etch + linux-image-2.6.18-3-xen-686 2.6.18-7 +
xen-ioemu-3.0.3-1 3.0.3-0-2.

I have an Debian pvm guest machine, using the Host kernel+initrd, also I
compiled the misdn kernel modules in the guest System...
The VM runs ~a week without problems..
This morning i openend an console from the VM and get the following error:

"------------[ cut here ]------------
kernel BUG at drivers/xen/core/evtchn.c:765!
invalid opcode: 0000 [#1]
SMP
Modules linked in: capi mISDN_dsp avmfritz mISDN_capi l3udss1 mISDN_l2
mISDN_l1 ipv6 uhci_hcd ohci_hcd ehci_hcd usbcore capifs kernelcapi
mISDN_isac mISDN_core 8250 serial_core ext3 jbd mbcache dm_mirror
dm_snapshot processor dm_mod
CPU:    0
EIP:    0061:[<c0206862>]    Not tainted VLI
EFLAGS: 00010006   (2.6.18-3-xen-686 #1)
EIP is at irq_resume+0x30/0x28e
eax: 00000012   ebx: 00000000   ecx: 00000000   edx: 00000400
esi: 00000042   edi: 00000000   ebp: 00042000   esp: ce253ef8
ds: 007b   es: 007b   ss: 0069
Process suspend (pid: 5073, ti=ce252000 task=c0f46550 task.ti=ce252000)
Stack: c0f46550 c0129ec1 ce253f00 ce253f00 00000000 00000002 ce253f48
c02070ac
       c1084d40 c0fea00c d1003000 c105bd10 c0146e64 ce253f80 c02c94a0
d1004000
       d1004000 c10527c0 c1065000 00000002 00000042 00000000 00042000
c0206e2d
Call Trace:
 [<c0129ec1>] autoremove_wake_function+0x0/0x2d
 [<c02070ac>] map_pte_fn+0x22/0x40
 [<c0146e64>] apply_to_page_range+0x272/0x2c4
 [<c0206e2d>] gnttab_resume+0x96/0xad
 [<c020708a>] map_pte_fn+0x0/0x40
 [<c0117ff0>] copy_process+0x837/0x10ae
 [<c0207e6b>] __do_suspend+0x286/0x3c7
 [<c011323f>] complete+0x2b/0x3d
 [<c0207be5>] __do_suspend+0x0/0x3c7
 [<c0129df3>] kthread+0xc2/0xef
 [<c0129d31>] kthread+0x0/0xef
 [<c0102941>] kernel_thread_helper+0x5/0xb
Code: c4 80 e8 ae f5 ff ff 31 d2 a1 84 a9 2c c0 f0 0f ab 90 80 08 00 00
42 81 fa 00 04 00 00 75 ea 31 c0 83 3c 85 80 14 37 c0 00 74 08 <0f> 0b
fd 02 05 b8 2a c0 40 3d 00 01 00 00 75 e6 b8 80 4e 37 c0
EIP: [<c0206862>] irq_resume+0x30/0x28e SS:ESP 0069:ce253ef8

Message from syslogd <at> rudi2 at Fri Jan 19 08:17:48 2007 ...
rudi2 kernel: ------------[ cut here ]------------

Message from syslogd <at> rudi2 at Fri Jan 19 08:17:48 2007 ...
rudi2 kernel: kernel BUG at drivers/xen/core/evtchn.c:765!

Message from syslogd <at> rudi2 at Fri Jan 19 08:17:48 2007 ...
rudi2 kernel: invalid opcode: 0000 [#1]

Message from syslogd <at> rudi2 at Fri Jan 19 08:17:48 2007 ...
rudi2 kernel: SMP

Message from syslogd <at> rudi2 at Fri Jan 19 08:17:48 2007 ...
rudi2 kernel: CPU:    0

Message from syslogd <at> rudi2 at Fri Jan 19 08:17:48 2007 ...
rudi2 kernel: EIP is at irq_resume+0x30/0x28e

Message from syslogd <at> rudi2 at Fri Jan 19 08:17:48 2007 ...
rudi2 kernel: eax: 00000012   ebx: 00000000   ecx: 00000000   edx: 00000400

Message from syslogd <at> rudi2 at Fri Jan 19 08:17:48 2007 ...
rudi2 kernel: esi: 00000042   edi: 00000000   ebp: 00042000   esp: ce253ef8

Message from syslogd <at> rudi2 at Fri Jan 19 08:17:48 2007 ...
rudi2 kernel: ds: 007b   es: 007b   ss: 0069

Message from syslogd <at> rudi2 at Fri Jan 19 08:17:48 2007 ...
rudi2 kernel: Process suspend (pid: 5073, ti=ce252000 task=c0f46550
task.ti=ce252000)

Message from syslogd <at> rudi2 at Fri Jan 19 08:17:48 2007 ...
rudi2 kernel: Stack: c0f46550 c0129ec1 ce253f00 ce253f00 00000000
00000002 ce253f48 c02070ac

Message from syslogd <at> rudi2 at Fri Jan 19 08:17:48 2007 ...
rudi2 kernel:        c1084d40 c0fea00c d1003000 c105bd10 c0146e64
ce253f80 c02c94a0 d1004000

Message from syslogd <at> rudi2 at Fri Jan 19 08:17:48 2007 ...
rudi2 kernel:        d1004000 c10527c0 c1065000 00000002 00000042
00000000 00042000 c0206e2d

Message from syslogd <at> rudi2 at Fri Jan 19 08:17:48 2007 ...
rudi2 kernel: Call Trace:

Message from syslogd <at> rudi2 at Fri Jan 19 08:17:48 2007 ...
rudi2 kernel: Code: c4 80 e8 ae f5 ff ff 31 d2 a1 84 a9 2c c0 f0 0f ab
90 80 08 00 00 42 81 fa 00 04 00 00 75 ea 31 c0 83 3c 85 80 14 37 c0 00
74 08 <0f> 0b fd 02 05 b8 2a c0 40 3d 00 01 00 00 75 e6 b8 80 4e 37 c0

Message from syslogd <at> rudi2 at Fri Jan 19 08:17:48 2007 ...
rudi2 kernel: EIP: [<c0206862>] irq_resume+0x30/0x28e SS:ESP 0069:ce253ef8"

Did anybody have an idea what can be wrong? How can I fix this?

thanks

greetings

Fabian

--

-- 
#---------------------------#-------------------------#
# Fabian Holler             #  Inmedias.it GmbH       #
#---------------------------#-------------------------#
# Tel.: +49 40-41436-406    #  Lippmannstraße 71      #
# Fax.: +49 40-41436-306    #  22769 Hamburg          #
# Jabber: fho <at> jabber.ccc.de #  http://www.inmedias.it #
#---------------------------#-------------------------#

_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users

Re: xm shutdown and reboot without console

Ulrich Windl wrote:
> Hi,
> 
> is there a specific reason, whe "xm create" has an option "-c" (for console), but 
> "xm shutdown" or "xm reboot" do not (in XEN 3.0.2)? The console is useful in any 
> case.

Good idea.
Having a "-c" option to "xm shutdown" and "xm reboot" would be great.

--

-- 
Tomasz Chmielewski
http://wpkg.org

Re: What Debian SDL package for SDL with/in Xen?

On Wednesday 31 January 2007 19:56, Henning Sprang wrote:
> > When I set "sdl=1" in the guest configuration file, and then
> > "xm start the-guest.cfg", to SDL window pops up.
> > When I use VNC, I can also connect. But I wonder why it doesnot work the
> > SDL way...
> What so you mean/expect?
> You say "an SDL window pops up", that sounds alllright, as long as you
> don't tell us what's wrong with it.

It _should_ pop up.
On my Debian installation, it does not.
May be am I missing something (a lib, or I dont know...)
On a default SuSe installation, it pops up, and I do want to use Debian on 
this box.

Running Redhat Advanced Server 2.1 on hvm

   Hi,

   I was trying to have a working RHEL2.1 domU and found a mail sent  
on January 26th to xen-users by Nelson Chan. I am subscribed to the  
list but didn't have the original mail in my mailbox, so I'm sending  
this message with the same subject. Sorry if I screw up you mail  
reader's threading algorithm :)

   Anyway, after successfully installing a RHEL2.1 in hvm mode from  
our kickstart server, I tried two things:

   - running with non-hvm using the 2.4 xenU kernel provided by  
xensource. The system would boot although the console was stuck on  
the last init script launched. The init process would give weird  
messages (sorry, I didn't wrote them down) but the system could be  
reached by ssh. Some binaries (yum for example) would segfault. The  
upgrade to RHEL3's glibc worked, but I didn't want to go that way...

   - running with hvm and the default RHEL2.1 kernel. This didn't  
work and gave a kernel panic upon boot (I tried with -52 and the  
latest -71 release level from RH). I then took the vmlinuz and initrd  
files from the installation cd and used them. They are actually built  
from the same srpm and are found in the -BOOT package. I just had to  
tweak the initrd file so that it wouldn't launch the install after  
booting, but it worked.

   I'm using the system with this setup. As soon as I'll have time,  
I'll diff the kernel config files to try and locate the option(s)  
that make the regular kernel crash.

--

-- 
Eric-Olivier Lamey

Re: RE: DomU boot fails with can't find root on Fedora 6

On 31 Jan 2007 at 14:31, Petersson, Mats wrote:

>  
> 
> > -----Original Message-----
> > From: Ligesh [mailto:myself <at> ligesh.com] 
> > Sent: 31 January 2007 13:18
> > To: Petersson, Mats
> > Cc: Xen-users <at> lists.xensource.com
> > Subject: Re: DomU boot fails with can't find root on Fedora 6
> > 
> > On Wed, Jan 31, 2007 at 02:10:21PM +0100, Petersson, Mats wrote:
> > > 
> > > Probably caused by the fact that you're using the same 
> > initrd for your
> > > guest as you do for the host - you should use a separate 
> > initrd for your
> > > guest (using the same kernel is fine). My guess is that the 
> > initrd is
> > > "messing" with the root argument.
> > > 
> > 
> >  But initrd is nothing but a archive of the drivers. I 
> > checked it, and it doesn't contain an etc or anything that 
> > can mess with the boot. Or if it does, that's a very wrong 
> > design. Anyway how do I create a new initrd that won't mess 
> > with the boot?
> 
> Usually, the initrd contains a little bit of scripting too, which sets
> up devices and such, and I suspect this is what causes a problem. 
> 
> You can create a new initrd with "mkinitrd file linuxver", such as
> "mkinitrd someplace/initrd-xen 2.6.18-xen" - obviously, don't overwrite
> your existing /boot initrd. 

For me (using SUSE) the following did help: mount your file structure in Dom0 
(plus the /dev tree like "mount --bind /dev /mnt/dev"), then do a "chroot /mnt 
mkinitrd", possibly with "-d root_device". Also assuming that some magic pulls out 
kernel and initrd from the device or image to boot those, like:
bootloader = '/usr/lib/xen/boot/domUloader.py'
bootentry = 'sda1:/boot/vmlinuz-xen,/boot/initrd-xen'

> 
> I'm by no means an expert on initrd (nor do I use LVM on any of my
> current machines), but the above is what I understand of it. (I had a
> look at mkinitrd, but it's a fairly BIG shell-script file - but from
> what I can see, it does set up a bunch of script stuff, and some are
> directly related to using LVM). 
> 
> --
> Mats
> > 
> >  PS: I solved the fedora-xen ml problem. I have around 60 
> > mailboxes, and it appears I had filtered all mails from 
> > redhat to another mbox, because rh used to spam me with their 
> > newsletter. So I will ask there too.
> > 
> >  Thanks.
> > 
> > 
> > 
> > 
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users <at> lists.xensource.com
> http://lists.xensource.com/xen-users

Re: What Debian SDL package for SDL with/in Xen?

On 2/1/07, Rakotomandimby (R12y) Mihamina
<mihamina.rakotomandimby <at> etu.univ-orleans.fr> wrote:
> On Wednesday 31 January 2007 19:56, Henning Sprang wrote:
> > > When I set "sdl=1" in the guest configuration file, and then
> > > "xm start the-guest.cfg", to SDL window pops up.
> > > When I use VNC, I can also connect. But I wonder why it doesnot work the
> > > SDL way...
> > What so you mean/expect?
> > You say "an SDL window pops up", that sounds alllright, as long as you
> > don't tell us what's wrong with it.
>
> It _should_ pop up.
> On my Debian installation, it does not.

Ah! That wasn't clear.

On Debian, root cannot easily start X programs, and in general, this
is not exactly a bad idea. Either you have to fiddle around with
Xauthority files or whatever is needed to get root to be allowed to
run X programs, or, this is what I do, run xm create with sudo as a
normal user.
You can also use gksudo, if you want to avoid the shell completely.

Henning.

Re: how to start X in the guest domain

On 1/31/07, Henning Sprang <henning_sprang <at> gmx.de> wrote:
> On 1/31/07, Mark Williamson <mark.williamson <at> cl.cam.ac.uk> wrote:
>  > You have CONFIG_FB switched on though, right?  Otherwise the above will fail.
>
> This is all correct - But still the same. I will try again later, but
> I think I run out of ideas what might be wrong...

Hmm, only one thing that I might change:

Mark, on which distribution did you test it for dom0 and domU?
I have all major ones available here for testing, and might try the
same combination as you did.

Henning

Re: DomU boot fails with can't find root on Fedora 6

On Wed, Jan 31, 2007 at 05:01:43PM +0100, Petersson, Mats wrote:
>  
> 
> Try giving mkinitrd a different fstab that contains no reference to LVM
> in the root disk... (--fstab=file)
> 

 Actually, I got it running. Thanks for the help. --fstab=myfstab and --preload=xenblk (and not
xenblk.ko). Fc6 initrd is dynamically generated, it is completely broken. It doesn't contain the
xenblk.ko driver, and it will use lvm, if the host has it.

 Thanks