Re: [smartos-discuss] Trouble starting a KVM

2016-10-07 Thread Ian Collins

On 10/ 8/16 07:22 AM, Jorge Schrauwen wrote:

Hi,

Do you have qemu_opts set? I see two -smp flags

The later one also seems wrong:
-smp cpus=2,cores=8,threads=2
probably needs to be
-smp sockets=2,cores=8,threads=2


I've been using cpus=2,cores=8,threads=2 without any issues thus far.

I changed it to sockets=2,cores=8,threads=2and the machine started and 
then stopped again.


Now trying with qemu_extra_opts="" and it is running again.  How odd...

--
Ian.



---
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] Trouble starting a KVM

2016-10-07 Thread Jorge Schrauwen

Hi,

Do you have qemu_opts set? I see two -smp flags

The later one also seems wrong:
-smp cpus=2,cores=8,threads=2
probably needs to be
-smp sockets=2,cores=8,threads=2

Regards

Jorge

On 2016-10-07 20:21, Ian Collins wrote:

On 10/ 8/16 05:28 AM, Robert Mustacchi wrote:

On 10/7/16 1:35 , Ian Collins wrote:

On 10/ 7/16 04:32 PM, Robert Mustacchi wrote:

On 10/6/16 16:26 , Ian Collins wrote:

Hello,

I'm having trouble starting a KVM (which had been shut down 
cleanly).

It times out waiting for zone to transition to running. I can't see
anything obvious in the zone log except for:

+ setup_cpu_baseline
+ nawk $'{\n\t\tif ($2 == "privileged") print $3\n\t}'
+ prctl -P -n zone.cpu-baseline -i zone
f3384dd7-5697-63cb-b194-d53911b0bfb8
prctl: f3384dd7-5697-63cb-b194-d53911b0bfb8: No controllable 
process

found in task, project, or zone.
+ curr_base=''

Which doesn't look good.  Any ideas for further debugging?


You'll want to go take a look at the log files in
/zones//root/tmp/vm.log. At least, I think that's pretty close 
to

the path you want, which will be the QEMU log.

Alas all the logs in there are empty...

ls -l /zones/f3384dd7-5697-63cb-b194-d53911b0bfb8/root/tmp
total 20
srwxr-xr-x   1 root root   0 Aug 21 03:49 vm.console
-rw-r--r--   1 root root   0 Oct  6 23:17 vm.log
-rw-r--r--   1 root root   0 Oct  6 21:38 vm.log.0
-rw-r--r--   1 root root   0 Oct  6 21:32 vm.log.1
-rw-r--r--   1 root root   0 Oct  6 20:00 vm.log.2
-rw-r--r--   1 root root   0 Oct  6 19:56 vm.log.3
-rw-r--r--   1 root root   0 Sep 20 08:00 vm.log.4
-rw-r--r--   1 root root   0 Sep 20 08:00 vm.log.5
-rw-r--r--   1 root root   0 Aug 21 03:00 vm.log.6
-rw-r--r--   1 root root   0 Aug 17 06:07 vm.log.7
-rw-r--r--   1 root root   0 Aug 16 08:13 vm.log.8
-rw-r--r--   1 root root   0 Aug 15 20:00 vm.log.9
-rw-r--r--   1 root staff 72 Oct  6 23:17 vm.metadata
-rw---   1 root root   6 Aug 21 03:49 vm.pid
srwxr-xr-x   1 root root   0 Aug 21 03:49 vm.qmp
-rw-r--r--   1 root root1281 Oct  6 23:17 vm.startvm.log
srwxr-xr-x   1 root root   0 Aug 21 03:49 vm.ttyb
srwxr-xr-x   1 root root   0 Aug 21 03:50 vm.vnc


What's in the vm.startvm.log file?

The launch command:

+ [[ -x /startvm.zone ]]
+ exec /smartdc/bin/qemu-exec /smartdc/bin/qemu-system-x86_64 -m 16384
-name f3384dd7-5697-63cb-b194-d53911b0bfb8 -uuid
f3384dd7-5697-63cb-b194-d53911b0bfb8
-cpu host -smp 2 -drive
file=/dev/zvol/rdsk/zones/f3384dd7-5697-63cb-b194-d53911b0bfb8-disk0,if=virtio,index=0,media=disk
-drive file=/dev/zvol/rdsk/zones/f3
384dd7-5697-63cb-b194-d53911b0bfb8-disk1,if=virtio,index=1,media=disk
-boot order=cd -device
virtio-net-pci,mac=90:b8:d0:14:d6:21,tx=timer,x-txtimer=20,x
-txburst=128,vlan=0 -net
vnic,name=net0,vlan=0,ifname=net0,ip=192.168.42.223,netmask=255.255.255.0,gateway_ip=192.168.42.3,hostname=f3384dd7-5697-63cb-b194-d
53911b0bfb8,dns_ip0=216.146.36.113,dns_ip1=216.146.35.113 -smbios
'type=1,manufacturer=Joyent,product=SmartDC
HVM,version=7.20161004T154212Z,serial=f3384dd7-
5697-63cb-b194-d53911b0bfb8,uuid=f3384dd7-5697-63cb-b194-d53911b0bfb8,sku=001,family=Virtual
Machine' -pidfile /tmp/vm.pid -vga std -chardev socket,id=qmp,pa
th=/tmp/vm.qmp,server,nowait -qmp chardev:qmp -chardev
socket,id=serial0,path=/tmp/vm.console,server,nowait -serial
chardev:serial0 -chardev socket,id=serial
1,path=/tmp/vm.ttyb,server,nowait -serial chardev:serial1 -vnc
unix:/tmp/vm.vnc -parallel none -usb -usbdevice tablet -k en-us -smp
cpus=2,cores=8,threads=2



---
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] Trouble starting a KVM

2016-10-07 Thread Ian Collins

On 10/ 8/16 05:28 AM, Robert Mustacchi wrote:

On 10/7/16 1:35 , Ian Collins wrote:

On 10/ 7/16 04:32 PM, Robert Mustacchi wrote:

On 10/6/16 16:26 , Ian Collins wrote:

Hello,

I'm having trouble starting a KVM (which had been shut down cleanly).
It times out waiting for zone to transition to running. I can't see
anything obvious in the zone log except for:

+ setup_cpu_baseline
+ nawk $'{\n\t\tif ($2 == "privileged") print $3\n\t}'
+ prctl -P -n zone.cpu-baseline -i zone
f3384dd7-5697-63cb-b194-d53911b0bfb8
prctl: f3384dd7-5697-63cb-b194-d53911b0bfb8: No controllable process
found in task, project, or zone.
+ curr_base=''

Which doesn't look good.  Any ideas for further debugging?


You'll want to go take a look at the log files in
/zones//root/tmp/vm.log. At least, I think that's pretty close to
the path you want, which will be the QEMU log.

Alas all the logs in there are empty...

ls -l /zones/f3384dd7-5697-63cb-b194-d53911b0bfb8/root/tmp
total 20
srwxr-xr-x   1 root root   0 Aug 21 03:49 vm.console
-rw-r--r--   1 root root   0 Oct  6 23:17 vm.log
-rw-r--r--   1 root root   0 Oct  6 21:38 vm.log.0
-rw-r--r--   1 root root   0 Oct  6 21:32 vm.log.1
-rw-r--r--   1 root root   0 Oct  6 20:00 vm.log.2
-rw-r--r--   1 root root   0 Oct  6 19:56 vm.log.3
-rw-r--r--   1 root root   0 Sep 20 08:00 vm.log.4
-rw-r--r--   1 root root   0 Sep 20 08:00 vm.log.5
-rw-r--r--   1 root root   0 Aug 21 03:00 vm.log.6
-rw-r--r--   1 root root   0 Aug 17 06:07 vm.log.7
-rw-r--r--   1 root root   0 Aug 16 08:13 vm.log.8
-rw-r--r--   1 root root   0 Aug 15 20:00 vm.log.9
-rw-r--r--   1 root staff 72 Oct  6 23:17 vm.metadata
-rw---   1 root root   6 Aug 21 03:49 vm.pid
srwxr-xr-x   1 root root   0 Aug 21 03:49 vm.qmp
-rw-r--r--   1 root root1281 Oct  6 23:17 vm.startvm.log
srwxr-xr-x   1 root root   0 Aug 21 03:49 vm.ttyb
srwxr-xr-x   1 root root   0 Aug 21 03:50 vm.vnc


What's in the vm.startvm.log file?

The launch command:

+ [[ -x /startvm.zone ]]
+ exec /smartdc/bin/qemu-exec /smartdc/bin/qemu-system-x86_64 -m 16384 
-name f3384dd7-5697-63cb-b194-d53911b0bfb8 -uuid 
f3384dd7-5697-63cb-b194-d53911b0bfb8
-cpu host -smp 2 -drive 
file=/dev/zvol/rdsk/zones/f3384dd7-5697-63cb-b194-d53911b0bfb8-disk0,if=virtio,index=0,media=disk 
-drive file=/dev/zvol/rdsk/zones/f3
384dd7-5697-63cb-b194-d53911b0bfb8-disk1,if=virtio,index=1,media=disk 
-boot order=cd -device 
virtio-net-pci,mac=90:b8:d0:14:d6:21,tx=timer,x-txtimer=20,x
-txburst=128,vlan=0 -net 
vnic,name=net0,vlan=0,ifname=net0,ip=192.168.42.223,netmask=255.255.255.0,gateway_ip=192.168.42.3,hostname=f3384dd7-5697-63cb-b194-d
53911b0bfb8,dns_ip0=216.146.36.113,dns_ip1=216.146.35.113 -smbios 
'type=1,manufacturer=Joyent,product=SmartDC 
HVM,version=7.20161004T154212Z,serial=f3384dd7-
5697-63cb-b194-d53911b0bfb8,uuid=f3384dd7-5697-63cb-b194-d53911b0bfb8,sku=001,family=Virtual 
Machine' -pidfile /tmp/vm.pid -vga std -chardev socket,id=qmp,pa
th=/tmp/vm.qmp,server,nowait -qmp chardev:qmp -chardev 
socket,id=serial0,path=/tmp/vm.console,server,nowait -serial 
chardev:serial0 -chardev socket,id=serial
1,path=/tmp/vm.ttyb,server,nowait -serial chardev:serial1 -vnc 
unix:/tmp/vm.vnc -parallel none -usb -usbdevice tablet -k en-us -smp 
cpus=2,cores=8,threads=2


--
Ian.



---
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] Trouble starting a KVM

2016-10-07 Thread Robert Mustacchi
On 10/7/16 1:35 , Ian Collins wrote:
> On 10/ 7/16 04:32 PM, Robert Mustacchi wrote:
>> On 10/6/16 16:26 , Ian Collins wrote:
>>> Hello,
>>>
>>> I'm having trouble starting a KVM (which had been shut down cleanly).
>>> It times out waiting for zone to transition to running. I can't see
>>> anything obvious in the zone log except for:
>>>
>>> + setup_cpu_baseline
>>> + nawk $'{\n\t\tif ($2 == "privileged") print $3\n\t}'
>>> + prctl -P -n zone.cpu-baseline -i zone
>>> f3384dd7-5697-63cb-b194-d53911b0bfb8
>>> prctl: f3384dd7-5697-63cb-b194-d53911b0bfb8: No controllable process
>>> found in task, project, or zone.
>>> + curr_base=''
>>>
>>> Which doesn't look good.  Any ideas for further debugging?
>>>
>> You'll want to go take a look at the log files in
>> /zones//root/tmp/vm.log. At least, I think that's pretty close to
>> the path you want, which will be the QEMU log.
> 
> Alas all the logs in there are empty...
> 
> ls -l /zones/f3384dd7-5697-63cb-b194-d53911b0bfb8/root/tmp
> total 20
> srwxr-xr-x   1 root root   0 Aug 21 03:49 vm.console
> -rw-r--r--   1 root root   0 Oct  6 23:17 vm.log
> -rw-r--r--   1 root root   0 Oct  6 21:38 vm.log.0
> -rw-r--r--   1 root root   0 Oct  6 21:32 vm.log.1
> -rw-r--r--   1 root root   0 Oct  6 20:00 vm.log.2
> -rw-r--r--   1 root root   0 Oct  6 19:56 vm.log.3
> -rw-r--r--   1 root root   0 Sep 20 08:00 vm.log.4
> -rw-r--r--   1 root root   0 Sep 20 08:00 vm.log.5
> -rw-r--r--   1 root root   0 Aug 21 03:00 vm.log.6
> -rw-r--r--   1 root root   0 Aug 17 06:07 vm.log.7
> -rw-r--r--   1 root root   0 Aug 16 08:13 vm.log.8
> -rw-r--r--   1 root root   0 Aug 15 20:00 vm.log.9
> -rw-r--r--   1 root staff 72 Oct  6 23:17 vm.metadata
> -rw---   1 root root   6 Aug 21 03:49 vm.pid
> srwxr-xr-x   1 root root   0 Aug 21 03:49 vm.qmp
> -rw-r--r--   1 root root1281 Oct  6 23:17 vm.startvm.log
> srwxr-xr-x   1 root root   0 Aug 21 03:49 vm.ttyb
> srwxr-xr-x   1 root root   0 Aug 21 03:50 vm.vnc
> 

What's in the vm.startvm.log file?


---
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] Trouble starting a KVM

2016-10-07 Thread Ian Collins

On 10/ 7/16 04:32 PM, Robert Mustacchi wrote:

On 10/6/16 16:26 , Ian Collins wrote:

Hello,

I'm having trouble starting a KVM (which had been shut down cleanly).
It times out waiting for zone to transition to running. I can't see
anything obvious in the zone log except for:

+ setup_cpu_baseline
+ nawk $'{\n\t\tif ($2 == "privileged") print $3\n\t}'
+ prctl -P -n zone.cpu-baseline -i zone
f3384dd7-5697-63cb-b194-d53911b0bfb8
prctl: f3384dd7-5697-63cb-b194-d53911b0bfb8: No controllable process
found in task, project, or zone.
+ curr_base=''

Which doesn't look good.  Any ideas for further debugging?


You'll want to go take a look at the log files in
/zones//root/tmp/vm.log. At least, I think that's pretty close to
the path you want, which will be the QEMU log.


Alas all the logs in there are empty...

ls -l /zones/f3384dd7-5697-63cb-b194-d53911b0bfb8/root/tmp
total 20
srwxr-xr-x   1 root root   0 Aug 21 03:49 vm.console
-rw-r--r--   1 root root   0 Oct  6 23:17 vm.log
-rw-r--r--   1 root root   0 Oct  6 21:38 vm.log.0
-rw-r--r--   1 root root   0 Oct  6 21:32 vm.log.1
-rw-r--r--   1 root root   0 Oct  6 20:00 vm.log.2
-rw-r--r--   1 root root   0 Oct  6 19:56 vm.log.3
-rw-r--r--   1 root root   0 Sep 20 08:00 vm.log.4
-rw-r--r--   1 root root   0 Sep 20 08:00 vm.log.5
-rw-r--r--   1 root root   0 Aug 21 03:00 vm.log.6
-rw-r--r--   1 root root   0 Aug 17 06:07 vm.log.7
-rw-r--r--   1 root root   0 Aug 16 08:13 vm.log.8
-rw-r--r--   1 root root   0 Aug 15 20:00 vm.log.9
-rw-r--r--   1 root staff 72 Oct  6 23:17 vm.metadata
-rw---   1 root root   6 Aug 21 03:49 vm.pid
srwxr-xr-x   1 root root   0 Aug 21 03:49 vm.qmp
-rw-r--r--   1 root root1281 Oct  6 23:17 vm.startvm.log
srwxr-xr-x   1 root root   0 Aug 21 03:49 vm.ttyb
srwxr-xr-x   1 root root   0 Aug 21 03:50 vm.vnc

--
Ian.



---
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] Trouble starting a KVM

2016-10-06 Thread Ian Collins

Hello,

I'm having trouble starting a KVM (which had been shut down cleanly).  
It times out waiting for zone to transition to running. I can't see 
anything obvious in the zone log except for:


+ setup_cpu_baseline
+ nawk $'{\n\t\tif ($2 == "privileged") print $3\n\t}'
+ prctl -P -n zone.cpu-baseline -i zone f3384dd7-5697-63cb-b194-d53911b0bfb8
prctl: f3384dd7-5697-63cb-b194-d53911b0bfb8: No controllable process 
found in task, project, or zone.

+ curr_base=''

Which doesn't look good.  Any ideas for further debugging?

# uname -a
SunOS atlantis 5.11 joyent_20161004T154212Z i86pc i386 i86pc

Ian.


---
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