[Qemu-devel] Solaris/x86 report

2007-08-04 Thread Nigel Horne

Solaris/x86 10 guest installs OK on Linux/x86 host, well done!

The only down side is I'm yet to get networking up.

-Nigel
begin:vcard
fn:Nigel Horne
n:Horne;Nigel
org:NJH Music
adr:Pogmoor;;28 Wharfedale Road;Barnsley;South Yorkshire;S75 2LJ;UK
email;internet:[EMAIL PROTECTED]
tel;fax:+44 870 705 9334
note:Skype: nigelhorne
x-mozilla-html:FALSE
url:http://www.bandsman.co.uk
version:2.1
end:vcard



Re: [Qemu-devel] Solaris/x86 report

2007-08-04 Thread Jonathan Kalbfeld
You should be able to do qemu -hda yourdiskimage.qcow2 -m 512 -net user \
-net nic,model=rtl8139

For solaris 10/x86

On 8/4/07, Nigel Horne <[EMAIL PROTECTED]> wrote:
>
> Solaris/x86 10 guest installs OK on Linux/x86 host, well done!
>
> The only down side is I'm yet to get networking up.
>
> -Nigel
>
>


-- 
--
Jonathan Kalbfeld
+1 323 620 6682


Re: [Qemu-devel] Solaris/x86 report

2007-08-04 Thread Nigel Horne

Jonathan DeKalb's wrote:

You should be able to do qemu -hda yourdiskimage.qcow2 -m 512 -net user \
-net nic,model=rtl8139


Yes indeed that is the sort of thing I've been trying without success.


Jonathan Kalbfeld
+1 323 620 6682


-Nigel

--
Nigel Horne. Arranger, Adjudicator, Band Trainer, Composer, Tutor, Typesetter.
NJH Music, Barnsley, UK.  ICQ#20252325
[EMAIL PROTECTED] http://www.bandsman.co.uk
begin:vcard
fn:Nigel Horne
n:Horne;Nigel
org:NJH Music
adr:Pogmoor;;28 Wharfedale Road;Barnsley;South Yorkshire;S75 2LJ;UK
email;internet:[EMAIL PROTECTED]
tel;fax:+44 870 705 9334
note:Skype: nigelhorne
x-mozilla-html:FALSE
url:http://www.bandsman.co.uk
version:2.1
end:vcard



[Qemu-devel] qemu cpu-exec.c hw/slavio_intctl.c hw/sun4m.c t...

2007-08-04 Thread Blue Swirl
CVSROOT:/cvsroot/qemu
Module name:qemu
Changes by: Blue Swirl   07/08/04 10:50:30

Modified files:
.  : cpu-exec.c 
hw : slavio_intctl.c sun4m.c 
target-sparc   : cpu.h 

Log message:
 Fix Sparc32 interrupt handling

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/cpu-exec.c?cvsroot=qemu&r1=1.109&r2=1.110
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/slavio_intctl.c?cvsroot=qemu&r1=1.17&r2=1.18
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/sun4m.c?cvsroot=qemu&r1=1.46&r2=1.47
http://cvs.savannah.gnu.org/viewcvs/qemu/target-sparc/cpu.h?cvsroot=qemu&r1=1.46&r2=1.47




Re: [Qemu-devel] Sparc guest - SCSI

2007-08-04 Thread Blue Swirl
I reworked the interrupt handling so that both e2fsck and SMP work.
Previously there may have been lost or spurious interrupts, now they
should be fixed. I pushed the interrupt priority handling   from
SLAVIO to CPU.




[Qemu-devel] qemu/hw m48t59.c

2007-08-04 Thread Blue Swirl
CVSROOT:/cvsroot/qemu
Module name:qemu
Changes by: Blue Swirl   07/08/04 10:56:26

Modified files:
hw : m48t59.c 

Log message:
 Use UTC/localtime flag in M48Txx

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/qemu/hw/m48t59.c?cvsroot=qemu&r1=1.11&r2=1.12




Re: [Qemu-devel] Patch: let qemu work with latest bochsbios

2007-08-04 Thread Bernhard Kauer
On Wed, Aug 01, 2007 at 11:02:58AM -0500, Anthony Liguori wrote:
> Bernhard Kauer wrote:
>> -boot_device = 'c'; /* to prevent confusion by the BIOS */
>> +//boot_device = 'c'; /* to prevent confusion by the BIOS */
>>  }
>>   
>
> Please don't comment out code.  Just delete it.

You are right. At the time i changed it I just wondered what the
comment means...


Bernhard
Index: vl.c
===
RCS file: /sources/qemu/qemu/vl.c,v
retrieving revision 1.323
diff -u -r1.323 vl.c
--- vl.c	29 Jul 2007 17:57:25 -	1.323
+++ vl.c	4 Aug 2007 13:05:28 -
@@ -7828,7 +7828,6 @@
 	fprintf(stderr, "No valid PXE rom found for network device\n");
 	exit(1);
 	}
-	boot_device = 'c'; /* to prevent confusion by the BIOS */
 }
 #endif
 
Index: hw/pc.c
===
RCS file: /sources/qemu/qemu/hw/pc.c,v
retrieving revision 1.81
diff -u -r1.81 pc.c
--- hw/pc.c	6 Jun 2007 16:26:13 -	1.81
+++ hw/pc.c	4 Aug 2007 13:05:29 -
@@ -197,6 +197,9 @@
 case 'd':
 rtc_set_memory(s, 0x3d, 0x03); /* CD-ROM boot */
 break;
+case 'n':
+rtc_set_memory(s, 0x3d, 0x04); /* Network boot */
+break;	
 }
 
 /* floppy type */


[Qemu-devel] merging kqemu into mainline kernel?

2007-08-04 Thread dragoran
Hello,
Is it planned to submit kqemu to lkml for inclusion into the mainline
kernel?
if not why?
if yes any idea when? is it possible to try to get it in 2.6.24 ?


Re: [Qemu-devel] merging kqemu into mainline kernel?

2007-08-04 Thread Ricardo Almeida
Hi,
I'm just a user...

Is it planned to submit kqemu to lkml for inclusion into the mainline
> kernel?


Never seen anyone talking about this...

if not why?


Maybe because KVM was included (
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7)


if yes any idea when? is it possible to try to get it in 2.6.24 ?
>

I don't know if Linus would accept it. As I said, KVM was included, although
kqemu as the advantage of working in older hardware (without AMD-V or Intel
equivalent virtualization instructions).
Maybe if it was possible to make merge kqemu into KVM to take the best of
the two... But I don't know anything about KVM nor kqemu code...

Regards,
Ricardo Almeida


Re: [Qemu-devel] merging kqemu into mainline kernel?

2007-08-04 Thread dragoran
On 8/4/07, Ricardo Almeida <[EMAIL PROTECTED]> wrote:
>
> Hi,
> I'm just a user...
>
> Is it planned to submit kqemu to lkml for inclusion into the mainline
> > kernel?
>
>
> Never seen anyone talking about this...
>
> if not why?
>
>
> Maybe because KVM was included 
> (http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=6aa8b732ca01c3d7a54e93f4d701b8aabbe60fb7
> )
>

I know that

if yes any idea when? is it possible to try to get it in 2.6.24 ?
> >
>
> I don't know if Linus would accept it. As I said, KVM was included,
> although kqemu as the advantage of working in older hardware (without AMD-V
> or Intel equivalent virtualization instructions).
> Maybe if it was possible to make merge kqemu into KVM to take the best of
> the two... But I don't know anything about KVM nor kqemu code...


thats the reason I  (and many other users) want to see it merged.
for ex. the fedora kernel maintainers don't want to add it until its part of
the upstream kernel.