8:25 a.m.
[Moved to libvir-list. The original thread was on fedora-devel-list,
starting here:
https://www.redhat.com/archives/fedora-devel-list/2007-July/thread.html#0...]
Till Maas wrote:
On Di Juli 10 2007, Richard W.M. Jones wrote:
> Till Maas wrote:
>> The idea is imho great, but for me with qemu it does not work properly.
> I'd really like to help out here. Did you get any error messages?
The first problem is, that it seems to be a tool to create persisten virtual
machines, e.g. virtual servers, but most of the time I only want to boot a
live cd, e.g. a Fedora one. But virt-manager seems to demand an virtual HD
drive. I only tested it twice or so, but it looked not promising.
The next version of virt-install will support this explicitly. I am
reliably assured that it should work in qemu & Xen.
Support is not there yet in virt-manager.
What I did so far was creating a new machine with a Fedora Live CD
Image and
booted it. When I hit the Pause button, it appeared to be pressed, but
nothing happened. The machine still responded and the following error
appeared on the commandline, where I started virt-manager:
-------------
libvir: QEMU error : operation failed: suspend operation failed
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/console.py", line 389, in
control_vm_pause
self.vm.suspend()
File "/usr/share/virt-manager/virtManager/domain.py", line 365, in suspend
self.vm.suspend()
File "/usr/lib/python2.5/site-packages/libvirt.py", line 350, in suspend
if ret == -1: raise libvirtError ('virDomainSuspend() failed', dom=self)
libvirt.libvirtError: virDomainSuspend() failed operation failed: suspend
operation failed
--------------
This is a bug. Do you know what version of libvirt & virt-manager this
happens with? Suspend _ought_ to work with QEMU with libvirt >= 0.2.0.
Then when I shut down the machine and clicked on "run", it
did not boot the
ISO Image I selected while creating the machine, but only complained that it
could not boot from HD (which is true, because I did not install anything to
the HD)
Then I wanted to delete the machine, but the "Delete" button was still greyed
out, even when I shut it down (Imho it should be available all the time and
provide a warning that the machine needs to be shut down before it can be
deleted). When I closed virt-manager and opened it again, then I was able to
delete the machine.
But I cannot find a way to add an iso image to the machine or make it boot the
iso image I selected at creation time.
I haven't played with live CDs & virt-manager at all, but I'll have a
go. What live CD were you trying?
Also the network selection seems not to work, when I want to add a
network
interface, I can choose between virtual and shared device, but both only have
an empty list, where I have to select something to be able to click
on "Forward".
This is another bug. If you get me the version of virt-manager, I'll
look into it.
I guess you cannot help here very much, because it seems to me that
virt-manager just needs a lot of coding, to become as userfriendly as
VirtualBox is.
Rich.
--
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in
England and Wales under Company Registration No. 03798903
8:50 a.m.
On Di Juli 10 2007, Richard W.M. Jones wrote:
Till Maas wrote:
> What I did so far was creating a new machine with a Fedora Live
CD Image
> and booted it. When I hit the Pause button, it appeared to be pressed,
> but nothing happened. The machine still responded and the following error
> appeared on the commandline, where I started virt-manager:
>
> -------------
> libvir: QEMU error : operation failed: suspend operation failed
> Traceback (most recent call last):
> File "/usr/share/virt-manager/virtManager/console.py", line 389, in
> control_vm_pause
> self.vm.suspend()
> File "/usr/share/virt-manager/virtManager/domain.py", line 365, in
> suspend self.vm.suspend()
> File "/usr/lib/python2.5/site-packages/libvirt.py", line 350, in
> suspend if ret == -1: raise libvirtError ('virDomainSuspend() failed',
> dom=self) libvirt.libvirtError: virDomainSuspend() failed operation
> failed: suspend operation failed
> --------------
This is a bug. Do you know what version of libvirt & virt-manager this
happens with? Suspend _ought_ to work with QEMU with libvirt >= 0.2.0.
I am using an uptodate Fedora 7:
dkms-kqemu-1.3.0-0.2.pre11
qemu-0.9.0-2.fc7
libvirt-0.2.3-1.fc7
virt-manager-0.4.0-2.fc7
> Then when I shut down the machine and clicked on
"run", it did not boot
> the ISO Image I selected while creating the machine, but only complained
> that it could not boot from HD (which is true, because I did not install
> anything to the HD)
>
> Then I wanted to delete the machine, but the "Delete" button was still
> greyed out, even when I shut it down (Imho it should be available all the
> time and provide a warning that the machine needs to be shut down before
> it can be deleted). When I closed virt-manager and opened it again, then
> I was able to delete the machine.
>
> But I cannot find a way to add an iso image to the machine or make it
> boot the iso image I selected at creation time.
I haven't played with live CDs & virt-manager at all, but I'll have a
go. What live CD were you trying?
I tried the Fedora 7 rescue CD and the Gnome Live CD, but I not boot further
than into grub to test "Pause" or shut it down and tried to boot it again.
> Also the network selection seems not to work, when I want to add
a
> network interface, I can choose between virtual and shared device, but
> both only have an empty list, where I have to select something to be able
> to click on "Forward".
This is another bug. If you get me the version of virt-manager, I'll
look into it.
See above,
Regards,
Till
9:25 a.m.
On Tue, Jul 10, 2007 at 03:50:20PM +0200, Till Maas wrote:
On Di Juli 10 2007, Richard W.M. Jones wrote:
> Till Maas wrote:
> > What I did so far was creating a new machine with a Fedora Live CD Image
> > and booted it. When I hit the Pause button, it appeared to be pressed,
> > but nothing happened. The machine still responded and the following error
> > appeared on the commandline, where I started virt-manager:
> >
> > -------------
> > libvir: QEMU error : operation failed: suspend operation failed
> > Traceback (most recent call last):
> > File "/usr/share/virt-manager/virtManager/console.py", line 389,
in
> > control_vm_pause
> > self.vm.suspend()
> > File "/usr/share/virt-manager/virtManager/domain.py", line 365, in
> > suspend self.vm.suspend()
> > File "/usr/lib/python2.5/site-packages/libvirt.py", line 350, in
> > suspend if ret == -1: raise libvirtError ('virDomainSuspend() failed',
> > dom=self) libvirt.libvirtError: virDomainSuspend() failed operation
> > failed: suspend operation failed
> > --------------
>
> This is a bug. Do you know what version of libvirt & virt-manager this
> happens with? Suspend _ought_ to work with QEMU with libvirt >= 0.2.0.
I am using an uptodate Fedora 7:
dkms-kqemu-1.3.0-0.2.pre11
qemu-0.9.0-2.fc7
libvirt-0.2.3-1.fc7
there is a 0.3.0-1.fc7 in Testing, could you check it out ?
Daniel
--
Red Hat Virtualization group http://redhat.com/virtualization/
Daniel Veillard | virtualization library http://libvirt.org/
veillard(a)redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
9:56 a.m.
On Di Juli 10 2007, Daniel Veillard wrote:
there is a 0.3.0-1.fc7 in Testing, could you check it out ?
With this version the last line number changed:
------------
libvir: QEMU error test123: suspend operation failed
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/console.py", line 389, in
control_vm_pause
self.vm.suspend()
File "/usr/share/virt-manager/virtManager/domain.py", line 365, in suspend
self.vm.suspend()
File "/usr/lib/python2.5/site-packages/libvirt.py", line 359, in suspend
if ret == -1: raise libvirtError ('virDomainSuspend() failed', dom=self)
libvirt.libvirtError: virDomainSuspend() failed suspend operation failed
------------
Regards,
Till
4:39 a.m.
Till Maas wrote:
On Di Juli 10 2007, Daniel Veillard wrote:
> there is a 0.3.0-1.fc7 in Testing, could you check it out ?
With this version the last line number changed:
------------
libvir: QEMU error test123: suspend operation failed
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/console.py", line 389, in
control_vm_pause
self.vm.suspend()
File "/usr/share/virt-manager/virtManager/domain.py", line 365, in suspend
self.vm.suspend()
File "/usr/lib/python2.5/site-packages/libvirt.py", line 359, in suspend
if ret == -1: raise libvirtError ('virDomainSuspend() failed', dom=self)
libvirt.libvirtError: virDomainSuspend() failed suspend operation failed
------------
This seems to be a problem with virt-manager calling domainSuspend twice
in a row. See:
https://www.redhat.com/archives/libvir-list/2007-July/msg00119.html
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=247755
Rich.
--
Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/
Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod
Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in
England and Wales under Company Registration No. 03798903
9:28 a.m.
On Tue, Jul 10, 2007 at 02:25:47PM +0100, Richard W.M. Jones wrote:
[Moved to libvir-list. The original thread was on fedora-devel-list,
starting here:
https://www.redhat.com/archives/fedora-devel-list/2007-July/thread.html#0...]
Till Maas wrote:
>On Di Juli 10 2007, Richard W.M. Jones wrote:
>>Till Maas wrote:
>>>The idea is imho great, but for me with qemu it does not work properly.
>>I'd really like to help out here. Did you get any error messages?
>
>The first problem is, that it seems to be a tool to create persisten
>virtual machines, e.g. virtual servers, but most of the time I only want
>to boot a live cd, e.g. a Fedora one. But virt-manager seems to demand an
>virtual HD drive. I only tested it twice or so, but it looked not
>promising.
The next version of virt-install will support this explicitly. I am
reliably assured that it should work in qemu & Xen.
Support is not there yet in virt-manager.
If you want to watch for updates, the feature request ticket is here
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=236782
This is a bug. Do you know what version of libvirt & virt-manager this
happens with? Suspend _ought_ to work with QEMU with libvirt >= 0.2.0.
>Then when I shut down the machine and clicked on "run", it did not boot
>the ISO Image I selected while creating the machine, but only complained
>that it could not boot from HD (which is true, because I did not install
>anything to the HD)
>
>Then I wanted to delete the machine, but the "Delete" button was still
>greyed out, even when I shut it down (Imho it should be available all the
>time and provide a warning that the machine needs to be shut down before
>it can be deleted). When I closed virt-manager and opened it again, then I
>was able to delete the machine.
Yeah, that's a bug in the code dealing with widget sensitivity. It forgets
to re-activate the delete button when the guest shuts down. Just select a
different guest, and then re-select the stopped one - it should enable the
button again then
>But I cannot find a way to add an iso image to the machine or
make it boot
>the iso image I selected at creation time.
I haven't played with live CDs & virt-manager at all, but I'll have a
go. What live CD were you trying?
Live CDs aren't really supported yet - it will boot the CD the first time,
but it expects you to perform an install to the disk, so on sequent boots
it will boot of harddisk. THis is basically the problem BZ 236782 is asking
to be addressed.
>Also the network selection seems not to work, when I want to add
a network
>interface, I can choose between virtual and shared device, but both only
>have an empty list, where I have to select something to be able to click
>on "Forward".
This is another bug. If you get me the version of virt-manager, I'll
look into it.
I think this probably happens if using QEMU in per-user (unprivileged)
mode. In that case only slirp style networking is available so it should
not actually show that screen at all.
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
9:45 a.m.
On Di Juli 10 2007, Daniel P. Berrange wrote:
Live CDs aren't really supported yet - it will boot the CD the
first time,
but it expects you to perform an install to the disk, so on sequent boots
it will boot of harddisk. THis is basically the problem BZ 236782 is asking
to be addressed.
This is not only a problem with LiveCDs, but also when an installation fails
or one wants to update a system, because there is no way to change or add a
CD to a virtual machine, like it is possible to add another harddisk or
network card. Is this within the scope of BZ 236782, too?
Regards,
Till
9:56 a.m.
On Tue, Jul 10, 2007 at 04:45:25PM +0200, Till Maas wrote:
On Di Juli 10 2007, Daniel P. Berrange wrote:
> Live CDs aren't really supported yet - it will boot the CD the first time,
> but it expects you to perform an install to the disk, so on sequent boots
> it will boot of harddisk. THis is basically the problem BZ 236782 is asking
> to be addressed.
This is not only a problem with LiveCDs, but also when an installation fails
or one wants to update a system, because there is no way to change or add a
CD to a virtual machine, like it is possible to add another harddisk or
network card. Is this within the scope of BZ 236782, too?
Not entirely - related, but different issues. We need to make it possible
to add a CDROM device to an existing guest:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=245205
And add ability to change CDROM media on the fly. There's a bug for this
too, but unfortunately its marked private.
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
6378
days inactive
6379
days old
7 comments
4 participants
participants (4)
-
Daniel P. Berrange -
Daniel Veillard -
Richard W.M. Jones -
Till Maas