RE: [smartos-discuss] Qemu keyboard layout -k

[TRITONIA SOLUTIONS LIMITED]

Peter,

I have not tried using the qemu_extra_opts when initially creating a vm. I used 
the vmadm update to change qemu_extra_opts after I had created the vm and setup 
the virtio drivers. I will try creating a new vm as the Windows 7 vm I was 
using refuses to run windows update. I copied the Windows 7 vm from Proxmox VE 
which is KVM+QEMU but it turns out the original had the same windows update 
issue. Apart from that the vm runs fine.

I might start with a new vanila Windows 7 SP1 vm and then use it to create a 
"golden image". I have managed to do that with Windows Server 2012 R2 and now 
have a local template (I had to sysprep the vm, create the manifest etc but it 
worked).

Sean.

From: Peter Kelm [peter.k...@peterkelm.com]
Sent: 08 March 2016 20:51
To: smartos-discuss@lists.smartos.org
Subject: Re: [smartos-discuss] Qemu keyboard layout -k

Sean,

That’s odd. I haven’t had any issue so far with the procedure as I described 
with both KVM Linux and Windows VMs. I haven’t found a need (yet?) to use 
qemu_opts for more than just changing the keyboard layout.

Below is the JSON for a Centos VM:

[root@santaana /opt/json]# cat centos7.json
{
"brand": "kvm",
"vcpus": 1,
"autoboot": false,
„alias": "centos",
"ram": 1024,
"resolvers": ["192.168.0.1"],
"disks": [
{
"image_uuid": "c41bf236-dc75-11e4-88e5-038814c07c11",
"boot": true,
"model": "virtio",
"size": 10240
}
],
"nics": [
{
"nic_tag": "admin",
"model": "virtio",
"ip": "192.168.0.2",
"netmask": "255.255.255.0",
"gateway": "192.168.0.1"
}
],
"qemu_extra_opts": "-k de"
}

The file for a Windows VM would be almost identical but without the 
„image_uuid“ line. However, keep in mind that you’d need to add the virtio 
drivers to the Windows install media (or mount them from a second iso file).

What is the reason for all the qemu_opts options in your "vmadm update“ command 
below?

Best regards,

Peter

Am 08.03.2016 um 21:17 schrieb TRITONIA SOLUTIONS LIMITED 
>:

Peter,

I did try that option but then the vm would not start: looks like I ended up 
with "-k en-us -k en-gb" on the qemu command-line.

So I used
vmadm update  qemu_opts='-vnc unix:/tmp/vm.vnc -parallel none -usb 
-usbdevice tablet -k en-gb'

as documented in 
https://github.com/joyent/smartos-live/blob/master/src/vm/man/vmadm.1m.md
 (I don't have a vnc password).

Thanks

Sean.

From: Peter Kelm 
[peter.k...@peterkelm.com]
Sent: 08 March 2016 20:10
To: 
smartos-discuss@lists.smartos.org
Subject: Re: [smartos-discuss] Qemu keyboard layout -k

Sean,

This is how I use that option:

[user@host /opt]# cat german.json
{
qemu_extra_opts: "-k de"
}

You can add the qemu_extra_opts line to a VM JSON file or apply the above via 
vmadm update afterwards.

Best regards,

Peter

Am 08.03.2016 um 18:44 schrieb TRITONIA SOLUTIONS LIMITED 
:

Hi,

I am using VNC to access some Windows vm's and the default keyboard layout is 
"en-us" whereas I need to use "en-gb". I can see the "-k en-us" option in the 
vm.startvm.log but cannot find the appropriate vmadm json value to change it.

I know I could use RDP but that restricts what you can do.

Sean Weatherall.


smartos-discuss | 
Archives
 
[https://www.listbox.com/images/feed-icon-10x10.jpg31e6b2b.jpg?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2ZlZWQtaWNvbi0xMHgxMC5qcGc]
 

  | 
Modify
 Your Subscription 
[https://www.listbox.com/images/listbox-logo-small.png31e6b2b.png?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2xpc3Rib3gtbG9nby1zbWFsbC5wbmc]
 




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 

RE: [smartos-discuss] Qemu keyboard layout -k

[TRITONIA SOLUTIONS LIMITED]

Peter,

I did try that option but then the vm would not start: looks like I ended up 
with "-k en-us -k en-gb" on the qemu command-line.

So I used
vmadm update  qemu_opts='-vnc unix:/tmp/vm.vnc -parallel none -usb 
-usbdevice tablet -k en-gb'

as documented in 
https://github.com/joyent/smartos-live/blob/master/src/vm/man/vmadm.1m.md (I 
don't have a vnc password).

Thanks

Sean.

From: Peter Kelm [peter.k...@peterkelm.com]
Sent: 08 March 2016 20:10
To: smartos-discuss@lists.smartos.org
Subject: Re: [smartos-discuss] Qemu keyboard layout -k

Sean,

This is how I use that option:

[user@host /opt]# cat german.json
{
qemu_extra_opts: "-k de"
}

You can add the qemu_extra_opts line to a VM JSON file or apply the above via 
vmadm update afterwards.

Best regards,

Peter

Am 08.03.2016 um 18:44 schrieb TRITONIA SOLUTIONS LIMITED 
>:

Hi,

I am using VNC to access some Windows vm's and the default keyboard layout is 
"en-us" whereas I need to use "en-gb". I can see the "-k en-us" option in the 
vm.startvm.log but cannot find the appropriate vmadm json value to change it.

I know I could use RDP but that restricts what you can do.

Sean Weatherall.

smartos-discuss | 
Archives
 
[https://www.listbox.com/images/feed-icon-10x10.jpg31e6b2b.jpg?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2ZlZWQtaWNvbi0xMHgxMC5qcGc]
 

  | 
Modify
 Your Subscription 
[https://www.listbox.com/images/listbox-logo-small.png31e6b2b.png?uri=aHR0cHM6Ly93d3cubGlzdGJveC5jb20vaW1hZ2VzL2xpc3Rib3gtbG9nby1zbWFsbC5wbmc]
 




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Qemu keyboard layout -k

[Peter Kelm]

Sean,

This is how I use that option:

[user@host /opt]# cat german.json 
{
qemu_extra_opts: "-k de"
}

You can add the qemu_extra_opts line to a VM JSON file or apply the above via 
vmadm update afterwards.

Best regards,

Peter

> Am 08.03.2016 um 18:44 schrieb TRITONIA SOLUTIONS LIMITED 
> :
> 
> Hi, 
> 
> I am using VNC to access some Windows vm's and the default keyboard layout is 
> "en-us" whereas I need to use "en-gb". I can see the "-k en-us" option in the 
> vm.startvm.log but cannot find the appropriate vmadm json value to change it. 
> 
> I know I could use RDP but that restricts what you can do.
> 
> Sean Weatherall.
> From: TRITONIA SOLUTIONS LIMITED
> Sent: 04 March 2016 22:06
> To: smartos-discuss@lists.smartos.org 
> 
> Subject: Windows on KVM differencing disk (golden image)
> 
> Hi, 
> 
> I've been using KVM on Linux (ProxMox VE) for some years and was interested 
> to try it out on SmartOS as wanted to use KVM + ZFS (although newer versions 
> of ProxMox do support ZFS on Linux). Using qcow2 files on linux, and VHDX 
> files on Hyper-V, you can create differencing disks so that you have a single 
> 'parent image' which is shared between all of your vm instances (saves a lot 
> of space as your obviously only storing changes for each vm). 
> 
> I created a custom KVM image from a sysprep'd Windows Server 2012 R2 x64 vm 
> and imported it locally as in the wiki. From that I was able to generate new 
> vm instances but I assume that the zvol created for each new instance is not 
> a clone of the original zvol (from the golden image) and thus each new vm is 
> getting a copy of the whole original zvol? 
> 
> I'm just interested to know if there is a method using a cloned snapshot of 
> the original zvol that means I can save all this duplicated space? or maybe I 
> am just misunderstanding what imgadm actually does?  
> 
> PS: I can't really afford the memory to enable dedup on the zones pool. 
> 
> Many thanks and sorry for being a novice...
> 
> Sean Weatherall  
> smartos-discuss | Archives 
>   
>  | 
> Modify  Your Subscription  
> 



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Qemu keyboard layout -k

[Josh Wilsdon]

Hi,

I am using VNC to access some Windows vm's and the default keyboard layout is 
"en-us" whereas I need to use "en-gb". I can see the "-k en-us" option in the 
vm.startvm.log but cannot find the appropriate vmadm json value to change it.


Hi,

If you look at the vmadm man page for qemu_opts that should help you out here.

Thanks,
Josh


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] Qemu keyboard layout -k

[TRITONIA SOLUTIONS LIMITED]

Hi,

I am using VNC to access some Windows vm's and the default keyboard layout is 
"en-us" whereas I need to use "en-gb". I can see the "-k en-us" option in the 
vm.startvm.log but cannot find the appropriate vmadm json value to change it.

I know I could use RDP but that restricts what you can do.

Sean Weatherall.

From: TRITONIA SOLUTIONS LIMITED
Sent: 04 March 2016 22:06
To: smartos-discuss@lists.smartos.org
Subject: Windows on KVM differencing disk (golden image)

Hi,

I've been using KVM on Linux (ProxMox VE) for some years and was interested to 
try it out on SmartOS as wanted to use KVM + ZFS (although newer versions of 
ProxMox do support ZFS on Linux). Using qcow2 files on linux, and VHDX files on 
Hyper-V, you can create differencing disks so that you have a single 'parent 
image' which is shared between all of your vm instances (saves a lot of space 
as your obviously only storing changes for each vm).

I created a custom KVM image from a sysprep'd Windows Server 2012 R2 x64 vm and 
imported it locally as in the wiki. From that I was able to generate new vm 
instances but I assume that the zvol created for each new instance is not a 
clone of the original zvol (from the golden image) and thus each new vm is 
getting a copy of the whole original zvol?

I'm just interested to know if there is a method using a cloned snapshot of the 
original zvol that means I can save all this duplicated space? or maybe I am 
just misunderstanding what imgadm actually does?

PS: I can't really afford the memory to enable dedup on the zones pool.

Many thanks and sorry for being a novice...

Sean Weatherall



---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] A deadlock issue of epoll_wait when used in branded zone environment

[Patrick Mooney]

Thanks for the detailed report.  I have written up a ticket
(https://smartos.org/bugview/OS-5222) and will be working on it today.

-Patrick

On 8 March 2016 at 01:21, 王靖  wrote:
> Hi ALL,
> Recently, we found a bug in SmartOS version 20160121 lx branded zone (UUID
> 1abb405a-d6a4-11e5-9bb8-bbe3fd09fb3c) system call epoll_wait, triggered by
> setting the timeout parameter of epoll_wait to -1. In this case, epoll_wait
> cannot return anything in some condition.
>
> Below is our test case:
>


---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Samsung 950 Pro on SmartOS?

[Dirk Steinberg]

> Am 07.03.2016 um 06:48 schrieb Fred Liu :
> 
> 
> 
> 2016-03-05 21:19 GMT+08:00 Dirk Steinberg  >:
> > Apart from that: is NVMe support in SmartOS considered stable?
>> 
>> There is driver support for it in the system. I have not heard many
>> reports positively or negatively about it.
>> 
>> [Fred]: I am testing some Intel P3600 NVMe SSD. In normal workload, they 
>> just work . But in burning mode like continuous scrubbings, I have got lots 
>> of checksum errors. And I tested the same scrubbings under Linux, no 
>> checksum errors were found.
>> Fred
> 
> Hi Fred,
> 
> do you attribute these errors to the SmartOS NVMe driver?
> Sounds like it since you are saying that the same SSD works under Linux.
> 
> So have you given up on NVMe on SmartOS?
> 
> [Fred]: I personally attribute those errors to the immaturity of the NVMe 
> driver in Illumos. But that  is not so severe based on the fact that there 
> are no substantial data loss with those checksum errors.
> I used to get some some kernel panics under "too may check sum erros" and 
> after disabling "sha512|skeun|edonr" checksum algorithm, the server has been 
> running well for more than two weeks.
> It looks like "sha512|skeun|edonr" checksum algorithm still has some glitches.
> 
> Thanks.
> 
> Fred

Sorry, I am not quite sure what you are trying to tell me.

I am running the sha512 hash on a regular disk pool without problems. I have 
also
run a number of scrubs. I assume the the sha512 hash is working correctly.
If I had a ton of checksum errors from ZFS I would be VERY concerned.
Just turning off the checksum may not be the solution… 
I do not think that a bug in sha512 is generating these.

Also, what do you mean by „no substantial data loss“? Either there is
data loss or there is no data loss. My policy here is that even a single
bit of data loss is not acceptable. This is why ZFS goes to all the
effort of using strong checksums and redundancy and scrubbing and so on…

If you are willing to accept „some nonsubstantial data loss“ and turn
of checksums so as not to be bothered by all these checksum errors
there is not much point in using ZFS in the first place!

Am I understanding something incorrectly?

Cheers
Dirk




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

RE: [smartos-discuss] Adding a new disk - too hard :(

[the outsider]

Are you sure you can't see the device with "format"? 

Please reply the "format" output. It should show the device as something
like c1t1d0 or something.

 

 

 

 

Van: David Preece [mailto:da...@zedkep.com] 
Verzonden: dinsdag 8 maart 2016 4:47
Aan: smartos-discuss@lists.smartos.org
Onderwerp: [smartos-discuss] Adding a new disk - too hard :(

 

Hi,

 

I'm trying to add a PCIe SSD to act as an L2ARC but it's not going well. The
device is found at boot:

 

2016-03-07T23:57:39.395442+00:00 i7 sata: [ID 663010 kern.info
 ] /pci@0,0/pci8086,3b42@1c/pci1b4b,9230@0 :

2016-03-07T23:57:39.395446+00:00 i7 sata: [ID 761595 kern.info
 ] #011SATA processor (ATAPI) device at port 7

2016-03-07T23:57:39.395451+00:00 i7 sata: [ID 846691 kern.info
 ] #011model MARVELL VIRTUALL

2016-03-07T23:57:39.395456+00:00 i7 sata: [ID 693010 kern.info
 ] #011firmware 1.09

2016-03-07T23:57:39.395460+00:00 i7 sata: [ID 163988 kern.info
 ] #011serial number 

2016-03-07T23:57:39.395465+00:00 i7 sata: [ID 594940 kern.info
 ] #011supported features:

2016-03-07T23:57:39.395477+00:00 i7 sata: [ID 981177 kern.info
 ] #011 DMA

2016-03-07T23:57:39.395495+00:00 i7 sata: [ID 514995 kern.info
 ] #011SATA Gen1 signaling speed (1.5Gbps)

 

Shows up in the picl tree (abbreviated)

 

[root@i7 /]# prtpicl

  / (picl, ab60001)

 platform (upa, ab60005)

 scsi_vhci (devctl, ab6003f)

 pci (pciex, ab60066)

 pci8086,3b42 (pciex, ab60200)

 pci1b4b,9230 (obp-device, ab6022a)

 pci1028,2da (obp-device, ab60286)

 hub (obp-device, ab602b0)

 storage (obp-device, ab602dc)

 disk (block, ab6030a)

 pci1028,2da (obp-device, ab60391)

 disk (block, ab603c1)

 

And under cfgadm (abbreviated)

 

[root@i7 ~]# cfgadm 

Ap_Id  Type Receptacle   Occupant
Condition

sata0/0::dsk/c1t0d0disk connectedconfigured   ok

sata1/7processorconnectedunconfigured ok

usb1/1 usb-hub  connectedconfigured   ok

usb1/1.6   usb-storage  connectedconfigured   ok

 

sata0/0::1t0d0 is the hard drive, usb1/1.6 is presumably the USB thumb
drive.

 

But if I try to configure the disk:

 

[root@i7 ~]# cfgadm -c configure sata1/7

cfgadm: Hardware specific failure: Failed to config device at ap_id:
/devices/pci@0,0/pci8086,3b42@1c/pci1b4b,9230@0:7

 

devfsadm also fails to create a /dev/dsk/ entry, unsurprisingly.

 

The device itself is a Marvell 88se9230 and is in the same family as
88se9128 which definitely has a driver:
http://lists.omniti.com/pipermail/omnios-discuss/2013-July/001002.html  and
https://www.illumos.org/issues/3815

 

Problem exists as of 20160304T005100Z.

 

I had a look for a compatibility table so I could just add new the pci id
and see if it goes, but to no avail. Any ideas?

 

Thanks,

Dave

 

 


smartos-discuss |  
Archives
 |
 Modify Your Subscription

  

 




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Introducing io-lx -- an attempt to port LX Zones to OmniOS

[Jorge Schrauwen]

When I still had most of my zones on OmniOS and heard the LX news I was 
thinking about how that would work on non-smartos stuff given the lack 
of vmadm.


In my head I seemed to end up on traditional tools + a script that would 
use debbootstrap to setup debian/ubuntu zones on the spot, just point it 
to the dataset.


In theory that 'should' work. In practice? I have no idea. I have many 
ideas but all seem a bit painful. But feel free to pluk my brain about 
it on IRC if you want.


Regards

Jorge


On 2016-03-08 03:47, Dan McDonald wrote:

Hello!

700+ cherrypicked commits later, and at least I haven't obviously
regressed lipkg/ipkg zones.  :)

This github repo:

https://github.com/danmcd/io-lx-public/

is the beginning of my attempt to port LX zones over to OmniOS.  I
KNOW there's a lot more work to be done, but I wanted to make sure
this repo is viewable by the public so:

1. ) People know about it.

2. ) People who are interested in helping can do so.

3. ) People can laugh at all of the mismerges and other flub-ups I'm
sure I haven't caught yet.  :)

4. ) I will be context-switching to OmniOS r151018 ramp-up very soon,
and want to checkpoint state.

I've Bcc:ed the SmartOS (home of LX zones) and the illumos (where I
hope this work can be upstreamed at some point) lists.  Discussion on
io-lx (Illumos-OmniOS-LX) should take place either on github or on the
OmniOS mailing list.

So far:

-  I've sidepulled 700+ commits, ending with illumos-joyent's
8443e038ef8eb3ca6a95818d6e90b2a1eb4e9cb6.  There are some more
illumos-joyent commits I'll need to bring over, but my cherrypicking
script and setups are primed & tested, so I *should* be able to make
short work of it.

-  I've smoke-tested a global-only OmniOS boot, and a single-lipkg zone
OmniOS boot.  After some mismerge-related consternation, I booted the
lipkg zone as well.  A rudimentary ppriv(1) comparison between root
shells in global and lipkg zones was part of the smoke test.

-  Any files I didn't know where they went I put into the "brand/lx"
package.  The inotify feature, for example, is in there, and perhaps
it shouldn't be.

-  If you ONU to io-lx, note that to install brand/lx, you will need to
UNINSTALL the "illumos-gate" consolidation package first.  I don't
have changes in omnios-build or any of the other repos (like pkg5)
yet.  I hope to avoid outside-illumos changes until it's time to
figure out the admin model.

After I'm comfortable with no ipkg/lipkg regressions, I will need to
spend some design time figuring out how LX zones will look on OmniOS.
I will not be porting vmadm(1M) over from SmartOS, so I need to think
about how LX will fit in with traditional zone tools.  I may discover
other problems, but until I start the '018 process, and immediately
after '018 ships, I will need to ensure no ipkg/lipkg regressions
first and foremost.

It's not much, but it's a start.

Thanks for your time & patience,
Dan




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com