[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] Re: Xen domUs on Ubuntu


  • To: Xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Allen Unrau <allen.unrau@xxxxxxx>
  • Date: Thu, 15 Nov 2007 13:33:43 -0700
  • Delivery-date: Thu, 15 Nov 2007 12:32:25 -0800
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Thread-index: AcgnC+jZzuSYn6YBRR2Z1cwNWcl3lwAtvonA
  • Thread-topic: [Xen-users] Re: Xen domUs on Ubuntu

> >> OK, I have made a little progress on this.  I mounted my VM image
on a 
> >> loopback and chroot'd to it.  I opened /etc/init.d/hwclock.sh 
> >> and /etc/init.d/hwclockfirst.sh and added the following to the top
of each 
> >> file:
> >>
> >>   exit 0
> > 

> I have verified that this fixed my issue as well.
> 
>I can second that. I experienced the same issue - gutsy domU's wouldn't
>boot.
>Disabling the hwclock.sh and hwclockfirst.sh scripts in the domU image
>fixed the problem.

Now some other issues have cropped up. The domu boots up and I can get a
console to it, but networking hasn't started, mount only shows proc and
sysfs mounted (but I can still access files on the root filesystem
-figure that one out) and my log files are empty:
root@wpgsrv5:~# mount
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
root@wpgsrv5:~# ifconfig
root@wpgsrv5:~# ls -al /var/log
total 192
drwxr-xr-x  5 root   root   4096 Nov 14 16:54 .
drwxr-xr-x 13 root   root   4096 Nov 14 16:49 ..
drwxr-xr-x  2 root   root   4096 Nov 14 16:55 apt
-rw-r-----  1 syslog adm       0 Nov 14 16:54 auth.log
-rw-r-----  1 root   adm      31 Nov 14 16:51 boot
-rw-r--r--  1 root   root  38486 Nov 14 16:54 bootstrap.log
-rw-rw-r--  1 root   utmp      0 Nov 14 16:49 btmp
-rw-r-----  1 syslog adm       0 Nov 14 16:54 daemon.log
-rw-r-----  1 syslog adm       0 Nov 14 16:54 debug
-rw-r-----  1 root   adm      31 Nov 14 16:51 dmesg
-rw-r-----  1 root   adm  113627 Nov 14 16:56 dpkg.log
-rw-r--r--  1 root   root   2496 Nov 14 16:56 faillog
drwxr-xr-x  2 root   root   4096 Nov 14 16:51 fsck
-rw-r-----  1 syslog adm       0 Nov 14 16:54 kern.log
-rw-rw-r--  1 root   utmp  30368 Nov 14 16:56 lastlog
-rw-r-----  1 syslog adm       0 Nov 14 16:54 lpr.log
-rw-r-----  1 syslog adm       0 Nov 14 16:54 mail.err
-rw-r-----  1 syslog adm       0 Nov 14 16:54 mail.info
-rw-r-----  1 syslog adm       0 Nov 14 16:54 mail.log
-rw-r-----  1 syslog adm       0 Nov 14 16:54 mail.warn
-rw-r-----  1 syslog adm       0 Nov 14 16:54 messages
drwxr-sr-x  2 news   news   4096 Nov 14 16:54 news
-rw-r-----  1 syslog adm       0 Nov 14 16:54 syslog
-rw-r-----  1 syslog adm       0 Nov 14 16:54 user.log
-rw-rw-r--  1 root   utmp      0 Nov 14 16:49 wtmp
root@wpgsrv5:~# mount
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)

I did find out through Googling that Ubuntu doesn't like moving /var
around, so I checked to see if /var/run and /var/lock exist on the root
partition. They do.

Can anyone tell me what is going on? Thanks.

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.