Re: [Qemu-devel] Serial Console / NoGraphic

2007-09-25 Thread GUERRAZ Francois
Hi Michael,

About your VNC problems : I have had problems w/ vnc too (see
http://qemu-forum.ipi.fi/viewtopic.php?p=10468) but had no answer as
well...

Anyway, it's better to do like you're doing : installing a VNC server
inside the vm is much better because you can have authentication and
such things... and no mouse / keyboard issues.

I'm using Qemu VNC server for the Qemu supervisor I'm developing (see
http://sourceforge.net/projects/casimir-web/ ) and it works very well
this way : ask qemu vnc to listen in a socket (-vnc
unix:/tmp//vmXXX.vnc) and use socat to make it listen on a tcp port when
you need it (socat TCP4-LISTEN:port UNIX-CONNECT:socket), socat will
die when the connexion closes, not Qemu :)
I don't know if it is because of the socat thing, but I don't have
problems anymore...

Le mardi 25 septembre 2007 à 11:11 +0100, Michael McConnell a écrit :
 Clemens Kolbitsch wrote:
  hi!
  i've been trying around for quite some time now trying to start qemu 
  without 
  the graphic screen... can someone tell me exactly what I'm supposed to do??
  
  i want to redirect the output of my i386 debian linux to my host-console 
  (also 
  a i386 debian) to fully see the output of a kernel panic (see previous 
  messages i have posted).
  
  i'm starting qemu:
  
  qemu -hda myimage -boot c -kernel-kqemu -kernel mykernel -initrd 
  myinitrd -append root=/dev/hda1 console=/dev/ttyS0 -nographic
  
  after tons of trial-and-error i finally got my system to boot, however, the 
  login-screen is not displayed (i see all output of the starting system up 
  until the login:). how do i connect to the serial line now to get to 
  the 
  login??
 
 Add this to /etc/inittab in the guest system:
 co:2345:respawn:/sbin/agetty ttyS0 9600 vt100-nav
 
 Without that it's only going to put the login prompts on the (now 
 hidden) virtual consoles.
 
 The (emulated) hardware display still exists, it's just not shown. I use 
 just such a setup for a Win2000 virtual-machine that's accessible by 
 VNC. I've had issues with QEMU's own VNC server (it crashes with a core 
 dump on disconnection, and no-one on the list was remotely interested) 
 so instead I run UltraVNC within Win2000 and connect to that instead.
 





Re: [Qemu-devel] [PATCH 3/4] Add support for HPET periodic timer.

2007-09-03 Thread GUERRAZ Francois
Hello,

Can you confirm to me that if I have only one periodic timer on my
motherboard I can only have one qemu-instance running using hpet?

Thanks.

François.

Le mardi 21 août 2007 à 21:40 +0200, Luca a écrit :
 On 8/21/07, Matthew Kent [EMAIL PROTECTED] wrote:
  On Sat, 2007-18-08 at 01:11 +0200, Luca Tettamanti wrote:
   plain text document attachment (clock-hpet)
   Linux operates the HPET timer in legacy replacement mode, which means that
   the periodic interrupt of the CMOS RTC is not delivered (qemu won't be 
   able
   to use /dev/rtc). Add support for HPET (/dev/hpet) as a replacement for 
   the
   RTC; the periodic interrupt is delivered via SIGIO and is handled in the
   same way as the RTC timer.
  
   Signed-off-by: Luca Tettamanti [EMAIL PROTECTED]
 
  I must be missing something silly here.. should I be able to open more
  than one instance of qemu with -clock hpet? Because upon invoking a
  second instance of qemu HPET_IE_ON fails.
 
 It depends on your hardware. Theoretically it's possible, but I've yet
 to see a motherboard with more than one periodic timer.
 
 dmesg | grep hpet should tell you something like:
 
 hpet0: 3 64-bit timers, 14318180 Hz
 
 Luca
 
 
 





Re: [Qemu-devel] Using Microsoft-provided Windows images

2007-08-02 Thread GUERRAZ Francois
Hello.

Yes but if I understood well, you can't boot on the SCSI device because
of BIOS limitations right?
So the problem remains ... :)

Maybe if you install GRUB and tell him to boot on SCSI.. :)

---
François.

Le mercredi 01 août 2007 à 10:55 -0500, [EMAIL PROTECTED] a écrit :
 on x86, qemu by default does not emulate a scsi device.
 
 if you look at my last set of postings, you will see a patch set for adding 
 scsi controllers on demand.
 
 its got some code formatting issues, so i understand why it hasnt been merged 
 as of yet. i intend to publish a new version in the next couple of days.
 
 Julia Longtin [EMAIL PROTECTED]
 
 On Wed, Aug 01, 2007 at 04:33:31PM +0200, GUERRAZ Francois wrote:
  Hello.
  
  Micro$oft's 64bits OSes are known to be problematic w/ kvm.
  
  I guess that the main problem w/ Qemu is that Microsoft Virtual Server
  can emulate a SCSI controller and Qemu cannot... I havent checked but I
  bet they installed their VM's with just SCSI drivers...
  Try to install IDE drivers from VM Ware and then to boot from QEMU.
  Also, try to disable ACPI (update the computer driver to Standard PC
  if available)
  
  Regards,
  
  François.
  
  Le mercredi 01 août 2007 à 23:35 +0930, Dan Shearer a écrit :
   I have been playing around with the demonstration Windows images
   downloadable from Microsoft just to see how hard it would be to use the
   OSs they provide. The images are designed for Microsoft Virtual Server,
   but can be successfully converted to qcow2 and vhdx using qemu-img. QEMU
   won't boot the images (not a difficult problem, I think) but VMware can.
   I'll try other free virtualisation systems at some point.
   
   See http://shearer.org/Microsoft_Demo_VMs for my notes so far.
   
  
  
  
 
 
 





Re: [Qemu-devel] Using Microsoft-provided Windows images

2007-08-01 Thread GUERRAZ Francois
Hello.

Micro$oft's 64bits OSes are known to be problematic w/ kvm.

I guess that the main problem w/ Qemu is that Microsoft Virtual Server
can emulate a SCSI controller and Qemu cannot... I havent checked but I
bet they installed their VM's with just SCSI drivers...
Try to install IDE drivers from VM Ware and then to boot from QEMU.
Also, try to disable ACPI (update the computer driver to Standard PC
if available)

Regards,

François.

Le mercredi 01 août 2007 à 23:35 +0930, Dan Shearer a écrit :
 I have been playing around with the demonstration Windows images
 downloadable from Microsoft just to see how hard it would be to use the
 OSs they provide. The images are designed for Microsoft Virtual Server,
 but can be successfully converted to qcow2 and vhdx using qemu-img. QEMU
 won't boot the images (not a difficult problem, I think) but VMware can.
 I'll try other free virtualisation systems at some point.
 
 See http://shearer.org/Microsoft_Demo_VMs for my notes so far.
 





[Qemu-devel] Qemu 0.9 segfault

2007-06-27 Thread GUERRAZ Francois
Hi everybody.

Could you please take a look at this post on the forum? No one was able
to answer me on that topic... Has is been fixed in the CVS version by
chance? 

http://qemu-forum.ipi.fi/viewtopic.php?t=3344

Thank you very much for this wonderful software anyway :)

See ya.

François.