In a previous thread I had posted problem of guest creation for a pv-ops
Dom0 kernel.
This week I recompiled every thing from scratch.
Following is my config file for 2.6.32.27
http://pastebin.com/AvSVgVQE
and the error this time I am getting trying to do with virt-install is
ERROR unable to connect to ''localhost:8000'': Connection
refused
Traceback (most recent call last):
File "/usr/bin/virt-install", line 943, in <module>
main()
File "/usr/bin/virt-install", line 715, in main
conn = cli.getConnection(options.connect)
File "/usr/lib/pymodules/python2.6/virtinst/cli.py", line 162, in
getConnection
conn = open_connection(connect)
File "/usr/lib/pymodules/python2.6/virtinst/cli.py", line 177, in
open_connection
open_flags)
File "/usr/lib/python2.6/dist-packages/libvirt.py", line 111, in
openAuth
if ret is None:raise libvirtError(''virConnectOpenAuth()
failed'')
libvirtError: unable to connect to ''localhost:8000'':
Connection refused
I am able to see xm info output but some how the guest creation is failing.
--
http://mightydreams.blogspot.com
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
> On Sat, 5 Mar 2011 22:54:31 +0530 <mightydreams@gmail.com> wrote: > > In a previous thread I had posted problem of guest creation for a > pv-ops Dom0 kernel. > This week I recompiled every thing from scratch. > Following is my config file for 2.6.32.27 > http://pastebin.com/AvSVgVQE > and the error this time I am getting trying to do with virt-install is > > > ERROR unable to connect to ''localhost:8000'': Connection refused > Traceback (most recent call last): > File "/usr/bin/virt-install", line 943, in > main() > File "/usr/bin/virt-install", line 715, in main > conn = cli.getConnection(options.connect) > File "/usr/lib/pymodules/python2.6/virtinst/cli.py", line 162, in > getConnection > conn = open_connection(connect) > File "/usr/lib/pymodules/python2.6/virtinst/cli.py", line 177, in > open_connection > open_flags) > File "/usr/lib/python2.6/dist-packages/libvirt.py", line 111, in openAuth > if ret is None:raise libvirtError(''virConnectOpenAuth() failed'') > libvirtError: unable to connect to ''localhost:8000'': Connection refused > > > I am able to see xm info output but some how the guest creation is failing.I could be wrong, but this doesn''t appear to be a kernel problem. Especially if xm info is working, so the xen service has started aleardy. Did you ever have a working Xen setup (kernel, hypervisor, and tools) that was able to create guests? If so what (if any) changes have you made to your Xen tools (e.g: xm or xl)? -M _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tapas Mishra
2011-Mar-06 06:21 UTC
Re: [Xen-users] guest creation problem on pv dom0 kernel
On Sun, Mar 6, 2011 at 12:00 AM, Mike Viau <viaum@sheridanc.on.ca> wrote:> > > On Sat, 5 Mar 2011 22:54:31 +0530 <mightydreams@gmail.com> wrote: > > > > In a previous thread I had posted problem of guest creation for a > > pv-ops Dom0 kernel. > > This week I recompiled every thing from scratch. > > Following is my config file for 2.6.32.27 > > http://pastebin.com/AvSVgVQE > > and the error this time I am getting trying to do with virt-install is > > > > > > ERROR unable to connect to ''localhost:8000'': Connection refused > > Traceback (most recent call last): > > File "/usr/bin/virt-install", line 943, in > > main() > > File "/usr/bin/virt-install", line 715, in main > > conn = cli.getConnection(options.connect) > > File "/usr/lib/pymodules/python2.6/virtinst/cli.py", line 162, in > > getConnection > > conn = open_connection(connect) > > File "/usr/lib/pymodules/python2.6/virtinst/cli.py", line 177, in > > open_connection > > open_flags) > > File "/usr/lib/python2.6/dist-packages/libvirt.py", line 111, in openAuth > > if ret is None:raise libvirtError(''virConnectOpenAuth() failed'') > > libvirtError: unable to connect to ''localhost:8000'': Connection refused > > > > > > I am able to see xm info output but some how the guest creation is > failing. > > > I could be wrong, but this doesn''t appear to be a kernel problem. > Especially if xm info is working, so the xen service has started aleardy. > > Did you ever have a working Xen setup (kernel, hypervisor, and tools) that > was able to create guests? > > If so what (if any) changes have you made to your Xen tools (e.g: xm or > xl)? > > -M > > NoI did not made any changes to any tools xm or any other things.I compiled a kernel from scratch and xen-4.0 and the rebooted my machine with an expectation of creating guests and that is where I got above problems.In any case I was not able to create guests. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Could you try to create and start a vm with plain xm tools, without the help of libvirt based solutions, maybe your libvirt version doesn''t know how to use the xen 4.0 utils or the pvops kernel?> > On Sun, Mar 6, 2011 at 12:00 AM, Mike Viau <viaum@sheridanc.on.ca > <mailto:viaum@sheridanc.on.ca>> wrote: > > > > On Sat, 5 Mar 2011 22:54:31 +0530 <mightydreams@gmail.com > <mailto:mightydreams@gmail.com>> wrote: > > > > In a previous thread I had posted problem of guest creation for a > > pv-ops Dom0 kernel. > > This week I recompiled every thing from scratch. > > Following is my config file for 2.6.32.27 > > http://pastebin.com/AvSVgVQE > > and the error this time I am getting trying to do with > virt-install is > > > > > > ERROR unable to connect to ''localhost:8000'': Connection refused > > Traceback (most recent call last): > > File "/usr/bin/virt-install", line 943, in > > main() > > File "/usr/bin/virt-install", line 715, in main > > conn = cli.getConnection(options.connect) > > File "/usr/lib/pymodules/python2.6/virtinst/cli.py", line 162, in > > getConnection > > conn = open_connection(connect) > > File "/usr/lib/pymodules/python2.6/virtinst/cli.py", line 177, in > > open_connection > > open_flags) > > File "/usr/lib/python2.6/dist-packages/libvirt.py", line 111, in > openAuth > > if ret is None:raise libvirtError(''virConnectOpenAuth() failed'') > > libvirtError: unable to connect to ''localhost:8000'': Connection > refused > > > > > > I am able to see xm info output but some how the guest creation > is failing. > > > I could be wrong, but this doesn''t appear to be a kernel problem. > Especially if xm info is working, so the xen service has started > aleardy. > > Did you ever have a working Xen setup (kernel, hypervisor, and > tools) that was able to create guests? > > If so what (if any) changes have you made to your Xen tools (e.g: > xm or xl)? > > -M > > No > I did not made any changes to any tools xm or any other things.I > compiled a kernel from scratch and xen-4.0 and the rebooted my machine > with an expectation of creating guests and that is where I got above > problems.In any case I was not able to create guests. > > > _______________________________________________ > 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
Fajar A. Nugraha
2011-Mar-06 10:23 UTC
Re: [Xen-users] guest creation problem on pv dom0 kernel
On Sun, Mar 6, 2011 at 3:03 PM, Gémes Géza <geza@kzsdabas.hu> wrote:> Could you try to create and start a vm with plain xm tools, without the help > of libvirt based solutions, maybe your libvirt version doesn''t know how to > use the xen 4.0 utils or the pvops kernel?That''s a VERY good suggestion. Instead of trying everything all at once and not knowing which ones went wrong, it''d be better to take it one step at a time. If you simply want something that "just works", then better stick with tested integrated solutions (like RHEL/Centos5, or XCP). But if you want to start from scratch, start with: - having a dom0 boot - look at example config files from /etc/xen/xmexample* - create a HVM guest using "xm create" and the example config file, if your system has VT/AMD-V. It''s simpler, and it allows you to use Live CD ISO (like systemrescued) - create a PV guest from scratch by creating a manual config file, like http://wiki.centos.org/HowTos/Xen/InstallingCentOSDomU . Don''t use a kickstart file yet though, start using the interactive installer Once you master the basics, then move on to tools like virt-manager/virt-install. Those tools might require a specific version combination, which might or might not work in your current environment. That will save you (and other people on this list) lots of problems and confusions.> > On Sun, Mar 6, 2011 at 12:00 AM, Mike Viau <viaum@sheridanc.on.ca> wrote: >> >> > On Sat, 5 Mar 2011 22:54:31 +0530 <mightydreams@gmail.com> wrote: >> > >> > In a previous thread I had posted problem of guest creation for a >> > pv-ops Dom0 kernel. >> > This week I recompiled every thing from scratch. >> > Following is my config file for 2.6.32.27 >> > http://pastebin.com/AvSVgVQE >> > and the error this time I am getting trying to do with virt-install is >> > >> > >> > ERROR unable to connect to ''localhost:8000'': Connection refusedFWIW, I think the error is related to xend-http-server and xend-port on /etc/xen/xend-config.sxp. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tapas Mishra
2011-Mar-06 10:36 UTC
Re: [Xen-users] guest creation problem on pv dom0 kernel
On Sun, Mar 6, 2011 at 3:53 PM, Fajar A. Nugraha <list@fajar.net> wrote:> On Sun, Mar 6, 2011 at 3:03 PM, Gémes Géza <geza@kzsdabas.hu> wrote: > > Could you try to create and start a vm with plain xm tools, without the > help > > of libvirt based solutions, maybe your libvirt version doesn''t know how > to > > use the xen 4.0 utils or the pvops kernel? > > That''s a VERY good suggestion. > > ok > >> > and the error this time I am getting trying to do with virt-install is > >> > > >> > > >> > ERROR unable to connect to ''localhost:8000'': Connection refused > > FWIW, I think the error is related to xend-http-server and xend-port > on /etc/xen/xend-config.sxp. >Ok but I never enabled it to work. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2011-Mar-06 12:15 UTC
Re: [Xen-users] guest creation problem on pv dom0 kernel
On Sun, Mar 6, 2011 at 5:36 PM, Tapas Mishra <mightydreams@gmail.com> wrote:>> >> > and the error this time I am getting trying to do with virt-install >> >> > is >> >> > >> >> > >> >> > ERROR unable to connect to ''localhost:8000'': Connection refused >> >> FWIW, I think the error is related to xend-http-server and xend-port >> on /etc/xen/xend-config.sxp. > > Ok but I never enabled it to work.Many things can make it not work. It could be the defaults have changed, so it''s disabled by default. It could be some extreme firewall settings blocking everything even on loopback. It could be that that the http server simply failed to start. In any case, when you''re already experienced with the basics, you''d know where to start looking. Like how xen-related logs should be on /var/log/xen/. Or how a simple "netstat -antp" can give you an overview on which TCP ports are open and which programs are using them. Or that you can safely restart xend to pickup new settings on xend-config.sxp, but you should never kill/restart xenstored. Those kinds of knowledge can go a long way to help you figure out what''s wrong and how to fix it. ... or at the very least, it will help you find out the quirks of the combination of OS-xen-libvirt version you''re using, and you''ll be able to help others experiencing similar problem in the future. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tapas Mishra
2011-Mar-08 13:57 UTC
Re: [Xen-users] guest creation problem on pv dom0 kernel
On Sun, Mar 6, 2011 at 5:45 PM, Fajar A. Nugraha <list@fajar.net> wrote:> On Sun, Mar 6, 2011 at 5:36 PM, Tapas Mishra <mightydreams@gmail.com> > wrote: > >> >> > and the error this time I am getting trying to do with virt-install > >> >> > is > >> >> > > >> >> > > >> >> > ERROR unable to connect to ''localhost:8000'': Connection refused > >> > >> FWIW, I think the error is related to xend-http-server and xend-port > >> on /etc/xen/xend-config.sxp. > > > > Ok but I never enabled it to work. > > Many things can make it not work. > >I just wanted to update in this thread (as others have suggested to use xm create type command options which I will be testing in short while) it appears that the when the options of creating guest OS from local ISO and PXE are disabled in virt-manager when you create a guest on a non VT machine and only thing available to you is installing via an http URL based where you expect to mount the install ISO and then doing an http install.This trick works for CentOS/RedHat systems but the same does not work with Debian/Ubuntu based systems and it appears I might need to create a local mirror as explained here http://www.howtoforge.com/local_debian_ubuntu_mirror http://www.debian.org/releases/stable/amd64/ch06s03.html.en#di-setup because I do see in apache logs the requests for installation reaching here is the apache log on host machine 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/ HTTP/1.1" 200 169 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/.treeinfo HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/Fedora HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/Server HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/Client HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/RedHat HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/CentOS HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/SL HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/directory.yast HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/current/images/MANIFEST HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/images/daily/MANIFEST HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/boot/platform/i86xpv/kernel/unix HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/platform/i86xpv/kernel/unix HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/STARTUP/XNLOADER.SYS HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/images/xen/vmlinuz HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/images/boot.iso HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/boot/boot.iso HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/current/images/netboot/mini.iso HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:27 +0530] "HEAD /sk/install/images/boot.iso HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:35 +0530] "HEAD /sk/ HTTP/1.1" 200 169 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:35 +0530] "HEAD /sk/.treeinfo HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:35 +0530] "HEAD /sk/Fedora HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:35 +0530] "HEAD /sk/Server HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:35 +0530] "HEAD /sk/Client HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:35 +0530] "HEAD /sk/RedHat HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:35 +0530] "HEAD /sk/CentOS HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:35 +0530] "HEAD /sk/SL HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:35 +0530] "HEAD /sk/directory.yast HTTP/1.1" 404 182 "-" "Python-urllib/2.6" 127.0.0.1 - - [08/Mar/2011:00:26:35 +0530] "HEAD /sk/current/images/MANIFEST HTTP/1.1" 404 182 "-" "Python-urllib/2.6" I will update the result when I finish creating the local mirror (or with even xm tools) I am trying on a non VT machine. -- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tapas Mishra
2011-Mar-09 13:02 UTC
Re: [Xen-users] guest creation problem on pv dom0 kernel
Continuing in the same thread where I had reported a problem in create PV guest on non VT machine http://lists.xensource.com/archives/html/xen-users/2011-03/msg00119.html after discussing it here and failed attempt to create PV guest on a non VT machine. I confirmed on virt-manager list https://www.redhat.com/archives/virt-tools-list/2011-March/msg00032.html excerpts from above link "If your machine does not have VT support, you will only be able to install a PV guest, and the only way to install a PV guest on linux is using a direct kernel/initrd boot (basically a URL install)." and as Cole Robinson suggests on above link to mount -o loop back for ISO trick does not work I have tested for Ubuntu 10.04.The virt-manager expects a url similar to Debian/Ubuntu mirror format. On Sun, Mar 6, 2011 at 1:33 PM, Gémes Géza <geza@kzsdabas.hu> wrote:> Could you try to create and start a vm with plain xm tools, without the help > of libvirt based solutions, maybe your libvirt version doesn''t know how to > use the xen 4.0 utils or the pvops kernel?I am trying out this option now.I want to know in the xen config file ========below is just a sample I am not using it ============name ="vm01" kernel ="/boot/vmlinuz-2.6.11.12-xenU" root ="/dev/hda1" memory =128 disk = [''file:/vserver/images/vm01.img,hda1,w'',''file:/vserver/images/vm01-swap.img,hda2,w''] nics=1 dhcp ="off" ip="192.168.0.101" netmask="255.255.255.0" gateway="192.168.0.1" hostname="vm01.example.com" extra="3" =========================================================== What should be the value of parameter kernel.As I am trying to create a PV guest on a non VT 64 bit machine. The guest is 32 bit PV.Do I need to compile a PV DomU kernel or what exactly do I give in place of kernel? I tried using a command xen-create-image also and that does not exists on my system. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2011-Mar-09 13:50 UTC
Re: [Xen-users] guest creation problem on pv dom0 kernel
On Wed, Mar 9, 2011 at 8:02 PM, Tapas Mishra <mightydreams@gmail.com> wrote:> I am trying out this option now.I want to know in the xen config file > > ========below is just a sample I am not using it ============> name ="vm01" > kernel ="/boot/vmlinuz-2.6.11.12-xenU" > root ="/dev/hda1" > memory =128 > disk = [''file:/vserver/images/vm01.img,hda1,w'',''file:/vserver/images/vm01-swap.img,hda2,w''] > nics=1 > dhcp ="off" > ip="192.168.0.101" > netmask="255.255.255.0" > gateway="192.168.0.1" > hostname="vm01.example.com" > extra="3" > ===========================================================So you''re trying a manual method, without virt-install/virt-manager? Good :D> What should be the value of parameter kernel.As I am trying to create > a PV guest on a non VT 64 bit machine. > The guest is 32 bit PV.Do I need to compile a PV DomU kernel or what > exactly do I give in place of kernel?See https://help.ubuntu.com/community/Installation/Netboot http://archive.ubuntu.com/ubuntu/dists/maverick/main/installer-i386/current/images/netboot/xen/ Or download initrd.gz and vmlinuz from there, and use a config similar to this #==============================================memory = "1000" vif = [ ''mac=00:16:3E:BD:96:42, bridge=eth0, vifname=u-e0'' ] disk = [ ''phy:/dev/VG/ubuntu-test,xvda,w'', ] vcpus=1 kernel = "/vm/install/ubuntu/vmlinuz" ramdisk = "/vm/install/ubuntu/initrd.gz" vfb=[ "type=vnc,vncunused=1,vnclisten=0.0.0.0" ] #============================================== Note the "bridge" parameter. It might be eth0, xenbr0, or some other bridge that you create manually (try runnning "brctl show"). After installation completes, delete both "kernel" and "ramdisk" line, add bootloader = "/usr/bin/pygrub" -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tapas Mishra
2011-Mar-09 19:55 UTC
Re: [Xen-users] guest creation problem on pv dom0 kernel
On Wed, Mar 9, 2011 at 7:20 PM, Fajar A. Nugraha <list@fajar.net> wrote:> On Wed, Mar 9, 2011 at 8:02 PM, Tapas Mishra <mightydreams@gmail.com> wrote: >> I am trying out this option now.I want to know in the xen config file >> >> ========below is just a sample I am not using it ============>> name ="vm01" >> kernel ="/boot/vmlinuz-2.6.11.12-xenU" >> root ="/dev/hda1" >> memory =128 >> disk = [''file:/vserver/images/vm01.img,hda1,w'',''file:/vserver/images/vm01-swap.img,hda2,w''] >> nics=1 >> dhcp ="off" >> ip="192.168.0.101" >> netmask="255.255.255.0" >> gateway="192.168.0.1" >> hostname="vm01.example.com" >> extra="3" >> ===========================================================> > So you''re trying a manual method, without virt-install/virt-manager? Good :D > >> What should be the value of parameter kernel.As I am trying to create >> a PV guest on a non VT 64 bit machine. >> The guest is 32 bit PV.Do I need to compile a PV DomU kernel or what >> exactly do I give in place of kernel? > > See > https://help.ubuntu.com/community/Installation/Netboot > http://archive.ubuntu.com/ubuntu/dists/maverick/main/installer-i386/current/images/netboot/xen/ > > Or download initrd.gz and vmlinuz from there, and use a config similar to this > #==============================================> memory = "1000" > > vif = [ ''mac=00:16:3E:BD:96:42, bridge=eth0, vifname=u-e0'' ] > disk = [ > ''phy:/dev/VG/ubuntu-test,xvda,w'', > ] > > vcpus=1 > > kernel = "/vm/install/ubuntu/vmlinuz" > ramdisk = "/vm/install/ubuntu/initrd.gz" > > vfb=[ "type=vnc,vncunused=1,vnclisten=0.0.0.0" ] > #==============================================> > Note the "bridge" parameter. It might be eth0, xenbr0, or some other > bridge that you create manually (try runnning "brctl show").Ok do you mean to say before I start installation I should have a bridge configured?>After > installation completes, delete both "kernel" and "ramdisk" line, addOk> bootloader = "/usr/bin/pygrub"Ok -- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tapas Mishra
2011-Mar-09 20:26 UTC
Re: [Xen-users] guest creation problem on pv dom0 kernel
On Wed, Mar 9, 2011 at 7:20 PM, Fajar A. Nugraha <list@fajar.net> wrote:> > >> What should be the value of parameter kernel.As I am trying to create >> a PV guest on a non VT 64 bit machine. >> The guest is 32 bit PV.Do I need to compile a PV DomU kernel or what >> exactly do I give in place of kernel? > > See > https://help.ubuntu.com/community/Installation/Netboot > http://archive.ubuntu.com/ubuntu/dists/maverick/main/installer-i386/current/images/netboot/xen/ > > Or download initrd.gz and vmlinuz from there, and use a config similar to thisOk I downloaded the vmlinuz and initrd from http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-i386/current/images/netboot/xen/> #==============================================> memory = "1000" > > vif = [ ''mac=00:16:3E:BD:96:42, bridge=eth0, vifname=u-e0'' ] > disk = [ > ''phy:/dev/VG/ubuntu-test,xvda,w'', > ] > > vcpus=1 > > kernel = "/vm/install/ubuntu/vmlinuz" > ramdisk = "/vm/install/ubuntu/initrd.gz" > > vfb=[ "type=vnc,vncunused=1,vnclisten=0.0.0.0" ] > #==============================================> > Note the "bridge" parameter. It might be eth0, xenbr0, or some other > bridge that you create manually (try runnning "brctl show").I am not clear here if I need to create a bridge before I begin the install. By the time of writing this message I had not configured any bridge. dd if=/dev/zero of=/mnt/1/vm1.img bs=4096k count=1024 dd if=/dev/zero of=/mnt/1/vm1-swap.img bs=1024k count=512 I want to also mention an entry of my /etc/fstab file UUID=a20a4466-24bc-42c5-93e2-2193e99847b5 /mnt/1 ext2 defaults 0 0 the /mnt/1 is basically always mounted so I mentioned here is my /etc/xen/ubuntu.vm ==============================================memory = "512" vif = [ ''mac=00:16:3E:BD:96:42, bridge=xenbr0, vifname=u-e0'' ] disk = [ ''file:/mnt/1/vm1.img,xvda1,w'',''file:/mnt/1/vm1-swap.img,xvda2,w'' ] vcpus=1 kernel = "/home/tapas/Documents/ISO\''s/forvm/vmlinuz" ramdisk = "/home/tapas/Documents/ISO\''s/forvm/initrd.gz" vfb=[ "type=vnc,vncunused=1,vnclisten=0.0.0.0" ] dhcp ="off" ip="192.168.1.7" netmask="255.255.255.0" gateway="192.168.1.1" hostname="vm01.ubuntu" ==============================================Now when I do xm create -c /etc/xen/ubuntu.vm Two things 1) Error: Device 0 (vif) could not be connected. Hotplug scripts not working. 2) I do not see any thing happening on my screen i.e. in bash if it is possible to see some out put as progress then I will be able to understand some thing how can that be possible?> After > installation completes, delete both "kernel" and "ramdisk" line, add > > bootloader = "/usr/bin/pygrub" > > -- > Fajar >-- http://mightydreams.blogspot.com _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2011-Mar-09 22:26 UTC
Re: [Xen-users] guest creation problem on pv dom0 kernel
On Thu, Mar 10, 2011 at 3:26 AM, Tapas Mishra <mightydreams@gmail.com> wrote:> here is my /etc/xen/ubuntu.vm > > > ==============================================> memory = "512" > vif = [ ''mac=00:16:3E:BD:96:42, bridge=xenbr0, vifname=u-e0'' ]Back to the basics. Xen has two basic networking methods, the default being bridge. You may have a bridge called "eth0" or "eth1" (depending on what interface you currently use) created by Xen during its startup phase (the original eth0 and eth1 is renamed to peth0 and peth1). If you have virt-manager installed then you should already have a bridge called virbr0. If you have no idea what I''m talking about just remove the "bridge=xenbr0," section.> dhcp ="off" > ip="192.168.1.7" > netmask="255.255.255.0" > gateway="192.168.1.1" > hostname="vm01.ubuntu"Those entries will be useless by default in bridge setup. DomU will be on the same network as dom0, and you need to setup networking from inside domU (e.g. setup DHCP or static IP)> > ==============================================> Now when I do > xm create -c /etc/xen/ubuntu.vm > Two things > > 1) Error: Device 0 (vif) could not be connected. Hotplug scripts not working.Cause you''re not listening. I specifically said " Note the "bridge" parameter. It might be eth0, xenbr0, or some other bridge that you create manually (try runnning "brctl show"). " Did you run "brctl show"? What is your bridge name? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tapas Mishra
2011-Mar-10 05:36 UTC
Re: [Xen-users] guest creation problem on pv dom0 kernel
On Thu, Mar 10, 2011 at 3:56 AM, Fajar A. Nugraha <list@fajar.net> wrote:> On Thu, Mar 10, 2011 at 3:26 AM, Tapas Mishra <mightydreams@gmail.com> wrote: >> here is my /etc/xen/ubuntu.vm >> >> >> ==============================================>> memory = "512" >> vif = [ ''mac=00:16:3E:BD:96:42, bridge=xenbr0, vifname=u-e0'' ] > > Back to the basics. Xen has two basic networking methods, the default > being bridge. You may have a bridge called "eth0" or "eth1" (depending > on what interface you currently use) created by Xen during its startup > phase (the original eth0 and eth1 is renamed to peth0 and peth1).Actually I have read it in Xen books and even on Xen networking wiki the same thing that you mentioned. That original eth0 and eth1 are renamed to peth0 and peth1 but practically I never found this happening never. I had tried this in Xen 3.* a long time back on Ubuntu 9.04 and now I am trying on 10.04 but any time this never happened.>If > you have virt-manager installed then you should already have a bridge > called virbr0.Ok I do have a bridge name virbr0.> If you have no idea what I''m talking about just remove the > "bridge=xenbr0," section.After reading your message here I did that so now my line looks as vif = [ ''mac=00:16:3E:BD:96:42,vifname=u-e0'' ] if this is what you meant.> >> dhcp ="off" >> ip="192.168.1.7" >> netmask="255.255.255.0" >> gateway="192.168.1.1" >> hostname="vm01.ubuntu" > > Those entries will be useless by default in bridge setup. DomU will be > on the same network as dom0, and you need to setup networking from > inside domU (e.g. setup DHCP or static IP)Ok this makes it clear.>> ==============================================>> Now when I do >> xm create -c /etc/xen/ubuntu.vm >> Two things >> >> 1) Error: Device 0 (vif) could not be connected. Hotplug scripts not working. > > Cause you''re not listening. I specifically said > > " > Note the "bridge" parameter. It might be eth0, xenbr0, or some other > bridge that you create manually (try runnning "brctl show").Since my wifi does not work when I boot with xen.gz and pv-ops dom0 combination so I switch to a the kernel which was installed along with Ubuntu installation for all work purposes and brctl show bridge name bridge id STP enabled interfaces pan0 8000.000000000000 no virbr0 8000.000000000000 yes but I for the sake of using Xen I reboot to pv-ops Dom0 kernel in combination with xen.gz (which is where I am trying every thing) and here brctl show bridge name bridge id STP enabled interfaces pan0 8000.000000000000 no tmpbridge 8000.000000000000 no virbr0 8000.000000000000 yes but this time I had removed the bridge=xenbr0 parameter and I get the same error Error: Device 0 (vif) could not be connected. Hotplug scripts not working. when I do a xm create -c /etc/xen/ubuntu.vm -- _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2011-Mar-10 05:54 UTC
Re: [Xen-users] guest creation problem on pv dom0 kernel
On Thu, Mar 10, 2011 at 12:36 PM, Tapas Mishra <mightydreams@gmail.com> wrote:> but this time I had removed the bridge=xenbr0 parameter and I get the same error > > Error: Device 0 (vif) could not be connected. Hotplug scripts not working. > > when I do a xm create -c /etc/xen/ubuntu.vmAs usual, what does /var/log/xen/xend.log say? Most likely it tries to use the default bridge (eth0, which does not exists on your system) you just need to add "bridge=virbr0" in the vif section. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Tapas Mishra
2011-Mar-10 08:07 UTC
Re: [Xen-users] guest creation problem on pv dom0 kernel
On Thu, Mar 10, 2011 at 11:24 AM, Fajar A. Nugraha <list@fajar.net> wrote:> On Thu, Mar 10, 2011 at 12:36 PM, Tapas Mishra <mightydreams@gmail.com> wrote: >> but this time I had removed the bridge=xenbr0 parameter and I get the same error >> >> Error: Device 0 (vif) could not be connected. Hotplug scripts not working. >> >> when I do a xm create -c /etc/xen/ubuntu.vm > > As usual, what does /var/log/xen/xend.log say? > Most likely it tries to use the default bridge (eth0, which does not > exists on your system) you just need to add "bridge=virbr0" in the vif > section. >Ok here is domain-builder-ng.log http://pastebin.com/Yd2QdmvB qemu-dm-ubuntu.vm.log http://pastebin.com/AD78E1C0 xend-debug.log http://pastebin.com/2DkSdN0i xend.log http://pastebin.com/YcZcM8AH xen-hotplug.log is empty I had also noted the strace output when I did xm create -c /etc/xen/ubuntu.vm here it is guest_prob.txt http://pastebin.com/9CFRD0Ku all the above logs are without the bridge=virbr0 in the file and now when I add bridge=virbr0 then I have following logs domain-builder-ng.log http://pastebin.com/8W45hjCV xend-debug.log http://pastebin.com/634FaJQP xend.log http://pastebin.com/y7wWs19K qemu-dm-ubuntu.vm.log http://pastebin.com/cRNqUGRf xen-hotplug.log is empty as it was empty when the line bridge=virbr0 was not there. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2011-Mar-10 09:21 UTC
Re: [Xen-users] guest creation problem on pv dom0 kernel
On Thu, Mar 10, 2011 at 3:07 PM, Tapas Mishra <mightydreams@gmail.com> wrote:> and now when I add bridge=virbr0 > > then I have following logs > > domain-builder-ng.log > http://pastebin.com/8W45hjCV > > > xend-debug.log > http://pastebin.com/634FaJQP > > xend.log > http://pastebin.com/y7wWs19K > > qemu-dm-ubuntu.vm.log > http://pastebin.com/cRNqUGRf > > xen-hotplug.log > is empty as it was empty when the line > bridge=virbr0 was not there. >Why do you use xvda1? I gave you an example PV domU config, which has "xvda" on it (NOT xvda1). There''s also xm-debian.cfg on http://archive.ubuntu.com/ubuntu/dists/maverick/main/installer-i386/current/images/netboot/xen/ (which also uses xvda, not xvda1). Yet you choose (from the log you provided) [''device'', [''vbd'', [''uname'', ''file:/mnt/1/vm1.img''], [''dev'', ''xvda1''], [''mode'', ''w'']]], [''device'', [''vbd'', [''uname'', ''file:/mnt/1/vm1-swap.img''], [''dev'', ''xvda2''], [''mode'', ''w'']]] I''ve said this many times, it''s fine if you want to introduce your own changes, but only if you know what they''re for. Don''t go complaining to others if your change breaks things. There''s a difference between mapping as xvda and xvda1, and if you want to use normal OS installer you need to map it as a disk (xvda) and not a partition (xvda2). To be honest though, while that change will prevent the installer from working, the domU should still start. I don''t know where you went wrong. Probably cause you use a path with single quote ('') in it ("/home/bond/Documents/ISO''s/forvm/vmlinuz"). Your xend.log also seems weird. It should show something like [2011-03-10 14:58:12 7832] DEBUG (XendDomainInfo:1891) XendDomainInfo.handleShutdownWatch [2011-03-10 14:58:12 7832] DEBUG (DevController:139) Waiting for devices vif2. [2011-03-10 14:58:12 7832] DEBUG (DevController:139) Waiting for devices vif. [2011-03-10 14:58:12 7832] DEBUG (DevController:144) Waiting for 0. [2011-03-10 14:58:12 7832] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vif/6/0/hotplug-status. [2011-03-10 14:58:12 7832] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vif/6/0/hotplug-status. [2011-03-10 14:58:12 7832] DEBUG (DevController:642) hotplugStatusCallback 1. [2011-03-10 14:58:12 7832] DEBUG (DevController:139) Waiting for devices vscsi. [2011-03-10 14:58:12 7832] DEBUG (DevController:139) Waiting for devices vbd. [2011-03-10 14:58:12 7832] DEBUG (DevController:144) Waiting for 51712. [2011-03-10 14:58:12 7832] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vbd/6/51712/hotplug-status. [2011-03-10 14:58:13 7832] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vbd/6/51712/hotplug-status. [2011-03-10 14:58:13 7832] DEBUG (DevController:642) hotplugStatusCallback 1. [2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for devices ioports. [2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for devices irq. [2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for devices vkbd. [2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for devices vfb. [2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for devices console. [2011-03-10 14:58:13 7832] DEBUG (DevController:144) Waiting for 0. [2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for devices pci. [2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for devices tap2. [2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for devices tap. [2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for devices vusb. [2011-03-10 14:58:13 7832] DEBUG (DevController:139) Waiting for devices vtpm. [2011-03-10 14:58:13 7832] INFO (XendDomain:1206) Domain ubuntu (6) unpaused. While yours simply show [2011-03-10 13:30:04 1705] DEBUG (DevController:628) hotplugStatusCallback /local/domain/0/backend/vif/1/0/hotplug-status. [2011-03-10 13:31:44 1705] DEBUG (XendDomainInfo:3053) XendDomainInfo.destroy: domid=1 Perhaps udevd is dead? Were you able to create any other domUs (whether using virt manager or manually)? At this point I''d suggest: - reboot the dom0 - use "normal" path (without single or double quote it it''s name) for kernel and initrd - make sure udevd is not dead - make sure you the disk image and bridge that you''re going to use exist - map domUs device as disk (xvda) - try creating the domU If that doesn''t work, I don''t know what went wrong in your setup. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users