fukumoto | 3 Mar 05:16 2007
Picon

Newbie question on Xen3 with NetBSD4Beta2

I'm trying to setup Xen 3 with NetBSD 4.0 Beta2 on an Athlon 64 X2 machine.

XEN3_DOM0 seems not configured with options MULTIPROCESSOR, and when I
tried it, it fails to compile.  Is it supposed to be so?

With XEN3_DOM0 kernel and a single XEN3_DOMU domainU, CPU is
noticeably hotter than with non-Xen kernel, according to onboard
temperature sensor.  In fact even when 100% idle state, it is close to
100% load of non-Xen kernel.  Is it normal?

When I configured azalia(4) driver with XEN3_DOM0, it crashed when
booting-up.  Should I send-pr?  Also, configuring fdc(4) with acpi
failed to link.

						FUKUMOTO Atsushi
						fukumoto <at> imasy.or.jp

Manuel Bouyer | 3 Mar 16:15 2007

Re: Newbie question on Xen3 with NetBSD4Beta2

On Sat, Mar 03, 2007 at 01:16:47PM +0900, fukumoto <at> imasy.or.jp wrote:
> I'm trying to setup Xen 3 with NetBSD 4.0 Beta2 on an Athlon 64 X2 machine.
> 
> XEN3_DOM0 seems not configured with options MULTIPROCESSOR, and when I
> tried it, it fails to compile.  Is it supposed to be so?

Yes, MULTIPROCESSOR is not supported by NetBSD/xen yet. This just means you
can't use both CPU in a single domain; xen itself is SMP, and if you have
several domains they will spread across all CPUs.

> 
> With XEN3_DOM0 kernel and a single XEN3_DOMU domainU, CPU is
> noticeably hotter than with non-Xen kernel, according to onboard
> temperature sensor.  In fact even when 100% idle state, it is close to
> 100% load of non-Xen kernel.  Is it normal?

what does 'xm top' says ? It's possible that the xen.gz kernel isn't using
power management options to stop the CPU when idle, but instead use
a spin loop waiting for something to do. 
> 
> When I configured azalia(4) driver with XEN3_DOM0, it crashed when
> booting-up.  Should I send-pr?  Also, configuring fdc(4) with acpi

Yes, please.

--

-- 
Manuel Bouyer <bouyer <at> antioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la difference
--

(Continue reading)

david l goodrich | 4 Mar 01:32 2007

grub "Error 3" and small partitions

Hi, I have a problem that's been dealt with in the past here:
http://mail-index.NetBSD.org/port-xen/2006/11/04/0010.html

I'm getting the same error when I try to boot the xen.gz kernel -
"Error 3: Bad or corrupt data while decompressing file"

The solution seems to be to make a small /, and set the block
size to 8k, and fragment size to 1k.

This has solved the problem for me, on other hardware, in the past.
This time, it didn't have any effect.

This is a Pentium D 3ghz (dual core), running NetBSD 4.0_BETA2
from 20070225.

/ is on a raid mirror, is 2GB in size, and has block and fragment 
sizes of 8k and 1k respectively.

The grub install seems alright, I'm able to run grub with this
configuration:
  root (hd0,0)
  chainloader +1

and get the NetBSD bootloader.

Does anyone have any advice on this?  Thanks.
  --david
Manuel Bouyer | 4 Mar 11:53 2007

Re: grub "Error 3" and small partitions

On Sat, Mar 03, 2007 at 06:32:42PM -0600, david l goodrich wrote:
> Hi, I have a problem that's been dealt with in the past here:
> http://mail-index.NetBSD.org/port-xen/2006/11/04/0010.html
> 
> I'm getting the same error when I try to boot the xen.gz kernel -
> "Error 3: Bad or corrupt data while decompressing file"
> 
> The solution seems to be to make a small /, and set the block
> size to 8k, and fragment size to 1k.
> 
> This has solved the problem for me, on other hardware, in the past.
> This time, it didn't have any effect.
> 
> This is a Pentium D 3ghz (dual core), running NetBSD 4.0_BETA2
> from 20070225.
> 
> / is on a raid mirror, is 2GB in size, and has block and fragment 
> sizes of 8k and 1k respectively.

I'm not sure 2GB is small enough. I always to / 512MB or smaller.

> 
> The grub install seems alright, I'm able to run grub with this
> configuration:
>   root (hd0,0)
>   chainloader +1

loading a file from filesystem or chain-booting a partition are really 2
different things. However I think grub will load menu.lst at boot, so
it probably can read at last parts of the filesystem properly. This should
(Continue reading)

david l goodrich | 4 Mar 17:57 2007

Re: grub "Error 3" and small partitions

On Sun, Mar 04, 2007 at 11:53:20AM +0100, Manuel Bouyer wrote:
> On Sat, Mar 03, 2007 at 06:32:42PM -0600, david l goodrich wrote:
> >
> > / is on a raid mirror, is 2GB in size, and has block and fragment 
> > sizes of 8k and 1k respectively.
> 
> I'm not sure 2GB is small enough. I always to / 512MB or smaller.

Well, okay.  I guess i'll try smaller.  2G was sufficient in the
past, though:

xen# df -h /
Filesystem    Size      Used     Avail Capacity  Mounted on
/dev/raid0a   1.9G      160M      1.7G     8%    /
xen# disklabel raid0 | grep ^\ a:
 a:   4194304         0     4.2BSD   1024  8192 46608  # (Cyl.
0 -   4095)
xen# uname -a
NetBSD xen.bwcws.dsrw.org 4.99.4 NetBSD 4.99.4 (XEN3_DOM0) #0:
Mon Nov 27 04:32:34 CST 2006
dlg <at> build-31.dsrw.org:/local/src/HEAD/src/sys/arch/i386/compile/obj/XEN3_DOM0
i386
xen# 

> 
> > 
> > The grub install seems alright, I'm able to run grub with this
> > configuration:
> >   root (hd0,0)
> >   chainloader +1
(Continue reading)

Manuel Bouyer | 4 Mar 18:03 2007

Re: grub "Error 3" and small partitions

On Sun, Mar 04, 2007 at 10:57:52AM -0600, david l goodrich wrote:
> On Sun, Mar 04, 2007 at 11:53:20AM +0100, Manuel Bouyer wrote:
> > On Sat, Mar 03, 2007 at 06:32:42PM -0600, david l goodrich wrote:
> > >
> > > / is on a raid mirror, is 2GB in size, and has block and fragment 
> > > sizes of 8k and 1k respectively.
> > 
> > I'm not sure 2GB is small enough. I always to / 512MB or smaller.
> 
> Well, okay.  I guess i'll try smaller.  2G was sufficient in the
> past, though:

Yes, and I also got it working once on a 128GB partition. It depends on
where the file is located in the partition.

> > 
> > loading a file from filesystem or chain-booting a partition are really 2
> > different things. However I think grub will load menu.lst at boot, so
> > it probably can read at last parts of the filesystem properly. This should
> > rule out issues with the raid setup.
> 
> Okay.  I saw this in the pkg_add output, and gave it a shot:
> 
>   title NetBSD (wd0)
>     root (hd0,0,a)
>     kernel /netbsd
> 
> and it seems to work fine as well.

Again, it depends on where the file is in the partition. /netbsd is one of the
(Continue reading)

david l goodrich | 4 Mar 22:28 2007

Re: grub "Error 3" and small partitions

On Sun, Mar 04, 2007 at 06:03:35PM +0100, Manuel Bouyer wrote:
> On Sun, Mar 04, 2007 at 10:57:52AM -0600, david l goodrich wrote:
> > On Sun, Mar 04, 2007 at 11:53:20AM +0100, Manuel Bouyer wrote:
> > > On Sat, Mar 03, 2007 at 06:32:42PM -0600, david l goodrich wrote:
> > > >
> > > > / is on a raid mirror, is 2GB in size, and has block and fragment 
> > > > sizes of 8k and 1k respectively.
> > > 
> > > I'm not sure 2GB is small enough. I always to / 512MB or smaller.
> > 
> > Well, okay.  I guess i'll try smaller.  2G was sufficient in the
> > past, though:
> 
> Yes, and I also got it working once on a 128GB partition. It depends on
> where the file is located in the partition.
> 

Point conceded.  It works fine with a 512 MB / partition.
Thanks.
  --david 
Anzi | 5 Mar 08:25 2007
Picon

xenbsd /netbsd: xennetback: can't get new mcl pages (0)

Hi,

In the weekend I had trouble with netbsd / xen. Console showed following 
text and xen guestdomains where not accessible from network. Also Dom0 
not allowed ssh login, only ping worked. Finally I had to reboot machine 
from powerswitch.
I think that problem started somewhere where automated rootfilesystem 
snapshot was being made or copied to NFS.

This was in the /var/log/messages (I copied only the relevant parts):

Mar  4 00:34:01 xenbsd /netbsd: nfs server nfsHOST:/LinuxBackup: not 
responding
Mar  4 00:34:01 xenbsd /netbsd: nfs server nfsHOST:/LinuxBackup: is 
alive again
Mar  4 00:36:16 xenbsd /netbsd: nfs server nfsHOST:/LinuxBackup: not 
responding
Mar  4 00:36:16 xenbsd /netbsd: nfs server nfsHOST:/LinuxBackup: is 
alive again
Mar  4 00:39:39 xenbsd /netbsd: nfs server nfsHOST:/LinuxBackup: not 
responding
Mar  4 00:39:39 xenbsd /netbsd: nfs server nfsHOST:/LinuxBackup: is 
alive again

Mar  4 00:41:13 xenbsd /netbsd: xennetback: got only 14 new mcl pages

Mar  4 00:41:53 xenbsd /netbsd: xennetback: can't get new mcl pages (0)
Mar  4 00:41:53 xenbsd /netbsd: xennetback_ifstart: no mcl_pages
Mar  4 00:41:53 xenbsd /netbsd: xennetback: can't get new mcl pages (0)
Mar  4 00:41:53 xenbsd /netbsd: xennetback_ifstart: no mcl_pages
(Continue reading)

Anzi | 5 Mar 09:05 2007
Picon

xenbsd /netbsd: xennetback: can't get new mcl pages (0)

Hi,

In the weekend I had trouble with netbsd / xen. Console showed following
text and xen guestdomains where not accessible from network. Also Dom0
not allowed ssh login, only ping worked. Finally I had to reboot machine
from powerswitch.
I think that problem started somewhere where automated rootfilesystem
snapshot was being made or copied to NFS.

This was in the /var/log/messages (I copied only the relevant parts):

Mar  4 00:34:01 xenbsd /netbsd: nfs server nfsHOST:/LinuxBackup: not
responding
Mar  4 00:34:01 xenbsd /netbsd: nfs server nfsHOST:/LinuxBackup: is
alive again
Mar  4 00:36:16 xenbsd /netbsd: nfs server nfsHOST:/LinuxBackup: not
responding
Mar  4 00:36:16 xenbsd /netbsd: nfs server nfsHOST:/LinuxBackup: is
alive again
Mar  4 00:39:39 xenbsd /netbsd: nfs server nfsHOST:/LinuxBackup: not
responding
Mar  4 00:39:39 xenbsd /netbsd: nfs server nfsHOST:/LinuxBackup: is
alive again

Mar  4 00:41:13 xenbsd /netbsd: xennetback: got only 14 new mcl pages

Mar  4 00:41:53 xenbsd /netbsd: xennetback: can't get new mcl pages (0)
Mar  4 00:41:53 xenbsd /netbsd: xennetback_ifstart: no mcl_pages
Mar  4 00:41:53 xenbsd /netbsd: xennetback: can't get new mcl pages (0)
Mar  4 00:41:53 xenbsd /netbsd: xennetback_ifstart: no mcl_pages
(Continue reading)

Anzi | 5 Mar 09:08 2007
Picon

xenbsd /netbsd: xennetback: can't get new mcl pages (0), (try#3)

Hi,

In the weekend I had trouble with netbsd / xen. Console showed following 
text and xen guestdomains where not accessible from network. Also Dom0 
not allowed ssh login, only ping worked. Finally I had to reboot machine 
from powerswitch.
I think that problem started somewhere where automated rootfilesystem 
snapshot was being made or copied to NFS.

This was in the /var/log/messages (I copied only the relevant parts):

Mar  4 00:34:01 xenbsd /netbsd: nfs server nfsHOST:/LinuxBackup: not 
responding
Mar  4 00:34:01 xenbsd /netbsd: nfs server nfsHOST:/LinuxBackup: is 
alive again
Mar  4 00:36:16 xenbsd /netbsd: nfs server nfsHOST:/LinuxBackup: not 
responding
Mar  4 00:36:16 xenbsd /netbsd: nfs server nfsHOST:/LinuxBackup: is 
alive again
Mar  4 00:39:39 xenbsd /netbsd: nfs server nfsHOST:/LinuxBackup: not 
responding
Mar  4 00:39:39 xenbsd /netbsd: nfs server nfsHOST:/LinuxBackup: is 
alive again

Mar  4 00:41:13 xenbsd /netbsd: xennetback: got only 14 new mcl pages

Mar  4 00:41:53 xenbsd /netbsd: xennetback: can't get new mcl pages (0)
Mar  4 00:41:53 xenbsd /netbsd: xennetback_ifstart: no mcl_pages
Mar  4 00:41:53 xenbsd /netbsd: xennetback: can't get new mcl pages (0)
Mar  4 00:41:53 xenbsd /netbsd: xennetback_ifstart: no mcl_pages
(Continue reading)


Gmane