Hi all,
since Google and archive searches weren''t particularly helpful,
please allow me to post my call for help here.
I''m running Xen 3.0.3-0 using Ubuntu feisty as DomO:
Linux calimero 2.6.19-4-server #2 SMP Thu Apr 5 06:07:34 UTC 2007 i686
This is a remote and headless server. I''ve installed a Debian etch
DomU client into it just fine using xen-tools. I even found my way
around ifrename to make sure that my client network devices aren''t
renamed anymore.
Using the standard Trixbox ISO install image, I would like to install
a full-virtualized Trixbox/CentOS image. My CPU has VT extensions as
indicated by xm dmesg.
My problem is I can''t attach to the boot terminal to track the
Trixbox install process. Here''s my xm dmesg output:
(XEN) (GUEST: 20) Start BIOS ...
(XEN) (GUEST: 20) Starting emulated 16-bit real-mode: ip=F000:FFF0
(XEN) (GUEST: 20) rombios.c,v 1.138 2005/05/07 15:55:26 vruppert Exp $
(XEN) (GUEST: 20) Remapping master: ICW2 0x8 -> 0x20
(XEN) (GUEST: 20) Remapping slave: ICW2 0x70 -> 0x28
(XEN) (GUEST: 20) VGABios $Id: vgabios.c,v 1.61 2005/05/24 16:50:50
vruppert Exp $
(XEN) (GUEST: 20) HVMAssist BIOS, 1 cpu, $Revision: 1.138 $ $Date:
2005/05/07 15:55:26 $
(XEN) (GUEST: 20)
(XEN) (GUEST: 20) ata1 master: QEMU CD-ROM ATAPI-4 CD-Rom/DVD-Rom
(XEN) (GUEST: 20) ata1 slave: Unknown device
(XEN) (GUEST: 20)
(XEN) (GUEST: 20) Booting from CD-Rom...
xm list output after xm create:
Name ID Mem(MiB) VCPUs State
Time(s)
Domain-0 0 3010 2 r-----
2385.9
asterisk.outernet 21 512 1
r----- 32.5
intranet.outernet 2 512 1 -b----
523.5
However xm top shows 100% CPU usage in the asterisk/trixbox domU:
asterisk.outernet -----r 93 100.0 537808 12.8
546000 13.0 1 1 0 0 2
0 0 0 0
Here''s my qemu output:
root@calimero:~# cat /var/log/xen/qemu-dm.7249.log
domid: 21
qemu: the number of cpus is 1
shared page at pfn:1ffff, mfn: 15a35
buffered io page at pfn:1fffd, mfn: 15a37
char device redirected to /dev/pts/2
False I/O request ... in-service already: 0, pvalid: 0, port: 0,
data: 0, count: 0, size: 0
My main problem is I can''t attach to the boot process. I''ve
tried
VNC, but the network setup is a bit convoluted and I''m unsure how to
set this up. Besides, I''m not sure whether my Xen config is correct
anyway:
kernel = ''/usr/lib/xen-ioemu-3.0/boot/hvmloader''
builder=''hvm''
memory = ''512''
root = ''/dev/sda1 ro''
disk = [ ''phy:calimero-volgroup-1/asterisk.outernet-
disk,sda1,w'',''file:/root/trixbox-2.2.iso,hdc:cdrom,r''
]
name = ''asterisk.outernet''
vif = [ ''type=ioemu,bridge=xenbr0,ip=192.168.123.13,mac=00:16:3E:
05:03:01'' ]
cdrom=''/root/trixbox-2.2.iso''
boot=''d''
device_model=''/usr/lib/xen-ioemu-3.0/bin/qemu-dm''
sdl=0
vnc=1
stdvga=0
serial=''pty''
ne2000=0
on_poweroff = ''destroy''
on_reboot = ''restart''
on_crash = ''restart''
Could someone validate I''m at least heading in the right direction?
Thanks,
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought Open Source Java & XML
stevenn at outerthought.org stevenn at apache.org
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
On 23 Jun 2007, at 09:14, Steven Noels wrote:> My main problem is I can''t attach to the boot process. I''ve tried > VNC, but the network setup is a bit convoluted and I''m unsure how > to set this up. Besides, I''m not sure whether my Xen config is > correct anyway: > > > kernel = ''/usr/lib/xen-ioemu-3.0/boot/hvmloader'' > builder=''hvm'' > memory = ''512'' > root = ''/dev/sda1 ro'' > disk = [ ''phy:calimero-volgroup-1/asterisk.outernet- > disk,sda1,w'',''file:/root/trixbox-2.2.iso,hdc:cdrom,r'' ] > name = ''asterisk.outernet'' > vif = [ ''type=ioemu,bridge=xenbr0,ip=192.168.123.13,mac=00:16:3E: > 05:03:01'' ] > cdrom=''/root/trixbox-2.2.iso'' > boot=''d'' > device_model=''/usr/lib/xen-ioemu-3.0/bin/qemu-dm'' > sdl=0 > vnc=1 > stdvga=0 > serial=''pty'' > ne2000=0 > on_poweroff = ''destroy'' > on_reboot = ''restart'' > on_crash = ''restart''I''ve changed the vnc-listen setting and I got it to work now, however the VNC connection seems to be dropped when connecting to it. It''s a bit irregular as I saw the image boot once, until the kernel booted and then the connection got hung. Using netstat, I see the VNC connection start listening when I xm create the client, but also see the port disappear the moment I connect to it. Is there any reason why the VNC server shuts down so easily, and how/ where could I debug this? Thanks, </Steven> -- Steven Noels http://outerthought.org/ Outerthought Open Source Java & XML stevenn at outerthought.org stevenn at apache.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Have you tried the vncserver log file in ~/.vnc directory? On 6/23/07, Steven Noels <stevenn@outerthought.org> wrote:> > On 23 Jun 2007, at 09:14, Steven Noels wrote: > > > My main problem is I can''t attach to the boot process. I''ve tried > > VNC, but the network setup is a bit convoluted and I''m unsure how > > to set this up. Besides, I''m not sure whether my Xen config is > > correct anyway: > > > > > > kernel = ''/usr/lib/xen-ioemu-3.0/boot/hvmloader'' > > builder=''hvm'' > > memory = ''512'' > > root = ''/dev/sda1 ro'' > > disk = [ ''phy:calimero-volgroup-1/asterisk.outernet- > > disk,sda1,w'',''file:/root/trixbox-2.2.iso,hdc:cdrom,r'' ] > > name = ''asterisk.outernet'' > > vif = [ ''type=ioemu,bridge=xenbr0,ip=192.168.123.13,mac=00:16:3E: > > 05:03:01'' ] > > cdrom=''/root/trixbox-2.2.iso'' > > boot=''d'' > > device_model=''/usr/lib/xen-ioemu-3.0/bin/qemu-dm'' > > sdl=0 > > vnc=1 > > stdvga=0 > > serial=''pty'' > > ne2000=0 > > on_poweroff = ''destroy'' > > on_reboot = ''restart'' > > on_crash = ''restart'' > > I''ve changed the vnc-listen setting and I got it to work now, however > the VNC connection seems to be dropped when connecting to it. It''s a > bit irregular as I saw the image boot once, until the kernel booted > and then the connection got hung. > > Using netstat, I see the VNC connection start listening when I xm > create the client, but also see the port disappear the moment I > connect to it. > > Is there any reason why the VNC server shuts down so easily, and how/ > where could I debug this? > > Thanks, > > </Steven> > -- > Steven Noels http://outerthought.org/ > Outerthought Open Source Java & XML > stevenn at outerthought.org stevenn at apache.org > > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 23 Jun 2007, at 21:08, Arie Goldfeld wrote:> Have you tried the vncserver log file in ~/.vnc directory?I don''t have any vnc logs nor a separate vncserver install. AFAIU, Xen comes with its own VNC server built in, no? </Steven> -- Steven Noels http://outerthought.org/ Outerthought Open Source Java & XML stevenn at outerthought.org stevenn at apache.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Steven,> > sdl=0 > > vnc=1Try setting sdl=0 - it''ll start an X11 window displaying the guest''s framebuffer. If you don''t have physical access to the dom0 you can connect to it using ssh -X so that X11 windows are forwarded to your local machine. Hopefully this''ll allow you to select the correct option at the bootloader... Let us know how you get on. Cheers, Mark> > serial=''pty'' > > ne2000=0 > > on_poweroff = ''destroy'' > > on_reboot = ''restart'' > > on_crash = ''restart'' > > I''ve changed the vnc-listen setting and I got it to work now, however > the VNC connection seems to be dropped when connecting to it. It''s a > bit irregular as I saw the image boot once, until the kernel booted > and then the connection got hung. > > Using netstat, I see the VNC connection start listening when I xm > create the client, but also see the port disappear the moment I > connect to it. > > Is there any reason why the VNC server shuts down so easily, and how/ > where could I debug this? > > Thanks, > > </Steven>-- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
On 27 Jun 2007, at 02:15, Mark Williamson wrote:> Hi Steven, > >>> sdl=0 >>> vnc=1 > > Try setting sdl=0 - it''ll start an X11 window displaying the guest''s > framebuffer. If you don''t have physical access to the dom0 you can > connect > to it using ssh -X so that X11 windows are forwarded to your local > machine. > > Hopefully this''ll allow you to select the correct option at the > bootloader... > Let us know how you get on.X isn''t installed on the machine... on purpose. I reckon I should do anyway and rather specify sdl=1, no? The behaviour of vnc disconnecting upon first connection is pretty consistent. I guess I''m paying the price of trying to stick to packaged distributions (ubuntu feisty), rather than compiling everything myself. The road using para-virtualized domains isn''t particularly well-paved either, as it seems to be the idea that Dom0 and DomU should share the same kernel, and the feisty xen-tools package has no debootstrap feisty build target. That, and the foulish idea to run an ISDN-based Asterisk installation on a DomU. ;-/ </Steven> -- Steven Noels http://outerthought.org/ Outerthought Open Source Java & XML stevenn at outerthought.org stevenn at apache.org _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Forgive me if I''m not entirely coherent... it''s 7am and I''ve not slept yet due to insomnia :-)> >>> sdl=0 > >>> vnc=1 > > > > Try setting sdl=0 - it''ll start an X11 window displaying the guest''s > > framebuffer. If you don''t have physical access to the dom0 you can > > connect > > to it using ssh -X so that X11 windows are forwarded to your local > > machine. > > > Hopefully this''ll allow you to select the correct option at the > > bootloader... > > Let us know how you get on. > > X isn''t installed on the machine... on purpose. I reckon I should do > anyway and rather specify sdl=1, no?You could try it... if you''ve got the necessary Xlibs / sdl installed you don''t actually need to have a full X11 install.> The behaviour of vnc disconnecting upon first connection is pretty > consistent. I guess I''m paying the price of trying to stick to > packaged distributions (ubuntu feisty), rather than compiling > everything myself.Maybe the domain is crashing and that''s making the display disappear?> The road using para-virtualized domains isn''t > particularly well-paved either, as it seems to be the idea that Dom0 > and DomU should share the same kernel, and the feisty xen-tools > package has no debootstrap feisty build target.They don''t need to share the same kernel, you can run whatever kernel you want in the PV domain and either specify its location on dom0''s filesystem in the config file, or leave that entry blank and allow the guest to specify it using a grub.conf. It''s also reasonably straightforward to either plug in a ready made domU image, or deboostrap one manually, so don''t necessarily let the tools put you off. Cheers, Mark -- Dave: Just a question. What use is a unicyle with no seat? And no pedals! Mark: To answer a question with a question: What use is a skateboard? Dave: Skateboards have wheels. Mark: My wheel has a wheel! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users