[Bug 210973] New: Failing "xm create" makes network of Dom0 unusable
https://bugzilla.novell.com/show_bug.cgi?id=210973 Summary: Failing "xm create" makes network of Dom0 unusable Product: SUSE Linux 10.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: Ulrich.Windl@rz.uni-regensburg.de QAContact: qa@suse.de When there is a problem when starting a VM (e.g. illegal disk configuration), the VM does not start, but at the same time the network of Dom0 is unreachable. The solution is to: /etc/xen/scripts/network-bridge stop netdev=eth0 rcnetwork restart /etc/xen/scripts/network-bridge start netdev=eth0 (Bug actually found in SLES10 with xen-3.0.2_09749-0.7) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210973 cgriffin@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|cgriffin@novell.com |kallan@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210973 kallan@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |Ulrich.Windl@rz.uni-regensburg.de ------- Comment #1 from kallan@novell.com 2006-10-09 16:19 MST ------- Can you provide the vm configuration script with the illegal disk configuration that will allow me to reproduce the problem? Was the vm configuration script created via yast? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210973 Ulrich.Windl@rz.uni-regensburg.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|Ulrich.Windl@rz.uni- | |regensburg.de | ------- Comment #2 from Ulrich.Windl@rz.uni-regensburg.de 2006-10-10 00:10 MST ------- The situation was produced by an attempt to boot a disk image cloned from a VMware installation using XEN, and no, it was not created using Yast. If you want to try to reproduce, possibly any disk image that fails to boot will do. I see little sense to attach a 4GB disk image to this bug report. Do you need more information? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210973 kallan@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |Ulrich.Windl@rz.uni-regensburg.de ------- Comment #3 from kallan@novell.com 2006-10-11 16:43 MST ------- Sorry, let me clarify, could you attach the VM configuration script that contains the disk= line that points to the non-bootable disk image? What are the steps needed to clone a disk image from a VMware installation? All my VM/disk images were created with YaST and boot OK, so I'm looking for steps to create a non-bootable disk image. When the VM fails to boot, is the VM still listed by the 'xm list' command? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210973 Ulrich.Windl@rz.uni-regensburg.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|Ulrich.Windl@rz.uni- | |regensburg.de | ------- Comment #4 from Ulrich.Windl@rz.uni-regensburg.de 2006-10-12 06:10 MST ------- Thre's nothing special with the disk configuration line, but with the disk image: A harddisk with LVM configuration was simply dumped into an image file, and that was _tried_ to boot. That did not work for several reasons, but I did not expect a global network damage to Dom0 and other DomUs. WHen cloning a VMware disk to an image, I booted the VMware VM into single user, mounted the image file's directory writable through NFS, dd'd the /dev/sda into the image file, and that was it roughly. The easiest way to a non-bootable image might be a LVM config or a non-XEN boot kernel in the image I guess. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210973 jdouglas@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |Ulrich.Windl@rz.uni-regensburg.de ------- Comment #5 from jdouglas@novell.com 2006-10-12 10:08 MST ------- I've been asked to help duplicate this issue. Could you attach your vm config file? Also, could you attach /var/log/xend*.log and the output from ifconfig (before and after the problem). That should be enough to get started. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=210973 Ulrich.Windl@rz.uni-regensburg.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|Ulrich.Windl@rz.uni- | |regensburg.de | Resolution| |INVALID ------- Comment #6 from Ulrich.Windl@rz.uni-regensburg.de 2006-10-13 03:09 MST ------- WHenb collecting the data you requested, I found out that I could no longer reporduc the problem with the current versions (xen-3.0.2_09763-0.8, kernel-xen-2.6.16.21-0.25). Closing as INVALID for now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com