This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 1612] x86-64 : Can't start VM when vif set

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 1612] x86-64 : Can't start VM when vif set
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Wed, 26 May 2010 23:47:30 -0700
Delivery-date: Wed, 26 May 2010 23:47:40 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bug-1612-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

s.groening@xxxxxxxxx changed:

           What    |Removed                     |Added
                 CC|                            |s.groening@xxxxxxxxx

------- Comment #14 from s.groening@xxxxxxxxx  2010-05-26 23:47 -------
I have encountered this problem within the last week or so - with two different
kernels, both from Jeremy's git repo: (Xen 3.4.2 stable) and
(Xen 4.0 stable) ... all on an Intel Xeon Q6600 Core 2 Quad w./ 8GB RAM.

I have run the pv-ops Dom0 setup on Debian Squeeze with the
without problems _AT ALL_ for quite a while, being very happy with both
performance and stability, at least up until two changes were made to my setup:

 1: I tried to autostart two domains though virsh XML-files, which caused my
system to crash with this exact problem occurring. Disabling the autostart of
my two domains stops the kernel from crashing the netback_uevent error
mentioned here, but after this, every domain start triggers the bug.

 2: I also tried enabling the APIC + ACPI options for a single domain after
first having disabled the autostart of my two domains mentioned above, and it
crashed with the same netback_uevent error as mentioned here.

Yesterday, I upgraded to Xen 4.0 upgrading my kernel to Jeremy's
kernel and this does not fix anything. Both domain XML-files have been reverted
completely as well as, but with no luck! Now it just crashes on every DomU-boot

Could Xen for some exotic reason keep track of what was going on the last time
a domain was loaded, since even my Xen .cfg-files produce the same error now,
which they've never done before the two above mentioned experiments?

Here's my Xen .cfg-file:

# PyGrub
memory = 1024
name = "sso"
vcpus = 1
vif = [ '' ]
disk = [ 'phy:xen_domains/stable,xvda1,w','phy:/dev/sdc1,xvdb1,w' ]
vfb = [ 'type=vnc' ]
on_poweroff = 'destroy'
on_reboot   = 'restart'
on_crash    = 'restart'

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>