Re: Xen 3.4.1: pygrub Error: Boot loader didn't return any data!

Fajar A. Nugraha wrote:
> On Friday, January 1, 2010, Gerry Reno <greno <at> verizon.net> wrote:
>   
>> I tried this and things are starting to work a little.  Here's what i get using pv-grub:
>>     
>
>   
>> Thread "main": pointer: 0x2040002f70, stack: 0xfd0000
>> "main" "(hd0,4)/boot/grub/menu.lst"
>>     
>
>
> shouldn't it be  (hd0,4)/grub/menu.lst on your setup?
>
>   
Yes.  And I just tried it and it still does the exact same thing.  It 
gets stuck in the same place.  Not sure what is causing this.  Here's 
xend.log:

[2009-12-31 18:08:50 1852] DEBUG (XendDomainInfo:92) 
XendDomainInfo.create(['vm', ['name', 'CLOUD-CC-1'], ['memory', 1024], 
['maxmem', 1024], ['on_poweroff', 'destroy'], ['on_reboot', 'restart'], 
['on_crash', 'restart'], ['vcpus', 1], ['on_xend_start', 'ignore'], 
['on_xend_stop', 'ignore'], ['image', ['linux', ['kernel', 
'/usr/lib/xen/boot/pv-grub-x86_64.gz'], ['videoram', 4], ['args', 
'(hd0,4)/boot/grub/menu.lst']]], ['s3_integrity', 1], ['device', ['tap', 
['uname', 'tap:aio:/var/lib/xen/images/CLOUD-CC-1.img'], ['dev', 
'xvda'], ['mode', 'w']]], ['device', ['vif', ['bridge', 'virbr0'], 
['mac', '00:16:1a:2a:ef:56']]]])
[2009-12-31 18:08:50 1852] DEBUG (XendDomainInfo:2296) 

Re: Scary!!! Lost domU!!!

James Pifer wrote:
> I've been on vacation (and still am) but had to work on a couple
> problems. I have a couple Citrix servers that are domU's on a sles10sp2
> server that has local storage and connects to two ocfs2 volumes. 
> 
> I tried to restart one of the Citrix servers and it would not restart,
> giving an error that the disk was already mounted in a loopback, etc. I
> looked at mount and didn't see anything mounted and I had just shut the
> domU down. I assumed it had not shut down completely. This domU runs
> from the local disk. 
> 
> So I decided to a restart of the host was in order. I downed the rest of
> the domU's, including an oracle server running off one of the ocfs2
> clusters. This servers has been being used for the last three weeks from
> this location. 
> 
> After restarting dom0 I started bringing the domU's back up. All of them
> came back up fine, except for the oracle server. It gave an error that
> the disk files did not exist, and they don't, they aren't there
> anymore. 
> 
> I checked and double checked history to see if any rm commands had been
> given and I didn't find any. 
> 
> When I restarted, there was an error on one of the local file systems
> that said "JDB: barrier-based sync failed...".
> 
> Luckily I have a copy of this domU from a few weeks ago BEFORE I copied
> it to the ocfs2 volume. What could explain the sudden deletion of a
> directory like this?

Re: Xen 3.4.1: pygrub Error: Boot loader didn't return any data!

Fajar A. Nugraha wrote:
> On Friday, January 1, 2010, Gerry Reno <greno <at> verizon.net> wrote:
>   
>> I tried this and things are starting to work a little.  Here's what i get using pv-grub:
>>     
>
>   
>> Thread "main": pointer: 0x2040002f70, stack: 0xfd0000
>> "main" "(hd0,4)/boot/grub/menu.lst"
>>     
>
>
> shouldn't it be  (hd0,4)/grub/menu.lst on your setup?
>
>   
Yes.  And I just tried it and it still does the exact same thing.  It
gets stuck in the same place.  Not sure what is causing this.  Here's
xend.log:

Sorry, sent wrong log entry last time...  Here's the right one.

> [2009-12-31 19:30:52 1852] DEBUG (XendDomainInfo:92) XendDomainInfo.create(['vm', ['name',
'CLOUD-CC-1'], ['memory', 1024], ['maxmem', 1024], ['on_poweroff', 'destroy'], ['on_reboot',
'restart'], ['on_crash', 'restart'], ['vcpus', 1], ['on_xend_start', 'ignore'], ['on_xend_stop',
'ignore'], ['image', ['linux', ['kernel', '/usr/lib/xen/boot/pv-grub-x86_64.gz'], ['videoram',
4], ['args', '(hd0,4)/grub/menu.lst']]], ['s3_integrity', 1], ['device', ['tap', ['uname',
'tap:aio:/var/lib/xen/images/CLOUD-CC-1.img'], ['dev', 'xvda'], ['mode', 'w']]], ['device',
['vif', ['bridge', 'virbr0'], ['mac', '00:16:1a:2a:ef:56']]]])
> [2009-12-31 19:30:52 1852] DEBUG (XendDomainInfo:2296) XendDomainInfo.constructDomain
> [2009-12-31 19:30:52 1852] DEBUG (balloon:166) Balloon: 6713852 KiB free; need 4096; done.

RE: Scary!!! Lost domU!!!

> 
> A note on LVM though; if you cluster it, it won't do LVM snapshots. I
> found this out late in the game, and had to create secondary partitions
> in the actual VM to use for snapshotting. I got luck that I had the
> space to do this, as I hadn't planned for it. That said, it's been a
> so-far successful setup.
> 

Is there any word on clustered LVM and snapshotting? Is it ever going to happen or are there fundamental
reasons why it won't work?

When I was first tinkering with it, probably 5 years ago, I somehow managed to make a snapshot on a clustered
LVM setup and boy did it blow up in my face!!! A word of advice - don't do that :)

James

_______________________________________________
Xen-users mailing list
Xen-users <at> lists.xensource.com
http://lists.xensource.com/xen-users

Re: Memory problems persist... Cannot allocate memory

On Thu, Dec 31, 2009 at 04:35:07PM -0500, James Pifer wrote:
> On Thu, 2009-12-31 at 21:48 +0200, Pasi Kärkkäinen wrote:
> > On Thu, Dec 31, 2009 at 03:45:36PM -0500, James Pifer wrote:
> > > > So what does "xm info" say about free memory? How much does the guest
> > > > you're trying to start have memory configured for it? 
> > > > 
> > > > -- Pasi
> > > 
> > > The domU only has 512meg. 
> > >
> > 
> > Ok. Really weird. 
> > How about dom0, does it have free memory? 
> > 
> > This was SLES11? 
> > 
> > -- Pasi
> > 
> > 
> > > # xm info
> > > host                   : xen06
> > > release                : 2.6.27.19-5-xen
> > > version                : #1 SMP 2009-02-28 04:40:21 +0100
> > > machine                : x86_64
> > > nr_cpus                : 16
> > > nr_nodes               : 1
> > > cores_per_socket       : 4
> > > threads_per_core       : 2
> > > cpu_mhz                : 2533
> > > hw_caps                : bfebfbff:28100800:00000000:00000340:009ce3bd:00000000:00000001:00000000

RE: Bluescreen with Latest GPLPV on Windows Server 2008 R2on XEN3.4.1

> 
> Hi all,
> 
> my system is a XEN3.4.1 Dom0 Host System with a HVM Windows 2008 R2
machine.
> After installation of the GPLPV driver
> ("gplpv_fre_wnet_AMD64_0.10.0.130.msi"), and an Reboot
> the Windows Server 2008 R2 comes up and ends in a bluescreen, and
immediately
> restarts.
> Testsigning is ON.
> 
> What else can be done, or better what needs to be checked? Is there
somebody
> who is facing the same problem?
> I would highly appreciate any help.

Unfortunately I don't have 2008 R2 to play with at this time.

Is testsigning on when you first do the install, or do you install and
turn on testsigning in the same session? If that's the case then the
drivers may not install because testsigning hasn't yet become active.
Try turning on testsigning, then rebooting, then installing.

My next release will have some registry keys added on install to put the
drivers in the critical devices database on install which will smooth
some of these problems over, assuming that's what the problem is.

James

Re: Bluescreen with Latest GPLPV on Windows Server 2008 R2on XEN3.4.1

On Fri, Jan 01, 2010 at 11:56:21AM +1100, James Harper wrote:
> > 
> > Hi all,
> > 
> > my system is a XEN3.4.1 Dom0 Host System with a HVM Windows 2008 R2
> machine.
> > After installation of the GPLPV driver
> > ("gplpv_fre_wnet_AMD64_0.10.0.130.msi"), and an Reboot
> > the Windows Server 2008 R2 comes up and ends in a bluescreen, and
> immediately
> > restarts.
> > Testsigning is ON.
> > 
> > What else can be done, or better what needs to be checked? Is there
> somebody
> > who is facing the same problem?
> > I would highly appreciate any help.
> 
> Unfortunately I don't have 2008 R2 to play with at this time.
> 
> Is testsigning on when you first do the install, or do you install and
> turn on testsigning in the same session? If that's the case then the
> drivers may not install because testsigning hasn't yet become active.
> Try turning on testsigning, then rebooting, then installing.
> 
> My next release will have some registry keys added on install to put the
> drivers in the critical devices database on install which will smooth
> some of these problems over, assuming that's what the problem is.
> 

RE: Bluescreen with Latest GPLPV on Windows Server 2008 R2on XEN3.4.1

> 
> James: Is it possible to detect (in the installer) if testsigning has
> been already enabled? Stopping the installer if there's no testsigning enabled
> would be better than a bluescreen..
> 

If it can be detected via a usermode API then it should be possible. A quick google and search of the registry
doesn't show anything obvious though...

I'm looking at how to put xenpci and xenvbd into the CriticalDeviceDatabase so that as long as the drivers
are installed, Windows can make the system boot even if it's never seen the device before. That might help
prevent leaving you with an unbootable system but I'm not sure if it has any other implications...

James

Re: Xen 3.4.1: pygrub Error: Boot loader didn't return any data!

I finally got the converted guest to boot using pv-grub.  The last 
problem was that pv-grub does not like tap:aio so I tried file: and it 
started working.

-Gerry

Re: Memory problems persist... Cannot allocate memory

> > 
> > Looks like dom0 is just about out of memory. It currently has 1 gb of
> > RAM. Looks like I changed menu.lst on Dec 12 to give it 2 gb of RAM, but
> > I haven't had a chance to restart it. It's been up for 29 days. It's a
> > dual quad core machine with 32gb of ram. It will probably run 12-18
> > domU's when all is said and done ranging anywhere from 512M to 4gb of
> > ram. Mixed Windows and Linux. Do you think 2gb of ram is enough for dom0
> > or should I go more, like 3 or 4gb?
> > 
> 
> 2GB definitely should be enough.. afaik.
> 
> > "top" gives me:
> > top - 14:18:13 up 29 days, 17:41,  3 users,  load average: 0.47, 0.77, 0.71
> > Tasks: 302 total,   3 running, 299 sleeping,   0 stopped,   0 zombie
> > Cpu(s):  0.4%us,  0.1%sy,  0.0%ni, 98.4%id,  0.7%wa,  0.0%hi,  0.0%si,  0.4%st
> > Mem:   1047040k total,  1036656k used,    10384k free,     7816k buffers
> > Swap:  2104472k total,  2104156k used,      316k free,    53876k cached
> > 
> 
> So what's eating all the memory and swap? 
> 
> -- Pasi
> 

What's the best way to see what's using all the memory and swap?

Thanks,
James