Re: QEMU crashes
Yes, the error is the 1st time said bridge is created. Call it a wart. ;-)
--
Todd Fries .. [EMAIL PROTECTED]
_
| \ 1.636.410.0632 (voice)
| Free Daemon Consulting, LLC \ 1.405.227.9094 (voice)
| http://FreeDaemonConsulting.com \ 1.866.792.3418 (FAX)
| ..in support of free software solutions. \ 250797 (FWD)
| \
\\
37E7 D3EB 74D0 8D66 A68D B866 0326 204E 3F42 004A
http://todd.fries.net/pgp.txt
Penned by Frank Bax on 20081203 22:31.57, we have:
Hi Todd:
You asked for feedback. Most of the time; qemu produces:
{tun0 (bridge0 - em0)}
But sometimes it produces:
{tun0 (bridge0 - em0)brconfig: bridge0: No such process
brconfig: bridge0: No such process
}
Network access still works, despite the error message.
Frank
On 2008-Nov-04, Todd T. Fries wrote:
Just out of curiosity, humor me, run qemu as root with the following added
options:
-net nic,vlan=0 -net tap,vlan=0
I've observed that at some point user mode networking has started segv'ed on
amd64 when running any qemu guest, and am sorry to report I have not yet
tracked down the source of the issue..
Please let me know if you have other experiences.
Thanks,
Re: QEMU crashes
And you are smart enough to fix it ;-)
It is ugly to see it fly by.
On Thu, Dec 04, 2008 at 06:39:50AM -0600, [EMAIL PROTECTED] wrote:
Yes, the error is the 1st time said bridge is created. Call it a wart. ;-)
--
Todd Fries .. [EMAIL PROTECTED]
_
| \ 1.636.410.0632 (voice)
| Free Daemon Consulting, LLC \ 1.405.227.9094 (voice)
| http://FreeDaemonConsulting.com \ 1.866.792.3418 (FAX)
| ..in support of free software solutions. \ 250797 (FWD)
| \
\\
37E7 D3EB 74D0 8D66 A68D B866 0326 204E 3F42 004A
http://todd.fries.net/pgp.txt
Penned by Frank Bax on 20081203 22:31.57, we have:
Hi Todd:
You asked for feedback. Most of the time; qemu produces:
{tun0 (bridge0 - em0)}
But sometimes it produces:
{tun0 (bridge0 - em0)brconfig: bridge0: No such process
brconfig: bridge0: No such process
}
Network access still works, despite the error message.
Frank
On 2008-Nov-04, Todd T. Fries wrote:
Just out of curiosity, humor me, run qemu as root with the following added
options:
-net nic,vlan=0 -net tap,vlan=0
I've observed that at some point user mode networking has started segv'ed
on
amd64 when running any qemu guest, and am sorry to report I have not yet
tracked down the source of the issue..
Please let me know if you have other experiences.
Thanks,
Re: QEMU crashes
See if this works any better.
--- emulators/qemu/files/qemu-ifup
+++ emulators/qemu/files/qemu-ifup
@@ -16,6 +16,15 @@ echo -n {$1 ($BRIDGE - $ETHER)
# Set the tun device into layer2 mode
$SUDO ifconfig $1 link0 up
+# setup up $ETHER incase it wasn't created before
+if ! ifconfig $ETHER /dev/null 21; then
+ if ! $SUDO ifconfig $ETHER create /dev/null 21; then
+ echo $ETHER creation failed, errors will follow
+ else
+ $SUDO ifconfig $ETHER up
+ fi
+fi
+
# Set up our bridge
$SUDO ifconfig $1 group tun /dev/null 21
$SUDO ifconfig $BRIDGE create /dev/null 21 {
--
Todd Fries .. [EMAIL PROTECTED]
_
| \ 1.636.410.0632 (voice)
| Free Daemon Consulting, LLC \ 1.405.227.9094 (voice)
| http://FreeDaemonConsulting.com \ 1.866.792.3418 (FAX)
| ..in support of free software solutions. \ 250797 (FWD)
| \
\\
37E7 D3EB 74D0 8D66 A68D B866 0326 204E 3F42 004A
http://todd.fries.net/pgp.txt
Penned by Marco Peereboom on 20081204 7:22.30, we have:
| And you are smart enough to fix it ;-)
|
| It is ugly to see it fly by.
|
| On Thu, Dec 04, 2008 at 06:39:50AM -0600, [EMAIL PROTECTED] wrote:
| Yes, the error is the 1st time said bridge is created. Call it a wart. ;-)
| --
| Todd Fries .. [EMAIL PROTECTED]
|
| _
| | \ 1.636.410.0632 (voice)
| | Free Daemon Consulting, LLC \ 1.405.227.9094 (voice)
| | http://FreeDaemonConsulting.com \ 1.866.792.3418 (FAX)
| | ..in support of free software solutions. \ 250797 (FWD)
| | \
| \\
|
|37E7 D3EB 74D0 8D66 A68D B866 0326 204E 3F42 004A
| http://todd.fries.net/pgp.txt
|
| Penned by Frank Bax on 20081203 22:31.57, we have:
| Hi Todd:
|
| You asked for feedback. Most of the time; qemu produces:
|
|{tun0 (bridge0 - em0)}
|
| But sometimes it produces:
|
|{tun0 (bridge0 - em0)brconfig: bridge0: No such process
| brconfig: bridge0: No such process
| }
|
| Network access still works, despite the error message.
|
| Frank
|
|
| On 2008-Nov-04, Todd T. Fries wrote:
| Just out of curiosity, humor me, run qemu as root with the following
added
| options:
|
|-net nic,vlan=0 -net tap,vlan=0
|
| I've observed that at some point user mode networking has started
segv'ed on
| amd64 when running any qemu guest, and am sorry to report I have not yet
| tracked down the source of the issue..
|
| Please let me know if you have other experiences.
|
| Thanks,
|
Re: QEMU crashes
Ok, based on some other feedback from Stuart, here is a new diff to test
that should work better ;-)
--- emulators/qemu/files/qemu-ifup
+++ emulators/qemu/files/qemu-ifup
@@ -16,16 +16,19 @@ echo -n {$1 ($BRIDGE - $ETHER)
# Set the tun device into layer2 mode
$SUDO ifconfig $1 link0 up
+# setup up $ETHER incase it wasn't created before
+if ! ifconfig $ETHER /dev/null 21; then
+ if ! $SUDO ifconfig $ETHER create /dev/null 21; then
+ echo $ETHER creation failed, errors will follow
+ else
+ $SUDO ifconfig $ETHER up
+ fi
+fi
+
# Set up our bridge
$SUDO ifconfig $1 group tun /dev/null 21
-$SUDO ifconfig $BRIDGE create /dev/null 21 {
- # Only add rules if the bridge creation succeeds; otherwise
- # duplicate rules get loaded each time qemu starts
- # The following two block carp packets from wasting cpu cycles inside the
- # qemu sessions, remove if testing carp inside qemu
- $SUDO brconfig $BRIDGE rule block in on $ETHER dst 33:33:0:0:0:12
- $SUDO brconfig $BRIDGE rule block in on $ETHER dst 01:00:5e:00:00:12
-}
+# Creation only happens once; if it was created before .. this will fail
+$SUDO ifconfig $BRIDGE create /dev/null 21 create=1
# Since we can specify ETHER and BRIDGE above, its possible that
# this tun interface or this physical interface was setup as part of
# a different bridge earlier, and that is never cleaned up, so we have
@@ -39,4 +42,13 @@ do
done
$SUDO brconfig $BRIDGE add $ETHER up
$SUDO brconfig $BRIDGE add $1 up || true
+# can not add rules until $ETHER is part of the $BRIDGE
+[ -n $created ] {
+ # Only add rules if the bridge creation succeeds; otherwise
+ # duplicate rules get loaded each time qemu starts
+ # The following two block carp packets from wasting cpu cycles inside the
+ # qemu sessions, remove if testing carp inside qemu
+ $SUDO brconfig $BRIDGE rule block in on $ETHER dst 33:33:0:0:0:12
+ $SUDO brconfig $BRIDGE rule block in on $ETHER dst 01:00:5e:00:00:12
+}
echo }
--
Todd Fries .. [EMAIL PROTECTED]
_
| \ 1.636.410.0632 (voice)
| Free Daemon Consulting, LLC \ 1.405.227.9094 (voice)
| http://FreeDaemonConsulting.com \ 1.866.792.3418 (FAX)
| ..in support of free software solutions. \ 250797 (FWD)
| \
\\
37E7 D3EB 74D0 8D66 A68D B866 0326 204E 3F42 004A
http://todd.fries.net/pgp.txt
Penned by Frank Bax on 20081203 22:31.57, we have:
Hi Todd:
You asked for feedback. Most of the time; qemu produces:
{tun0 (bridge0 - em0)}
But sometimes it produces:
{tun0 (bridge0 - em0)brconfig: bridge0: No such process
brconfig: bridge0: No such process
}
Network access still works, despite the error message.
Frank
On 2008-Nov-04, Todd T. Fries wrote:
Just out of curiosity, humor me, run qemu as root with the following added
options:
-net nic,vlan=0 -net tap,vlan=0
I've observed that at some point user mode networking has started segv'ed on
amd64 when running any qemu guest, and am sorry to report I have not yet
tracked down the source of the issue..
Please let me know if you have other experiences.
Thanks,
Re: QEMU crashes
Todd T. Fries wrote: Just out of curiosity, humor me, run qemu as root with the following added options: -net nic,vlan=0 -net tap,vlan=0 I've observed that at some point user mode networking has started segv'ed on amd64 when running any qemu guest, and am sorry to report I have not yet tracked down the source of the issue.. Please let me know if you have other experiences. Thanks, This was interesting; I learned some new things. First I tried su -; then qemu ... - but this results in sdl errors. The above -net options cause /etc/qemu-ifup to be invoked; it took me a few minutes to figure out how to make that work properly. When I try export ETHER=em0 ; sudo -E qemu ...; I am now able to send my files out of the guest - THANKS. One problem - when I shutdown the guest, I get: /etc/qemu-ifdown: could not launch network script I run the script manually no problem. BTW: Since I first started using Win98 under qemu about a year ago; I noticed that Win98 guest does not keep accurate time? It looks like only every other second is counted; so that after 2 hours, Win98 clock advanced only one hour. Does this also happen on other guests? Frank
QEMU crashes
I've been using qemu to run a Win98 guest on i386 host for about a year. On Aug.2, I installed an i386 snapshot that was a few days old. Since then, I've been running a Win98 guest on qemu-0.9.1p3 with no issues. Sometime over the past 12 months I realised I could be running amd64 on my Core2Duo processor; so (using purchased cdrom's) I made the switch to 8.4 amd64 release over the weekend. Not sure if I did it correctly; but I did it as an upgrade, then deleted and added all packages. Seems to be working fine so far; except for some problems with qemu. I notice that both -no-kqemu and -kernel-kqemu result in invalid option. Am I allowed to run a guest like Win98 on host running amd64? It seems to work ok when running a couple of apps (win dos); as long as there is no network access. The Win98 guest system crashes (segmentation fault, core dumped) when I access internet from the guest. This can be either accessing a website with IE or running pscp (an scp program for windows, from makers of PuTTY). Ping does not cause guest to crash. Ping to 10.0.2.2 (host) works (time is 1ms). Ping to internet ip address results in Request timed out. Ping to name does manage dns lookup; but still gets Request timed out. When the Win98 guest crashes; my mouse pointer goes with it. I'm using icewm. I manage to shutdown other apps with keyboard shortcuts; then restart X. Is there a way to get mouse pointer back? kqemu is not installed. I don't know what other information about this issue to include here. I'm not sure if a dmesg is appropriate; but here it is: OpenBSD 4.4 (GENERIC.MP) #1812: Tue Aug 12 17:22:53 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3206639616 (3058MB) avail mem = 3109740544 (2965MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (68 entries) bios0: vendor LENOVO version 7IET30WW (1.11 ) date 07/13/2007 bios0: LENOVO 8744J2U acpi0 at bios0: rev 2 acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) LURT(S3) DURT(S3) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1994.62 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR,LONG cpu0: 4MB 64b/line 16-way L2 cache cpu0: apic clock running at 166MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1994.34 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR,LONG cpu1: 4MB 64b/line 16-way L2 cache ioapic0 at mainbus0 apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus 4 (EXP2) acpiprt5 at acpi0: bus 12 (EXP3) acpiprt6 at acpi0: bus 21 (PCI1) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2 acpicpu1 at acpi0: C3, C2 acpitz0 at acpi0: critical temperature 127 degC acpitz1 at acpi0: critical temperature 100 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 not present acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock at acpi0 not configured acpivideo at acpi0 not configured acpivideo at acpi0 not configured cpu0: unknown Enhanced SpeedStep CPU, msr 0x06130c2806000c28 cpu0: using only highest and lowest power states cpu0: Enhanced SpeedStep 2000 MHz (1340 mV): speeds: 2000, 1000 MHz pci0 at mainbus0 bus 0: configuration mode 1 pchb0 at pci0 dev 0 function 0 Intel 82945GM Host rev 0x03 ppb0 at pci0 dev 1 function 0 Intel 82945GM PCIE rev 0x03: apic 1 int 16 (irq 11) pci1 at ppb0 bus 1 vga1 at pci1 dev 0 function 0 ATI Mobility FireGL V5250 rev 0x00 wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) agp0 at vga1: no integrated graphics drm at vga1 unsupported azalia0 at pci0 dev 27 function 0 Intel 82801GB HD Audio rev 0x02: apic 1 int 17 (irq 11) azalia0: codec[s]: Analog Devices/0x1981, Conexant/0x2bfa, using Analog Devices/0x1981 audio0 at azalia0 ppb1 at pci0 dev 28 function 0 Intel 82801GB PCIE rev 0x02: apic 1 int 20 (irq 11) pci2 at ppb1 bus 2 em0 at pci2 dev 0 function 0 Intel PRO/1000MT (82573L) rev 0x00: apic 1 int 16 (irq 11), address 00:1a:6b:6b:20:6c ppb2 at pci0 dev 28 function 1 Intel 82801GB PCIE rev 0x02: apic 1 int 21 (irq 11) pci3 at ppb2 bus 3 wpi0 at pci3 dev 0 function 0 Intel PRO/Wireless 3945ABG rev 0x02: apic 1 int 17 (irq 11),
Re: QEMU crashes
On Mon, Nov 3, 2008 at 9:07 PM, Frank Bax [EMAIL PROTECTED] wrote: I've been using qemu to run a Win98 guest on i386 host for about a year. On Aug.2, I installed an i386 snapshot that was a few days old. Since then, I've been running a Win98 guest on qemu-0.9.1p3 with no issues. Sometime over the past 12 months I realised I could be running amd64 on my Core2Duo processor; so (using purchased cdrom's) I made the switch to 8.4 amd64 release over the weekend. Not sure if I did it correctly; but I did it as an upgrade, then deleted and added all packages. Seems to be working fine so far; except for some problems with qemu. That is not the right way to do it, but probably didn't hurt too much. amd64 is not an upgrade, you should have done a clean install. Am I allowed to run a guest like Win98 on host running amd64? It seems to work ok when running a couple of apps (win dos); as long as there is no network access. I don't know. I've been running qemu on amd64 for a long time without issues. guests are openbsd (i386 and amd64) and freedos.
Re: QEMU crashes
Just out of curiosity, humor me, run qemu as root with the following added options: -net nic,vlan=0 -net tap,vlan=0 I've observed that at some point user mode networking has started segv'ed on amd64 when running any qemu guest, and am sorry to report I have not yet tracked down the source of the issue.. Please let me know if you have other experiences. Thanks, -- Todd Fries .. [EMAIL PROTECTED] _ | \ 1.636.410.0632 (voice) | Free Daemon Consulting, LLC \ 1.405.227.9094 (voice) | http://FreeDaemonConsulting.com \ 1.866.792.3418 (FAX) | ..in support of free software solutions. \ 250797 (FWD) | \ \\ 37E7 D3EB 74D0 8D66 A68D B866 0326 204E 3F42 004A http://todd.fries.net/pgp.txt Penned by Frank Bax on 20081103 21:07.44, we have: I've been using qemu to run a Win98 guest on i386 host for about a year. On Aug.2, I installed an i386 snapshot that was a few days old. Since then, I've been running a Win98 guest on qemu-0.9.1p3 with no issues. Sometime over the past 12 months I realised I could be running amd64 on my Core2Duo processor; so (using purchased cdrom's) I made the switch to 8.4 amd64 release over the weekend. Not sure if I did it correctly; but I did it as an upgrade, then deleted and added all packages. Seems to be working fine so far; except for some problems with qemu. I notice that both -no-kqemu and -kernel-kqemu result in invalid option. Am I allowed to run a guest like Win98 on host running amd64? It seems to work ok when running a couple of apps (win dos); as long as there is no network access. The Win98 guest system crashes (segmentation fault, core dumped) when I access internet from the guest. This can be either accessing a website with IE or running pscp (an scp program for windows, from makers of PuTTY). Ping does not cause guest to crash. Ping to 10.0.2.2 (host) works (time is 1ms). Ping to internet ip address results in Request timed out. Ping to name does manage dns lookup; but still gets Request timed out. When the Win98 guest crashes; my mouse pointer goes with it. I'm using icewm. I manage to shutdown other apps with keyboard shortcuts; then restart X. Is there a way to get mouse pointer back? kqemu is not installed. I don't know what other information about this issue to include here. I'm not sure if a dmesg is appropriate; but here it is: OpenBSD 4.4 (GENERIC.MP) #1812: Tue Aug 12 17:22:53 MDT 2008 [EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 3206639616 (3058MB) avail mem = 3109740544 (2965MB) mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.4 @ 0xe0010 (68 entries) bios0: vendor LENOVO version 7IET30WW (1.11 ) date 07/13/2007 bios0: LENOVO 8744J2U acpi0 at bios0: rev 2 acpi0: tables DSDT FACP SSDT ECDT TCPA APIC MCFG HPET SLIC BOOT SSDT SSDT SSDT SSDT acpi0: wakeup devices LID_(S3) SLPB(S3) LURT(S3) DURT(S3) EXP0(S4) EXP1(S4) EXP2(S4) EXP3(S4) PCI1(S4) USB0(S3) USB1(S3) USB2(S3) USB7(S3) HDEF(S4) acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1994.62 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR,LONG cpu0: 4MB 64b/line 16-way L2 cache cpu0: apic clock running at 166MHz cpu1 at mainbus0: apid 1 (application processor) cpu1: Intel(R) Core(TM)2 CPU T7200 @ 2.00GHz, 1994.34 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,SBF,SSE3,MWAIT,DS-CPL,VMX,EST,TM2,CX16,xTPR,LONG cpu1: 4MB 64b/line 16-way L2 cache ioapic0 at mainbus0 apid 1 pa 0xfec0, version 20, 24 pins ioapic0: misconfigured as apic 2, remapped to apid 1 acpihpet0 at acpi0: 14318179 Hz acpiprt0 at acpi0: bus 0 (PCI0) acpiprt1 at acpi0: bus 1 (AGP_) acpiprt2 at acpi0: bus 2 (EXP0) acpiprt3 at acpi0: bus 3 (EXP1) acpiprt4 at acpi0: bus 4 (EXP2) acpiprt5 at acpi0: bus 12 (EXP3) acpiprt6 at acpi0: bus 21 (PCI1) acpiec0 at acpi0 acpicpu0 at acpi0: C3, C2 acpicpu1 at acpi0: C3, C2 acpitz0 at acpi0: critical temperature 127 degC acpitz1 at acpi0: critical temperature 100 degC acpibtn0 at acpi0: LID_ acpibtn1 at acpi0: SLPB acpibat0 at acpi0: BAT0 not present acpibat1 at acpi0: BAT1 not present acpiac0 at acpi0: AC unit online acpithinkpad0 at acpi0 acpidock at acpi0 not configured acpivideo at acpi0 not configured acpivideo at acpi0 not configured cpu0: unknown Enhanced SpeedStep CPU, msr 0x06130c2806000c28 cpu0: using only
