Hi Michael,
The e1000 works just by chance.
The pcnet virtual network interface seems to be more stable,
but if I do a ping to the Solaris guest, then some pings are
not answered. Sample session:
# ping 192.168.0.151
PING 192.168.0.151 (192.168.0.151) 56(84) bytes of data.
64 bytes from
On 05/08/10 10:54, Michael Tokarev wrote:
30.04.2010 19:28, Harald Dunkel wrote:
Just to be sure: I can live with the e1000 emulation.
Ok, downgrading the bug to minor.
Seems that e1000 doesn't work much better. At the first
start of the Solaris guest it seems to work, but if I
restart
severity 579751 minor
thanks
30.04.2010 19:28, Harald Dunkel wrote:
On 04/30/10 15:14, Michael Tokarev wrote:
Please show the kvm command line in use.
/usr/bin/kvm -S -M pc-0.11 -enable-kvm -m 4096 -smp
2,sockets=2,cores=1,threads=1 -name solaris10u6-x86-template -uuid
Package: qemu-kvm
Version: 0.12.3+dfsg-4
If I use rtl8139 network device emulation, then this
device doesn't show up in the Solaris 10 guest.
Using e1000 instead there is no such problem.
There was no such problem for qemu-kvm 0.11.0+dfsg-1.
Seems that this problem is restricted to Solaris
Harald Dunkel wrote:
Package: qemu-kvm
Version: 0.12.3+dfsg-4
If I use rtl8139 network device emulation, then this
device doesn't show up in the Solaris 10 guest.
Using e1000 instead there is no such problem.
There was no such problem for qemu-kvm 0.11.0+dfsg-1.
Seems that this
On 04/30/10 15:14, Michael Tokarev wrote:
Please show the kvm command line in use.
/usr/bin/kvm -S -M pc-0.11 -enable-kvm -m 4096 -smp
2,sockets=2,cores=1,threads=1 -name solaris10u6-x86-template -uuid
9575f7a9-c101-460a-b4a2-a5a11f52608f -nodefaults -chardev
6 matches
Mail list logo
