22.05.2010 10:29, Harald Dunkel wrote:
It took me some time to get back into Solaris, too. To change the
network driver:
After changing the kvm configuration you should boot Solaris at usual.
It will complain about some services not being run, and put you into
single user mode.
It does not enter single-user mode, it boots as usual (but indeed,
it complains about some services not started).
I can perform reconfiguration boot - either by touching /reconfigure
or adding -r kernel command line in grub (I used solaris some 10
years ago and still remember _some_ things).
Now you can run "ifconfig -a" to get the new network device name (e.g.
"e1000g0". Rename "/etc/hostname.rtl0" to "/etc/hostname.e1000g0". Rename
"/etc/dhcp.rtl0" to "dhcp.e1000g0". Reboot.
But the problem is that even after reconfigure step, it
does not show anything but lo0 in `ifconfig -a' output.
More, prtdiag -v shows no add-on cards at all, even if
the NIC is configured and running and network is working.
I don't remember something like lspci in linux...
I should have mentioned that my virtual Solaris hosts are supposed to
get IP address and host name via DHCP. Sorry, I forgot. I will try a
fixed address when I am back in the office.
I used dhcp too. But it does not matter (or should not matter),
since once the IP address is obtained, the NIC will be configured
the same way as when using static address.
> I left `ping -f $solaris-ip' process running for whole
> night - it were still running in the morning without any
> visible issues, at 100% CPU usage (2 cores - for ping,
> host kernel and kvm processes).
No ping replies have been lost?
There were several replies lost. Ping -f prints a dot when
it sends a packet out and backspace when receives a reply.
There were several dots printed after whole night of pings
4 or 5, I don't remember.
I re-installed it yesterday, using -nic ...,model=e1000.
Setup procedure recognized Intel NIC and configured it.
I didn't try to stress-test it for whole night, but quick
(over 5 minutes) ping -f didn't reveal anything, it all
just works.
But now when I re-read the whole bugreport thread, I've
an idea. Let's try it, both of us.
I used the old, "traditional", qemu -net..-net syntax.
You're using libvirt which uses the new -netdev syntax.
Let's try the other way around, -netdev for me and -net
for you, and share the results.
Thanks!
/mjt
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
