I have 4 virtual servers, all 4 run fine on the xen-unstable I downloaded with a nov 16 date I download the latest 3.0 testing or unstable and I can only run one at a time, I start one it runs, I go to start any other one ( in any random order even ) and I can''t, get errors about my lvm already in use by another guest. I have 4 seperate lvm ext3 partions and 4 seperate lvm swap partions. I back down to my saved nov 16 version and all 4 domU servers can be started up once again. -- Richard Thomas - CEO Cyberlot Technologies Group Inc. 507.398.4124 - Voice _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> I download the latest 3.0 testing or unstable and I can only > run one at > a time, I start one it runs, I go to start any other one ( in > any random > order even ) and I can''t, get errors about my lvm already in use by > another guest. > > I have 4 seperate lvm ext3 partions and 4 seperate lvm swap partions. > > I back down to my saved nov 16 version and all 4 domU servers can be > started up once again.I suspect you just need to make sure you''ve deleted all traces of your Nov 16 version before installing 3.0. If you build from src use ''make uninstall'', otherwise the following will probably work: mv /etc/xen /etc/xen.old rm -rf /usr/lib/python/xen /usr/lib/python*/site-packages/xen If it still doesn''t work, please give details of your dom0 root filesystem. Ian _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Are there any major changes I need to make to my domain config files? Richard Thomas - CEO Cyberlot Technologies Group Inc. 507.398.4124 - Voice Ian Pratt wrote:>>I download the latest 3.0 testing or unstable and I can only >>run one at >>a time, I start one it runs, I go to start any other one ( in >>any random >>order even ) and I can''t, get errors about my lvm already in use by >>another guest. >> >>I have 4 seperate lvm ext3 partions and 4 seperate lvm swap partions. >> >>I back down to my saved nov 16 version and all 4 domU servers can be >>started up once again. > > > I suspect you just need to make sure you''ve deleted all traces of your > Nov 16 version before installing 3.0. If you build from src use ''make > uninstall'', otherwise the following will probably work: > > mv /etc/xen /etc/xen.old > rm -rf /usr/lib/python/xen /usr/lib/python*/site-packages/xen > > If it still doesn''t work, please give details of your dom0 root > filesystem. > > Ian > > _______________________________________________ > 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
Reinstalled as you suggested, getting the same problem. [root@localhost xen]# xm create -c Alpha Using config file "Alpha". Error: Device 2049 (vbd) could not be connected. Device /dev/phy:dev/mapper/VolGroup00-Virtual3 is mounted in a guest domain, and so cannot be mounted now. Nothing else is started up at all Richard Thomas - CEO Cyberlot Technologies Group Inc. 507.398.4124 - Voice Richard Thomas wrote:> Are there any major changes I need to make to my domain config files? > > > Richard Thomas - CEO > Cyberlot Technologies Group Inc. > 507.398.4124 - Voice > > > Ian Pratt wrote: > >>> I download the latest 3.0 testing or unstable and I can only run one >>> at a time, I start one it runs, I go to start any other one ( in any >>> random order even ) and I can''t, get errors about my lvm already in >>> use by another guest. >>> >>> I have 4 seperate lvm ext3 partions and 4 seperate lvm swap partions. >>> >>> I back down to my saved nov 16 version and all 4 domU servers can be >>> started up once again. >> >> >> >> I suspect you just need to make sure you''ve deleted all traces of your >> Nov 16 version before installing 3.0. If you build from src use ''make >> uninstall'', otherwise the following will probably work: >> >> mv /etc/xen /etc/xen.old >> rm -rf /usr/lib/python/xen /usr/lib/python*/site-packages/xen >> >> If it still doesn''t work, please give details of your dom0 root >> filesystem. >> Ian >> >> _______________________________________________ >> 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 >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I downloaded it from somewhere, centos image.. It runs with the older version of Xen without a problem so the image does work. I have 4 seperate domains all made the same way sometimes its the Virtual partion, other domains fail on the Swap partion Richard Thomas - CEO Cyberlot Technologies Group Inc. 507.398.4124 - Voice Eric S. Johansson wrote:> Richard Thomas wrote: > >> Reinstalled as you suggested, getting the same problem. >> >> >> [root@localhost xen]# xm create -c Alpha >> Using config file "Alpha". >> Error: Device 2049 (vbd) could not be connected. >> Device /dev/phy:dev/mapper/VolGroup00-Virtual3 is mounted in a guest >> domain, >> and so cannot be mounted now. >> >> Nothing else is started up at all >> > > I remember getting that kind of problem if I had an improperly created > domU image. How did you create yours? > > ---eric >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Richard Thomas wrote:> I downloaded it from somewhere, centos image.. It runs with the older > version of Xen without a problem so the image does work.unfortunately, I have found that if it runs with an older version of xen, it will fool you by mostly running on 3.0. I would seriously recommend building a new guest image. It''s not terribly difficult, only time tedious. the steps below work for me on ubuntu but there''s nothing keeping it from being distribution independent. "install" onto a file disk image using qemu create a new partition-less disk image mount the root partition on a loopback device using losetup mount your partition-less disk image also using a loopback device. cp -a from the root partition to the partition-less disk image cp -a domU modules onto the partition-less disk image fixup fstab, host names, ethernet interface definition (there are probably more but I can''t remember right now) unmount everything (very important as my recent experiences shown ;-)) Create your .xm file xm create ... I believe this will give you better results. Or if you prefer, I can also make available an ubuntu very raw disk image (i.e. fresh out of the qemu oven). ---eric _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
The problem though is its not even getting to load the OS, it refuses to even mount the partition saying its already mounted by another guest ( I am using full partitions not a loopback file system ). All 4 domains where created at the same time using the same image and they randomly work or don''t work its not a specific issue. Sometimes the problem is related to allowing access to the seperate swap partitions not the OS partition as well, In that case when its playing that game I have tried redoing the swap partition 100% and it still says its already in use by another guest os Richard Thomas - CEO Cyberlot Technologies Group Inc. 507.398.4124 - Voice Eric S. Johansson wrote:> Richard Thomas wrote: > >> I downloaded it from somewhere, centos image.. It runs with the older >> version of Xen without a problem so the image does work. > > > unfortunately, I have found that if it runs with an older version of > xen, it will fool you by mostly running on 3.0. I would seriously > recommend building a new guest image. It''s not terribly difficult, only > time tedious. the steps below work for me on ubuntu but there''s nothing > keeping it from being distribution independent. > > "install" onto a file disk image using qemu > create a new partition-less disk image > mount the root partition on a loopback device using losetup > mount your partition-less disk image also using a loopback device. > cp -a from the root partition to the partition-less disk image > cp -a domU modules onto the partition-less disk image > fixup fstab, host names, ethernet interface definition (there are > probably more but I can''t remember right now) > > unmount everything (very important as my recent experiences shown ;-)) > > Create your .xm file > > xm create ... > > I believe this will give you better results. Or if you prefer, I can > also make available an ubuntu very raw disk image (i.e. fresh out of the > qemu oven). > > ---eric >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users