From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Mathias Diehl" Subject: next release? - two reboot issues... Date: Mon, 9 Jan 2006 15:03:30 +0000 Message-ID: <2EADA7A43429786F@evoconcept.de> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hi Devels, as I'm still playing around with XEN I kindly ask for your help and advi= se. As mentioned below I face two problems that were not answered on the use= r list - I found similar issues on the devel list but understood they ar= e solved. According to my experience they aren't. I would like to switch my xen installation to production quite soon but = I'm not in a hurry. Please advise if it's worth to wait for a new XEN re= lease, take 3.0.0 or just pick the latest tarball? As I would like to use own bridge names 3.0.0 is not the best choice?=20 Any advise? even though I found my two problems mentioned on this list - there no su= lution that I can google... :-( =20 I have two diffrent reboot problems. =20 The first one is a debian sarge domU with 1024 M allocated RAM - the ent= iere machine has 2048 and dom0 128. When rebooting my domU I find in xen= d-log: =20 =20 http://nopaste.debianforum.de/2061 (for better readability - to get it a= s plain text click: http://nopaste.debianforum.de/get/2061) =20 To create this domU again using xm create works fine. =20 =20 Second, more serious problem is a fedora core3 domU that is not rebootab= le. =20 http://nopaste.debianforum.de/2062 (for better readability - to get it a= s plain text click: http://nopaste.debianforum.de/get/2062) =20 =20 unfortunatly xm create wont work after that and I have to reboot the ent= iere system..... =20 linus:~# xm create /etc/xen/auto/tta.conf Using config file "/etc/xen/auto/tta.conf". Error: Device 2049 (vbd) could not be connected. File /opt/xen/domains/tta/disk.img is loopback-mounted through /dev/loop= 10, which is mounted in a guest domain, and so cannot be mounted now. =20 Any idea what's wrong? =20 cheers, =20 mat