From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefano Stabellini Subject: Re: no console when using xl toolstack xen 4.1.2 Date: Tue, 24 Apr 2012 11:37:00 +0100 Message-ID: References: <0DC43CA6-6F9A-4C8D-BB7C-785D646C5474@tacomatelematics.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <0DC43CA6-6F9A-4C8D-BB7C-785D646C5474@tacomatelematics.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Sam Mulvey Cc: "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org On Tue, 24 Apr 2012, Sam Mulvey wrote: > Hello! > > I was asking for help on the Freenode channel, and I was pointed here. > > I have a situation where, using xl, I can create a functional PV domU, with or without pv-grub, but I cannot access the console. Firing up xend and using xm works without trouble. Since xend and company is being deprecated, I would like to transition to using the xl toolstack. > > The system is an Arch Linux system running under VMWare Fusion-- I normally build and test packages this way before I test them on my dev hardware as my dev hardware is a rather loud HP server. I'm compiling Xen in a package, based off of the one in AUR but with some changes (the AUR package doesn't compile pv-grub, for instance). It's Xen 4.1.2, and my linux kernel is the standard Arch Linux kernel version 3.3.2, and it is very near the stock kernel. Clearly, I have done no HVM testing yet. > > > Here's what it looks like when I try xl: > __START__ > [root@xentest2012 noauto]# xl create -c finnix.cfg > Parsing config file finnix.cfg > Unable to attach console > Daemon running with PID 851 > [root@xentest2012 noauto]# xl console finnix > Unable to attach console > [root@xentest2012 noauto]# ls > domutest.cfg finnix.cfg > [root@xentest2012 noauto]# xl create -c domutest.cfg > Parsing config file domutest.cfg > xc: error: panic: xc_dom_bzimageloader.c:556: xc_dom_probe_bzimage_kernel: kernel is not a bzImage: Invalid kernel > Unable to attach console > Daemon running with PID 916 > [root@xentest2012 noauto]# xl console domutest > Unable to attach console > [root@xentest2012 noauto]# > __END__ > > Firing up xend, it works just as you would expect. > > > Here are the configuration files: > > finnix.cfg: > __START__ > kernel = "/var/finnix/linux64" > ramdisk = "/var/finnix/initrd.xz" > name = "finnix" > memory = "128" > disk = [ 'file:/var/finnix/finnix-104.iso,xvda,r', ] > vif = [ 'bridge=outer0', ] > __END__ > > domutest.cfg: > __START__ > kernel = "/usr/lib/xen/boot/pv-grub-x86_64.gz" > extra = "(hd0)/boot/grub/menu.lst" > > memory = 512 > vcpus = 4 > name = "domutest" > disk = [ "phy:/dev/xtG0/domutest-root,xvda1,w", > "phy:/dev/xtG0/domutest-swap,xvda2,w" ] > vif = [ "bridge=outer0" ] > vfb = [ "type=vnc,vnclisten=0.0.0.0,vncdisplay=5,vncpasswd=smeghead" ] > __END__ > > I can see finnix ask for a DHCP address, and I can connect to domutest using the VNC vfb and use it as normal, so I've concluded that the domUs are running. > > > That's what I've got. Any pointers would help. Thanks! I couldn't find any clues in the logs you posted. Maybe the output of xenstore-ls would be useful.