Re: Subject: [Xen-users] Starting Guest VM on debian etch

Hi, try brclt show to see if the bridge is created.-

regards.-

2009/6/8 <xen-users-request@xxxxxxxxxxxxxxxxxxx>

Send Xen-users mailing list submissions to
xen-users@xxxxxxxxxxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.xensource.com/mailman/listinfo/xen-users
or, via email, send a message with subject or body 'help' to
xen-users-request@xxxxxxxxxxxxxxxxxxx

You can reach the person managing the list at
xen-users-owner@xxxxxxxxxxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Xen-users digest..."

Today's Topics:

1. Starting Guest VM on debian etch (Fasiha Ashraf)
2. Major corruption of Windows HVM disks - Xen 3.4 (Adam Wilbraham)
3. Re: Starting Guest VM on debian etch (Fajar A. Nugraha)
4. xm vcpu-set doesn't work (Pepo Viola)
5. RE: Major corruption of Windows HVM disks - Xen 3.4 (James Harper)
6. Re: Major corruption of Windows HVM disks - Xen 3.4
(Adam Wilbraham)

----------------------------------------------------------------------

Message: 1
Date: Mon, 8 Jun 2009 16:23:29 +0530 (IST)
From: Fasiha Ashraf <feehapk@xxxxxxxxxxx>
Subject: [Xen-users] Starting Guest VM on debian etch
To: xen-users@xxxxxxxxxxxxxxxxxxx
Message-ID: <332239.81466.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="utf-8"

Hi there!

I am trying to start virtual server just created using this command, but it gives an error.

xm create /etc/xen/debian-guest.cfg

Using config file "/etc/xen/debian-guest.cfg".

Error: Device 0 (vif) could not be connected. Backend device not found.

when I checked interfaces using "ifconfig" there's no bridge interface. br0

although I have started "xend"

What could be the problem, I think bridge interface should be created automatically by starting xend

Anybody has the solution? please provide!

Regards,

Fasiha Ashraf

Cricket on your mind? Visit the ultimate cricket website. Enter http://beta.cricket.yahoo.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.xensource.com/archives/html/xen-users/attachments/20090608/4389ea3f/attachment.html

------------------------------

Message: 2
Date: Mon, 08 Jun 2009 12:02:54 +0100
From: Adam Wilbraham <adam.wilbraham@xxxxxxxxxxxxxxxx>
Subject: [Xen-users] Major corruption of Windows HVM disks - Xen 3.4
To: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Message-ID: <4A2CEFDE.7030802@xxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

I've come back into work after the weekend and noticed that all (3) of
our Windows HVMs have had massive issues with corruption of the hard
disks. These have all been running rock solid on Xen 3.2.1 for the past
9 months or so but I upgraded their host to Xen 3.4 last week.

I noticed on Friday morning that all 3 had randomly rebooted on
Thursday evening but tried not to think too much of it. Unfortunately
as I say I have come in this morning and they are all in various states
of disrepair.

One VM is claiming ntloader.exe is not on the disk (presumably with a
number of other files), the other had crashed so I started it back up,
it ran checkdsk before running through lots of corrupt and missing
files, rebooting and is now BSODing on boot and the third boots but has
an event log full of SQL Server errors talking about file corruption. As
such I'm having to restore all three from backups which is not ideal.

Has anyone experienced anything similar to this? Is it likely to be a
problem with qemu rather than Xen? Either way, I am left with no choice
than to roll back to a previous version of Xen as I cannot risk this
happening again.

Thanks,

--
Adam Wilbraham - Systems Administrator
TechnoPhobia Limited
The Workstation
15 Paternoster Row
SHEFFIELD
England
S1 2BX
t: +44 (0)114 2212123
f: +44 (0)114 2212124
e: adam.wilbraham@xxxxxxxxxxxxxxxx
w: http://www.technophobia.com/

Registered in England and Wales Company No. 3063669
VAT registration No. 598 7858 42
ISO 9001:2000 Accredited Company No. 21227
ISO 14001:2004 Accredited Company No. E997
ISO 27001:2005 (BS7799) Accredited Company No. IS 508906
Investor in People Certified No. 101507

The contents of this email are confidential to the addressee
and are intended solely for the recipients use. If you are not
the addressee, you have received this email in error.
Any disclosure, copying, distribution or action taken in
reliance on it is prohibited and may be unlawful.

Any opinions expressed in this email are those of the author
personally and not TechnoPhobia Limited who do not accept
responsibility for the contents of the message.

All email communications, in and out of TechnoPhobia,
are recorded for monitoring purposes.

------------------------------

Message: 3
Date: Mon, 8 Jun 2009 18:58:15 +0700
From: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Subject: Re: [Xen-users] Starting Guest VM on debian etch
To: Xen User-List <xen-users@xxxxxxxxxxxxxxxxxxx>
Message-ID:
<7207d96f0906080458y6fbb80f7l1cef9a3a793eed8e@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Jun 8, 2009 at 5:53 PM, Fasiha Ashraf<feehapk@xxxxxxxxxxx> wrote:
> What could be the problem, I think bridge interface should be created
> automatically by starting xend

Not necesssarily. Especially on Debian.

>
> Anybody has the solution? please provide!

Try http://wiki.debian.org/Xen#Error.22Device....28vif.29couldnotbeconnected.22

--
Fajar

------------------------------

Message: 4
Date: Mon, 8 Jun 2009 09:29:51 -0300
From: Pepo Viola <pepoviola@xxxxxxxxx>
Subject: [Xen-users] xm vcpu-set doesn't work
To: xen-users@xxxxxxxxxxxxxxxxxxx
Message-ID:
<7d63fa0e0906080529h4ab1d060he4ba866e6bd95a08@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

Hi all,
I can't change the number of vcpu with this command, when I run the
command gives no error, but does not update the amount of vcpus.
The version of the xen is 3.2.1 running on Debian 5.
This is the vm config file:

name = 'vm-999998'
memory = '512'
disk = [ 'file:xxxxx.root,hda,w',
'file:xxxxxx1.swap,hdb,w',
'file:xxxxxx2.opt,hdc,w' ]
vif = [ 'mac=00:16:3e:xx:xx:xx, bridge=xenbrxxx', ]
vfb = [ 'type=vnc,vncpasswd=xxxx,vncdisplay=xxx']
root = '/dev/hda1'
extra = 'ro xencons=xvc video=xenfb'
kernel = '/opt/vm-manager/kernel-domU-64'
vcpus=2
maxvcpus=4
> on_reboot = 'restart'
on_crash = 'restart'
cpu_cap = '100'
cpu_weight = 256

==============

This is the patched function (file XendDomainInfo.py):

(...)
def setVCpuCount(self, vcpus):
if vcpus <= 0:
raise XendError('Invalid VCPUs')

self.info['vcpu_avail'] = (1 << vcpus) - 1
if self.domid >= 0:
self.storeVm('vcpu_avail', self.info['vcpu_avail'])
# update dom differently depending on whether we are adjusting
# vcpu number up or down, otherwise _vcpuDomDetails does not
# disable the vcpus
if self.info['VCPUs_max'] > vcpus:
# decreasing
self._writeDom(self._vcpuDomDetails())
self.info['VCPUs_live'] = vcpus
else:
# same or increasing
self.info['VCPUs_live'] = vcpus
self._writeDom(self._vcpuDomDetails())
else:
self.info['VCPUs_live'] = vcpus
self.info['VCPUs_max'] = vcpus
xen.xend.XendDomain.instance().managed_config_save(self)
log.info("Set VCPU count on domain %s to %d", self.info
['name_label'],
vcpus)
(...)

==============================================
When I run the command (xm vcpu-set) i see this log:

#xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 1000 8 r-----
5252.7
vm-999998 6 512 2 -b----
30.7

#xm vcpu-set vm-999998 1

( tail /var/log/xen/xend.log )
[2009-06-08 09:23:02 32568] TRACE (XendDomainInfo:1039)
XendDomainInfo.storeChanged
[2009-06-08 09:23:02 32568] INFO (XendDomainInfo:1176) Set VCPU count on
domain vm-999998 to 1

xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 1000 8 r-----
5253.2
vm-999998 6 512 2 -b----
30.7

Regards

Viola Villanueva Javier.-
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.xensource.com/archives/html/xen-users/attachments/20090608/b76ef646/attachment.html

------------------------------

Message: 5
Date: Mon, 8 Jun 2009 22:49:10 +1000
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] Major corruption of Windows HVM disks - Xen
3.4
To: "Adam Wilbraham" <adam.wilbraham@xxxxxxxxxxxxxxxx>, "xen-users"
<xen-users@xxxxxxxxxxxxxxxxxxx>
Message-ID: <AEC6C66638C05B468B556EA548C1A77D016DD65D@trantor>
Content-Type: text/plain; charset="US-ASCII"

>
> I've come back into work after the weekend and noticed that all (3) of
> our Windows HVMs have had massive issues with corruption of the hard
> disks. These have all been running rock solid on Xen 3.2.1 for the
past
> 9 months or so but I upgraded their host to Xen 3.4 last week.
>
> I noticed on Friday morning that all 3 had randomly rebooted on
> Thursday evening but tried not to think too much of it. Unfortunately
> as I say I have come in this morning and they are all in various
states
> of disrepair.
>
> One VM is claiming ntloader.exe is not on the disk (presumably with a
> number of other files), the other had crashed so I started it back up,
> it ran checkdsk before running through lots of corrupt and missing
> files, rebooting and is now BSODing on boot and the third boots but
has
> an event log full of SQL Server errors talking about file corruption.
As
> such I'm having to restore all three from backups which is not ideal.
>
> Has anyone experienced anything similar to this? Is it likely to be a
> problem with qemu rather than Xen? Either way, I am left with no
choice
> than to roll back to a previous version of Xen as I cannot risk this
> happening again.
>

Have you established that the virtual disks are definitely corrupt, as
opposed to something gone wrong in Dom0 that makes them seem corrupt. I
can't think what would cause that situation to arise though.

Are you using my GPLPV drivers? If so, then I would really like to hear
more about what went wrong so I can look into it and make sure it isn't
a problem with the drivers, although for all 3 domU's to fail
simultaneously like that it would be unlikely to be a DomU side problem.

In my experience, the qemu drivers are prone to this sort of thing on
unclean shutdowns unfortunately, although I would have thought less so
with 3.4 than with 3.2... I have seen it before under 3.1 with Dom0
running out of memory and firing up the OOM killer (snmpd memory leak),
although the worst I've seen was a corrupt Exchange database that
restored without further problems.

Did you upgrade the Dom0 kernel when you upgraded xen?

Good luck with the restores.

James

------------------------------

Message: 6
Date: Mon, 08 Jun 2009 14:04:27 +0100
From: Adam Wilbraham <adam.wilbraham@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-users] Major corruption of Windows HVM disks - Xen
3.4
To: James Harper <james.harper@xxxxxxxxxxxxxxxx>
Cc: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Message-ID: <4A2D0C5B.6080900@xxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

On 08/06/09 13:49, James Harper wrote:
> Have you established that the virtual disks are definitely corrupt, as
> opposed to something gone wrong in Dom0 that makes them seem corrupt. I
> can't think what would cause that situation to arise though.

The first thing I did was to try and bring up all 3 VMs on the host that
they are replicated to using DRBD. This host is still using Xen 3.2.1 as
I haven't upgraded it yet - I was waiting to see how things went before
doing both.

> Are you using my GPLPV drivers? If so, then I would really like to hear
> more about what went wrong so I can look into it and make sure it isn't
> a problem with the drivers, although for all 3 domU's to fail
> simultaneously like that it would be unlikely to be a DomU side problem.

A couple of the VMs do have an older version of the GPLPV drivers on but
they were not active - I experienced problems with live migration when
using your drivers so had to stick with pure HVM. I will be trying them
out again in the near future as they appear to have progressed well over
the last number of months, but as I say they are currently disabled so I
would be 99% sure that they aren't to blame.

> In my experience, the qemu drivers are prone to this sort of thing on
> unclean shutdowns unfortunately, although I would have thought less so
> with 3.4 than with 3.2... I have seen it before under 3.1 with Dom0
> running out of memory and firing up the OOM killer (snmpd memory leak),
> although the worst I've seen was a corrupt Exchange database that
> restored without further problems.

The corruption did seem pretty bad on all 3 but I am indeed thinking
qemu may have been part of problem here. I'm just about to start
trawling the logs to see if there is anything useful in there.

> Did you upgrade the Dom0 kernel when you upgraded xen?

No - still using 2.6.18-6 which is a standard Debian Etch kernel. I
contemplated moving to the custom compiled one but everything I read on
the list suggested that the Etch one would be fine. Can you see any
benefit in upgrading the dom0 kernel too? Like I say this entire system
has been rock solid on 3.2.1 since it was built in late 2008. The only
driver for upgrade was that it was running a 32bit hypervisor and we
needed more memory - I just thought bringing the base platform up to
date would be a good idea at the same time.

> Good luck with the restores.

Thankfully everything is back up and running now - backups are a great
thing when you actually take them!

--
Adam Wilbraham - Systems Administrator
TechnoPhobia Limited
The Workstation
15 Paternoster Row
SHEFFIELD
England
S1 2BX
t: +44 (0)114 2212123
f: +44 (0)114 2212124
e: adam.wilbraham@xxxxxxxxxxxxxxxx
w: http://www.technophobia.com/

Registered in England and Wales Company No. 3063669
VAT registration No. 598 7858 42
ISO 9001:2000 Accredited Company No. 21227
ISO 14001:2004 Accredited Company No. E997
ISO 27001:2005 (BS7799) Accredited Company No. IS 508906
Investor in People Certified No. 101507

The contents of this email are confidential to the addressee
and are intended solely for the recipients use. If you are not
the addressee, you have received this email in error.
Any disclosure, copying, distribution or action taken in
reliance on it is prohibited and may be unlawful.

Any opinions expressed in this email are those of the author
personally and not TechnoPhobia Limited who do not accept
responsibility for the contents of the message.

All email communications, in and out of TechnoPhobia,
are recorded for monitoring purposes.

------------------------------

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

End of Xen-users Digest, Vol 52, Issue 48
*****************************************

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

WARNING - OLD ARCHIVES

xen-users

Re: Subject: [Xen-users] Starting Guest VM on debian etch