Bug#435039: closed by Miguel Gea Milvaques [EMAIL PROTECTED] (qemuctl: fails to start)

2007-08-10 Thread Iván Zaera Avellón
I have tried to uninstall completely qemu-launcher and qemuctl and install
it over again and still doesn't work.

This is the command line of qemuctl as launched from qemu-launcher:

/usr/bin/qemuctl -boot c -m 768 -hda '/var/chroot/qemu-windowsxp' -cdrom
'/dev/dvd' -net nic,vlan=0 -net user,vlan=0 -smb /home/ivan -localtime
-soundhw sb16 -std-vga -kernel-kqemu -usb -usbdevice host:04b8:0007 

I have run strace on it and I have found that qemu is telling qemuctl that
parameter -kernel-kqemu is invalid. It is clearly a qemu-launcher error.

This is what is happening when I select in qemu-launcher:
  -System type = x86_64
  -Provide a control panel = checked
  -Acceleration = full

qemuctl is launched with -kernel-kqemu parameter and qemuctl tries to
launch /usr/bin/qemu, which complains about the parameters and makes qemuctl
disappear. It would be a good idea to tell something to the user about the
error in qemuctl.

This is what is happening when I select in qemu-launcher:
  -System type = x86_64
  -Provide a control panel = unchecked
  -Acceleration = full

qemu is launched via /usr/bin/qemu-system-x86_64 which, in fact, DOES
understand the -kernel-kqemu parameter, thus working correctly.

So, you can reproduce the problem with the first configuration.

I suppose that two things should be done:

1) Improve qemuctl so it says something whenever it detects an error of qemu
2) Change qemu-launcher so it tells qemuctl to launch the proper qemu flavor


Bug#435039: closed by Miguel Gea Milvaques [EMAIL PROTECTED] (qemuctl: fails to start)

2007-08-09 Thread Ivan Zaera Avellon
Hi Miguel:

I'm sorry, I didn't explain the problem correctly. I'm not launching qemuctl 
from the command line, I'm launching qemu-launcher from a terminal, and then 
it launches qemuctl when I start the virtual machine. 

I run qemu-launcher from a terminal to see the stdout/err output of 
qemu-launcher and qemuctl (which is the one I pasted in the bug). 

By the way, I have the same distro in a laptop (Debian testing) based on i386 
and qemuctl works fine. It only fails in my AMD64 distro. I can't figure out 
why this difference.


El Jueves, 9 de Agosto de 2007 00:39, Debian Bug Tracking System escribió:
 This is an automatic notification regarding your Bug report
 #435039: qemuctl: fails to start,
 which was filed against the qemuctl package.

 It has been closed by Miguel Gea Milvaques [EMAIL PROTECTED].

 Their explanation is attached below.  If this explanation is
 unsatisfactory and you have not received a better one in a separate
 message then please contact Miguel Gea Milvaques [EMAIL PROTECTED] by
 replying to this email.

 Debian bug tracking system administrator
 (administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#435039: closed by Miguel Gea Milvaques [EMAIL PROTECTED] (qemuctl: fails to start)

2007-08-09 Thread Miguel Gea Milvaques
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Ivan Zaera Avellon wrote:
 Hi Miguel:
 
 I'm sorry, I didn't explain the problem correctly. I'm not launching qemuctl 
 from the command line, I'm launching qemu-launcher from a terminal, and then 
 it launches qemuctl when I start the virtual machine. 
 
 I run qemu-launcher from a terminal to see the stdout/err output of 
 qemu-launcher and qemuctl (which is the one I pasted in the bug). 
 
 By the way, I have the same distro in a laptop (Debian testing) based on i386 
 and qemuctl works fine. It only fails in my AMD64 distro. I can't figure out 
 why this difference.

I have AMD64 and I have no problems using qemu-launcher with qemuctl.
Maybe you have any configuration problem in your qemu-launcher? Which
config do you have?
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGu3VUNTNQylgICMQRAqG/AKDHehtcxD+AHy9/6tthG7tM3BQMkwCeO0AT
Gmez2M71QQ/CZjjELBghzLY=
=7b03
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]