Mailinglist Archive: opensuse-bugs (13451 mails)
| < Previous | Next > |
[Bug 335113] New: Can not start a PVM-domain with domUloader
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Fri, 19 Oct 2007 01:13:34 -0600 (MDT)
- Message-id: <bug-335113-21960@xxxxxxxxxxxxxxxxxxxxxxxxx/>
https://bugzilla.novell.com/show_bug.cgi?id=335113
Summary: Can not start a PVM-domain with domUloader
Product: openSUSE 10.3
Version: Final
Platform: x86
OS/Version: openSUSE 10.3
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Xen
AssignedTo: cgriffin@xxxxxxxxxx
ReportedBy: franz.fleischmann@xxxxxxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---
Created an attachment (id=179378)
--> (https://bugzilla.novell.com/attachment.cgi?id=179378)
domain-config-file
Since the update to OpenSuSE 10.3 there is a greate problem with domUloader In
a normal way i can not start them anymore. In XEN shipped with OpenSuSE 10.2 it
was possible to work with the bootentry option. In OpenSuSE 10.3 the
configuration won't run so i switched to bootargs, but it fails also.
With the attachend domain-configfile xen reports me after starting the domain
the following error-msg:
xm create kmu-vtiger-baycix
Using config file "./kmu-vtiger-baycix".
Error: Boot loader didn't return any data!
After invoking domUloader manualy with the arguments shown in
/var/log/xen/xend.log the following error_msg will be printet:
/usr/lib/xen/boot/domUloader.py --args=root=/dev/sda1
--entry=xsda:/boot/vmlinuz-xenpae,/boot/initrd-xenpae
/opt/vm/xen/kmu-vtiger-baycix-hvm/vdsk-sda1
mount: /opt/vm/xen/kmu-vtiger-baycix-hvm/vdsk-sda1 ist kein blockorientiertes
Gerät
(Vielleicht probieren Sie „-o loop“?)
domUloader error: Error 8192 from mount -o ro
'/opt/vm/xen/kmu-vtiger-baycix-hvm/vdsk-sda1' on /var/lib/xen/tmp/xsda.I5u5WQ
The solution for me was to modify line 245 from domUloader from
def mount(self, fstype = None, options = "ro"):
to
def mount(self, fstype = None, options = "ro,loop"):
Is there another possibility to get the config running, perhaps i am using the
wrong syntax, or is it realy a bug
--
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.
Summary: Can not start a PVM-domain with domUloader
Product: openSUSE 10.3
Version: Final
Platform: x86
OS/Version: openSUSE 10.3
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Xen
AssignedTo: cgriffin@xxxxxxxxxx
ReportedBy: franz.fleischmann@xxxxxxxxxxxx
QAContact: qa@xxxxxxx
Found By: ---
Created an attachment (id=179378)
--> (https://bugzilla.novell.com/attachment.cgi?id=179378)
domain-config-file
Since the update to OpenSuSE 10.3 there is a greate problem with domUloader In
a normal way i can not start them anymore. In XEN shipped with OpenSuSE 10.2 it
was possible to work with the bootentry option. In OpenSuSE 10.3 the
configuration won't run so i switched to bootargs, but it fails also.
With the attachend domain-configfile xen reports me after starting the domain
the following error-msg:
xm create kmu-vtiger-baycix
Using config file "./kmu-vtiger-baycix".
Error: Boot loader didn't return any data!
After invoking domUloader manualy with the arguments shown in
/var/log/xen/xend.log the following error_msg will be printet:
/usr/lib/xen/boot/domUloader.py --args=root=/dev/sda1
--entry=xsda:/boot/vmlinuz-xenpae,/boot/initrd-xenpae
/opt/vm/xen/kmu-vtiger-baycix-hvm/vdsk-sda1
mount: /opt/vm/xen/kmu-vtiger-baycix-hvm/vdsk-sda1 ist kein blockorientiertes
Gerät
(Vielleicht probieren Sie „-o loop“?)
domUloader error: Error 8192 from mount -o ro
'/opt/vm/xen/kmu-vtiger-baycix-hvm/vdsk-sda1' on /var/lib/xen/tmp/xsda.I5u5WQ
The solution for me was to modify line 245 from domUloader from
def mount(self, fstype = None, options = "ro"):
to
def mount(self, fstype = None, options = "ro,loop"):
Is there another possibility to get the config running, perhaps i am using the
wrong syntax, or is it realy a bug
--
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.
| < Previous | Next > |